Cloud Computing and System Development

The assignment delves into the advantages and disadvantages of cloud computing, focusing on its influence on the financial services industry. It examines the security aspects of cloud computing, comparing Agile and Waterfall methodologies in software development. Furthermore, it discusses non-functional requirements (NFRs) for software architecture and emphasizes the importance of user interface design in cloud applications.

SYSTEM ANALYSIS AND DESIGN 1
Assignment 3
[Student Name Here]
[Institution’s Name Here]
[Professor’s Name Here]
[Date Here]

SYSTEM ANALYSIS AND DESIGN 2
Table of Contents
Introduction.............................................................................................................3
Critical analysis of the non-functional requirements (NFR)...............................3
System qualities......................................................................................................4
System interface.....................................................................................................4
System constraints..................................................................................................5
An analysis of the cloud-based solutions...............................................................5
Strengths of cloud resources..................................................................................6
Weaknesses............................................................................................................6
Securing the data....................................................................................................6
SDLC methods (Software development life cycle)...............................................7
Predictive approach................................................................................................7
Pros of the predictive method.............................................................................8
Cons.....................................................................................................................8
Adaptive approach..................................................................................................8
Pros of the method..............................................................................................9
Cons.....................................................................................................................9
Recommendation.....................................................................................................9
Conclusion..............................................................................................................10
References..............................................................................................................11

SYSTEM ANALYSIS AND DESIGN 3
Introduction
Cloud-based solutions have recently been identified as critical components of software
engineering because they facilitate the deployment and support of computational resources. In
most cases, these solutions will offer system developers a means to store and support IT
resources over networking infrastructures. Furthermore, with cloud-based solutions, the
developers are able to increase the benefits of information systems through the conveniences of
virtualised structures (Garg, 2015). However, those interested in this technology must balance
out the benefits with the potential risks involved. In this case, the subscribers of the technology
need to analyze the existing standards and operational structures of the service providers to attain
an optimal decision (Dailogic, 2017). Similarly, this report highlights the key features of cloud
computing where its integration with the proposed Headspace system is outlined. This report also
highlights some of the non-functional requirements of the system that will yield a desirable
system having established the development procedure.
Critical analysis of the non-functional requirements (NFR)
First, the differences with the functional requirements; which among many definitions outline the
behaviours and functions of a system e.g. storage space, drive format and displaying names etc.
Now, non-functional requirements describe the system in terms of how it operates to meet its
objectives i.e. the functions. Therefore, while one specifies the functions and operations, the
other outlines how they are performed (UT, 2003). Furthermore, with non-functional
requirements, the users can judge the system’s functions based on certain set criteria i.e. the
elements of NFR.
Consider the FURPS+ model where, elements such as performance, reliability, usability and
security are highlighted.

SYSTEM ANALYSIS AND DESIGN 4
 Performance – the overall system responsiveness to functions and user’s inputs.
 Reliability – the ability to provide consistent performance despite the changes in the
deployment platforms or user personnel.
 Usability – the ability to satisfy the user’s requirements including their envisioned system
characteristics.
 Security – the system ability to secure and block unauthorized access.
System qualities
These are the factors that dictate the system’s run-time characteristics and user experiences.
These factors determine the system’s ability to live up to the quality properties of a good
application i.e. the FURP+ model (CS2, 2014). In this case, the proposed project must possess
the following qualities:
 Interoperable – the system must be able to exchange data with other external systems
more so, those of the cloud facilities.
 Available and accessible – the time period that the system is functional should be
adequately extensive, a function that may be supported by the cloud resources in this
instance.
 Scalable – the Headspace project will handle extensive records thus will require facilities
that can accommodate the changes in payload size while having consistent performance
and functionality (Losavio & Chirinos, 2003).
System interface
A lot of emphases are needed on the system interface as they arguably interact with the end user.
In all, interfaces will form the crucial boundaries between different systems that exchange
information. This outcome is exhibited in interfaces such as those of the cloud solutions, the in-

SYSTEM ANALYSIS AND DESIGN 5
house system (SI), and those of the end user (UI) (Sommerville, 2004). Therefore, both
interfaces (SI and UI) must possess the following requirements:
 Clarity and conciseness – the entire purpose of the interface is to offer an interaction
platform for the end user. Therefore, the interface must be easy to access having simple
structures and operation guidelines.
 Familiarity – the interface must be intuitive i.e. it should be easily understood by the
users because of its familiar outlook.
 Responsiveness – First, the system must respond fast to the user’s request in order to
maintain the user’s attention. Moreover, it must offer rapid responses to all the user’s
requests (Mandel, 2012).
System constraints
These are the elements that will restrict the development process of the system either by delaying
its implementation process or by facilitating fewer functionalities of the final system (Ambler,
2014). In all, the Headspace project will face the following limitations:
 New operation infrastructure – the cloud resources will limit the user’s functionalities
more so due to its security.
 Online resource – furthermore, the cloud facilities may limit offline operations and
functionalities.
An analysis of the cloud-based solutions
In an event, the cloud solutions are adopted by the Headspace project, the users will have to
consider the security standards of the service provider since their resources will be hosted and
maintained by them. Moreover, the security of the access method i.e. the internet will come into
play where encryption and authentication procedures will be necessary. However, with good

SYSTEM ANALYSIS AND DESIGN 6
security measures, the cloud resources will improve the overall functionalities of the final system
(Lynch, 2016).
Strengths of cloud resources
 At first instance, the users will experience improved access and availability of computing
resources because they will be supported by an online infrastructure. Therefore, the user
will access the organization’s data so long as they have an internet connection.
 Furthermore, the users will have extended flexibility because their resources will be
hosted in multiple locations by the service provider. This outcome will not only increase
the availability of services but will also boost the scalability and redundancy functions.
 Finally, the total expense of developing and maintaining the system will be drastically
reduced because they will only perform end-user functions without the consideration of
the back end functionalities i.e. resource maintenance (networks, 2017).
Weaknesses
 Data’s security and privacy will always be at risk because the users will have to move
their sensitive data into foreign facilities. Furthermore, this information will be accessed
via public infrastructures i.e. the internet.
 Secondly, the subscriber will have minimal management functionalities which will affect
their overall control of the leased systems. Now, this limitation may facilitate the loss of
data as the user will not be able to track the traffic involved (Lynch, 2016).
Securing the data
Cloud-based solutions have many vulnerabilities and threats which affect the implementation of
the technology in information management. Moreover, the operation environment is never
adequately covered by the law which also limits the security and legal stipulations. Therefore,
the system at hand, having applied the cloud solution will have to implement its own security

SYSTEM ANALYSIS AND DESIGN 7
measures to safeguard the data used. For one, the communication channels (networks) will
require extensive encryption standards to protect their access. Moreover, the data used will also
require encryption standards such as AES which will only grant access to the verified members.
Finally, the system’s access will require proper monitoring and maintenance parameters such as
those of. firewalls and intrusion detection systems (Onlinetech, 2017).
SDLC methods (Software development life cycle)
In general, SDLC represents a framework that designs and develops software systems based on
specific pre-defined implementation stages. In essence, SDLC uses a project-like approach to
system development where specific phases are executed in a logical manner. An overview of the
framework will include six general phases i.e. system planning, analysis, design,
development/implementation, deployment and maintenance (Northcampus, 2017). Therefore,
while developing a software package, this procedure will be followed and on occasions will have
certain variations to improve the quality of the final solution. Now, these variations produce the
different approaches associated with the framework, which this report highlights below.
Predictive approach
This approach follows a conventional process that basis its functionalities on the assumption that
the system requirements will never change. However, before establishing this assumption, the
developer will highlight the system requirements including the user’s preferences and the
functionalities of the final system. From this initial determinations, the approach will then outline
a detailed plan for implementing the system which is thoroughly documented and adhered to
(Awad, 2005). Now, this plan is then followed sequentially where each stage of development is
implemented independently requiring specific developer’s sign-offs before proceeding to the

SYSTEM ANALYSIS AND DESIGN 8
subsequent stages. Therefore, during the SDLC process, the approach implements one stage at a
go.
Pros of the predictive method
 One, the approach is very accountable owing to its thorough documentation process.
Moreover, the developers and users can compare the final results with the initial
assumptions.
 Two, the method is simple and easy to use because a logical pattern is followed during
the implementation process.
 In addition to this, the method is cheaper as compared to other techniques owing to its
minimal resource requirements.
Cons
 The approach consumes a lot of time since all development stages are executed
independently and sequentially.
 Moreover, it does not respond to changes, an outcome that limits its application in
modern systems (Kannan, hajharia, & Verma, 2014).
Adaptive approach
According to system developers, the adaptive approach is an industrial response to the
limitations of the predictive method that lacks adaptability features. In essence, the predictive
method represents the traditional way of designing and developing systems, whereas the adaptive
method is the modern way of system engineering. To this end, the approach uses an agile
procedure to implement projects where a general assumption of uncertainty is given i.e. a room
for possible system variations is made available (Kannan, hajharia, & Verma, 2014). Therefore,
having established the requirements, the approach will divide the implementation process into

SYSTEM ANALYSIS AND DESIGN 9
certain stages that are then executed independently and simultaneously. In the end, these
independent phases are integrated to assemble the final solution of the system.
Pros of the method
 First and foremost, the approach is flexible a feature that facilitates the implementation of
agile solutions that have varying requirements.
 Secondly, it's time efficient owing to its ability to implement its SDLC stages
concurrently.
 Thirdly, its assembly process of the final solution uses iterative techniques which produce
many functional prototypes that are used to perfect the operations of the final system.
Cons
 Expensive, the adaptive approach requires a lot of resources to implement the final
solution. These resources include expertise for the various development phases.
Moreover, its ability to adapt to changes periodically increases the overall resource
requirement (Kannan, hajharia, & Verma, 2014).
Recommendation
Both methods are practical solutions for implementing projects however their suitability usually
depends on the requirements at hand. Now, the Headspace project requires a modern system that
will be able to integrate with cloud resources. Moreover, the same system should enhance user’s
usability by constantly meeting the non-functional requirements. Finally, the system should be
flexible to adapt to the changes of the healthcare industry i.e. changes in personnel and the
volume of information (Awad, 2005). From these requirements, the method of choice is the
adaptive approach as it facilitates the development of agile solutions having varying user
requirements. In addition to this, the adaptive approach will model the implementation process
based on the needs of the users i.e. their cost, resource and time requirements.

SYSTEM ANALYSIS AND DESIGN 10
Conclusion
There are many benefits of leasing cloud resources, for one, the overall cost of implementing and
maintaining the IT infrastructure is drastically reduced. Moreover, the technology increases the
availability of IT resources, an outcome that promotes the flexibility and scalability of software
systems. However, the technology also does possess various risks as facilitated by its security
limitations. In essence, the users (subscribers) have minimal control over the cloud resources
which raises the concern of data security and privacy. Nevertheless, these limitations can be
minimized by adopting proper security standards and good development procedures such as
those of agile system that respond to the immediate demands of the user or the environment.

SYSTEM ANALYSIS AND DESIGN 11
References
Ambler, S. (2014). Constraints: An Agile Introduction. Agile modelling, Retrieved 03 October,
2017, from: http://agilemodeling.com/artifacts/constraint.htm.
Awad, M. (2005). A Comparison between Agile and Traditional. Retrieved 03 October, 2017,
from: http://citeseerx.ist.psu.edu/viewdoc/download?
doi=10.1.1.464.6090&rep=rep1&type=pdf.
CS2. (2014). Software Requirements. Software Engineering notes, Retrieved 03 October, 2017,
from: http://www.inf.ed.ac.uk/teaching/courses/cs2/LectureNotes/CS2Ah/SoftEng/
se02.pdf.
Dailogic. (2017). Introduction to Cloud computing. White paper, Retrieved 03 October, 2017,
from: https://www.dialogic.com/~/media/products/docs/whitepapers/12023-cloud-
computing-wp.pdf.
Garg, A. (2015). CLOUD COMPUTING FOR THE FINANCIAL SERVICES INDUSTRY.
Retrieved 03 October, 2017, from:
http://www.sapient.com/content/dam/sapient/sapientglobalmarkets/pdf/thought-
leadership/GM_Cloud_Computing.pdf.
Kannan, V., hajharia, S., & Verma, S. (2014). Agile vs waterfall: A Comparative Analysis.
International Journal of Science, Engineering and Technology Research (IJSETR),
Retrieved 03 October, 2017, from: http://ijsetr.org/wp-content/uploads/2014/10/IJSETR-
VOL-3-ISSUE-10-2680-2686.pdf.
Losavio, F., & Chirinos, L. (2003). Quality Characteristics for Software Architecture. JOURNAL
OF OBJECT TECHNOLOGY, Retrieved 03 October, 2017, from:
http://www.jot.fm/issues/issue_2003_03/article2.pdf.
Lynch, J. (2016). What Are the Benefits and Drawbacks of Cloud Computing? Tech soup,
Retrieved 03 October, 2017, from: http://www.techsoup.org/support/articles-and-how-
tos/what-are-the-benefits-and-drawbacks-of-cloud-computing.
Mandel, T. (2012). The Golden Rules of User Interface Design. The Elements of User Interface
Design, Retrieved 03 October, 2017, from:
http://theomandel.com/wp-content/uploads/2012/07/Mandel-GoldenRules.pdf.
networks, S. (2017). Advantages and Disadvantages of Cloud Computing. Stratosphere
networks, Retrieved 03 October, 2017, from:
https://www.stratospherenetworks.com/advantages-and-disadvantages-of-cloud.html.
Northcampus. (2017). System Development Life Cycle. Retrieved 03 October, 2017, from:
http://northcampus.uok.edu.in/downloads/20161127213336188.pdf.
Onlinetech. (2017). Top 5 Tips For Cloud Computing Security. Online tech, Retrieved 03
October, 2017, from: http://www.onlinetech.com/resources/references/top-5-tips-for-
cloud-computing-security.

SYSTEM ANALYSIS AND DESIGN 12
Sommerville, I. (2004). User interface design. Software Engineering, Retrieved 03 October,
2017, from: https://ifs.host.cs.st-andrews.ac.uk/Books/SE7/Presentations/PDF/ch16.pdf.
UT, U. o. (2003). Non-Functional Requirements (NFRs). Department of Computer Science,
Retrieved 03 October, 2017, from:
http://www.cs.toronto.edu/~campbell/340/05w/utm/lectures/18-NFRs4-up.pdf.