Chapter 4 Object-Oriented Software Engineering: Using UML, Patterns, and Java, 2 nd Edition By B. Bruegge and A. Dutoit Prentice Hall, 2004. Requirements Elicitation. Requirements Elicitation Activities. Identifying Actors Identifying Scenarios Identifying Use Cases Refining Use Cases
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
CreateIncident<<Include>>: Functional Decomposition
AllocateResources<<Include>>: Reuse of Existing Functionality
Note: The base case cannot exist alone. It is always called with the supplier use case
ReportEmergency<Extend>> Association for Use Cases
Note: The base use case can be executed without the use case extension in extend associations.
Top Level Use Case
Level 2 Use Cases
Level 3 Use Cases
LegalIdentifying Nonfunctional Requirements(FURPS+ Classification Scheme)
User interface and human factors
Error handling and extreme conditions
Resources and Management Issues