Food Processing Software: Functional and Non-Functional Requirements

This report explores the functional and non-functional requirements for developing software in a food processing and distribution company, focusing on automating human resource allocation and leave management. Functional requirements include software functionality for tracking employee leaves, resource allocation, authorization levels for management and employees, and ensuring data security. Non-functional requirements cover system availability, reliability in resource allocation, maintainability for software improvements, and data integrity to ensure scalability and accountability. The report emphasizes the importance of both functional and non-functional aspects for the successful operation and indirect contribution to the proper running of the software.

Running head: FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS
FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS
Name of the Student:
Name of the University:
Author Note:

1FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS
During the development of the software there are some functional and non functional rules
exist during the development phase. The functional requirements includes the rules and the regulations
regarding the implementation of the software, functioning of the software and level of authorization
(Eckhardt, Vogelsang and Fernández 2016). The non functional requirements includes the scalability,
maintenance and control over the software. In this paper the discussion is regarding a food processing
organization where some of the activities are needed to be taken into account for the automation (Khan
et al.2016). In order to do this the development of the specific software is needed to be done. In order
to do this the functional and non functional requirements for the implementation of the software is
needed to be evaluated.
Discussion
The organization where the software is needed to be implemented is a food processing and
distribution company. The automation is needed to be done in the human resource allocation along
with keeping the accountability of the leaves of the employees (Zou et al. 2015). In this context the
functional and non functional requirements are needed to be evaluated.
Functional requirements:
Implementation of the functionality of the software: The analysis of the functionality needed to
be implemented in the software is a functional requirement. The software is needed to be able to count
and keep the track of the number of leaves of the employees in the organization in a proper way. On the
other hand the allocation of the resources for each of the production is needed to be done properly by
the software.
Authorization: Determination of providing the authorization to the management is another
requirement. The admin needed to have the full control over the software whereas the employees in
the organization needed to have the partial access to the software.
External interface and keeping the data safe: The data in stored and processed within the software
system are needed to be kept in a proper way (Dabbagh and Lee 2014). It is expected from the
software that the data stored in the software would be protected from the breaches and the external
threats.
Non- Functional requirements:
Some of the non-functional requirements those can be mentioned in this context are:
Availability: The system is needed to be available all the time to the employees and the
management of the organization.
Reliability: The reliability and the allocation of the resources are needed to be done by the
system in a proper way. The allocation of the resources are needed to be done in a realistic way.
Maintenance: the functions of the software are needed to be controlled and evaluated in
proper way so that the improvisation and the modifications can be made accordingly.
Data integrity: the integrity of the data is needed to be maintained in a proper way. This will
help to deliver a scalable and accountable result to the organization.

2FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS
The functional requirements mentioned in the list are important as it would be helpful to run
the software in a proper way along with fulfilling all the requirements. On the other hand the non
functional requirements mentioned in the list are important as these factors have their indirect
contribution for the proper running of the software.

3FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS
References
Dabbagh, M. and Lee, S.P., 2014. An approach for integrating the prioritization of functional and
nonfunctional requirements. The Scientific World Journal, 2014.
Eckhardt, J., Vogelsang, A. and Fernández, D.M., 2016, May. Are" Non-functional" Requirements really
Non-functional? An Investigation of Non-functional Requirements in Practice. In Software Engineering
(ICSE), 2016 IEEE/ACM 38th International Conference on (pp. 832-842). IEEE.
Khan, F., Jan, S.R., Tahir, M., Khan, S. and Ullah, F., 2016. Survey: Dealing Non-Functional Requirements
at Architecture Level. VFAST Transactions on Software Engineering, 9(2), pp.7-13.
Zou, J., Xu, L., Guo, W., Yan, M., Yang, D. and Zhang, X., 2015, May. Which non-functional requirements
do developers focus on? an empirical study on stack overflow using topic analysis. In Mining Software
Repositories (MSR), 2015 IEEE/ACM 12th Working Conference on (pp. 446-449). IEEE.