Eliciting Requirements - Requirements Sources
4 important questions on Eliciting Requirements - Requirements Sources
What are the different kinds of requirements sources
- Stakeholders (people or organizations that are influence the requirements of the system(direct or indirect))
- Documents (Universal documents, legal documents)
- Systems in operation (predecessor systems)
Requirements documentation contain at least the following information
- Name
- Rol (function)
- Additional personal an contact data
- Temporal and spatial availability during the project progress
- Relevance of the stakeholder
- Their area and extent of expertise
- Their goals and interests regarding the project
What are the consequence of missing requirement sources?
- Higher grades + faster learning
- Never study anything twice
- 100% sure, 100% understanding
Name the obligations of the requirements engineer?
- Speaks the language of the stakeholders,
- Becomes thoroughly familiar with the application domain,
- Creates a requirements document,
- Is able to get work results across (e.g., by means of diagrams and graphs),
- Maintains a respectful relationship with any stakeholder,
- Presents her ideas and alternatives as well as their realizations,
- Allows stakeholders to demand properties that make the system user-friendly and simple,
- Ensures that the system satisfies the functional and qualitative demands of the stakeholders.
The question on the page originate from the summary of the following study material:
- A unique study and practice tool
- Never study anything twice again
- Get the grades you hope for
- 100% sure, 100% understanding
![Trustpilot Logo](/images/design_2020/lp/clp-trustpilot-en.png)