ITC 548 System Analysis Assignment

ITC 548 System Analysis Assignment

ITC 548 System Analysis Assignment

This is the assessment 3 of ITC 548 System Analysis

Non-functional Requirements

We have made a cloud-based solution for Headspace project “My health record”.  Head space organization can use “platform as a service “cloud solution for the proposed project where the proposed system can be developed. Data will be stored and retrieved from the cloud. The owner can log into the cloud and can store data there like the patient first story, their medical report, and the details of medical professional and emergency department. Medical professionals also find their patient details and can upload their medical report there.

ITC 548 System Analysis Assignment, itc 548 assignment help

Cloud-based solution for Headspace project fulfills the following requirements:

User interface requirements: User interface requirement includes a document for the “my health record” system in which we will explain the details of the proposed software. In this headspace, organization specifies what thing will be changed during implementation and when will be changed. This documentation also includes the open issues of the proposed software, logical flow of the software, error and exception cases.

Click here for assessment 1&2 of ITC 548 System Analysis 

System qualities: Cloud computing ensure that services which are provided are based. The service level agreement of cloud computing guarantees the 99.99 % availability, performance, adequate resources. The user can use any resource from a pool of IT resources (Cloudtweaks, 2012).

System constraints:The proposed system constraints include the following system quality attributes:

Automatic software updates: Cloud computing provides automatic updates. Cloud service provider takes care of regular software updates; we need to worry about that.

Consistency: In case of any server failure cloud computing transfer the entire another available server. Cloud computing ensures the consistency of the data and also ensure that data will not be modified.

Flexibility: Cloud-based model provides flexibility. If headspace organization needs increases than cloud capacity can be scaled up or scale down if needs decrease. Cloud computing helps the organization to be in control and helps to make the decision to the current and future needs. Headspace organization can access the proposed system without interaction of the cloud service provider.

Pricing:Cloud computing reduced cost.It charges to pay for use basis i.e.  Only charge for the resources which organization use. Headspace organization use platform as a service so it doesn’t need to purchase platform where they will develop “Health record system” .they only need to pay for use basis.

Maintainability:Maintainability includes maximize the efficiency, reliability of the proposed system, ability of the system to replace or recover faulty component without replacing the working components of the proposed system.

System interface requirements:It includes the description of my health record system. The description includes the functional and nonfunctional requirements of the system.

Nonfunctional requirements: A non-functional requirement describes how a system performs a specific function. Cloud-based solution for Headspace project fulfill the following non-functional requirements:

FURPS Acronym:

Usability: Usability means software can be used by the user with effectiveness, efficiency, and satisfaction. The headspace organization can access the medical record system on cloud effectively because it can store a large amount of data there without being worry about backup. It can also retrieve data whenever needed. The Patient report can be accessed by medical professional directly rather than focusing on technology the headspace organization can focus on their goal.

Reliability:Cloud-based model provides availability, accuracy, recoverability. The user can access data from anywhere and anytime. He can login into the system and after successful login, he can access data. Cloud-based solution also provides a solution for disaster recovery. There is no need to back so it saves time and money.

Performance:  The performance of the system involves short response time, High availability of the system, high throughput, and short data transmission time. Cloud provides high availability of the system. Headspace organization owner, medical professional, emergency department can access the data anytime and from anywhere and he can get in a few seconds.

Security:  The greatest benefit of cloud computing is security. Laptop loss or damage is a big problem of every organization so that by storing data on cloud headspace organization can access data anytime and from anywhere no matter what happened to your device.  Cloud also provides privacy i.e. only authorized person can access the data. The owner, the medical professional and emergency department have login id and password.They will login into the system and can access the data (Salesforce UK Blog, n.d.).

Functional requirements:

Functional requirements describe the behavior of the system after its completion. The functional requirement includes the business rules, Administrative functions, Authentication, Authorization levels, audit tracking, external interfaces, Certification requirements, Reporting requirements, Historical data, Legal requirements. These requirements are different from on functional requirements be

Review of Cloud-Based

Strength and Weakness of Cloud-based system are as follows:


Table 1: Strengths of Cloud-based system



Cost saving

 Cloud computing reduces the cost of purchasing the resources for software development. The organization can use resources from the cloud computing and can pay according to their uses. Normally service provider charges based on weekly, monthly basis.


Cloud-based solution is more reliable compared to in-house infrastructure. We need not back up for our data, cloud computing provides recoverability. In case of any failure service provider transfer data to another server with consistency.


Cloud computing provides enhancement in IT resources management and maintenance.

Strategic edge

Using cloud-based solution organization need not focus on technology and can focus on the business objective. Organization need not purchase resources for a new application, it can use cloud-based resources and can reduce time.


Table 2: Weakness of Cloud-based system



  Limited control

Cloud infrastructure is managed and owned by the service provider so the customer has limited control on them. The customer can only manage and control the application which he developed but don’t manage and control the infrastructure.

Vendor lock-in

The organization has difficulty to migrate their services from one vendor to another vendor so cloud computing ensures that cloud computing service is flexible and easy to integrate.


If customer internet connection is offline then he cannot access the services and data from the cloud. Sometimes business processes suspend due to the workload on the cloud (Levelcloud, n.d.).

Considering the environment in which the solution would be deployed:

The proposed system is “My health record system” is a medical field project for youth which is surfing from mental illness problem. The medical records are sensitive so I have considered “Platform as Service (PASS)” cloud solution for the proposed system. In platform as a service cloud solution headspace can develop the proposed system and can store data there. Medical professionals can login into the system to see the medical reports of their patients and upload the new medical report. The organization can also store the patients first tell the story in the cloud and medical professional can access them from the cloud. Headspace organization need not be worried about software updates because “PAAS” provider will take care of that. The organization can scale up or down the cloud capacity according to their needs so it saves cost and time.

 How data kept secure on the cloud:

The Australian Privacy Act is designed to collect and handles the personal information of an individual. This personal information is sensitive and applied on private. Data security is the first concern for Headspace organization transferring information on the cloud because medical information is very sensitive and it must go on wrong hands.   Cloud solution also provides data security because only authorized person can login into the system with have login id and password. In case of failure, it also transfers data to another available server. Once the medical information saved into the cloud there may be a less direct control on it. cloud computing provides strong encryption of the data and holds data into the server, this can help to protect data from misuse. The cloud-based solution makes data centrally accessible so organization minimizes the number of copies of login details to the cloud (Solomon, 2010).

SDLC Approach

Predictive SDLC Model

Predictive SDLC is also known as a sequential model in which a set of steps flows in a definable manner. In Predictive SDLC model, each step must be completed before next step begins.  Predictive SDLC model already defines when the previous phase will be complete and next one will start. The classic example of a predictive model is “Waterfall model” (Parks, n.d). 

Predictive SDLC Model

Table 3: Pros and Cons of Predictive SDLC Model



 The predictive model is simple.

After going in the testing stage it is very difficult to go back and make any changes.

It is easy to use and understand

High chances of risk and uncertainty

This model is best for small projects because requirements are understood very well.

Not good for large projects.

The phases of this model can be completed one at a time so there are no chances for phases overlap.

This model is not good where high chances for changing the requirements.

Adaptive SDLC Model

The classic example of adaptive SDLC is XP (Extreme programming) and other methodology which are considered as Agile. In this model software development process is divided into the small build and provides customer satisfaction by rapid delivery of the working build. Next releases are made on previous functionality (Istqbexamcertification, n.d.).

Adaptive SDLC Model

Table 4: Pros and Cons of Adaptive Model



 In this model customer, the developer made face to face communication which is the best form of communication.

Lack of documentation

Late changes can be  easily made in the requirement

The project can be gone on the wrong track if the customer doesn’t have knowledge about final output.

This model provides customer satisfaction by continuous delivery of the working software

This model requires experience programmer and no place for the newly programmer.

Emphasize people and communication rather than tools and process.

In case of some software development is not possible to predict efforts at the starting of the software development life cycle.

I will recommend agile model because “Health record system” is a long and ongoing project. Agile model is good for project management. We can make changes easily in the requirement. Agile .there are fewer chances of risk and uncertainty in the agile model. The adaptive model is good for service-oriented project because in these project changes are expected. The agile model is flexible and focuses on a developer team able to make change rapidly according to the users need.


LevelCloud. (2017). Advantages and Disadvantages of Cloud Computing. Retrieved from

Cloudtweaks. (2012). Key Features Of Cloud Computing. Retrieved from

Parks, A. (n.d.). What is Waterfall model- advantages, disadvantages and when to use it?.  Retrieved from

Solomon, A. (2010).  Privacy and the cloud| office of the Australian Commissioner - OAIC. Retrieved from

Istqbexamcertification. (n.d.). What is Agile model – advantages, disadvantages and when to use it?. Retrieved from

Salesforce. (2015). Why move to the Cloud? 10 Benefits of Cloud Computing. Retrieved from