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

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

This video is part of a course on software development, focusing on the crucial first phase: requirements gathering. It introduces and details the first of several techniques used to collect software requirements—the interview technique—highlighting its importance and best practices.

Main Ideas and Concepts

Importance of requirements gathering:
- It is the first and most critical phase in software development.
- Properly gathering requirements ensures the system meets user needs.
Common requirements gathering Techniques:
- Interviews
- questionnaires
- observation
- Study of documents
- prototyping
Focus on the interview technique:
- Widely used and well-known.
- Requires careful preparation, execution, and post-interview analysis.

Detailed Methodology: interview technique

1. Preparation

Know your interviewee:
- Understand their role, position, and responsibilities.
- Have some knowledge of the business area or domain related to the system.
Learn about the business domain:
- Visit the client’s site.
- Research online and in books.
- Talk to domain experts.
- Analyze existing documents, reports, and systems.
Schedule the interview:
- Set date, time, and location.
Choose a private, neutral location:
- Avoid distractions and interruptions.
- No phone calls during the interview.

2. Execution

Create a comfortable environment:
- Make the interviewee feel at ease to share needs and ideas.
Take notes:
- Use a notepad or computer.
Recording:
- Only record with explicit permission from the interviewee.
Clarify doubts immediately:
- Ask for explanations if something is unclear.
Respect pauses:
- Allow the interviewee time to think and organize their thoughts.
Avoid rushing with too many questions.

3. Post-Interview

Review and detail notes while fresh in memory.
Identify doubts or gaps:
- Resolve through follow-up interviews or questionnaires.

Additional Tips for Interviews in requirements gathering

Clients may not fully know what they want:
- Analysts must guide and propose better or alternative solutions.
Look beyond the client’s initial request:
- Sometimes the client needs a different or additional system.
Discuss reports and data needs:
- Reports are critical and help define data requirements.
Always ask about exceptions to standard processes:
- Users often omit exceptions; these are important for accurate requirements.
Identify non-functional requirements:
- Examples include portability (running on various devices) and simultaneous access (handling multiple users).
- These impact system design and implementation.

Next Steps

The next video will cover the other four techniques: questionnaires, observation, study of documents, and prototyping.

Speakers / Sources

Main Speaker: Course instructor / requirements analyst (unnamed) presenting the class on requirements gathering techniques.

This summary encapsulates the core lessons and detailed methodology for conducting effective interviews as a requirements gathering technique in software development.