Software requirements elicitation and specification Functional and non functional requirements


Software requirements elicitation and specification

Functional and non functional requirements



Requirements Elicitation is the process to find out the requirements for an intended software system by communicating with client, end users, system users and others who have a stake in the software system development.

Requirement Elicitation Process:



Why is requirement elicitation necessary?

  • Knowing what problems to be solved and recognizing system boundaries.
  • Identifying who are the stakeholders.
  • Recognizing the goal of system is the target to be achieved.


Software Requirement Specification is a document created by system analyst after the requirements are collected from various stakeholders. Defines how the intended software will interact with hardware, external interfaces, speed of operation.  


The functional requirement is describing the behavior of the system as it relates to the system's functionality. Functional requirements are the main things that the user expects from the software

The non-functional requirement elaborates a performance characteristic of the system. The definition for a non-functional requirement is that it essentially specifies how the system should behave and that it is a constraint upon the systems behaviour. One could also think of non-functional requirements as quality attributes for of a system.

Sources & Links:

Comentarios

Entradas más populares de este blog

Security Countermeasures and Denial of Service

Reflection about Security and Privacy course