Requirements Specification

De productpatterns_wiki
Saltar a: navegación, buscar

Spanish.jpg Español

Box-In.png
Entries

  • Initial obtained requirements specification of the software system or provided by the client.
    • Can it be used configuration management ?: Yes

Box-Out.png
Exit

  • Requirements specification document
    • Can it be used configuration management ?: Yes

Star.png
Solution

process-descending-24px.png
Process

Requirements Specification.png

time-24px.png
Development time

    • To acquire the necessary knowledge to develop the software product: 1 day
    • To create the Product Pattern: 1 day
    • To apply the Product Pattern: 1 day

video-24px.png
Explanatory Video

    • Not applicable



bricks.png
Related Patterns

Search-32px.png
Quality Controllers

  • None

stuff.png
Examples

  • None

start-flag.png
Initial Context

It is desired to describe the functioning and behavior of a software system.It is wanted to take into account customer requirements as well as users system software to develope; Likewise, it is desired to describe design constraints and system implementation.

end-flag.png
Result Context

It has a document that describes the functioning and behavior of a software system. This document takes into account all functional and non-functional requirements of the system and has the approval of the development team and the customer or end user.

cloud.png
Problem

Creation of a document detailing precisely and explicithy all the features and capabilities that a software system must provide(this includes all functional and non-functional requirements of the system to be developed). Likewise, this document must specify the constraints to be taken into account in developing the system.

forces.png
Restrictions (Forces)

  • Type of Organization: SMEs, Large Companies.
  • System Type: It applies to all types of systems.
  • Programming Paradigm: OO (Object Oriented), structured, logical, functional.

roles.png
Roles

  • Analyst
  • Customer
  • Project Manager
  • System Users

lightbulb.png
Lessons Learned

  • Benefits of using this pattern
    • Facilitate the creation of a description of the system to be developed and how it will be used.
    • It can describe scenarios that exemplify the perspective of the system from the point of view of different users.
    • The customer has a clear idea about what it will and will not do the system to be developed.

award.png
Capability Level

  • Capability Level 2 CMMI.

Options.png
Basic Knowledge and Skills

board-24px.png
Knowledge

  • Definition of software requirements (functional and non-functional).

help-24px.png
Habilidades

  • Capacity of abstraction.
  • Capacity of analysis.
  • Eloquence in speech.

Information-Sources.png
Information Resources