System Analysis and Design - UI and System Interface
Added on 2020-03-16
12 Pages2727 Words260 Views
Running Head: SYSTEM ANALYSIS AND DESIGNAssessment 3 [Student Name Here][Institution’s Name Here] [Professor’s Name Here][Date Here]
SYSTEM ANALYSIS AND DESIGN2Table of ContentsIntroduction.............................................................................................................3System’s non-functional requirements..................................................................3System qualities......................................................................................................4System interface.....................................................................................................4UI and system interface requirements.................................................................5System constraints..................................................................................................5A review of the cloud solutions...............................................................................5Strengths of cloud computing................................................................................6Weaknesses............................................................................................................6Protecting the project’s data...................................................................................6Analysis of the SDLC Approach............................................................................7Predictive approach................................................................................................7Advantages of the approach................................................................................8Disadvantages.....................................................................................................8Adaptive method....................................................................................................8Advantages of the approach................................................................................9Disadvantages.....................................................................................................9Recommendation.....................................................................................................9Conclusion..............................................................................................................10References..............................................................................................................11
SYSTEM ANALYSIS AND DESIGN3IntroductionAs the demands for faster connectivity increases, the application of cloud facilities will alsoincrease to support the functional requirements of the end users. These facilities among manyother characteristics will offer flexibility benefits owing to their availability across the WorldWide Web. Moreover, they will be resilient because of the redundancy programs of the serviceproviders who will frequently set up multiple resources in different areas[ CITATION Sta16 \l1033 ]. In addition to this, the technology will drastically reduce the overall cost of operation asthe end users (subscribers) will have minimal managerial roles. These roles in today’s on-premise infrastructure will include the implementation functionalities as well as the generalmaintenance operations, which are eliminated after the application of the cloud facilities. Now,the project at hand requires extensive storage because of the growing demands made by thepatient’s records. Therefore, to meet this objective, the project aims to integrate cloud resourcesinto the proposed system. This report analyses this requirement where the various aspects ofcloud solutions are outlined.System’s non-functional requirementsIn system design, the non-functional requirements represent the general constraint of thesystem’s functionalities. In essence, these requirements restrict the operations of the resources asdefined by the functional requirements[ CITATION Chu15 \l 1033 ]. Furthermore, they will outlinethe process in which the functionalities of a system are achieved i.e. the how of operations andnot the “what” of the system’s operations. In general, there are four main groups of the non-functional requirements:Usability – a group of requirements that require the system to priorities its functionalitiesbased on the user application patterns i.e. the usage characteristics.
SYSTEM ANALYSIS AND DESIGN4Reliability – the system ability to satisfy the user demands after a long time of operation.Performance - the system’s response to the user’s initial specifications and commands.Security – the ability to maintain the integrity of the system’s resources[ CITATION Ter12 \l1033 ].System qualitiesThere are specific minimal services and operations that the system must perform, these servicesdefine the qualities of the system where certain distinctive attributes are highlighted. Moreover,they specify the characteristics of the system from the end user’s perspective[ CITATION Lév03 \l1033 ]. In this project, the following qualities must form the basis of its functionalities:Serviceability – the ease in which the system will be maintained while using a wide rangeof monitoring activities. Latent capacity – considering the field of application, the system’s ability to handleunusually high loads will facilitate its performance and usability.Availability – finally, the system should have a reasonable service time when the overallresources are readily available to the end users[ CITATION Gor111 \l 1033 ].System interfaceIn the computing industry, an interface represents a general boundary area that separates severalcomputing components while facilitating the exchange of information. In this project, the mainsystem interface will be between the Headspace system and the cloud resources. This boundaryas highlighted above will facilitate the exchange of information between the end users and thecloud storage resources[ CITATION Mul07 \l 1033 ]. Moreover, the system at hand will have anotheradditional interface that will deliver results to the end users (user interface). In both instances,the following requirements will have to be met:
End of preview
Want to access all the pages? Upload your documents or become a member.
Related Documents
System Analysis & Design | Assignmentlg...
|12
|2693
|215
System Analysis PG - Doclg...
|12
|2727
|288
System Analysis and Design - Headspace Projectlg...
|11
|2353
|94
System Analysis & Design: Assignmentlg...
|12
|2698
|93
SYSTEM ANALYSIS AND DESIGN 12 Running Head: System ANALYSIS AND DESIGN 12lg...
|13
|2777
|157
System Analysis PG (Doc): Assessmentlg...
|11
|2322
|43