Cloud Based Solutions and SDLC

Questions: 1. Non-Functional Requirements? 2. Review of Cloud Based Solution? 3. SDLC Approach? 4. Presentation, Writing style, Grammer and References? Answers: Introduction 1. Since the inception of cloud-based solutions, the information technology industry has drastically changed its outlook on service delivery. Today, cloud computing has changed how data is managed more so, in consumptions and scaling capabilities where owners now optimise on the available resources through leased infrastructure (cloud solutions). In essence, organisations like Commonwealth governments can now deliver services at minimal costs due to the affordability offered by cloud-based solutions. Moreover, these solutions are seen across all technological platforms seen today as highlighted by Gartner Inc. study that saw more 60 percent of all online processes being conducted through cloud-based solutions. Nevertheless, this widespread application necessitates the existing variations in cloud solutions where versatility is developed through the development and implementation process. This outlook has established the different development environments which are seen today to cater for the users needs. Now, this paper will highlight these development options as used in cloud solutions while maintaining a close relation with the different elements of software development. These elements will entail the solutions usability, reliability, performance and security. Moreover, this analysis will categorise cloud computing based on two software development options/models i.e. adaptive and predictive. Non-functional requirements The proposed health system will be used by a wide range of users, from medical practitioners to departmental officials. There is a need to understand their requirements in order to facilitate the functionalities of the system. A user-centred approach will integrate the needs for a high usability system with the overall performance. Moreover, the reliability of the project will depend on the level of satisfaction of the users who accomplish their tasks inconvenient time. Therefore, cognitive recognition and high usability are factors to consider when choosing the development approach i.e. either predictive of adaptive. In the end, the approach chosen should enhance, these attributes i.e. performance, usability and reliability while meeting the basic needs of security (Kathuria, 2011). These non-functional requirements are highlighted while evaluating both development methods. SDLC and Cloud Solutions First, SDLC i.e. software development life cycle, a mantra or technique that defines the procedures and stages of software development. These stages will include system research, design and deployment among many other processes (Kathuria, 2011). On the other hand, cloud solutions, more importantly, cloud computing offers different perceptions to system/software implementation by introducing a refined way to supporting the underlying physical and software infrastructure. This refined method offers more flexibility, scalability and robustness. These benefits offer business many other extended advantages, however, the extent and variation depend on the development process which now links cloud-based solutions with SDLC (Velagapudi, 2012). Analysis of Predictive and Adaptive SDLC As the name suggests, a presumed procedure is used to develop the system this outcome is made possible by the developers who know and understand the stages leading up to the intended solution. Therefore, a predicted procedure is used to develop the solution with very minimal alterations. Consider the project at hand, My Health Project, the developers would have all the parameters needed including things like professionals, implementation resources, personnel files and system priorities (MSB, 2011). Furthermore, a logical and sequential process would be followed to achieve the final objective again with minimal interruptions or stage overlaps. Waterfall design model is a common design method that follows predictive SDLC procedures. In it, the method will follow certain notable features including the absolute completion of a phase before proceeding to the next. A typical procedure will have six steps comprising of initiation of project, planning, analysing, design, building, and testing and deployment. 2. The advantages of Predictive SDLC Simple and easy to use, particularly because all the defining elements are known and can be manipulated to meet the system objectives. Predictive SDLC approach is very safe because the overall outcomes are defined before the start of the design process, regardless of the development personnel. This approach requires a strict documentation policy to track the development process, this outcome makes it easier to use increasing its overall reliability and efficiency. Moreover, the users are always reassured in terms of system quality and product visibility since results are always seen at the end of a development stage (phase). In the end, this increases the system performance as the developers collaborate with the needs of the end user (Mikoluk, 2013). Disadvantages Predictive SDLC is very stringent on the development procedure which makes it rigid and extremely inflexible to system changes. In fact, slight design changes can alter the entire development process. The performance will depend on the accuracy of the predicted parameters and for a cloud based solution, this can change affecting the system performance. Furthermore, the approach depends on the completion of the different development phases which can slow a design project if a certain phase stalls. Finally, this development method will only produce a working system at the end of the development cycle which limits its application especially in long term projects (Gupta, 2014). Adaptive SDLC approach An approach that accounts for the different technological and development changes, in essence, an adaptive approach will acknowledge the possibility of changes and put in place procedures to cater for system requirements and their variations. For instance, the project at hand may change the design personnel, priorities or even the data selected to have a wider scope of medical professionals. Furthermore, when integrated with cloud computing the developers may desire to change the cloud structure and architecture. These changes can be accommodated by an adaptive SDLC method (MSB, 2011). Nevertheless, this approach will break down a project into different sections, with each section designated with a specific task. Through this approach, the unforeseeable changes are accommodated. Furthermore, these design sections are then combined in an iterative process to produce the final system. The most notable method that follows this development structure is the agile method which uses an iterative technique to design and implement Softwares. The agile method will have different development stages which are run concurrently to achieve a common goal. Moreover, the system obtained depends on the priority given which means different solutions can be achieved using the same development parameters 3. The Advantages of adaptive SDLC approach First, adaptive methods are very flexible as their design procedures anticipate changes which essentially meets the needs of the modern day systems. Efficiency, in terms of saving resources such as time and money which again is determined by the immediate needs. Improved usability since the user determines the interfaces and design chosen. Furthermore, the end user is also involved at an early stage of system development. This advanced involvement and usability increase system performance which produces an effective and efficient product. Finally, it enhances collaboration amongst developers who design different system modules to produces a common, overall project. This outlook enhances the properties of the systems including the security protocols (Mikoluk, 2013). An adaptive approach lacks a presumed implementation procedure which makes it difficult to determine the dates of system delivery. Moreover, its adaptive procedure limits business procedures that desire to critically outline the system parameters in a defined setup such as a table. Finally, it requires highly trained personnel. 4. Recommendations to My Health Record project First, the requirement for the project at hand, a cloud solution that offers access to health records with all the necessary (modern) features i.e. top notch security, access (authentication and authorization for the users), and optimal non-functional requirements. These requirements highlight a versatile system that requires multiple levels of adjustments in the form of customization. Furthermore, remember, predictive methods are traditional ways of system development. In fact, at their time of development, little design variables were known which always led to linear procedures. However, adaptive methods are modern and also are responsible for the modern systems (Kommalapati Zack, 2011). Cloud-based solution require a versatile approach where room for change is made available for elements such as system architecture and design parameters. Moreover, the project at hand may require changes in the future e.g. additional departments or changes in the development environment to cater for technological change. These outcomes can be easily met using an adaptive approach. Furthermore, with predictive methods, the focus is always on the functional requirements i.e. storage, system capabilities, and bandwidth etc, with minimal considerations on the users needs. In addition to this, they are rigid which exposes them to many security threats. Adaptive methods, on the other hand, balance the two requirements (functional and non-functional) to suit the needs of the end users (Kommalapati Zack, 2011). If these benefits are not enough, consider cloud computing as a whole, a technological innovation that banks on flexibility and scalability. Through these features, it has increased information movement across the internet by increasing its access. Furthermore, it has reduced the cost of system development by lowering the implementation costs as well as the development time. These outcomes can only be met by an efficient method that integrates different variables to optimise on the resources offered by the development environments. This outlook necessitates the need for an adaptive SDLC method to meet the needs of the project while capitalising on the efficiency of the development cycle (Kathuria, 2011). Conclusion Cloud-based solutions offer a number of advantages particularly in system development which as stated above is the sole deployment environment. Through cloud computing, this project aims to incorporate the benefits of digital media (IT) with record keeping to have an optimal system that has a wider scope and demographic. Through an adaptive approach, this project will achieve its objectives while maintaining the modern principles of system development such as modern encryption methods. Furthermore, the system designed will have improved functionalities including system reliance, usability, performance, flexibility and scalability. These non-functional aspects are paramount for system success as they improve the overall system functionality. References Feher. D. (2013). What are the pros and cons of the waterfall and agile/scrum project management approach? Quora. Retrieved 24 January, 2017, from: https://www.quora.com/What-are-the-pros-and-cons-of-the-waterfall-and-agile-scrum-project-management-approach 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 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 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/ Sen. J. (2012). Security and privacy issues in cloud computing. Innovation labs, Tata consultancy services limited. Retrieved 24 January, 2017, from: https://pdfs.semanticscholar.org/4dc3/70d253020947a8e66b701e12dd0233161229.pdf Velagapudi. M. (2012). SDLC for Cloud Computing How Is It Different From the Traditional SDLC? Retrieved 24 January, 2017, from: https://bootstraptoday.wordpress.com/2012/02/06/sdlc-for-cloud-computing-how-is-it-different-from-the-traditional-sdlc/