Isy00243 System Analysis And Design-Cloud Assessment Answers

Answer:

Cloud solutions offer subscription-based computer resources to users, based on their immediate and future needs. Essentially, these subscribers will lease resource over the internet from service providers who owns computation resources such as storage, networking equipment and applications (Baylor, 2013). Furthermore, since these resources are accessed using online platforms, they are always available based on the connectivity of the said digital environments. This outcome increases their benefits and conveniences, which in most cases is usually enhanced flexibility and mobility. Moreover, because customers only pay for the resources they need, cloud solutions are cost effective which further increases their application and practicality.

In the project, the Commonwealth Government seeks to develop a health system to support its functionalities where among many other objectives, it hopes to increase the overall availability of information. In essence, health practitioners and stakeholders will have increased access to the fields’ information such as patients’ records. These objectives have led to the proposed solution that integrates a modern information system with cloud solutions. This report analysis cloud solutions a key service and resource to system development and maintenance. Moreover, it outlines the non-functional requirements needed for an effective solution. Finally, it highlights the approaches that can be used to enact the solution based on the outlined requirements.

The non-functional requirements

In the proposal, a vague description is given on the need for security where data ownership should be clearly outlined. Now, non-functional requirements depict the properties or attributes that affect the operations and functionality of the developed system. These properties determine the interaction with the end user who in this project are a wide range of people, from doctors to departmental employees (Fernández-Cardeñosa, Torre-Díez & López-Coronado, 2015). To meet these requirements, a user-centred approach is needed to understand the requirements of these users. Moreover, the same approach will provide a fundamental framework for the integration with the cloud solutions.

The requirements:

1.    User qualities: usability– the overall ability of the health system to meet the desires of the users so as to offer a satisfactory service. Therefore, the product developed should be intuitive, simple and globalised in functions (Ryerson, 2017).
2.    Run-time qualities: Performance – a convenient system that responds to the actions of the user and the affiliated systems. In essence, it outlines the responsiveness where actions are immediately executed.

Reliability – a robust requirement, where despite the conditions i.e. platform, threats and infrastructure etc. the system is able to remain operational.

Security – other than dictating the ownership of data, this requirement highlights the overall ability to avoid unauthorised system modifications (Microsoft, 2017).

Review of cloud solutions

Cloud-based solutions according to ICT experts are the next generation of the internet technology, as they outline the provision of resources through internet systems and connections (Harding, 2017). At an application and functional level, this outcome makes a lot of sense as they optimise IT resources which in the most case tend to be very expensive. Now, cloud-based solutions come in layered formats having on-demands and flexible services which the project needs. This project (My Health Record) requires a wide range of functionalities where an independent system will be developed and linked with a cloud solution. Therefore, on the platform or service model used, accessibility and control (for security) should be considered. This can be met by IaaS (Infrastructure as a service) (Taylor, 2000).

Strengths

1.    Cost efficiency – cloud solutions optimise resources where minimal costs are considered for the set-up and maintenance of in-house resources.
2.    Mobility and flexibility – the proposed system will be used by many users across the country, who based on its integration with the cloud solution will be able to access its functionalities all the time using online platforms (Level cloud, 2017).
3.    Reliability – service providers will have multiple IT infrastructures which improve redundancy outcomes enhancing the resilience of the solutions.
4.    Strategic Edge – incorporating cloud solutions into an organisation, facilitates future development programs as the service offered are dynamic and can adjust with time.

Weaknesses

1.    Security – the top most concern for cloud solutions, as information is stored in unknown locations and is handled by third party members. Moreover, the Internet is used to transmit the said information and based on its security threats presents substantial risks.
2.    Loss of control – it’s sometimes hard for subscribers (e.g. the projects at hand) to track their resources as they are continuously moved from one IT resource to another.
3.    Downtime – owing to the infrastructure of the service provider, the system can be overwhelmed with requests and services leading to delays and other technical hitches.
4.    Vendor lock-in – consider the system at hand, owing to its size the organisation may find its difficult to switch its provider due to the procedures involved and the resources used. So, users can be forced to stick to a service provider regardless of the quality of service provided (Ward, 2017).

SDLC Approach

Software/system development life cycle outlines procedures or the processes that are used to develop systems or applications. To meet this objective, SDLC holds several general development objectives: One, it enhances and facilitates high-quality systems through adequate development procedures. Two, it increases the users’ system control which in itself enhances management. Three, it ensures users ‘attain maximum output out of the developed systems i.e. maximum productivity is achieved (Bender RBT Inc., 2003). In meeting these objectives, SDLC approaches will vary their design methods based on the requirements at hand. This consideration means that SDLC approaches can change based on the system priorities, management and even tracking requirements. For instance, data ownership is a priority in this project thus should serve a key determinant of the method chosen (Cerritos, 2011).

Two methods are discussed for the proposed system: predictive and adaptive SDLC.

1.    Predictive SDLC approach

True to the definition of the name, this method uses presumed and pre-determined procedures to develop solutions. Therefore, all the steps and stages of implementation are predicted before the start of the project through a strategic planning phase that outlines all the variables/parameters involved. So, for it to be effective, the system requirements must be predictable for the developers to highlight them and optimise them. Moreover, a consistent and sequential development procedure is used having zero interruptions e.g. overlaps of phases and development stages (MSB, 2011). Consider the diagram below where the Waterfall model, a good example of the predictive approach is illustrated.

This method will use sequential phases that flow in a logical manner i.e. each development stage is completed before moving on to the next. Moreover, once completed, a phase is never revisited for development (Cerritos, 2011).

Pros of Predictive methods

1.    They have a complete outline of the steps and development procedures thus are easy to use.
2.    Furthermore, their strategic outline requires strict documentation guidelines which promote accountability.
3.    Moreover, it’s easier to estimate the development timelines as all the requirements including development parameters are known (Mikoluk, 2013).
4.    It’s also easier to define system requirements such as security since the resources available are known.

Cons

1.    Highly inflexible owing to the presumed conditions that must remain constant throughout the process.
2.    It also tends to have a high dependency on the development stages where each phase is determined by the subsequent phase.
3.    Time-consuming owing to the sequential development procedures i.e.no concurrent stage development.
4.    Finally, operational systems are only seen at the end of the development process which makes testing impossible (Gupta, 2014).

The ability of a system development process to adapt to an existing condition characterises this approach. Adaptive methods are a modern outlook on system design where the developers are given room for change based on the varying requirements as well as priorities. Unlike the predictive approach, this method does not assume the conditions (stages and variable) instead the development process remains open for new entries. Therefore, in case new demands are given in the development cycle, the process does not stop but it re-adjusts to fit the new demands. This functionality is enabled by the design structure of the method where the development cycle is split into several sections, each having a unique function (MSB, 2011).

These sections can be based on the functional or non-function requirements where specific task are executed to meet these functionalities. Moreover, these sections are run concurrently i.e. unlike predictive methods where each stage is executed sequentially, all development sections are conducted at once and later on assemble into one system. To accomplish this assembly objective, an iterative process or technique is used where the process of combining the development process is continuously repeated until an optimised solution is achieved. This iterative technique yields several solutions known as prototypes which can be tested for different functionalities and user requirements boosting the overall performance of the system. Now, the diagram below highlights and example of this approach i.e. the agile method that uses several development sections and an iterative assembly technique.

 Pros of the approach

1.    Flexibility where changes in requirements are easily accommodated into the development process to meet the desired objectives.
2.    Resource optimisation mostly time where the concurrent stage execution minimises the development process.
3.    Adaptive methods are user centred which enhances the usability and performance of the systems as the user requirements are known.
4.    Reliable approach as all the development requirements are always met (Stoica, Mircea, & Ghilic-Micu, 2013).

 Cons

1.    Its biggest fault is the inability to predict the actual development timelines because of the allowances are given for changes in the development requirements.
2.    Secondly, it requires highly trained and experienced expertise which tends to make it a little bit expensive (Utexas, 2017).

Recommendation for the project

A predictive approach would not be fitted for the project, for one it's only beneficial functionality would be the stringent documentation process which many long-term projects require for accountability measures. However, this aspect of system development can be incorporated into any other approach more so, modern systems that have varying requirements. Nevertheless, the system at hand has extensive requirements as a result of its application environment where a wide range of people (users) are considered. Therefore, inevitably the system design is set to change on several occasions. Moreover, the said system must fulfil the user requirements based on the non-functional requirements outlined before. These aspects of system design require agile development methods so as to adapt the solutions developed based on the immediate needs. Finally, the system needs to link with the cloud solution, which is a technology in its infancy stages thus has regular technological changes (Kathuria, 2011).

An adaptive approach will meet all these requirements based on it development models. For one, the development cycles led by the iterative techniques will split the project based on the requirements given. Therefore, after developing the final solutions, the developers can tune the system to fit the criteria needed, for instance, some prototypes can focus on a health system meant for medical practitioners and other on departmental officials. In the end, a final solution having attributes for both prototype systems is developed which satisfies all parties’ involved thus boosting usability, performance and reliability. Furthermore, the same process can be used to tune the security protocols i.e. authentication and access control based on the data ownership policy outlined. Finally, the same approach will meet any demand set by cloud resources as it can adjust its operational parameters (Kommalapati & Zack, 2011).

Conclusion

Cloud Solutions offer many services and benefits that boost business performance because of their ability to optimise resources. However, it’s important for organisations to highlight their requirements before embarking on an implementation process. My Health Record is in desperate need for cloud resources as they will enhance its availability and accessibility to the users. Moreover, it will help manage resources and improve the disaster recovery procedures i.e. back-up which are essentials for systems using large volumes of data. Now, in order to meet its objective, the Commonwealth Government must implement a versatile system that meets the requirements of the users. These users have varying preferences which necessitate an agile approach, an approach outlined in this report. If adopted, the adaptive approach would offer the best solution as it’s adjustable to meet any development changes which are common with long-term projects.

 References

Baylor. (2013). Cloud storage. Non-profit Technology Collaboration. Retrieved 17 April, 2017, from: https://www.baylor.edu/business/mis/nonprofits/doc.php/197132.pdf

Cerritos. (2011). Chapter 8 –Approaches to System Development. Systems Analysis and Design in a Changing World, 6(1). Retrieved 20 May, 2017, from: https://web.cerritos.edu/dwhitney/SitePages/CIS201/LectureNotesOnTalonNet/Chapter08Lecture.pdf

Fernández-Cardeñosa. G, Torre-Díez. I & López-Coronado. M. (2015). Analysis of cloud

-based solutions on EHRs systems in different scenarios. Department of Signal Theory and Communications, University of Valladolid. Retrieved 20 May, 2017, from: https://netgna.it.ubi.pt/files/Cloud%20computing%20EHRs_JOMS_FV.pdf

Harding. N. (2017). Key aspects of cloud computing services. Tech target. Retrieved 20 May, 2017, from: https://searchitchannel.techtarget.com/tip/Key-aspects-of-cloud-computing-services. 

Gupta. N. (2014). Project Management Life Cycle-Iterative & Adaptive. IZenBridge. Retrieved 24 January, 2017, from: https://www.izenbridge.com/blog/project-management-life-cycle-iterative-adaptive/ 

Kathuria. K. (2011). Software Development Lifecycle and Cloud Computing. Scribd. Retrieved 24 January, 2017, from: https://www.scribd.com/document/37345932/SDLC-and-Cloud-Computing

Kommalapati. H & Zack. W. H. (2011). The SaaS Development Lifecycle. InfoQ. Retrieved 24 January, 2017, from: https://www.infoq.com/articles/SaaS-Lifecycle

Level cloud. (2017). Advantages and Disadvantages of Cloud Computing. Retrieved 22 May, 2017, from: https://www.levelcloud.net/why-levelcloud/cloud-education-center/advantages-and-disadvantages-of-cloud-computing/ 

McCombs school of business (MSB). (2011). the System Development Life Cycle. Retrieved 24 January, 2017, from: https://utexas.instructure.com/courses/1166782/files/38198507/download

Stoica. M, Mircea. M & Ghilic-Micu. (2013). Software Development: Agile vs. Traditional. Informatica Economic? 17(4). Retrieved 20 May, 2017, from: https://www.revistaie.ase.ro/content/68/06%20-%20Stoica,%20Mircea,%20Ghilic.pdf

Taylor. A. (2000). Design Constraints and Limitations. Introduction. Retrieved 22 May, 2017, from: https://www.cse.msu.edu/~cse470/F97/Projects/F00/F00-Cheng/diagnostics/diagnostics2/web/documents/designdoc/document/node5.html. 

Mikoluk. K. (2013). Agile vs. Waterfall: Evaluating The Pros and Cons. Udemy blog. Retrieved 24 January, 2017, from: https://blog.udemy.com/agile-vs-waterfall/

Taylor. A. (2000). Design Constraints and Limitations. Introduction. Retrieved 22 May, 2017, from: https://www.cse.msu.edu/~cse470/F97/Projects/F00/F00-Cheng/diagnostics/diagnostics2/web/documents/designdoc/document/node5.html. 

Utexas. (2017). The System Development Life Cycle. Retrieved 19 May, 2017, from: https://utexas.instructure.com/courses/1166782/files/38198507.