Review Of Cloud Solutions And SDLC Approach Essay

Question:

Review of Benefits and Disadvantages of Cloud Solutions and SDLC Approach?

Answer:

Introduction:

The “My Health Record” has been the initiative by “Commonwealth Government” in Australia. It has been providing people with the integrated platform through online. This has helped in recording, viewing, modifying and handling the information regarding health issues.

The project of “My Health Record” has been considering solutions to be “cloud based”. This has been required to be investigated.

The report has discussed various non-functional requirements, review of benefits and disadvantages of cloud solutions and SDLC approach.

The non-functional requirements:

The “cloud-based” refers to the servers, resources and applications made available on demand of the users through online from the servers of the cloud computing providers. The non-functional requirements are the qualities expected to be possessed by a system. It also considers the constraints within which the system operates (Botta et al., 2016). Used to the FURPS+ acronym as the reference, the non-functional requirements have been sometimes called as the “ilities”. This is because it might end with the term “ility” like reliability, maintainability, availability and so on.

Moving of “My Health Record” to cloud has various advantages like decreasing of capital costs, operating costs with increase in support for mobile and remote staffs. It also supports the infrastructure flexibility. As implemented appropriately, the cloud services could change the corporate view of “My Health Record’s” IT as center of cost to the competitive advantage. This would able to affect positively the top-line revenue.

The project should assure that the provider of cloud service delivers the services that the company needs for running the business. This has been critical for effective migration of all the IT services to cloud. In order to ensure the proper choice, some attributes of the non-functional requirements are to be followed while evaluating the service provider (Buyya, Vecchiola & Selvi, 2013).

Usability: This has been different depending upon the identification of the clients. The clients might be the architects or developers, business rulers or the IT operations. In every case the company requires to consider the easy usage of the software. They must also consider how well the interfaces have been designed. The IT would be no longer secret in the company. Rather, the engaging systems have been out there for the external world. The effective designing of the systems become more significant than before.

Reliability: The business-critical services have been very complicated. The business at many times could not afford to possess their services of IT going down due to an outrage impacting the business effectively. Missed calls, e-mails, unshared documents and delayed quotes could affect the top-line revue with the bottom-line costs (Toosi, Calheiros & Buyya, 2014). The reliability has been concerned about decreasing the probability of the service outrage. The company should seek for the service providers that possess the least history of cloud outages.

Performance: It deals with the method how well the cloud architecture has been suited for supporting the workloads deployed over it as the workloads increase.

Security: One of the primary disadvantages to move to external cloud has been the poor security. As the service provider of cloud does not possess the necessary and proper security measures, the security gets compromised (Wei et al., 2014). Hence, the cloud providers should be searched for who acquires multi-factor authentication created in their service along with full encryption at-rest and in-transit for content. Here, the policies of centralized security to control the local or remote servers have also been important.

As the software interfaces are considered, the reason of the linking between the system and the “Google Big Table” has been to put away and fetch information. The reason behind the connection between the mobile devices and systems has been to deliver the mobile access to that system. Apart from this, the system has been integrated to social media networks like Twitter and Facebook.

The interfacing of the system with the users has been of two kinds. Firstly, in the system administrator interface the administrator has been privileged with permissions for accessing the overall system (Tebaa & Hajji, 2014). In the organization administrator interface, the administrators get permission for modifying and accessing the overall data belonging to “My Health Record” they administrate. As per as the member interface is concerned, the members are able to observe and update their personal data and the profiles and the public pages of the company they were not belonging to. As the application of the project would be working over the “Google App Engine” there has been no existence of any particular hardware interface.

Thus the non-functional requirements must consider in terms of those qualities the company want from the IT system along with the constraints they have been doing. The decision for moving into the cloud has been adding in many ways the constraints they have been doing (Chen et al., 2015). The company would not have the overall free reign to perform whatever they need if they go for off-premise cloud. This cloud has been operated by vendors but had to align the service levels provided by them.

Review of cloud-based solution:

The industry experts have believed that the trend of cloud computing would continue to grow and develop further. As this technology has been undoubtedly advantageous for companies of all sizes, it has not been without downsides. The various strengths and weaknesses regarding the implementation of cloud-computing have been described below (Gai et al., 2016).

Strengths:

Cost efficiency:

Cloud computing has been likely the most cost effective strategy to utilize, keep up and update. Conventional desktop software has been costing organizations a lot in terms of economy. Including the licensing charges for various clients can turn out to be extremely costly for the establishment. The cloud, then again, is accessible at considerably less expensive rates and thus, can altogether bring down the organization's IT costs (Rittinghouse & Ransome, 2016). Also, there are numerous one-time-installments, pay-as-you-go and other adaptable choices accessible, which make it exceptionally sensible for the organization being referred to.

Practically Unlimited Storage:

Putting away data in the cloud provides practically boundless capacity limit. Thus, “My Health Record” requires more need to stress over coming up short on storage room or expanding the present storage room accessibility.

Reinforcement and Recovery:

Since all the information is put away in the cloud, backing it up and reestablishing the same is significantly less demanding than putting away the same over physical devices. Moreover, most cloud specialist organizations are typically sufficiently equipped to deal with recuperation of data (Hwang, Dongarra & Fox, 2013).

Thus, this makes the whole procedure of reinforcement and recuperation substantially more straightforward than other conventional strategies for information storage.

Programmed Software Integration:

In cloud, the software reconciliation is normally something that happens naturally. This implies that the company does not have to take extra endeavors to tweak and incorporate the applications according to the inclinations (Leymann et al., 2014).

Simple Access to Information:

When the individuals enroll themselves in the cloud, they can get to the data from anyplace, where there is an Internet. This advantageous element gives the chance to move past time zone and geographic area issues.

Quick Deployment:

In conclusion and above all, cloud computing gives the upside of quick deploying. When anyone decides on this strategy for working, y the whole framework can be completely functional in a matter of a couple of minutes. Obviously, the measure of time taken here will rely on upon the exact type of technology needed for the business (Jula, Sundararajan & Othman, 2014).

Weaknesses:

Technical Issues:

Despite the fact the data and information on cloud can be gotten to at whatever time and from anyplace, there have been times when this framework can have some genuine brokenness. The company ought to know about the way that this innovation is constantly inclined to blackouts and other technological issues.

Security in Cloud:

The other significant issue while in the cloud is that of the security issues. Before receiving this innovation, the company ought to realize that they have to surrender all the sensitive data to an outsider service provider of cloud (Leymann et al., 2014). This could possibly put the organization to incredible hazard. Henceforth, they have to ensure that they pick the most dependable specialist organization, who would keep their data absolutely secure.

Inclined to Attack:

Putting away data in the cloud could make the organization powerless against outside hacking attacks and dangers.

The SDLC approach:

The “Systems Development Life Cycle” or the “Software Development Life Cycle” or SDLC has been the framework defining tasks to be done at every step in the cloud computing process. Two types of SDLC are to be discussed here.

The predictive SDLC:

The most prominent and surely understood predictive approach is the waterfall method. The term waterfall has turned into the token predictive strategy about debating the benefits of predictive versus adaptive (Zhang et al., 2014). The quality of a predictive approach is its emphasis on structure and keeping up a comprehensive vision of the resolution space. Its shortcoming is the unyielding thoroughness. However there is no reason not to reap what is required from these systems with an eye for general efficiencies.

The adaptive SDLC:

By and by, there are more than adequate in genuine cases to demonstrate that the adaptive procedures do work in the "huge." Adaptive SDLC run from the Rapid Application Development or RAD, that essentially prototypes items into reality, to Scrum, with its overwhelming dependence on group collaboration (Kalloniatis et al., 2014). This continues up to XP, which takes adaptive to the outrageous with its adaptation of combined programming and consistent surveys. These lighter and more agile system make cloud computing rapidly. Yet they do have a tendency to be somewhat strategic, frequently missing key strategic scopes.

Recommendation to the SDLC for the current project:

For the given project the Adaptive methodology is suggested. The adaptive methodology is also known as the agile methodology. This is because they follow “Agile Manifesto” which is a collection of central principles supporting iterative development. The cloud SDLC is flexible in utilizing the Agile SDLC using “IBM Rational Unified Process or the SCRUM”. These have been designed as an iterative approach for developing and quick deployment life-cycles. For bringing the operations on the similar table, the DevOps could be used that has to be particularized in the framework of cloud SDLC.

Conclusion:

Like everything the cloud computing also contains certain pros and cons. While this innovation could prove a great asset for “My Health Record”, it could also harm as it is misused or not understood properly. In short, the data as stored in big data center all over the globe, it could turn as the target of hackers or not used properly by the employees of providers of cloud. The professionals of “My Health Record” need to assure that the cloud computing never become any service used by few users. Like other innovations in this capitalized world, the cloud computing has been the first to be commercialized. Then its pros and cons are taken into the consideration.

References:

Botta, A., De Donato, W., Persico, V., & Pescap?, A. (2016). Integration of cloud computing and internet of things: a survey. Future Generation Computer Systems, 56, 684-700.

Buyya, R., Vecchiola, C., & Selvi, S. T. (2013). Mastering cloud computing: foundations and applications programming. Newnes.

Chen, M., Zhang, Y., Hu, L., Taleb, T., & Sheng, Z. (2015). Cloud-based wireless network: Virtualized, reconfigurable, smart wireless network to enable 5G technologies. Mobile Networks and Applications, 20(6), 704-712.

Choi, C., Choi, J., & Kim, P. (2014). Ontology-based access control model for security policy reasoning in cloud computing. The Journal of Supercomputing, 67(3), 711-722.

Gai, K., Qiu, M., Zhao, H., Tao, L., & Zong, Z. (2016). Dynamic energy-aware cloudlet-based mobile cloud computing model for green computing. Journal of Network and Computer Applications, 59, 46-54.

Grewal, R. K., & Pateriya, P. K. (2013). A rule-based approach for effective resource provisioning in hybrid cloud environment. In New Paradigms in Internet Computing (pp. 41-57). Springer Berlin Heidelberg.

Hu, F., Hao, Q., & Bao, K. (2014). A survey on software-defined network and openflow: From concept to implementation. IEEE Communications Surveys & Tutorials, 16(4), 2181-2206.

Hwang, K., Dongarra, J., & Fox, G. C. (2013). Distributed and cloud computing: from parallel processing to the internet of things. Morgan Kaufmann.

Jula, A., Sundararajan, E., & Othman, Z. (2014). Cloud computing service composition: A systematic literature review. Expert Systems with Applications, 41(8), 3809-3824.

Kalloniatis, C., Mouratidis, H., Vassilis, M., Islam, S., Gritzalis, S., & Kavakli, E. (2014). Towards the design of secure and privacy-oriented information systems in the cloud: Identifying the major concepts. Computer Standards & Interfaces, 36(4), 759-775.

Leymann, C. F. F., Retter, R., Schupeck, W., & Arbitter, P. (2014). Cloud computing patterns. Springer, Wien. doi, 10, 978-3.

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.

Li, Q., Wang, Z. Y., Li, W. H., Li, J., Wang, C., & Du, R. Y. (2013). Applications integration in a hybrid cloud computing environment: Modelling and platform. Enterprise Information Systems, 7(3), 237-271.

Lu, P., Sun, Q., Wu, K., & Zhu, Z. (2015). Distributed online hybrid cloud management for profit-driven multimedia cloud computing. IEEE Transactions on Multimedia, 17(8), 1297-1308.

Wei, L., Zhu, H., Cao, Z., Dong, X., Jia, W., Chen, Y., & Vasilakos, A. V. (2014). Security and privacy for storage and computation in cloud computing. Information Sciences, 258, 371-386.

Zhang, H., Jiang, G., Yoshihira, K., & Chen, H. (2014). Proactive workload management in hybrid cloud computing. IEEE Transactions on Network and Service Management, 11(1), 90-100.

How to cite this essay: