Eliciting Requirements - Requirements Sources

4 important questions on Eliciting Requirements - Requirements Sources

What are the different kinds of requirements sources

  1. Stakeholders (people or organizations that are influence the requirements of the system(direct or indirect))
  2. Documents (Universal documents, legal documents)
  3. Systems in operation (predecessor systems)

Requirements documentation contain at least the following information

  1. Name
  2. Rol (function)
  3. Additional personal an contact data
  4. Temporal and spatial availability during the project progress
  5. Relevance of the stakeholder
  6. Their area and extent of expertise
  7. Their goals and interests regarding the project

What are the consequence of missing requirement sources?

This can have significant negative consequences for the project because requirements may remain undetected. They could come later as more expensive change requests or lead to non-acceptance by stakeholders.
  • Higher grades + faster learning
  • Never study anything twice
  • 100% sure, 100% understanding
Discover Study Smart

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
Remember faster, study better. Scientifically proven.
Trustpilot Logo