| 1: | What are the three kinds of requirements defined in this chapter? |
| 2: | Map each of the following requirements types (from the "UML for Systems Engineering" work-in-progress) into requirements types identified in question 1: operational, design constraint, functional, interface, performance, physical, storage, stakeholder need, and specialized. Be prepared to defend your mapping! |
| 3: | Define the term use case. |
| 4: | Compare and contrast use cases, specifications, and scenarios. |
| 5: | What are the primary representational forms (in the UML) for specification? What are the pros and cons of each, and under what conditions might each be applied? |
| 6: | What are the primary representational forms (in the UML) for scenario depiction? What are the pros and cons of each? |
| 7: | What is an actor? What kinds of objects may be actors? |
| 8: | How does the ROPES process map system requirements down to subsystems? |
| 9: | Should use cases be independent or interdependent? Why? |
| 10: | How are the use case relations generalization, «extends», and «includes»different in their usage? |
| 11: | What is the realization of a use case in your systems design? |
| 12: | How do you validate that your use case realization is good? |
| 13: | Scenarios best capture what kind of requirements? |
| 14: | In each of the diagrams used in requirements capture, where and how are QoS requirements captured? |
| 15: | How do activity diagrams and statecharts differ semantically? How do they differ in usage? |
