Non-Functional Requirements Report

Added on - 17 Oct 2019

  • 9


  • 2632


  • 107


  • 0


Showing pages 1 to 3 of 9 pages
Requirements Report1Non-Functional RequirementsNonfunctional requirements are often referred to as qualities of a system. Other terms used fornonfunctional requirements are quality goals, quality attributes, non-behavioral requirements andquality of service. For a physician, words "meaningful usage" may means something thatcontributes towards increased care and a better experience of work or says better safety. Theseare non-functional requirements, to the point where MHR deliver qualities which facilitaterealization these goals, physicians will say the use of such system is "meaningful." For efficientuse of the system, it is necessary that user is entirely involved and are being given opportunitiesfor participation as much as possible (Hatley, D., & Pirbhai, I. 2013). This leads to correction ofvarious problems associated with change management, and users being accustomed to new waysof doing things, as compared to traditional patient record system. Users have explained some ofthe requirements of the system which are patient search, registration of staff, updating of staffrecords and patients; they should be able to view all reports. Then the system should be able tovalidate and verify all the input by the user's and should be notified in case any errors aredetected while using the system. The system should be able to expand, in the case of any changesare required to be done. Moreover, the system should have high reliability and performancelevel. Nonfunctional requirements are those properties which the system should have. These aresome characteristics and qualities which will attract and make the system more reliable and easyto use. Various nonfunctional requirements that might help MHR are: Validity and Accuracy- thesystem should have numerous quality data assurance elements consisting of the ability todefining organization specific data requirements, should consist of drop down menus, text fieldsinputs and search functions for matching records. Reliability- MHR should allow users tosynchronize information when the connection is available, should have a backup of information
Requirements Report2that can be recovered in case of system failure, it should be able to perform tasks withinappropriate time and should allow various devices with less bandwidth. Performance- Systemshould be able to operate efficiently on various hardware system and even mobiles, should beable to support approx. 6000 client records and around 2000 employee records, it should havethe capability for adding 200 users for handling login capability during peak time, and it shouldbe able to provide real-time transactions through connected devices by volume of configuration.Security and Privacy- The system should be able to prevent unauthorized access to information,and should allow the administrator to control and establish different user login for every user andsupport access privileges. It should be able to support admin for editing, viewing, deleting andauditing and generation of privacy reports for knowing information like date and time of accessby the user and should also provide flexible control over passwords. Usability- the system ofMHR should allow the administrator to configure by the purpose of usage; it should also providethe user with the interactive and pleasing user interface. Further, it should enable data entrywhich is easy and organized, and should also be user-friendly that can be learned fast by the userto usage and also it should be compatible with various devices to improve the efficiency of thesystem. Other than this it should support data that is real time and use logic and validation forpreventing any errors in data entry and should allow its users to locate various functions easily invery fewer clicks (Li, M., et. al. 2010, September).Review of cloud-based solutionsThere are various advantages of implementation of cloud technology in health care sector. CloudComputing can be defined as a computerized model that provides access to users for anapplication, and it related data via third party service provider by using the internet.
You’re reading a preview

To View Complete Document

Become a Desklib Library Member.
Subscribe to our plans

Download This Document