Requirements

General

• What is the goal of the requirements phase?
• Which are the main steps of the process for capturing requirements?
• What is the difference between validation and verification?
• Which stakeholders can contribute to the requirements?
• What is the purpose of requirement elicitation?
• How can requirement elicitation be performed?
• What is functional requirements? Give examples.
• What is non-functional requirements? Give examples.
• What is a design constraint?
• What is a process constraint?
• Why do we want requirements to be testable? Why could this be a problem?
• If there are conflicting requirements from several stakeholders, how can then these conflicts be resolved?
• Sometimes the requirements are divided into two separate documents. Which documents? Why? Who is the target audience?
• Which are the main characteristics of good requirements?
• What is the Z language?
• What does requirements validation mean?
• What does it mean to verify a specification?
• How does requirements reviews work?
• How are documents compliant to the IEEE std 830 Software Requirements Specification organized?
• Why do we want requirements to be enumerated?
• What purpose does the title or the slogan of a requirement serve?
• Why is it good to state the source of a requirement?
• Why do we want requirements to be prioritized?
• Why is it so hard to write non-ambiguous requirements?
• Reliability is a probability that can be hard to measure, how do you practically formulate requirements on reliability?
• What are the benefits and drawbacks of using UML models as a complement to the requirements specification?
• What are the benefits and drawbacks of using formal methods to describe requirements?
• What are the benefits and drawbacks of using natural language as the only way to describe requirements?
• Give an example of a system comprising two actors and five use-cases.

Page responsible: Kristian Sandahl
Last updated: 2011-12-02