Summary of "Analisis de requerimientos"

Requirements analysis in software development

Requirements Documented needs of the system in terms of behavior, constraints, and required quality.
Functional requirements Describe the system behaviors the client requests (must be implemented or the system is incomplete). Typical elements include:
- Input data
- Operations on data
- Workflows
- Outputs/reports
- Users
- Applicable regulations
Non-functional requirements (quality attributes) Criteria that affect value or usability but not core operation. Common attributes:
- Performance
- Reliability
- Availability
- Security
- Maintainability

A practical, step-by-step guide to analyze requirements before design and implementation.

Conception Describe the problem naturally and identify stakeholders who are information sources.
Inquiry Validate understanding by asking stakeholders about needs, scope limits, domain concepts, and volatility (what may change).
Elaboration Document the analysis for design. Key artifacts produced here are the requirements specification (a contract of what the system will and will not do) and use cases describing system operation.
Prioritization For each requirement, estimate resource cost, development risk, and client impact; assign numerical values to decide priority.
Validation Review documentation to remove ambiguities and inconsistencies, and ensure compliance with industry standards before design/implementation.

Start by describing the problem in natural language before formalizing it technically.
Fill knowledge gaps by questioning stakeholders and identifying volatile elements.
Document findings (preferably with graphical representations) and validate documentation directly with the client.
Apply the process to concrete examples (the tutorial uses designing a system to streamline obtaining a military service card).
The video suggests a book for deeper study of the stages and requirement characteristics (the specific title is not shown in subtitles).