Tag: #software requirements

Software Requirements Elicitation and Specification

 

  • Requirement elicitation: Is the first step of creating a project. The client tells the programmer what they expect the program to do and how to do it. The information can be retrieved by interviews, observation, brainstorming, etc. The general process can be described as Discovering the needs of the costumer. (Discovering the needs of the costumer)
  • Requirement specification: This is the process of documenting the previous requirements and analyzing them in order to optimize the project

 

Goldsmith, R. (2015). Use elicitation techniques to discover software requirements. October 28th, 2016, de Search Software quality Sitio web: http://searchsoftwarequality.techtarget.com/feature/Use-elicitation-techniques-to-discover-software-requirements

Rouse, M. (2007). software requirements specification (SRS). October 28th, 2016, de Search Quality Software Sitio web: http://searchsoftwarequality.techtarget.com/definition/software-requirements-specification


All you need is requirements

6471739593_8ec4276428_b
via Flickr

Requirements, requirements, requirements, requirements, requirements, requirements

There’s nothing you can do that can’t be done.
Nothing you can elicit that can’t be elicited.
Nothing you can say, but you can specify
How to play the game
It’s easy.

Every engineering system must be specified, based on user requirements. Elicitation is the practice of collecting this requirements.

Requirements need to be explicitly stated and documented for system implementation, they are the descriptions of the system services that the customer requires from it and constraints under which it operates. Software Requirement Specification or SRS is a document created after the requirements are collected and defines how the intended software will interact with hardware, external interfaces, speed of operation, response time of system, portability of software across various platforms, maintainability, speed of recovery after crashing, Security, Quality, Limitations etc.

There are two types: user requirements and system requirements; they can also be either functional, involving the interaction between a system and its environment, or nonfunctional, which involves the restriction on the system that limits our choices for constructing a solution.

RESOURCES: Carleton