Systems Thinking and Constraints Analysis

This assignment delves into the concepts of systems thinking and constraints analysis within a design context. It requires students to analyze a system, identify its components, understand their interactions, and recognize potential constraints that might limit the system's performance or effectiveness. The focus is on applying these principles to real-world scenarios and demonstrating a comprehension of how systems function within defined boundaries.

System Analysis and Design
Headspace
10/4/2017
1

My Health Record
Table of Contents
Introduction.................................................................................................................................................3
Non-Functional System Requirements........................................................................................................3
System Usability......................................................................................................................................3
Reliability................................................................................................................................................3
Performance of the System......................................................................................................................4
Supportability..........................................................................................................................................4
List of System Interfaces.............................................................................................................................4
Set of User Interfaces..............................................................................................................................4
Set of External Systems/Devices Interfaces.............................................................................................5
System Constraints......................................................................................................................................5
Cloud Based Solutions................................................................................................................................6
Software Development Life Cycle (SDLC) Approach................................................................................7
Predictive Approach................................................................................................................................7
Adaptive Approach..................................................................................................................................7
Recommendations & Conclusions...........................................................................................................7
References...............................................................................................................................................9
2

My Health Record
Introduction
There are various industries that have been set up in different parts of the globe that comprise of
several organizations and business units. Due to the presence of so many different entities, there
is a lot of competition that has been witnessed to maintain an edge over the others. Technology
plays a major role in the maintenance of this edge over the competitors in the market. It is
because of this reason and various other advantages that the organizations are making a move to
adapt latest technological elements. Headspace, a healthcare organization that provides medical
treatment, assistance and services to the patients has decided to implement a health record
system in its organization.
Non-Functional System Requirements
In any of the automated systems and applications, there are several requirements and
specifications that need to be fulfilled. Each of these categories of requirements has their own
significance and relevance to the system. Non-functional requirements are also known as the
system qualities and these are the requirements that determine the user satisfaction levels and the
behavior of the system. The following requirements shall be maintained in the system so that the
system behavior and response is adequate and is efficient enough to achieve high levels of user
satisfaction.
System Usability
Any of the automated system or an application that is implemented in an organization is done
with a purpose to overcome the existing issues and provide the end-users with amazing user
experience. The same holds valid for the automated system that is being developed for
Headspace. There shall be an element of usability included in the system so as to make sure that
the system is easy to use and navigate and is also equipped with the desired set of functions and
features (Lauesen & Younessi, 2016).
Reliability
There are various categories of information that will be associated with the automated system for
Headspace. However, the primary category would be the mental health details of the patients and
3

My Health Record
this category of information will be extremely sensitive in nature (Chung, 2016). It would be
required to make sure that the system presents the response to the user queries in such a manner
that the reliability of the response is always maintained and followed.
Performance of the System
The automated system shall have utmost levels of performance which shall be determined by
indicators and parameters, such as, response time and throughput time. All of these elements
must be minimal so that the user does not suffer from any lags or performance issues (Malan &
Bredemeyer, 2010).
Supportability
Technology is not stagnant or static in nature and keeps on experiencing many changes and
alterations. The automated system that will be developed for Headspace must be designed in
such a manner and with the use of such a methodology that such changes and alterations can be
easily incorporated in the system and other changes in terms of usage and requirements can also
be met with ease (Shaikh & Misbahuddin, 2016).
List of System Interfaces
Set of User Interfaces
 The design methodology used in the system design phase shall be responsive web design.
It is because of the reason that the users expect the present day systems to behave and
respond according to their actions and preferences which would be easily made possible
by this design method.
 The use of colors shall be kept simple and light which shall fall in line with the purpose,
aim and theme of the system.
 Visual appeal shall be enhanced by enhancing the interaction level by making good use
of responses such as highlights, change of colors, change of text etc.
 Customization shall be incorporated in the system by allowing the users to change the
system theme and the colors used in the application (Fosse & Delp, 2016).
4

My Health Record
 All the screens on the system shall make sure that the consistency is reflected and shown
in terms of the layout that is present along with the size of the text elements, headings,
color of the text etc.
 The flow of the system on one screen or within the screen in terms of scrolling and
navigation must be extremely smooth.
 The use of styles and font face for the headings and the textual content in the body must
be kept uniform across all the screens.
Set of External Systems/Devices Interfaces
 Users shall be allowed to send and receive emails which shall be made possible by using
protocols like Simple Mail Transfer Protocol.
 Transmission and sharing of files shall be allowed and made possible by using suitable
protocols and mechanisms.
 Network connections and communications shall be allowed and made possible by using
protocols like Transmission Control Protocol.
 Communication is one of the most important aspects of the system and the same shall be
maintained by using and integrating the communication protocols in the system.
 There shall be health equipment and tools that must be connected with the system so that
the users can record the health signs using the same (Conde et al., 2010).
 Information privacy and security shall be maintained by making use of security protocols
at the network and transport layers (Wheatcraft, 2010).
System Constraints
 The source code shall be created in JAVA programming language so that the code is
flexible and inter-operatable. NetBeans shall be used as the tool for coding purposes.
 The back end shall be set up using NoSQL and Cloud databases such as MongoDB.
 Test creation and execution shall be done by using the tool as TestLink (Dettmer, 2016).
 Defect logging, tracking and management shall be done through Bugzilla.
5

My Health Record
Cloud Based Solutions
Cloud computing plays a significant role in the automated system that will be developed for
Headspace. The back end of the system will be entirely dependent upon the cloud database and
services. Also, deployment and delivery of the system will be made possible by using and
implementing suitable cloud models.
For the purpose of system delivery, there are three choices that are present which can be
analyzed and selected for this case. These include cloud models on the basis of software,
platform or infrastructure.
Platform as a Service (PaaS) is the cloud delivery model that has been selected and
recommended for this case. There will be many advantages that will be offered by the PaaS
model to the automated system for Headspace. These include the upgraded levels of security of
the system and the information sets associated with it that will be made possible. There would
also be easier management and maintenance that will be possible along with the platform for
execution of the operations. This model may score a little higher in terms of the budget but it
would otherwise fit to the needs and requirements.
Similarly, there are various models that can be selected for the deployment of the system which
include hybrid, public and private cloud models. The model that has been recommended for the
system is hybrid cloud model. This model has been recommended because it includes the
features and benefits of both the public and private cloud models. The handling and management
of the information will be accordingly done on the basis of the information type. The deployment
services necessary as per the information classification will also be possible accordingly.
There are cloud services that are present for information security and privacy as well. Cloud
based security solutions in terms of network security, intrusion detection, malware detection and
anti-denial tools shall be implemented so that the information is always kept secured and
protected from the security threats and attacks.
6

My Health Record
Software Development Life Cycle (SDLC) Approach
Many methodologies, techniques and approaches have been designed for the development of the
system or software. The two categories of approaches with their features and parameters have
been discussed and described below.
Predictive Approach
In this approach, all the project tasks and activities that shall be executed for the development of
the system are determined and listed in the initial phase. The project estimations in terms of the
effort, schedule, costs, resources etc. are done during the first phase and the developmental
activities are accordingly planned. There is a great degree of dependency of the project activities
on the other tasks that is witnessed. The execution takes place in a set of phases and this
approach is applicable when the probability of risks and requirements inflation is less. Waterfall
model is one of the popular examples of predictive SDLC approach.
Adaptive Approach
This is the approach that is ad-hoc and adaptive in nature and does not pre-determine any of the
tasks or activities. In this case, the execution takes place as per the information available in terms
of specifications and requirements. There is no set series or plan that is followed and a number of
interactive iterations are used for the purpose of execution. It leads to the ability to easily manage
the changes. Agile SCRUM framework is one of the popular methodologies that come under this
SDLC approach.
Recommendations & Conclusions
The report includes numerous suggestions and recommendations in terms of the programming
language, database, testing tools, cloud deployment and delivery models, security protocols etc.
The most important element of the project that will determine its success or failure is the
development approach. The recommended approach in this case is the adaptive approach which
shall include agile SCRUM framework for this case. The recommendation is based upon several
reasons which include the higher level of interaction with the project client, increased
transparency with the customers, higher scalability, supportability and flexibility along with
enhanced communication that come along with this approach. All of these elements are a part of
the feature list of the agile SCRUM framework which would make it easier for the project team
7

My Health Record
to achieve project goals and objectives. There are also additional benefits that will be offered in
terms of decreased probability of risks and better change management.
Management, planning and communication are the three elements that also have an extremely
significant role to play in the success of the projects. The methodology and approach that is used
in these activities also have a lot of relevance. Project Management Body of Knowledge
(PMBOK) is the approach that must be used in these areas so that the results that are achieved
are positive and the project goals and objectives are met. The project risks and conflict areas will
also be managed efficiently by making use of PMBOK methodology. There may be many
different conflicts, disputes and problems that may come up among the project resources which
will be easily handled along with the management of project costs and schedule.
8

My Health Record
References
Agilemodeling,. (2016). UML 2 Use Case Diagramming Guidelines. Agilemodeling.com.
Retrieved 04 October 2017, from http://agilemodeling.com/style/useCaseDiagram.htm
Bourne, L. (2016). Stakeholder Relationship Management. Retrieved 04 October 2017, from
http://www.mosaicprojects.com.au/PDF_Papers/P128b_Stakeholder_Relationship_Manage
ment.pdf
Chung, L. (2016). Non-Functional Requirements. Retrieved 04 October 2017, from
https://www.utdallas.edu/~chung/SYSM6309/NFR-18-4-on-1.pdf
Conde, J., De, S., Hall, R., Johansen, E., Meglan, D., & Peng, G. (2010). Telehealth Innovations
in Health Education and Training. Telemedicine And E-Health, 16(1), 103-106.
http://dx.doi.org/10.1089/tmj.2009.0152
Dettmer, H. (2016). Systems and Constraints: The Concept of Leverage. Retrieved 04 October
2017, from http://goalsys.com/systemsthinking/documents/Part-6-
SystemsandConstraints.pdf
Fakhroutdinov, K. (2016). UML actor is a role played by a human user of the designed system,
some other system or hardware that interacts with the subject by using services of the
subject.. Uml-diagrams.org. Retrieved 04 October 2017, from http://www.uml-
diagrams.org/use-case-actor.html
Fosse, E. & Delp, C. (2016). Systems Engineering Interfaces: A Model Based Approach.
Retrieved 04 October 2017, from
http://www.omgsysml.org/System_Engineering_Interfaces-IEEE_2013.pdf
Lauesen, S. & Younessi, H. (2016). Six Styles for Usability Requirements. Retrieved 04 October
2017, from http://www.itu.dk/~slauesen/Papers/SixStyles.pdf
Malan, R. & Bredemeyer, D. (2010). Defining Non-Functional Requirements. Retrieved 04
October 2017, from http://www.bredemeyer.com/pdf_files/NonFunctReq.PDF
McAtee, M. (2016). A good compliance system takes the administrating out of managing.
Qualitydigest.com. Retrieved 04 October 2017, from
9

My Health Record
http://www.qualitydigest.com/nov01/html/paperless.html
Rhyous,. (2011). The 8 Types of Technical Documentation and Why Each Is Important. Rhyous.
Retrieved 04 October 2017, from https://www.rhyous.com/2011/07/21/the-different-types-
of-technical-documentation-for-software-and-why-each-is-important/
Shaikh, A. & Misbahuddin, M. (2016). A system design for a telemedicine health care system.
Retrieved 04 October 2017, from
https://gupea.ub.gu.se/bitstream/2077/10498/1/gupea_2077_10498_1.pdf
Walker, D. (2016). Influence, Stakeholder Mapping and Visualisation. Retrieved 04 October
2017, from
https://mosaicprojects.com.au/PDF_Papers/P062_Influence_Stakeholder_Mapping_and_Vi
sualisation.pdf
Watt, A. (2016). 5. Stakeholder Management | Project Management. Opentextbc.ca. Retrieved
04 October 2017, from https://opentextbc.ca/projectmanagement/chapter/chapter-5-project-
stakeholders-project-management/
Wheatcraft, L. (2010). Everything you wanted to know about interfaces, but were afraid to ask.
Retrieved 04 October 2017, from
http://spacese.spacegrant.org/uploads/images/UserContributedFiles/
WheatcraftInterfaces110909.pdf
Wick, S. (2016). User Stories and Use Cases - Don’t Use Both!. Batimes.com. Retrieved 04
October 2017, from https://www.batimes.com/articles/user-stories-and-use-cases-dont-use-
both.html
10