Summary of "Técnicas de Levantamento de Requisitos - Parte2"

Summary of "Técnicas de Levantamento de Requisitos - Parte 2"

This video continues a class on techniques for gathering requirements in Software Development. It covers five main techniques, explaining their purpose, application, and key considerations.

Main Ideas and Concepts

Questionnaire
- Used after interviews to clarify doubts that arise during the analysis of interview data.
- Should contain objective, direct questions to facilitate easy and clear responses.
- Questions must be progressive, increasing in involvement with the subject gradually.
- Proper sequencing is essential: group related questions, avoid jumping between unrelated topics, and never ask questions without a clear purpose.
- Avoid circular or confusing questioning to ensure quality answers.
Observation
- Involves directly observing the environment where the system will be used and how users perform their tasks.
- Provides rich, contextual information about users, processes, and environmental factors.
- Example: Observing a supermarket cashier shows the need for a special keyboard and clear monitor display due to the fast-paced environment and customer expectations.
- Environmental factors such as noise, lighting, and physical layout can influence System Design (e.g., audible alerts may fail in noisy factory floors; lighting affects screen visibility).
- Observation helps tailor the system interface and alerts to real-world conditions.
Document Study
- Involves analyzing existing company documents, such as manual forms, spreadsheets, and previous computerized systems.
- Important for understanding current processes and for database design.
- Helps identify reusable components and areas that need modification in the new system.
Prototyping
- Used primarily to clarify unclear or critical requirements.
- Can be a functional prototype (interactive) or a simple paper sketch.
- Presented to users or clients to confirm that the requirement is correctly understood and captured.
- Useful throughout Software Development but especially valuable during requirements gathering to ensure alignment.

Methodology / Instructions for Using Each Technique

Questionnaire
- Develop after interviews to resolve doubts.
- Write objective and direct questions.
- Organize questions progressively and logically.
- Avoid unrelated or purposeless questions.
- Ensure clarity and ease of response.
Observation
- Visit and observe the actual work environment.
- Note interactions between users and system interfaces.
- Identify environmental constraints (noise, lighting, space).
- Use observations to inform System Design and user interface needs.
Document Study
- Collect all relevant existing documents.
- Analyze manual and computerized records.
- Extract useful data for system modeling.
- Identify features to keep or improve.
Prototyping
- Create a prototype to represent unclear requirements.
- Use tools or paper sketches.
- Present to users/clients for feedback.
- Adjust requirements based on prototype validation.