System Analysis and Design | Assignment

Added on - 15 Mar 2020

  • 15

    Pages

  • 3651

    Words

  • 81

    Views

  • 0

    Downloads

Trusted by +2 million users,
1000+ happy students everyday
Showing pages 1 to 4 of 15 pages
Running Head: SYSTEM ANALYSIS AND DESIGNAssignment 3[Student Name Here][Institution’s Name Here][Professor’s Name Here][Date Here]
SYSTEM ANALYSIS AND DESIGN2Table of ContentsIntroduction.............................................................................................................3Non-functional requirements.................................................................................3System qualities......................................................................................................4System interface.....................................................................................................5User interface (UI) requirements............................................................................6System constraints..................................................................................................6A review of the cloud-based solutions....................................................................7Benefits of cloud solutions.....................................................................................7Drawbacks/weaknesses..........................................................................................8Software development life cycle (SDLC)...............................................................9Predictive SDLC....................................................................................................9Advantages of the method.................................................................................10Disadvantages...................................................................................................10Adaptive SDLC approach.................................................................................10Advantages of the method.................................................................................11Disadvantages...................................................................................................11Recommendation...................................................................................................12Conclusion..............................................................................................................12References...............................................................................................................13
SYSTEM ANALYSIS AND DESIGN3IntroductionIn any given day, there is always a significant amount of data generated by the healthcareindustry. This data is very important as it determines the decision made by the institutionsinvolved, an outcome that also includes the diagnosis and treatments given to the patients.Moreover, the same data is used in making managerial decisions that aim to improve the servicesof the institution. Similarly, Headspace, a healthcare organization aims to build a moderninformation system to capture the data of patients most of who are young people with mentalillnesses. Now, the system will mainly store patient’s stories, data that will determine thetreatments given to the patients. Therefore, a large storage facility is needed to support thisfunctionality as the content will continuously increase with time[ CITATION Pat17 \l 1033 ].Now, cloud-based solutions are been sort out as a desirable alternative to this requirement asthey offer extended IT resources at affordable prices. In essence, the organization will lease thecomputational infrastructure from a service provider to store and process the data. In the process,the organization will increase its overall service availability and accessibility. In addition to this,the organization will be able to minimize its overall expenditures since most of the resourceneeded will be acquired based on the immediate demands[ CITATION Bis11 \l 1033 ]. In light ofthese objectives, this report offers an in-depth analysis of the cloud solutions where the variousaspects of the technology are highlighted. The report also discusses the various non-functionalrequirements of the system including its development process.Non-functional requirementsIn software development, non-functional requirements represent the systematic elements ofbuilding quality systems based on the needs of the users. In essence, the system must reflectsome envisioned qualities characteristics such as performance, security, reliability and usability.
SYSTEM ANALYSIS AND DESIGN4However, developing these qualities is not as easy as enacting the functional requirements of thesystems, because they are not solely based on the technical aspects of the softwarepackages[ CITATION Chu17 \l 1033 ]. In essence, non-functional requirements are usuallydetermined by the interaction between the end user and the proposed system. Furthermore, theirdetermination is often subjective to certain conditions which intensify their definition.Nevertheless, their presence must be reflected in a system and in most cases must be outlined assoft goals that will depend on the trade-off of various functionalities.System qualitiesA quality system must have increased maintainability and reliability outcomes both during itsdevelopment time as well as its execution time. Furthermore, as stated above its performancemust be consistent based on an adequate usability, where all the requirements of the end usersare met while continuously engaging the end user[ CITATION Ebe11 \l 1033 ]. Therefore, the systemqualities will represent the general characteristics that will determine the run-timebehaviour,system experience and the system design. In this case, they represent different areas of systemconcern that have a potential to impact the package at wider layers and operation tiers. For theHeadspace system, the following characteristics will be necessary:Application availability – this attribute represents the duration of time that the system isavailable to the user offering the different functionalities and operations. While its anabstract factor, its measurement is done using percentages of the overall downtimes at agiven period of time.Interoperability – this represents the ability of an application to perform differentfunctionalities including communicating with other external systems for the successful
desklib-logo
You’re reading a preview
Preview Documents

To View Complete Document

Click the button to download
Subscribe to our plans

Download This Document