Developing a Health Record System

This assignment delves into the design and implementation of a 'My Health Record System'. It recommends a hybrid cloud environment for its deployment, considering factors like security and scalability. The assignment further analyzes various Software Development Life Cycle (SDLC) models, concluding that a predictive SDLC approach is most suitable for this project.

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

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

2
SYSTEM ANALYSIS AND DESIGN
6. Conclusion.......................................................................................................................7
7. References........................................................................................................................8

3
SYSTEM ANALYSIS AND DESIGN
1. Introduction
Government of Australia and headspace organization has collaborated in developing an
information system that would record the story of mentally ill patients during the very first time
it is told. This would eliminate the need of retelling the story on visiting a new professional. The
system is to be implemented in a cloud environment and therefore it is essential to consider all
the security risks associated with deployment of the system on cloud (Steele, Min & Lo, 2012).
The non functional requirements of the system along with the chosen cloud environment and
SDLC approach are elaborated in the following paragraphs.
2. Non-Functional Requirements
Non-functional requirements of a system are specific criteria that are needed to be
considered while judging the operation of a system. It mainly defines the critical system
qualities, interfaces and system constraints. The different non-functional requirements identified
for the system are elaborated below (Chung, Nixon & Mylopoulos, 2012)-
2.1. Functionality
Functionality of a system defines the essential criteria a system needs to perform to meet
its objectives. The non functional requirement of functionality includes the presence of an option
quick update and access of the data into the system.
2.2. Usability
The system usability is another primary criterion to consider while identifying the non
functional requirements of the system. An easy user interface may increase the usability of the
system to a greater extent.

4
SYSTEM ANALYSIS AND DESIGN
2.3. Reliability
The reliability of the system is essential to consider, as the implementation of the system
will be successful only if the patients find it reliable enough to store their health records in the
system. Therefore, it should have a recovery option for considering the cases of data loss.
2.4. Performance
The implementation of this information system will be successful only if it is able to
perform according to the expectation. The ease of access is a major non-functional requirement
of the system that measures the system performance.
2.5. Security
Maintaining a proper security of the system is one of the major non-functional
requirements. The mental health data of patients are very confidential and sensitive and therefore
it requires proper security (Kulkarni et al., 2012). Encryption of data should therefore be
considered as major non-functional requirement.
3. Functional Requirements Vs Non-functional requirements
While functional requirements define the basic functionality of the system, the non-
functional requirements identified for the system is responsible for enhancing the system’s
performance level. The non-functional requirement of security is however essential to include in
the system as it is one of the major criteria for developing a proper information system for
storing the health record of the patients (Pearce & Bainbridge, 2014).
4. Cloud Environment: Hybrid

5
SYSTEM ANALYSIS AND DESIGN
The chosen cloud environment for this project is a hybrid cloud environment. This is
because the implementation of the system in public cloud although is cost effective, it is not
secure enough. There are larger chances of attack in the public cloud as the access of data from a
public cloud is easier (AlZain et al., 2012). Private cloud cannot be used in this case, as the data
access is difficult and limited in private cloud. The patient would not be able to access their data
outside the network of the organization and therefore this cannot be considered as well.
4.1. Hybrid Cloud: Strength
The advantages of using a hybrid cloud environment are listed below-
1. Security and data confidentiality is maintained in the hybrid cloud environment and
therefore it would be appropriate to implement this system in a hybrid cloud environment (Li et
al., 2015).
2. The cost of implementation of hybrid cloud is lower than the private cloud as the
public environment of the hybrid cloud can be leveraged from a trusted third party source.
4.2. Hybrid Cloud: Weakness
The weaknesses of hybrid cloud environment are listed below-
1. An attacker can target the data movement between the public and the private zone of
the hybrid cloud and therefore proper security is essential.
2. The initial cost of implementing a system is hybrid cloud is way more than that of
public cloud (Chen & Zhao, 2012).
5. The SDLC Approach

6
SYSTEM ANALYSIS AND DESIGN
The software development life cycle defines the number of phases required to implement
a software application successfully. The different SDLC approaches include the waterfall model,
agile model and so on. The predictive and adaptive SDLC approaches are discusses in the
following paragraphs.
5.1. Predictive SDLC
The project is pre planned in the predictive SDLC approach and the schedule of the
project is set before the project implementation. This is traditional waterfall approach of project
management and therefore the chances of project completion within the set time are very high in
this approach.
5.1.1. Pros
1. The resource requirement is estimated at the beginning of the project and therefore
budget estimation becomes easier.
2. The scope of the project remains unchanged thprought the project implementation and
therefore the probability of project completion within the set time is very high
5.1.2. Cons
1. The primary disadvantage of predictive SDLC is that, there is no scope of improvising
the project once it is implemented.
2. The feedback path is absent in predictive SDLC.
5.2. Adaptive SDLC

7
SYSTEM ANALYSIS AND DESIGN
The phases of the software development and the system implementation are not defined
at the beginning of the project and successful implementation of every phase is checked during
the implementation of Adaptive SDLC (Balaji & Murugaiyan, 2012). Therefore, modifying the
system features is easier in this project management approach.
5.2.1 Pros
1. The main advantage of adaptive SDLC is that, it is capable of adding new
requirements or improvising the system if required.
2. It incorporates a thorough testing of every phase and therefore the probability of
project success is very high.
5.2.2 Cons
1. Time required and cost of implementation is high
Therefore, it can be deduced that since the development of” My health record system” is a
medium sized project with a clear scope, it would be better to use the predictive SDLC approach.
6. Conclusion
Therefore, from the above discussion, it can be concluded that project under
consideration should be developed in a hybrid cloud environment. The report identifies the major
non-functional requirements of the system along with a proper SDLC approach for project
execution.

8
SYSTEM ANALYSIS AND DESIGN
7. References
AlZain, M. A., Pardede, E., Soh, B., & Thom, J. A. (2012, January). Cloud computing security:
from single to multi-clouds. In System Science (HICSS), 2012 45th Hawaii International
Conference on (pp. 5490-5499). IEEE.
Balaji, S., & Murugaiyan, M. S. (2012). Waterfall vs. V-Model vs. Agile: A comparative study
on SDLC. International Journal of Information Technology and Business Management,
2(1), 26-30.
Chen, D., & Zhao, H. (2012, March). Data security and privacy protection issues in cloud
computing. In Computer Science and Electronics Engineering (ICCSEE), 2012
International Conference on (Vol. 1, pp. 647-651). IEEE.
Chung, L., Nixon, B. A., Yu, E., & Mylopoulos, J. (2012). Non-functional requirements in
software engineering (Vol. 5). Springer Science & Business Media.
Kulkarni, G., Gambhir, J., Patil, T., & Dongare, A. (2012, June). A security aspects in cloud
computing. In Software Engineering and Service Science (ICSESS), 2012 IEEE 3rd
International Conference on (pp. 547-550). IEEE.
Li, J., Li, Y. K., Chen, X., Lee, P. P., & Lou, W. (2015). A hybrid cloud approach for secure
authorized deduplication. IEEE Transactions on Parallel and Distributed Systems, 26(5),
1206-1216.
Pearce, C., & Bainbridge, M. (2014). A personally controlled electronic health record for
Australia. Journal of the American Medical Informatics Association, 21(4), 707-713.

9
SYSTEM ANALYSIS AND DESIGN
Steele, R., Min, K., & Lo, A. (2012). Personal health record architectures: technology
infrastructure implications and dependencies. Journal of the Association for Information
Science and Technology, 63(6), 1079-1091.