System Analysis and Design - Australia

Added on -2020-02-23

| 12 pages| 2724 words| 54 views

Trusted by 2+ million users,
1000+ happy students everyday

Showing pages 1 to 4 of 12 pages

Running head: SYSTEM ANALYSIS AND DESIGNSystem Analysis and DesignName of the StudentName of the UniversityAuthor Note
1 SYSTEM ANALYSIS AND DESIGNTable of Contents1. Introduction......................................................................................................................22. Functional Requirements.................................................................................................23. Non-Functional Requirements.........................................................................................34. Strength and weakness of Cloud based Solution.............................................................54.1. Strength of Cloud......................................................................................................54.2. Weakness of Cloud...................................................................................................65. SDLC Approach..............................................................................................................65.1. Predictive Approach.................................................................................................65.1.1. Pros....................................................................................................................75.1.2 Cons....................................................................................................................75.2. Adaptive Approach...................................................................................................86.1.1. Pros....................................................................................................................86.1.2 Cons....................................................................................................................96. Conclusion.......................................................................................................................97. References......................................................................................................................10
2 SYSTEM ANALYSIS AND DESIGN1. IntroductionThe Commonwealth Government of Australia undertakes the project under discussion,which aims at building an automated health record system to store and access patient’s data. Thisis undertaken in order to prevent the manual data keeping. This project will make it easier forboth patients and the professional to access the health record information. The record of ‘Myhealth Record System’ is to be stored in cloud and therefore, the security essentials of the cloudstorage are needed to be kept in mind. The different security essentials include, theconfidentiality, integrity and the availability of the data when required (Pearce & Bainbridge,2014). Data security is an important aspect of cloud solution as with the increasing use of cloudstorage and the concept of data mining, the information stored within the system is exposed tovarious security risks and therefore proper measures should be implemented to built a securehealth record system. The relevant aspect of cloud solution, functional and non functionalrequirement of the project, along with the recommended SDLC approach of the project areelaborated in the following paragraphs (Steele, Min & Lo, 2012). 2. Functional RequirementsFunctional requirements outline the specific behaviors or the functions that a system orproject is needed to incorporate or perform. The functional requirements identified for thisproject are elaborated below- 1) Authentication- In order to make the process of data storage and data access moresecure, this property is necessary need. This defines the members or the users who are allowed toaccess the system and prevents the unauthorized user from accessing the system (Jain, &Nandakumar, 2012). In is an important functional requirement as this acts as a boundary between
3 SYSTEM ANALYSIS AND DESIGNthe authorized and unauthorized access of data. Therefore, this can be considered as an importantfunctional requirement of the project. 2) Authorization levels- This is essential to limit particular information to an authorizeduser only. The different authorization levels are needed to be set in order to ensure that only acorrect individual is allowed to access the information. 3)Edit and Update Documents- Another important functional requirement is edit/update document option. This gives the user or the patients to edit and update their health recorddocuments. 4) Summary Record: This option is necessary to provide a summarized option of thehealth record and the details of the medications the patients had undergone over the years. Thiswill help the professionals as well as the patients to review the medication they are undergoing.This will be a useful functional requirement of the project under consideration. 3. Non-Functional RequirementsThe non-functional requirement is a requirement that specifies the criteria to be used inorder to judge the operation of a system (Chung, Nixon & Mylopoulos, 2012). The nonfunctional requirements in a project can be varied in number and helps in implementing theprojects in a better way. The non-functional requirements that are needed to be considered forthis project are listed below- 1) Functionality: One of the major non-functional requirements of this project is thatthe system to be developed will abide by the functionality of the system. The major functionalityof the system is the storage of patients’ data in cloud in a secure manner.

Found this document preview useful?

You are reading a preview
Upload your documents to download
or
Become a Desklib member to get accesss

Premium

$45

Q&A Library Access

Chat support

12

Document Unlocks

4

Answer Unlocks

Students who viewed this