elicitation and interview Flashcards
What are the requirements elicitation and analysis stages include?
a. Requirements discovery : interacting with stakeholder to discover their requirements.
b. Requirements classification and organization, Grouping the related requirements.
c. Requirements prioritization and negotiation, and resolving conflicts.
d. Requirements specification.
req are documented and input into the next round of spiral.
What are the Types of interview?
a) Closed interviews based on pre-determined list of questions
b) Open interviews where various issues are explored with stakeholders.
What are recommended skills of an effective interviewing ?
- Be open-minded, avoid pre-conceived ideas about the requirements and are willing to listen to stakeholders.
- Prompt the interviewee to get discussions going using a requirements proposal, or by working together on a prototype system.
What are features of interviews in practice?
Normally a mix of closed and open-ended interviewing.
Interviews are good for getting an overall understanding of what stakeholders do and how they might interact with the system.
Interviews are not good for understanding domain requirements
Because Requirements engineers cannot understand specific domain terminology;
o Some domain knowledge is so familiar that people find it hard to articulate or think that it isn’t worth articulating.
What is requirements validation?
Is demonstrating that the requirements define the system that the customer really wants.
what are sides of Requirements checking?
- validity
- consistency
- completeness
- realism
- verifiability
What are the requirements validation techniques?
a) Requirements reviews
Systematic manual analysis of the requirements.
b) Prototyping
Using an executable model of the system to check requirements.
c) Test-case generation
Developing tests for requirements to check testability.
What are the requirements reviews?
a) Regular reviews should be held while the requirements definition is being formulated.
b) Both client and contractor staff should be involved in reviews.
c) Reviews may be formal (with completed documents) or informal. Good communications between developers, customers and users can resolve problems at an early stage.
what points the review checks ?
a) Verifiability
Is the requirement realistically testable?
b) Comprehensibility
Is the requirement properly understood?
c) Traceability
Is the origin of the requirement clearly stated?
d) Adaptability Can the requirement be changed without a large impact on other requirements?
What are the requirements management?
a) Requirements management is the process of managing changing requirements during the requirements engineering process and system development.
b) New requirements emerge as a system is being developed and after it has gone into use.
c) You need to keep track of individual requirements and maintain links between dependent requirements so that you can assess the impact of requirements changes
What is the requirements management planning?
Requirements management decisions:
a) Requirements identification: Each requirement must be uniquely identified so that it can be cross-referenced with other requirements.
b) A change management process: This is the set of activities that assess the impact and cost of changes.
c) Traceability policies: These policies define the relationships between each requirement and between the requirements and the system design that should be recorded.
d) Tool support: Tools that may be used range from specialist requirements management systems to spreadsheets and simple database systems.
what decisions should check if a requirements change should be accepted ?
a) Problem analysis and change specification.
, the problem or the change proposal is analyzed to check that it is valid. This analysis is fed back to the change requestor who may respond with a more specific requirements change proposal, or decide to withdraw the request.
b) Change analysis and costing The effect of the proposed change is assessed using traceability information and general knowledge of the system requirements.
once completed the decision is made.
c) Change implementation
The requirements document and, where necessary, the system design and implementation, are modified.
