System Analysis & Design Samples for Students †MyAssignmenthelp.com

Question: Discuss about the ICT System Analysis and Design. Answer: Introduction Cloud-based solutions offer a wide range of benefits when dealing with ICT resources such as extending systems mobility and flexibility. Its because of these benefits that the Commonwealth Government hopes to integrate its proposed health system with a cloud resource that will extend the application and functionality of the resource (Fernndez-Cardeosa, Torre-Dez Lpez-Coronado, 2015). However, to meet this objective an intricate development approach is needed to offer the foundational elements that will meet the operational requirements of both the cloud solution and the system package itself. This paper highlights these considerations to be made including the non-functional requirements as well as the development approaches. Non-functional requirements These are the attributes that will affect the systems operations and functionalities. Since a wide range of people will use the said health care system, an assessment based on the user needs will be needed to establish their requirements. This assessment will facilitate the functionalities of the users. In light of these considerations, the following non-functional requirements that will have to be met: Usability satisfying the users based on their expectations and operational requirements. This outcome is met if the system is intuitive, easy to use and has a global factor that enhances the overall experience. Performance The general indication of responsiveness based on the feedbacks given by certain actions e.g. how quick the interface responds to a click of a button. Moreover, this performance should be consistent across all operational environments. Reliability Regardless of the conditions and environment it faces, the developed system should be able to operate consistently without interruptions, this includes changes in operational platforms/environments. Security a paramount requirement where no unauthorised access or authentication should not be conducted or facilitated. There should also be a clear outline on the ownership of the data used (Microsoft, 2017). Review Cloud solutions As the next evolution of internet services, cloud solutions offers a number of services that are usually designated by the resources they provide, from computational resources to application development. In all instances, the resources are based on a layered approach that is similar to a stack package (Harding, 2017). This package will offer on-demand and flexible services based on the user requirements. Now, the My Health Record project outlines an extensive system with a broad range of functionalities which necessitates control and accessibility. Moreover, data ownership should serve as a serious security consideration in the cloud service provided. Therefore, based on this analysis, the cloud model chosen should offer hosting services in the form of storage and computation resources. These resources can be offered by the IaaS (Infrastructure as a service) service model which has a higher control and accessibility as compared to the other models (Harding, 2017). However, these functionalities and attributes present several challenges more so, with security which the underlying system and hardware components must deal with to accomplish the overall systems goal. These considerations necessitate the need for an optimal development approach. SDLC (System/software development life cycle) Approach SDLC facilitates the production of high-quality systems that enhance users management and increases productivity. These objectives are met through concise development procedures that cater for each and every requirement. In this evaluation, two general approaches/methods are considered i.e. predictive SDLC and Adaptive SDLC. Predictive SDLC An old and traditional approach that uses a presumed procedure to develop the systems based on predefined variables and parameters. In essence, the project at hand would assume all the components required, where based on a thorough assessment they would be identified and implemented without any changes (MSB, 2011). The predictive approach offers little room for changes and is thus used in the development of systems that have minimal requirements. The best example that can help conceptualise the method is the Waterfall development model that usually executes development procedures in a sequential manner without any form of overlaps or adjustments (Cerritos, 2011). Pros of the approach Its a very easy approach that can be easily followed and understood which is usually facilitated by its strategic development procedure. Secondly, its predefined outlines lead to a rigid system that enhances developers collaboration, an outcome that yields better results in terms of performance. Furthermore, its associated with strict documentation processes which are good for accountability measures. Finally, its pre-determined model makes its suitable for the development of small systems and projects (Stoica, Mircea Ghilic-Micu, 2013). Cons Lacks flexibility, in fact, changes in requirements will necessitate the restart of the entire development process. Since all stages are accomplished sequentially, its a time-consuming approach. Furthermore, it's characterised by many uncertainties as there are no rooms for errors. Adaptive SDLC The complete opposite of predictive approach, where system development is based on an intricate procedure that offers room for adjustments and changes. To meet its flexibility objectives, the approach will split the development process into several stages or phases that are then implemented concurrently to produce a common solution. Furthermore, the deployment process involves an iterative procedure that repeatedly assembles the phases outlined to yield multiple primary solutions (prototypes) that are then optimised (MSB, 2011). Now, consider the spiral and agile models that will split the development cycle based on the functional aspects outlined. These aspects are the combined through the repetitive assembly cycles outlined above to yield a favourable outcome (Okoli Carillo, 2010). Pros of the approach A highly flexible method that can cater for development changes including expenditure costs and objective outcomes. Unlike predictive approach, adaptive methods will yield functional systems at the end of each development cycle (iterative stage). This approach enhances performance as it allows developers to optimise solutions based on the prototypes produced. Moreover, the same procedure facilitates the mitigation of risks such as security flaws which improve the security of the systems. Finally, its the end users are usually involved in the development process which boosts usability another key non-functional requirements (Okoli Carillo, 2012). Cons As a result of the endless development stages (iterative procedure), the approach may have the challenge of predicting the actual implementation timelines. Moreover, it accommodates too many variables that its difficult to establish a proper business outline linking the development process with the financial aspects of business. Finally, based on its high-end requirements, it requires competent developers with high development skills an outcome that requires a lot of financial considerations (Rackspace, 2017). Recommendations for the project at hand First, the project is highly extensive owing to the number of people who will be using it from medical practitioners to departmental officials. Therefore, the approach adopted should be able to cope with the needs of a big project. Secondly, although the system objective and requirements are outlined, they are set to change based on technological changes and systems functional requirements. Moreover, these changes are further intensified when one considers the collaboration with cloud resources who functional outlines dictate frequent operational changes. However, at the same time, the project will also require a strict documentation process for accountability requirements. Now, the adaptive approach meets these requirements, where on top of its ability to meet the functional requirements its also able to fulfil the non-functional requirements i.e. usability, performance, reliability and security through its intricate development cycles. Furthermore, based on the projects extensive development timeline, the approach will be able to adjust to development changes including system modifications as well as technological outcomes. In all, its overall flexibility will meet the demands of the project regardless of when they are introduced in the development stages. References 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 Fernndez-Cardeosa. G, Torre-Dez. I Lpez-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 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 Microsoft. (2017). Chapter 16: Quality Attributes. Retrieved 22 May, 2017, from: https://msdn.microsoft.com/en-us/library/ee658094.aspx Okoli. C Carillo. K (2010). The best of adaptive and predictive methodologies: Open source software development, a balance between agility and discipline. Retrieved 20 May, 2017, from: https://pdfs.semanticscholar.org/af41/c5a586c46d5803edbafbe18273c94278eb43.pdf Okoli. C Carillo. K (2012). The best of adaptive and predictive methodologies: Open source software development, a balance between agility and discipline. Research gate. Retrieved 20 May, 2017, from: https://www.researchgate.net/publication/220490309_The_best_of_adaptive_and_predictive_methodologies_Open_source_software_development_a_balance_between_agility_and_discipline Rackspace. (2017). Understanding the Cloud Computing Stack: SaaS, PaaS, IaaS. Support networking. Retrieved 20 May, 2017, from: https://support.rackspace.com/white-paper/understanding-the-cloud-computing-stack-saas-paas-iaas/ 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