The document outlines the non-functional requirements for a medical information system, including requirements for user interfaces, hardware interfaces, and other considerations. The user interface is designed to be simple, with main functions for searching, listing medical information, and listing diseases. It also displays the drugs used to treat different diseases. The hardware requirements are based on Microsoft SQL Server 2008 database specifications and will be further detailed in the infrastructure design. Performance requirements specify that medical and disease data must be complete and absolutely accurate, and the server must support multiple simultaneous users. Other non-functional requirements address design constraints, including only supporting English and ensuring the interface is intuitive for all users.
The document outlines the non-functional requirements for a medical information system, including requirements for user interfaces, hardware interfaces, and other considerations. The user interface is designed to be simple, with main functions for searching, listing medical information, and listing diseases. It also displays the drugs used to treat different diseases. The hardware requirements are based on Microsoft SQL Server 2008 database specifications and will be further detailed in the infrastructure design. Performance requirements specify that medical and disease data must be complete and absolutely accurate, and the server must support multiple simultaneous users. Other non-functional requirements address design constraints, including only supporting English and ensuring the interface is intuitive for all users.
The document outlines the non-functional requirements for a medical information system, including requirements for user interfaces, hardware interfaces, and other considerations. The user interface is designed to be simple, with main functions for searching, listing medical information, and listing diseases. It also displays the drugs used to treat different diseases. The hardware requirements are based on Microsoft SQL Server 2008 database specifications and will be further detailed in the infrastructure design. Performance requirements specify that medical and disease data must be complete and absolutely accurate, and the server must support multiple simultaneous users. Other non-functional requirements address design constraints, including only supporting English and ensuring the interface is intuitive for all users.
3.2.1 External Interface Requirements 3.2.1.1 User interfaces
User interface is designed to be simple and easy to see. The main interface consists of functions: search,list medical , list disease. With 2 main function is to display the diseases and shown the drug to be used for each type of disease.
3.2.1.2 Hardware Interfaces
These hardware requirements are based on hardware requirements of Microsoft SQL Server 2008 Database. The hardware requirements should be changed according to the actual through put of the system. The detailed information of hardware configuration will be described in Infrastructure Design.
3.2.1.3 Software Interfaces N/A
3.2.2 Other Nonfunctional Requirements 3.2.2.1 Performance Requirements Data on medication and disease must complete and absolute accuracy. The ability of the server to be large enough to support multiple users. 3.2.2.2 Design constraints The system will be implemented to support for English only. The interface must be designed so that everyone can become familiar. The icons have been designed so that users can realize its function. The color of the interface as well as the icons are not too many colors. Items "Search" should display search results can have while typing each character. Interface compact, easy to use 3.2.2.3 Safety Requirements N/A 3.2.2.4 Security Requirements N/A 3.2.2.5 Software Quality Attributes
Ability to sort the data according to different themes to classify information according to user. Accuracy: Validate carefully the data before insert to database. Timesheet information has to consistency in all system. Code is written as a module and has comment for easy upgrade later. Provide full documentation of the program code. Each function must have at least one comment. Once a month, the system will be tested carefully again based on the results of its operation at time before. Check logs must be kept to support the maintain process.