A newly developed hospital requires an Electronic Decision Support System (DSS) for clinicians. This DSS is required to have all the necessary features to help the practice. Develop a Software Requirements Specification (SRS) document that identifies all the necessary requirements for the system. This document must strictly follow the IEEE template uploaded on canvas. However, there may be sections in the template that may not apply to the project, these sections can be eliminated.

5. Other Nonfunctional Requirements

5.1 Performance Requirements

here and explain their rationale, to help the developers understand the intent and make suitable

design choices. Specify the timing relationships for real time systems. Make such requirements as

specific as possible. You may need to state performance requirements for individual functional

requirements or features.>

Software

Requirements Specification for

Page 5

5.2 Safety Requirements

result from the use of the product. Define any safeguards or actions that must be taken, as well as

actions that must be prevented. Refer to any external policies or regulations that state safety

issues that affect the products design or use. Define any safety certifications that must be

satisfied.>

5.3 Security Requirements

protection of the data used or created by the product. Define any user identity authentication

requirements. Refer to any external policies or regulations containing security issues that affect the

product. Define any security or privacy certifications that must be satisfied.>

5.4 Software Quality Attributes

customers or the developers. Some to consider are: adaptability, availability, correctness, flexibility,

interoperability, maintainability, portability, reliability, reusability, robustness, testability, and

usability. Write these to be specific, quantitative, and verifiable when possible. At the least, clarify

the relative preferences for various attributes, such as ease of use over ease of learning.>

5.5 Business Rules

which functions under specific circumstances. These are not functional requirements in

themselves, but they may imply certain functional requirements to enforce the rules.>

6. Other Requirements

requirements, internationalization requirements, legal requirements, reuse objectives for the

project, and so on. Add any new sections that are pertinent to the project.>

Appendix A: Glossary

abbreviations. You may wish to build a separate glossary that spans multiple projects or the entire

organization, and just include terms specific to a single project in each SRS.>

Appendix B: Analysis Models

state-transition diagrams, or entity-relationship diagrams

.>

Software

Requirements Specification for

Page 6

Appendix C: To Be Determined List

can be tracked to closure.