Chat with us, powered by LiveChat After reviewing the concepts of advanced software engineering in the previous assignment, your task is to design a three-tier client-server and d | EssayAbode

After reviewing the concepts of advanced software engineering in the previous assignment, your task is to design a three-tier client-server and d

 

After reviewing the concepts of advanced software engineering in the previous assignment, your task is to design a three-tier client-server and distributed-architecture model. You also need to design the interactive workflow diagrams (called sequence diagrams) for each activity associated with Phase 2 class diagrams. In this next phase, you also must design the user interfaces for the proposed project. Use MS Word to add those individual files in the document by taking screenshots or submit individual files. You must use MS Visio for this assignment.

In this phase, you will need to develop the following diagram associated with the project introduced in Phase 1. Include:

  1. Sequence diagram for each entity, also called interactive workflows.
  2. System architecture:
    • Three-tier client-server architecture.
    • Distributed component architecture.
  3. User interface design as a part of System of Systems engineering process.

Your assignment must follow these requirements:

  • Include charts or diagrams created in MS Visio. The completed diagrams or charts must be placed in the Word document before the document is submitted.
  • Create a cover page. Refer to the sample paper provided in the Strayer Writing Standards area in the left-hand menu for further guidance.

The specific course learning outcome associated with this assignment is:

  • Create sequence diagrams, system architecture models, and user interface designs for a software development project.

Software Requirement Specification

Tenia Daniels

Professor: Osama (CIS 421)

May 8, 2022

Software Requirement Specification

A patient information system for mental health care is an essential tool for maintaining data for patients suffering from mental health problems. Besides acting as a system for collecting and storing mental health information, the system can also help in making well-informed decisions. The system is used by different people working in the health facility. Some of these include the, nurses, physicians, and doctors. Therefore user requirements are essential when designing the system; each user will require unique interfaces suited to their needs. It is also important to consider system, functional and nonfunctional requirements when designing the system.

User requirements involve what the users expect the system to perform (Fidan, 2017). Some of the user requirements for the Mentcare system include; it should collect information about the patient; the people using the system should be able to enter data into the system. The system should also allow the staff to access necessary data used in patient care; it should provide medical staff with timely information for the patients' treatment. In addition, the system should have features that allow individual care management and patient monitoring. It should be possible to monitor the records of patients undergoing treatment. Lastly the Mentcare system should generate reports about the patient's conditions and the cost of prescriptions.

System requirements refer to the functionalities needed for the software to be used efficiently. System requirements may fall under performance requirements, functional and system technical requirements (Fidan, 2017). For instance, the Mentcare system can work on a computer with a minimum of 4GB of Ram and the computer system should be running on a 64-bit operating system. The processor should be a minimum of 1.8 Gigahertz to ensure the efficient operation of the software system. In addition, the system needs a minimum of 120 GB of hard disk space to install the software. Security is another essential requirement; the hardware and software should provide safe functioning of the system without data loss.

Functional requirements involve what the system should do or how it should function (Fidan, 2017). Functional requirements include authentication of users, administrative functions, authorization levels, and reporting functions. The system is being used by people working in different capacities, and thus authorization levels are significant. What the caregivers, physicians, and doctors need from the system is different. For instance, the Patients require fewer privileges than doctors. Authentication is the process of proving you are the authorized user. Every user needs to be authenticated to allow access to resources in the system. Reporting functionality is essential to help extract reports and statistical information about patients. Such reports help make informed decisions. Authorization is the rights and permissions granted to a user and determines the extent of rights the user can access the system.

Nonfunctional requirements place constraints on how the system should work. Some of the system's nonfunctional requirements include reliability, scalability, usability, security, performance, and maintainability. Reliability is the ability of the system to perform the intended function without failing and being stable in conditions of data overload. Usability is an essential requirement that includes the software interface and functionality, making it easy to use the system. Security is another critical requirement implemented in functions, procedures, and mechanisms in which the system operates. Security will be essential in Metacare system, considering we are dealing with personal data. Performance requirements imply that the system should accomplish certain functions under specific conditions (Rosencrance, 2019). For instance, the software should efficiently support the user tasks and have a fast response and considerable execution time.

Security Control Assessment

Security control assessment involves testing and evaluating security controls to ensure they operate as intended, are implemented correctly, and meet security requirements. It is crucial for the software as it allows assess possible risks and prevents them before deployment of the system (NIST, 2022). Some of the risk assessments that can be carried out to enhance the security of the software include preliminary risk assessment, design risk assessment, and operational risk assessment. A preliminary risk assessment identifies vulnerabilities before the system is implemented. It involves the analysis of all technical, administrative and physical variables and assesses qualitative and quantitative risks involved. Design risk assessment entails evaluating all aspects of the design phases, including the technology used and architectural design. It helps identify defects that might make the software unstable, infeasible, and below standards. Operation risk assessment looks at all risks that might arise when the system is used. Such risk can arise from flawed processes, employees' errors, and external factors.

Figure 1. Security control assessment matrix

The security control assessment matrix help in allocating risk ratings based on the likelihood and the impact. The matrix helps in prioritizing components based on their importance and vulnerability. Risks that are minor and rarely happen are given less priority, while risks that are most likely to happen and are considered severe are the most prioritized (Baze, 2016).

In conclusion, the patient information system for mental health care is an essential tool that will significantly help improve the care provided to the patients. The significant concerns related to the system include the security and privacy of data and the patient's record records. System usability and operation cost are also other concerns that need to be considered. Therefore software evaluation and security assessment to ensure all risks are resolved and software meets all requirements will be critical.

Figure 2. Use case diagram

References

Baze, A. (2016). Global Information Assurance Certification Paper. Giac.org. Retrieved from https://www.giac.org/paper/gccc/458/realistic-risk-management-cis-20-security-controls/146604

Fidan, G. (2017). D1.2.1 – System Requirements Specification. Itea4.org. Retrieved from https://itea4.org/project/workpackage/document/download/4842/D1.2.1.%20INSIST%20-%20System%20Requirements%20Specification.pdf.

NIST. (2022). security control assessment – Glossary | CSRC. Csrc.nist.gov. Retrieved 8 May 2022, from https://csrc.nist.gov/glossary/term/security_control_assessment#

Rosencrance, L. (2019). Software Requirements Specification (SRS). Search Software Quality. Retrieved from https://www.techtarget.com/searchsoftwarequality/definition/software-requirements-specification

Related Tags

Academic APA Assignment Business Capstone College Conclusion Course Day Discussion Double Spaced Essay English Finance General Graduate History Information Justify Literature Management Market Masters Math Minimum MLA Nursing Organizational Outline Pages Paper Presentation Questions Questionnaire Reference Response Response School Subject Slides Sources Student Support Times New Roman Title Topics Word Write Writing