SE 133 Chapter 4: Requirements Elicitation

What is the definition of use case associations?

Dependencies between use cases

What does the requirement process contain?

Requirement elicitation and Analysis

What are Associations used for?

To reduce complexity

T or F: We should not rely on questions and questionares alone.

True

Does analysis use natural language or formal/semi formal language notation?

formal/semi-formal language notation

Does requirement specification use natural language or formal/semi formal language notation?

natural language

* What does Requirement Validation check?

• Correctness: - The requirements represent the client's view • Completeness: - All possible scenarios, in which the system can be used,are described • Consistency: -There are no requirements that contradict each other. • Clarity: - A requirement cannot be interpreted in two mutually exclusive ways. • Verifiability: -Requirements can be tested repeatedly to demonstrate the functionality • Realism: - Requirements can be implemented and delivered • Traceability: - Each system component and behavior can be traced to a set of functional requirements

What are the Types of Nonfunctional Requirements?

• Usability • Reliability - Robustness - Safety • Performance - Response time - Scalability - Throughput - Availability • Supportability - Adaptability - Maintainability • Implementation • Interface • Operation • Packaging • Legal - Licensing (GPL, LGPL) - Certification - Regulation

What are the requirement elicitation activities?

1. Identify actors 2. Identify Scenarios 3. Identify Use cases 4. Refine Use cases

What needs to be in each use case?

1. Use Case name 2. Participating actors 3. Entry Conditions 4. Flow of events 5. Exit conditions 6. Exceptions 7. Quality Requirements