Develop a Software Design document that identifies all the necessary requirements for the following: A newly developed hospital requires a Patient Scheduling System for clinicians. This system is required to have all the necessary features to help the practice.

Please help with the following$-$

$1.$ Design Considerations

Instructions: Describe issues which need to be addressed or resolved before attempting

to devise a complete design solution.

$2.$ Goals and Guidelines

Instructions: Describe any goals, guidelines, principles, or priorities which dominate or

embody the design of the system and its software. Examples of such goals might be: an

emphasis on speed versus memory use; or working, looking, or "feeling" like an existing

product. Guidelines include coding guidelines and conventions. For each such goal or

guideline, describe the reason for its desirability unless it is implicitly obvious. Describe

any design policies and$/$or tactics that do not have sweeping architectural implications

$($meaning they would not significantly affect the overall organization of the system and

its high$-$level structures$),$ but which nonetheless affect the details of the interface and$/$or

implementation of various aspects of the system $($e$.$g$.,$ choice of which specific product

to use$).$

$3.$ Architectural Strategies

Instructions: Describe any design decisions and$/$or strategies that affect the overall

organization of the system and its higher$-$level structures. These strategies should

provide insight into the key abstractions and mechanisms used in the system

architecture. Describe the reasoning employed for each decision and$/$or strategy

$($possibly referring to previously stated design goals and principles$)$ and how any design

goals or priorities were balanced or traded$-$off.

Describe compliance with CMS Enterprise Architecture $($EA$)$ and standards. Specifically

identify any deviations that were made from the CMS EA and standards, and provide

rationale to support the deviation$($s$).$ When describing a design decision, discuss any

other significant alternatives that were considered, and the reasons for rejecting them

$($as well as the reasons for accepting the alternative finally chosen$).$ Sometimes it may

be most effective to employ the "pattern format" for describing a strategy.

Examples of design decisions might concern $($but are not limited to$)$ things like the

following:

a$)$ Use of a particular type of product $($programming language, database, library,

commercial off$-$the$-$shelf $($COTS$)$ product, etc.$)$

b$)$ Reuse of existing software components to implement various parts$/$features of

the system

c$)$ Future plans for extending or enhancing the software

d$)$ User interface paradigms $($or system input and output models$)$

e$)$ Hardware and$/$or software interface paradigms

f$)$ Error detection and recovery

g$)$ Memory management policies

h$)$ External databases and$/$or data storage management and persistence

i$)$ Distributed data or control over a network

j$)$ Generalized approaches to control

k$)$ Concurrency and synchronization

l$)$ Communication mechanisms

m$)$ Management of other resources

$4.$ Performance Engineering

A contributing factor to System Design will be Performance Requirements.

Performance Requirements are the defined scalability or responsiveness expectations

of specific workloads that process on a system.

Instructions:

$($a$)$ Using the Performance Requirements defined in the Requirements Document,

provide a detailed explanation that describes how the Performance Requirements were

incorporated into the system's design.

$($b$)$ Start preparing Production Load Model$($s$)$ in preparation for Performance testing.