Assignment on System Analysis and Design

Running head: SYSTEM ANALYSIS AND DESIGN
System Analysis and Design
Name of the Student
Name of the University
Author Note

1SYSTEM ANALYSIS AND DESIGN
Table of Contents
1. Introduction......................................................................................................................3
2. The non-functional Requirements of the system.............................................................3
2.1. Functionality.............................................................................................................3
2.2. Usability....................................................................................................................4
2.3. Reliability.................................................................................................................4
2.4. Performance..............................................................................................................4
2.5. Security.....................................................................................................................4
3. Functional Requirements Vs the Non-functional Requirements of the system...............5
4. The cloud Environment Chosen: Hybrid cloud...............................................................5
4.1. Strength of Hybrid cloud environment.....................................................................6
4.2. Weakness of the Hybrid cloud..................................................................................6
5. SDLC Approach, Predictive or Adaptive........................................................................7
5.1. Predictive SDLC Approach......................................................................................7
5.1.1. Pros....................................................................................................................8
5.1.2 Cons....................................................................................................................8
5.2. Adaptive SDLC Approach........................................................................................8
5.2.1. Pros....................................................................................................................9
5.2.2. Cons...................................................................................................................9
6. Conclusion.......................................................................................................................9

2SYSTEM ANALYSIS AND DESIGN
7. References......................................................................................................................10

3SYSTEM ANALYSIS AND DESIGN
1. Introduction
The organization headspace works with the mental ill health patients of 12 to 25 who
experience several problems due to depression and anxiety. The organization decided to develop
an information system that would store the patients’ data and information in the very first time it
is told. The primary aim of developing this system is the elimination of story retelling. A cloud
based environment is would be effective for the system implementation (Steele, Min & Lo,
2012). The report highlights a proper cloud environment that will be appropriate for the system
implementation along with the recommendation of a proper SDLC approach for project
implementation.
2. The non-functional Requirements of the system
The proper operation of the system is judged by specifying the non-functional
requirements of the system. Therefore, along with the functional requirements it is essential to
consider the non-functional requirements as well. The non-functional requirements identify the
different system requirements, interfaces and system constraints (Chung, Nixon & Mylopoulos,
2012). The different non-functional requirements that are identified for this project are discussed
in the section below-
2.1. Functionality
The system’s functionality is one major non-functional requirement of the system.
Maintaining a proper functionality of the system includes the non functional requirement of data
availability and scalability of the system. This is therefore a major non-functional requirement of
the system.