Teknik Pengumpulan Kebutuhan : Wawancara dan Joint Application Develpment

Summary

This video discusses five key techniques for gathering system requirements: interviews, Joint Application Development (JAD), questionnaires, document analysis, and observation. The first two techniques, interviews and JAD, are explained in detail. Interviews involve direct one-on-one discussions with stakeholders to gather insights, while JAD brings together groups of stakeholders to collaboratively determine system needs. The video emphasizes the importance of choosing the right participants, preparing questions carefully, and analyzing the collected data for effective system development. These techniques are crucial for ensuring that a system meets user needs and avoids failure.

Takeaways

• 😀 Interviewing is a common and effective technique for gathering system requirements, allowing direct information from users and stakeholders.
• 😀 Choosing the right interview targets is crucial – interview people who understand the processes you are analyzing, not random individuals.
• 😀 Well-designed interview questions are essential. They should be specific, clear, and focused to gather the right information.
• 😀 Preparation for interviews is key: familiarize yourself with the topic and bring necessary tools like recorders or notes to capture the details.
• 😀 Professionalism during interviews is important: listen actively, avoid interrupting, and show respect for the interviewee's time and insights.
• 😀 Follow-up after interviews involves analyzing the gathered data and summarizing key requirements to build the system's requirements document.
• 😀 Joint Application Development (JAD) is a group-based technique where stakeholders collaborate in structured sessions to define system requirements.
• 😀 JAD is especially useful for large-scale projects, such as developing hospital information systems or university academic systems, involving multiple parties.
• 😀 JAD sessions require facilitators to guide the discussion, scribes to document the outcomes, and users to provide input on system needs.
• 😀 Communication through JAD is more open, allowing quicker clarification of issues and faster decision-making, making it ideal for complex projects.

Q & A

What is the importance of understanding system requirements?

Understanding system requirements is crucial because if you misunderstand the user's needs, the system you create may not be used or may even add to existing problems.

What are the five common techniques used in system requirements gathering?

The five common techniques are: interviews, Joint Application Development (JAD), questionnaires, document analysis, and observation.

How is an interview used in gathering system requirements?

Interviews are used to directly gather information from key stakeholders such as users or managers. The process involves selecting the right interviewees, designing relevant questions, preparing for the interview, conducting the interview professionally, and following up with the gathered data.

What should you consider when selecting interviewees for system requirements gathering?

You should select people who have a deep understanding of the work process being analyzed. For example, when creating a system for borrowing laboratory equipment, you would interview the lab staff, not the campus parking attendant.

What is Joint Application Development (JAD) and how does it differ from interviews?

JAD is a group-based method for gathering system requirements, where all relevant stakeholders meet in structured sessions to discuss and determine system needs. Unlike interviews, which are individual, JAD fosters collective decision-making and clarification of issues.

What is the role of the facilitator in a JAD session?

The facilitator is responsible for leading the session, ensuring that discussions remain focused and productive, and guiding the group through the process of identifying system requirements.

How does a questionnaire help in gathering system requirements?

A questionnaire allows you to collect data from a large group of people quickly, such as students for a system that manages lab equipment borrowing. However, it has limitations, such as the inability to clarify responses or ask follow-up questions.

What is document analysis and when is it used in system requirements gathering?

Document analysis is the process of reviewing existing documents, such as Standard Operating Procedures (SOPs), to understand the current system. It's particularly useful when updating or improving existing systems, like an employee management system.

How does observation contribute to system requirements gathering?

Observation involves directly watching how processes are carried out in real time. This technique allows you to identify issues or inefficiencies that may not be reported by users, providing valuable insights into system needs.

Why is it important to understand the user's workflow during the interview process?

Understanding the user's workflow ensures that you can gather accurate, relevant information about the system's needs. Without this understanding, the interview may lead to confusion or irrelevant data, affecting the overall quality of the system requirements.