Dynamics of Information Technology

Question: Discuss about the Dynamics of Information Technology. Answer: Introduction Cloud computing has drastically shifted the dynamics of information technology, more so on how information is managed, consumed and scaled by those who own it. Since its inception, cloud computing seems to have had substantial benefits in business because it allows organisations and individuals to deliver services that would otherwise be unaffordable. In fact, consider the analysis done by Gartner Inc. in 2013 that saw cloud-based services take up to 60 percent of all online earnings. However, these benefits are tailored differently based on the development procedures as well as deployment options/models. This paper will review the different development environments used to develop cloud-based solutions. Moreover, the analysis will be done in reference to the different aspects of software development i.e. their usability, performance, security and the system itself among many others. Furthermore, we will focus on two main approaches to software development, that is; predictive and ad aptive software/system development life cycle (SDLC). Cloud based solutions and SDLC SDLC defines the stages or steps used to develop a software or system, its basically a framework that designers use to develop a system (Kathuria, 2011). Now, cloud computing offers a different abstract of the underlying system hardware making it flexible, scalable and more robust (Velagapudi, 2012). The integration between these concepts provides organisations and businesses with better options to develop their systems. However, these options also depend on an organisations needs and resource availability. Lets discuss these options by analysing two commonly used methods of system development i.e. predictive and adaptive SDLC on cloud-based solutions. Predictive vs. Adaptive SDLC While following a predictive approach to a system design, a project assumes that all the steps leading up to the solution are known and can be predicted. Therefore, the solution adopted is developed based on these predicted steps. For instance, in the case study of Headspace organisation, we would assume all the parameter relating to the project are known and will never change e.g. personnel files (young person), professionals and even priorities (MSB, 2011). In essence, a logical or sequential process is followed with little or no overlap considered, either at the start or at the finish. A common model or method that follows this approach is the waterfall design method. In waterfall, the notable feature is the completion of each phase before proceeding to the next one. Typically, its design will follow a sequential procedure having six steps: Initiation, project planning, analysis, the design of specifications, building and testing, and finally, deployment (Feher, 2013). This sequen tial flow has its own advantages and disadvantages on the features and usability of a system as detailed below. Advantages of Predictive SDLC First, predictive SDLC yield systems that are easy to use because all the defining parameters are set to suit the overall systems and its objectives. Moreover, this approach tends to be more secure since the outcomes are planned prior to the start of the project, regardless of the people involved. Furthermore, this approach calls for stringent documentation which makes it easier to track a projects progress, which again makes it reliable and efficient to use. In addition to this, a predictive approach in system development reassures one of system quality and visibility because the results are always seen at the end of each phase. In the end, this makes it easier to communicate to designers and users about the project progress especially the systems delivery date (Mikoluk, 2013). As can be assumed the predictive approach is extremely rigid and therefore inflexible to change, a slight change in the system design could alter the overall system performance. In this case, the performance of the system be it a cloud-based solution will depend on the accuracy of the predicted system parameters at the start of the project. Moreover, its extremely dependent on the different phases of the project which can halt the system design if a delay is experienced in a given phase. Furthermore, consider the fact that a working software is only produced at the end of the life cycle, this means it can never be used for long time projects or projects with regular adjustments (Gupta, 2014). Adaptive SDLC An adaptive approach methods to system design acknowledges the possibility of changes in both system design and system requirements. For instance, changes may occur in system priorities, design personnel and for our case study change may occur in cloud infrastructure or even the overall architecture. To accommodate these foreseeable changes the project design is broken down into small sections, each holding a specific task. After completion, these sections are deployed together in an iterative procedure to produce the final project (MSB, 2011). Agile is a good example of an adaptive design approach that uses an iterative technique to develop a software or system. In it, the requirements and the design phases are executed concurrently at the same time to meet a common set objective. However, unlike predictive approach, the design and the solution obtained is dependent on the priority. In essence, a system design will have several iterations until the final and desired objective is met . Advantages of Adaptive SDLC Flexibility is the emphasis of this design system and with requirements ever changing, this approach offers the best solution to meet the modern day demand for system requirements. Moreover, this flexibility saves time and money as the projects requirements are determined by the users demands and the available resources. This approach also promotes user interface and system design because the customers is involved the project design at an early stage of system development. This involvement increases system performance and makes it easier to use for the front end user (Mikoluk, 2013). Finally, this approach makes collaboration amongst system designer easier as different modules can be developed simultaneously and integrated at a later stage for the benefit of the overall project. Since adaptive methods lack a planned procedure its hard to predict the end result, especially the date of target delivery. This limitation also makes it difficult to represent the desired project in a business setup where all the defining requirements are laid out on the table. Furthermore, in terms of personnel requirements, adaptive methods require highly trained personnel with the utmost skills in system design. Recommendation for the Headspace Project Before providing the recommendation for the project at hand, its good to point out that predictive SDLC methods are the traditional techniques of systems development. They are traditional because at the time of their development there was little variable to consider which led to linear systems. Adaptive methods, on the other hand, are the response provided by the industry to the current state of events (Kommalapati Zack, 2011). Now, having established this, cloud services and solutions (like the one suggested here) require a dynamic approach to meet their objectives. In our example, the organisation is set to develop a system with a young mans information which is later on accessed by different professionals who will continuously improve on it. Think of the different alterations and modifications that will take place. From this simple description, its clear to see that the adaptive approach will best meet the demands of this project. In addition to this, most traditional SDLC methods focus on the functional aspects of the systems where an on premise hardware system (infrastructure) is used. Furthermore, these features make these systems have implicit security that is sometimes rigid and often compromised by the reduced control. However, adaptive methods, unlike the predictive ones, highlight the non-functional aspects of a system, aspects such as the quality, interface and the constraints faced by the system. In addition to this, consider the advantages raised above where a projects design can shift based on the priorities and the feedback given by the end user (Kommalapati Zack, 2011). Therefore, if our cloud based solution uses an adaptive approach it will be able to adapt based on the requirements and the needs set by the end user, which again can change with time. However, if a predictive approach is followed a change in the system design could halt or stop the entire project which could call for a fresh sta rt. A fresh start would consume more money and time affecting the viability of the project. Cloud computing (CC) is all about flexibility and scalability where solutions are offered to increase movement of information over the World Wide Web. Furthermore, CC tries to cut the production cost by increasing the speed of system development. This form of efficiency can only be achieved through integrated system designs where a project optimises on the benefits of each development environment to meet a common goal. These objectives can only be met through an adaptive approach that aims to capitalise on the strengths possessed by different development techniques (Kathuria, 2011). Conclusion Headspace organisation proposes an innovative system that seeks to leverage the benefits of a digital media by incorporating cloud services into its organisation. Cloud services, unlike other systems, are designed to reach a wider, targeted demographic which is usually supported by its adaptive mechanisms. However, these adaptive mechanisms or techniques are based on certain foundations that later on produce the principles of modern system design. These principles such as usability, performance, security, reliability and scalability among many others set cloud computing apart as an innovative idea. Now, for these principles to be met, the development process must fit the dynamic nature of modern systems which change constantly to meet the needs of the end user. Furthermore, to meet other aspects of the system such as security, the development process must also consider the future and the changes it might have on security procedures. All these requirements among others can only be met by an adaptive approach to SDLC that uses a dynamic approach to develop systems. 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/