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.
Use the template below to answer the above statement.
Include diagrams
Software Requirements Specification
1 Introduction
1.1 Document Purpose
TO DO: Write 1-2 paragraphs describing the purpose of this document as explained above.>
1.2 Product Scope
TO DO: 1-2 paragraphs describing the scope of the product. Make sure to describe how it is associated with other product or subsystems.>
1.3 Definitions, Acronyms and Abbreviations
TO DO: Please provide a list of all abbreviations and acronyms used in this document sorted in alphabetical order.>
1.4 References and Acknowledgments
2 Overall Description
2.1 Product Functionality
TO DO:
1. Provide a bulleted list of all the major functions of the system.>
2.2 End Users and Characteristics
TO DO:
1. Describe the characteristics of each user. Certain requirements may affect (relate) only to certain users.
3. Distinguish the most important users for this product from those who are less important to satisfy.>
2.3 System Stakeholders
You should build a list of your system stakeholders. You should define the role of each stakeholder in the big system.
2.4 Operating Environment
TO DO: in at least one paragraph, describe the environment your system will have to operate in. Make sure to include the minimum platform requirements for your system. >
3 Specific Requirements
3.1 User Interface
TO DO: The least you can do for this section is to describe in words the different User Interfaces and the different screens that will be available to the user. Those who will be able to provide optional Graphical User Interface screenshots will be rewarded by extra marks.>
3.2 Functional Requirements
TO DO: Break the functional requirements to several functional areas and divide this section into subsections accordingly. Provide a detailed list of all product operations related to these functional areas.
3.3 Use Case Diagram
TO DO: Provide a use case diagram which will encapsulate the entire system and all possible actors. Do not include detailed use case descriptions, but make sure to include a short description of what every use-case is, who are the actors in your diagram>
4 Non-functional Requirements
4.1 Software Quality Attributes
5 Other Requirements