logo

Non Functional System Requirements

12 Pages2738 Words143 Views
   

Added on  2020-03-28

Non Functional System Requirements

   Added on 2020-03-28

ShareRelated Documents
Running Head: SYSTEM ANALYSIS AND DESIGNAssignment [Student Name Here][Institution’s Name Here] [Professor’s Name Here][Date Here]
Non Functional System Requirements_1
SYSTEM ANALYSIS AND DESIGN2Table of ContentsIntroduction.............................................................................................................3Non-functional system requirements.....................................................................3System qualities......................................................................................................4System interface and User interface (UI) requirements.........................................4System constraints..................................................................................................5Cloud-based solutions.............................................................................................5Strengths of cloud-based solutions.........................................................................6Weaknesses............................................................................................................6Software/system development life cycle (SDLC)..................................................7Predictive SDLC....................................................................................................7Pros of predictive approach.................................................................................8Cons.....................................................................................................................8Adaptive approach..................................................................................................8Pros of the approach............................................................................................9Cons.....................................................................................................................9The recommendation...............................................................................................9Conclusion..............................................................................................................10References..............................................................................................................11
Non Functional System Requirements_2
SYSTEM ANALYSIS AND DESIGN3IntroductionHeadspace project requires an efficient solution based on the current need for informationmanagement where patients record more so their diagnostic stories are stored by an elaborateinformation system. From the initial assessments given, the patients and the health practitionersface serious challenges of information availability and accessibility because the current servicemodel lacks a means to store the patient's ordeals. Now, a modern information system coupledwith cloud-based resources would offer the necessary solution for meeting the needs of themedical services[ CITATION Gho12 \l 1033 ]. In essence, the stories (detailed accounts) of thepatients would be stored conveniently in the cloud infrastructure which is an endless storageresource that would facilitate the treatments given despite the changes in the medical personnel.This report analyses this system from a design perspective where the resource requirementsincluding the affiliated cloud facilities are given. Furthermore, the report also compares thedifferent design methods of implementing software packages and offers a conclusiverecommendation. Non-functional system requirementsWhile using the proposed system, the users will develop their own personalized judgments basedon the performance exhibited. In this case, they will assess the system’s usability, performance,security and even reliability. Now, these elements outline the non-functional requirements whichgenerally are the criteria used to assess the operation of any given system. Moreover, whilefunctional requirements are determined by the technical specification and define exact behaviourof the system, non-functional requirements stem from the collaboration of the technicalcomponents[ CITATION CSI04 \l 1033 ].
Non Functional System Requirements_3
SYSTEM ANALYSIS AND DESIGN4System qualitiesAlthough several subsidiary objectives are given for the project, the proposed system shouldsolve the main problem of data management where its availability and accessibility should beimproved. Moreover, the system must be able to maintain records based on the specificationsgiven by the users i.e. data management[ CITATION Chu12 \l 1033 ]. Finally, the system must beresilient i.e. it must have the ability to withstand attacks. In all, it should possess the followingqualities:Enhanced usability – a measure of the practicality quota of the system where users have optimalsatisfaction rates.Optimal performance – the system should facilitate all the actions of the users regardless of theircomplexities.System reliability – not only the ability to withstand attacks and other hardships but also theconsistency of service delivery regardless of the platforms used.Security – data safety as provided by good authentication and encryption standards. Moreover,the policies used should specify the owners of the data[ CITATION Rah15 \l 1033 ]. In this case,since cloud facilities are to be used yet they do not fall under the jurisdiction of the Australianlaw, encryption more so during transmission will be used. In addition to this, virtual privatenetworks (VPNs) will facilitate personalized access of the cloud resourced based on personalizedportals. Finally, end to end authentication should be used to ensure access is managed, dependingon the user’s access.
Non Functional System Requirements_4

End of preview

Want to access all the pages? Upload your documents or become a member.

Related Documents
System Design and Analysis Assignment
|11
|2251
|76

Assignment | System Analysis and Design
|13
|2740
|290

Headspace Newaccess Project 2022
|12
|2731
|5

System Analysis PG (Doc): Assessment
|11
|2322
|43

Headspace Project Assignment
|12
|2626
|213

System Analysis and Design Assignment - Headspace Organization
|13
|2617
|96