System Analysis Of Headspace

Non-Functional Requirement

Discuss about the System Analysis of Headspace.

The non-functional requirement that Headspace can use in its cloud application system is FURPS+. The acronym of FURPS+ is functionality, usage, reliability, the system performance and the supportability. The + is to specify the constraints of the non functional requirements of cloud system of Headspace. The technique of FURPS+ is to make validation to all the requirements that are prioritized and also understands the necessities and needs of the client (Al-Rawashdeh, Al’azzeh & Al-Qatawneh, 2014). The non functional requirements helps to understand the different types of classification that are related to stress which is solved by the FURPS+ technique. The explanation of the FURPS+ technique is as follows:

Functionality: The acronym of F in FURPS+ is Functionality. F defines the main feature of the product which is similar with the cloud solution that is to be developed in Headspace. The requirements of the functionality of FURPS+ are very much technical oriented (Awan, Malik & Javed, 2015). The functional requirements that are mainly required include the functional requirement of licensing, mail, printing, security, workflow, system management, localization, printing and also auditing.

Usability: U in FURPS+ is the acronym of Usability. This usability includes all the issues of user interface such as capturing, stating and looking at that are required. Usability ensures the technique of using the non functional requirements of cloud system properly in Headspace.

Reliability: The aspect which includes accuracy, recoverability and availability are included in reliability. The reliability on recovery and computations are the factors of reliability that prevents the system from being shut down.

Performance: The performance is the acronym of P in FURPS+ (Punia & Kaur, 2014). The feature that are included in performance are the information throughput in the clod system, time take by the cloud system to response and the start up time of the system and also the recovery time that the cloud system needs.

Supportability: The supportability is the S in the FURPS+. The supportability includes other requirements that are needed in the cloud system which includes adaptability, configurability, localizability, scalability, testability, installability and also maintainability.

The FURPS+ has a + sign which indicates some of the specific constraints which includes interface, physical constraints, design and implementation constraints.

Interface Constraints- The constraint of interference is the requirement that is required to interact with the entire external item (Ameller et al., 2013). When the interface of Headspace is developed, it is difficult to interact with all the external systems.

Difference between functional and non-functional requirements

Physical Constraints- The physical constraints of non functional requirements affects all the hardware that is required in the system of cloud. The shape, weight and size of the hardware are determined in physical constraints.

Design Constraints- The design constraint of non functional requirement implements the design of the system (Penzenstadler et al., 2013). The required database that is required in the cloud system of Headspace is designed in the Design Constraints.

Implementation Constraint- The limit that is given to the constriction and the coding which includes implementation language, standards and platforms are all determined in the Implementation Constraints.

Functional Requirements	Non Functional Requirements
The requirements that are functional specify the doing of the service.	The requirements for non functional denotes the property that the service must possess.
All the actions that are carried out by the service so that the fundamental reasons that are required for existence are satisfied (Dick, J., Hull, E., & Jackson, 2017).	The properties of non functional specify the qualities and characteristics that are required to make the service usable, fast, reliable and also attractive.
Fundamental activities such as manipulating data and computation are done.	Fundamental activities such as manipulating data and computation are not required (Mijumbi et al., 2016).
Functional requirements do not change the functionality of the service ignoring whatever properties are attached with them.	Adding functionality to non functional requirement make the service easy to use, interactive and also secured.
A specific behavior of a function in a system is described in a functional requirement when some of the conditions that are certain are met.	The behavior of the system is elaborated in non functional requirement of Cloud system and also keeps a limit on the functionality of the system.
The function requirements are included in a cloud system are: ·         Authorization levels ·         Transaction corrections, cancellation and adjustments ·         Historical data ·         Administrative functions ·         Certification requirements ·         Business Rules ·         Regulatory and legal requirements ·         External Interfaces ·         Reporting requirements ·         Authentication and ·         Audit Tracking	The function requirements are included in a cloud system are: o    Capacity o    Reliability o    Scalability o    Maintainability o    Regulatory o    Environmental o    Interoperability o    Usability o    Manageability o    Security o    Performance that includes throughput, response time, static volumetric and utilization o    Availability o    Serviceability o    Data Integrity o    Recoverability
The example of Functional requirement is sending an email when a new customer signs up an account or opens a new account.	The characteristics and attributes of system quality are specified such as all users who are accessing the database are to have a modified updated data.

Table 1: Showing Difference of Functional and Non-Functional Requirements

The advantages of Cloud Based Storage are as follows:

1. Usability: The services of cloud storage are reviewed in usability in the desktop folders that uses PCs and MACs (Abolfazli et al., 2014). This helps the users to drop and drag the files in between local storage and cloud storage.
2. Bandwidth: The emails files that are sent to individuals are avoided and web link are sent to all recipients via email.
3. Accessibility: The files that are stored can be accessed via Internet from anywhere the user wants. The files are accessed easily by the users.
4. Disaster Recovery: The service of cloud has a high backup plan in case if some emergency occurs. Backup plan for any business can use the cloud storage to keep a second copy of a data or information that is important. The files that are backup in the cloud can be accessed by the user from anywhere via internet connection.
5. Cost Saving: Organizations and businesses use operational costs that are needed annually by using the cloud storage. The cost of storing data internally in cloud is almost 3 cents per GB. The additional cost saving can be found in using cloud because internal power is not needed to remotely store the information.

1. Usability: Users have to be careful in using the drop and drag feature of cloud for moving the document in folder of cloud storage (Rahimi et al., 2014). Copy and paste is not allowed in this process. The users have to be careful to use drag and drop feature.
2. Bandwidth: Specific bandwidths are allowed by specific cloud services. The users of the cloud services have to be careful in using the amount of bandwidth. If the users exceed the amount of bandwidth that is allowed to tem, then extra charge is taken from them for the extra amount that is used.
3. Accessibility: The cloud storage cannot be accessed without the internet connection. If there is no internet, the user will not be able to get access to the files.
4. Data Security: The safety and privacy of the data are to be maintained by cloud storage. This proves the main disadvantage for the cloud system storage. The data privacy can be hampered in the cloud storage service. This makes the business more uneasy and unsafe.
5. Software: The software that is used to access the data have to be installed on all the devices that uses the cloud service, otherwise the files are not accessible.

The data are to be kept secured by using a cloud service in the Headspace. The following aspects are to be kept in mind to give a security to all the data that is stored in the cloud storage. First of all the security agreement that s given by the cloud are to be read properly by the user. The users have to be sure what agreement the provider of cloud is giving to the user. The user agreement are to be made clear so that their does not come any data related threat to the data that are stored in the cloud (Wei et al., 2014). The documents that are stored usually faces data security which hampers the privacy if the user. Secondly the passwords that are created in for the security of the applications are to be very securely done. The passwords are to be strong enough so that any data breach does not take place the technologies that are used by the cyber attacker takes very less time to break the passwords that are used in application in cloud storage. The cloud storages are very much prone to data breach.  Hackers find it easy to hack the applications that are connected to cloud. The passwords for the emails and other needed applications are to be made double secured. Lastly, a cloud service that is securely encrypted is to be used. To protect the data breach and secure the data, encryption process is the most important method that is used. Different cloud services have different encryption process. It is recommended to use cloud services like Wuala or Spideroak so that the data is kept secured in Headspace.

Advantages of Predictive Model	Disadvantages of Predictive Model
This model is very easy and simple to understand and implement.	It is very difficult to go back to the previous stages once it reaches to the testing stage.
Management of this model is very easy because of the rigidity of the model (Kazim, 2017). All the phases have particular review process and deliverables.	This model proves a disadvantages to the projects that are object oriented process and are complex
All the processes and phases are completed at the same time. Overlapping of phases does not occur.	This model have high amount of uncertainty and risk (Modi, H. S., Singh, N. K., & Chauhan, 2017).
Works well with smaller projects where there is clear understand of the requirement.	This model does not work well with the big project that runs long.

Table 2: Advantages and Disadvantages of Predictive Model

Advantages of Adaptive Model	Disadvantages of Adaptive Model
In the life cycle of this adaptive model, some functions that are needed can be developed early.	Requires many resources.
The results of this method can be determined early and in a periodic way (Stoica, M., Mircea, M., & Ghilic-Micu, 2013).	More management attention is required.
The development of the project can be planned parallel.	Design issues arise as it deals with big projects.
Measurement of progress can be checked.	Suitable for bigger projects (Kanan, M., Weheba, G., & Assaf, 2017).
If change of requirements is needed, then cost less.	Time taking method as it works with big projects.
Debugging and testing is very easy.	Complete systems have to be defined for defining the increments.

Table 2: Advantages and Disadvantages of Adaptive Model

The best model that Headspace can use is the Adaptive model because it works best with bigger projects. As storing data in cloud service is a bigger process, adaptive method is the best model. The results of adaptive method can be determined early and in a periodic way. It leads to less the risk to data breach.

References

Abolfazli, S., Sanaei, Z., Ahmed, E., Gani, A., & Buyya, R. (2014). Cloud-based augmentation for mobile devices: motivation, taxonomies, and open challenges. IEEE Communications Surveys & Tutorials, 16(1), 337-368.

Al-Rawashdeh, T. A., Al’azzeh, F. M., & Al-Qatawneh, S. M. (2014). Evaluation of ERP systems quality model using analytic hierarchy process (AHP) technique. Journal of Software Engineering and Applications, 7(04), 225.

Ameller, D., Ayala, C., Cabot, J., & Franch, X. (2013). Non-functional requirements in architectural decision making. IEEE software, 30(2), 61-67.

Awan, S., Malik, F., & Javed, A. (2015). An Efficient and Objective Generalized Comparison technique for Software Quality Models. International Journal of Modern Education and Computer Science, 7(12), 57.

Dick, J., Hull, E., & Jackson, K. (2017). Requirements engineering. Springer.

Kanan, M., Weheba, G., & Assaf, R. (2017). Economic Advantages of Utilizing the Integrated Quality Software Development Model. Ind Eng Manage, 6(210), 2169-0316.

Kazim, A. (2017). A Study of Software Development Life Cycle Process Models. International Journal of Advanced Research in Computer Science, 8(1).

Mijumbi, R., Serrat, J., Gorricho, J. L., Bouten, N., De Turck, F., & Boutaba, R. (2016). Network function virtualization: State-of-the-art and research challenges. IEEE Communications Surveys & Tutorials, 18(1), 236-262.

Modi, H. S., Singh, N. K., & Chauhan, H. P. (2017). Comprehensive Analysis of Software Development Life Cycle Models.

Penzenstadler, B., Raturi, A., Richardson, D., & Tomlinson, B. (2014). Safety, security, now sustainability: The nonfunctional requirement for the 21st century. IEEE software, 31(3), 40-47.

Punia, M., & Kaur, A. (2014). Software Maintainability Prediction Using Soft Computing Techniques.

Rahimi, M. R., Ren, J., Liu, C. H., Vasilakos, A. V., & Venkatasubramanian, N. (2014). Mobile cloud computing: A survey, state of art and future directions. Mobile Networks and Applications, 19(2), 133-143.

Stoica, M., Mircea, M., & Ghilic-Micu, B. (2013). Software development: Agile vs. traditional. Informatica Economica, 17(4), 64.

Wei, L., Zhu, H., Cao, Z., Dong, X., Jia, W., Chen, Y., & Vasilakos, A. V. (2014). Security and privacy for storage and computation in cloud computing. Information Sciences, 258, 371-386.