Requirements Engineering Flashcards
Q: What is the purpose of Requirements Elicitation?
A: Elicitation is the process of identifying the needs for the purpose of defining requirements to meet the needs of an organization.
Q: What is the difference between Requirements Elicitation and Requirements Gathering?
A: Gathering is typically used to describe asking a client for a list of things they want done while Elicitation is a much more involved interactive and investigative process.
Q: What are the types of Requirements Documentation?
A: There are two types: Text-based (natural language) requirements documentation and Model-based requirements documentation.
Q: What is the main goal of Validation in Requirements Engineering?
A: The main goal of Validation is to review the requirement specification for errors ambiguities omissions and conflicts with the sponsors.
Q: What does Requirements Management involve?
A: Requirements Management involves managing changing requirements throughout the project and having a good plan to manage change.
Q: What is the main task during the Elicitation phase?
A: The main task is to draw out the requirements from stakeholders and identify what is to be done how the product fits into business needs and how the product is used on a day-to-day basis.
Q: What is the difference between Wants and Needs in Requirements Engineering?
A: Wants are desired functions the client would like to see in the product while Needs are the core functions required to address the specific problem that the product is intended to solve.
Q: What are the key Strategies in Requirements Elicitation?
A: The key strategies are Business Process Automation (BPA) Business Process Improvement (BPI) and Business Process Reengineering (BPR).
Q: What does Business Process Automation (BPA) involve?
A: BPA involves the least amount of change to the current system and uses computer technology to automate some portions of the business process.
Q: What is Business Process Reengineering (BPR)?
A: BPR institutes maximum change with a focus on the “to-be” system using techniques like outcome analysis technology analysis and activity elimination.
Q: What are the tasks involved in Requirements Elicitation?
A: The tasks include Fact Finding Collecting Requirements Evaluation Prioritization and Consolidation.
Q: Why is Requirements Elicitation difficult?
A: Problems arise from scope issues misunderstandings volatility and difficulties in communicating needs between clients and engineers.
Q: What are the types of Requirements Sources?
A: The three types of requirements sources are Stakeholders Existing documents and Existing systems (legacy systems).
Q: What are some typical issues in Requirements Elicitation?
A: Issues include wrong stakeholders untrained analysts failure to collect enough information and users misunderstanding what computers can do.
Q: How should Stakeholders be categorized in Requirements Elicitation?
A: Stakeholders should be classified into three categories: Primary/end users Secondary users and Tertiary users.
Q: What is the role of analysts in Requirements Elicitation?
A: Analysts need to collect and verify the requirements from stakeholders and ensure the information is consistent with the goals of the organization.
Q: What can lead to Volatility in Requirements?
A: Requirements can change over time leading to volatility which is a challenge in maintaining stability during the project.
Q: Why is it important to manage the requirements scope?
A: Managing scope ensures that only the necessary requirements are included and prevents the project from experiencing scope creep.
Q: What can cause Failure to Collect Enough Information during Elicitation?
A: Difficulty tracking down stakeholders lack of subject matter experts or incomplete access to information can lead to insufficient data collection.
Q: How can stakeholders’ different languages impact Requirements Elicitation?
A: Stakeholders may use both natural and technical languages so it’s recommended to use visual techniques like models and diagrams to communicate clearly.
