Software requirements are simply the needs of stakeholders that will be solved by software.
We can’t start design software architecture, or decide a software development model without knowing any requirements.
Identifying requirements are important in software process. Any design activities should begin after requirements are understood.
Functional and Nonfunctional requirements
####Why it matters?
- Functional Requirements specifies the functionality of the system.
- Non functional Requirements specifies the quality of the system.
If the system has been build does not do what stakeholders want (functionalities does not meet the stakeholders need), the system will be considered failure.
If the system do what stakeholder want but without quality (low satisfiability, availability …), for example, the system must send a warning message if the server is down with a latency of no greater than 5 minutes, and the stakeholders wouldn’t happy if warning message was sent after few hours or days.
Functional requirements describes what a software system must do, the behavior of the system which is related to system’s functionality.
Functional requirements are captured in
Functional requirements are supported by non functional requirements.
Non functional requirements
No functional requirements place constraints on how the system will do, specifies criteria that can be used to judge the software system.
Non functional requirements may include:
- Disaster recovery
- Fault tolerance
- Open source
- Response time
#####Reference Software requirementscomments powered by Disqus