Non-Functional Requirements for NewAccess System
The case that is taken in this report is the new information system of NewAccess. The NewAccess is mental health institution of Headspace. The main aim of NewAccess is to store the records as well as all the stories of the patients when they come to Headspace for the first time. Headspace deals with the mentally ill patients. The new system of Headspace needs to keep all those previous data of the patients so that they their doctors can get all the data related to their health and can also recommend medicines to all patients (Fenton & Bieman, 2014). With the developed system of NewAccess which is proposed in this report, all the issues that are involved in the treatment process can be mitigated. The mentally ill patients can get treatment from Headspace. With the treatment process that the Headspace is planning to provide, the patients gets advantage as they do not have to explain all their problem every time they visit the doctor and they have to say very little for the second visit.
This report describes the new system of Headspace known as NewAccess by identifying as well as discussing non-functional requirements that are involved in the system. Moreover, this report also discusses a cloud approach that can be selected for evaluating the project. The cloud approach states the weakness as well as strength of the new system in Headspace. There is also a SDLC approach that is described for implementing this project. The SDLC approach is further categorized into two categories that are explained briefly in this report.
For developing a system, many non-functional requirements are to be considered. All those non-functional requirements are to be considered for implementing the NewAccess system in Headspace. The non-functional requirements involved in a system mainly specifies many criteria that are used for judging all operations for the system that is being developed in the system (Kerzner & Kerzner, 2017). The non-functional requirements are also known as quality attributes that are implemented in the system. Non-functional requirement needed for system of NewAccess is mainly evaluated with FURPS+. The FURPS+ contains functionality, usability, reliability, performance, as well as the security that are to be implemented in the system.
The first feature that is to be implemented is functionality. This functionality is an important aspect while implementing a system (Hatley & Pirbhai, 2013). All the requirements stated in the system should function properly according to the functionality feature of FURPS+. It is very important for enforcing some the features which helps to improve functionality of the system.
The second feature of FURPS+ is usability. This usability is one of the most important non-functional requirement while developing a system. The system of NewAccess should be usable to all the users who tries to use the system (Highsmith, 2013). The interface of the system should be user friendly so that the user can efficiently use it. The professionals who are involved with Headspace should use the system with easy. The patients should also be able to use the system effectively.
FURPS+ Approach for Evaluating Non-Functional Requirements
The third feature that is involved in FURPS+ is reliability. The application of NewAccess that is to be developed is to be reliable so that all the data that are stored in the system is secured and user feels reliable to keep their personal data in the system. The users are also to be key ensured about the failure frequency of NewAccess system (Pluzhnik, Nikulchev & Payain, 2014). If also the system fails, there should be quick recoverable mode for NewAccess system. Reliability is one of the most important feature that is to be implemented while developing NewAccess for Headspace.
The measurement of performance of the system is also an important factor while developing the system of NewAccess. The system that is developed should be ensured about its performance level. It is essential that the system performs well. The response time involved in a project should be higher with high throughput. It is very much essential for system to ensure the results that are involved in NewAccess system (Fuggetta & Di Nitto, 2014). The system should have a very high accuracy level while the professionals and the patients are using it. The system of NewAccess should also ensure that there is an easy data availability and usage of resource are also to be kept limited. One of the important aspect related to functionality is performance and it should be correct in the system.
The last feature that is involved in FURPS+ is security. This is the most important factor involved while a system development. As the NewAccess system stores all the personal data of the patients and those sensitive information are to be kept secured. The process of encryption is involved in the non-functional requirement while implementing a system. So, security is also needed for the NewAccess system that Headspace has decide to implemented. The registration feature is to be implemented in the system. The encryption and the registration are to be ensured accurately in the NewAccess system. The data stored in the system should be secured with all the process of encryption that are possible and the users are also t be ensured that the data is available only to those users who have permission to access the data. So, controlling the authorization helps to ensure proper data protection proper security system is to be implemented in the NewAccess system.
The team who is involved for developing a system mainly uses an approach of cloud for storing the data. Since, the system stores effective as well as personal data of the patients that are needed to be secured using a cloud data storage. So, choosing a correct cloud approach is always needed before implementing a system. Using a public cloud is not at all safe to use as public clouds are not at all safe at al since there is no secure mechanism implemented in the system. There is no security of data in public cloud. The private cloud that are available for the system is very much costly and implementing cloud service on the system is also very costly (Abrahamsson et al., 2017). So, for the Headspace, it is recommended not to use the private cloud for the new system of NewAccess. The availability of data will reduce implementation of the private cloud. Using a hybrid cloud can be feasible for the system that is implemented. It is recommended to use hybrid cloud for the system of NewAccess. The hybrid cloud ensures proper data security of the data that are stored in NewAccess system. This also ensures data accessibility very easily. Using the hybrid cloud storage, the system will get many advantages. The benefits as well as the limitations are describe below in the next section that can be encountered while implementing private cloud in the system.
Cloud Approach for NewAccess System
The advantages that are offered by implementing a hybrid cloud in a system are described below:
- The hybrid technology is a combination of both the public cloud as well as the private cloud and it is the most appropriate cloud storage system for NewAccess.
- Using this cloud approach the scalability of the system is increased along with an easier implementation of the storage system.
- Using the hybrid cloud mainly ensures the proper security of data that are stored in the system and thus this cloud structure is recommended for this NewAccess system.
The limitations that are offered by implementing a hybrid cloud in a system are described below:
- One of the most important disadvantage of hybrid cloud is that implementing this system cost more compared to the public system cloud.
- Another limitation of hybrid cloud is the compatibility problems that is involved with the hybrid cloud implementation for the NewAccess.
For the NewAccess system, there should be proper development methodology for developing the software for Headspace. There are two SDLC approach that can be implemented for developing the system in Headspace (Li et al, 2013). There is predictive SDLC approach and there is adaptive SDLC approach.
The methodology that is involved in the predictive SDLC approach is that this method can be used for some particular projects that are planned from first. This planned approach mainly follows the implementation of project and also ensures that the project is delivered on time. Projects that have clear requirements are appropriate for using this predictive SDLC method. The benefits and limitations are as follows:
The benefits of using the predictive SDLC approach of model implementation are:
- With this SDLC method, the project implementation and completion can be done at the scheduled time that was fixed earlier.
- This also ensure the project implementation as per the requirements.
The limits of using the predictive SDLC approach of model implementation are:
- This approach does not entertain any changes after the starting of the project after the implementation phase.
- Complex projects are not appropriate for the predictive SDLC approach.
The adaptive model of SDLC mainly ensures that the project is done according to the requirement that the clients has fixed for it. The implementation of the process in the adaptive SDLC approach has many opportunities for the clients as well as for the stakeholders. The benefits and limitations are as follows:
The benefits of using the adaptive SDLC approach of model implementation are:
- It helps in improving the changes even after the implementation phase is being completed.
- The requirement of the project is set according to the requirement of the client.
The limits of using the adaptive SDLC approach of model implementation are:
- Implementation time is high.
- The complexity of project increases.
The recommended SDLC model for the NewAccess system is adaptive SDLC model. Testing of NewAccess is also needed for ensuring the working system.
Conclusion
From the above discussion it can be concluded that all the non-functional requirements that are needed for developing the NewAccess is explained in this report. This report also evaluates the non-functional requirements that are needed for headspace and the features of FURPS+ are also discussed elaborately in this report. A comparative study of Adaptive SDLC and predictive SDLC is discussed with a recommendation is provided for the system for NewAccess. A cloud storage provider is also recommended for the Headspace in this report. Proper recommendation for the system of NewAccess is also stated in this report.
References
Abrahamsson, P., Salo, O., Ronkainen, J., & Warsta, J. (2017). Agile software development methods: Review and analysis. arXiv preprint arXiv:1709.08439.
Fenton, N., & Bieman, J. (2014). Software metrics: a rigorous and practical approach. CRC press.
Fuggetta, A., & Di Nitto, E. (2014, May). Software process. In Proceedings of the on Future of Software Engineering (pp. 1-12). ACM.
Goyal, S. (2014). Public vs private vs hybrid vs community-cloud computing: a critical review. International Journal of Computer Network and Information Security, 6(3), 20.
Hatley, D., & Pirbhai, I. (2013). Strategies for real-time system specification. Addison-Wesley.
Highsmith, J. R. (2013). Adaptive software development: a collaborative approach to managing complex systems. Addison-Wesley.
Kerzner, H., & Kerzner, H. R. (2017). Project management: a systems approach to planning, scheduling, and controlling. John Wiley & Sons.
Li, J., Li, Y. K., Chen, X., Lee, P. P., & Lou, W. (2015). A hybrid cloud approach for secure authorized deduplication. IEEE Transactions on Parallel and Distributed Systems, 26(5), 1206-1216.
Li, Q., Wang, Z. Y., Li, W. H., Li, J., Wang, C., & Du, R. Y. (2013). Applications integration in a hybrid cloud computing environment: Modelling and platform. Enterprise Information Systems, 7(3), 237-271.
Moniruzzaman, A. B. M., & Hossain, D. S. A. (2013). Comparative Study on Agile software development methodologies. arXiv preprint arXiv:1307.3356.
Pluzhnik, E., Nikulchev, E., & Payain, S. (2014, June). Optimal control of applications for hybrid cloud services. In Services (SERVICES), 2014 IEEE World Congress on (pp. 458-461). IEEE.
Stark, J. (2015). Product lifecycle management. In Product Lifecycle Management (Volume 1) (pp. 1-29). Springer, Cham.
Order an Essay Now & Get These Features For Free:
Turnitin Report
Formatting
Title Page
Citation
Outline
