logo

The Chosen Cloud Enviro

13 Pages2794 Words364 Views
   

Added on  2020-03-16

About This Document

The Predictive SDLC approach 8 5.1.1 The pros/ advantages of predictive Approach 8 5.1.2 Cons 9 5.2. The report identifies the different non-functional requirements of the system (Steele, Min & Lo, 2012). The Non-functional Requirements of the system The non-functional requirement of any project is responsible for evaluating and enhancing the performance of a system. The non-functional requirement for implementation of “My Health record system” is identified according to the critical system qualities associated with the

The Chosen Cloud Enviro

   Added on 2020-03-16

ShareRelated Documents
Running head: SYSTEM ANALYSIS AND DESIGNSystem Analysis and DesignName of the StudentName of the UniversityAuthor Note
The Chosen Cloud Enviro_1
1 SYSTEM ANALYSIS AND DESIGNTable of Contents1. Introduction......................................................................................................................32. The Non-functional Requirements of the system............................................................32.1. Functionality.............................................................................................................32.2. Usability....................................................................................................................42.3. Reliability.................................................................................................................42.4. Performance..............................................................................................................42.5. Security.....................................................................................................................43. Non functional requirement Vs the Functional requirement of the system.....................54. The Chosen Cloud Environment: Hybrid Cloud.............................................................64.1. Strength of the hybrid cloud Environment...............................................................74.2. Weakness..................................................................................................................75. The SDLC approach Predictive, Adaptive......................................................................75.1. The Predictive SDLC approach................................................................................85.1.1 The pros/ advantages of predictive Approach....................................................85.1.2 Cons....................................................................................................................95.2. The Adaptive SDLC approach..................................................................................95.2.1. Pros....................................................................................................................95.2.2. Cons...................................................................................................................96. Conclusion.....................................................................................................................10
The Chosen Cloud Enviro_2
2 SYSTEM ANALYSIS AND DESIGN7. References......................................................................................................................11
The Chosen Cloud Enviro_3
3 SYSTEM ANALYSIS AND DESIGN1. Introduction The organization Headspace is implementing an information system for storage andaccess of the patient’s health record in a cloud based environment. The various security risk andconcerns associated with this are analyzed in order to evaluate different aspects and the details ofthe system implementation. The report identifies the different non-functional requirements of thesystem (Steele, Min & Lo, 2012). The report discusses the advantages of using a hybrid cloud-based solution. The report discusses the proper SDLC approach that would be beneficial forconsidering in the project. The details about the implementation of the information system inelaborated in the following paragraphs. 2. The Non-functional Requirements of the systemThe non-functional requirement of any project is responsible for evaluating andenhancing the performance of a system. The non-functional requirement for implementation of“My Health record system” is identified according to the critical system qualities associated withthe project, system interfaces, user interface requirements and different system constraints. Itdefines the different operations of the system and proper identification of the same is responsiblemaintaining the objective and functionality of the system. The major non-functionalrequirements identified for the project are discussed below (Chung, Nixon & Mylopoulos, 2012)-2.1. Functionality Functionality of the system comes under the non-functional requirement of the systembecause it is essential for the system to perform according to the set functions. This is similar tothe functional requirement of the system as well because the functional requirements also dealswith measuring the functionality of the system. The ease of update and data access are from any
The Chosen Cloud Enviro_4

End of preview

Want to access all the pages? Upload your documents or become a member.

Related Documents
Assignment | System Analysis and Design
|13
|2740
|290

Assignment on System Analysis and Design
|12
|2461
|34

System Analysis Name of the Student Name of the University Author
|13
|2764
|377

System Analysis and Design Assignment - Headspace Organization
|13
|2617
|96

System Analysis and Design System Name of the University Author
|10
|1654
|51

Report | System Analysis and Design
|13
|2815
|49