Introduction to the UML Use Case View
Every development effort must determine what users are expecting to receive, yet every organization, even groups within organizations, has its own ideas about what makes a good requirements document.
Many different kinds of requirements affect the course of a development project. Financial and time constraints, policy, technology, existing systems, and even staff can affect project processes and solutions.
The first challenge in a development project is to identify the types of requirements that most directly influence the analysis and design effort.
Use case view
The use case view is focused on the critical success factors of the application to be developed and its functionality or features.
By focusing on the application's features, we create a set of conceptual "slots" into which all the widely varied requirements can be placed.
Focus on Features
Features can be tested, modeled, designed, and implemented. Users who require a particular feature become the audience for modeling activities.
By focusing on features, we define the scope of the project; what features will and will not be supported by the final solution; or the list of features that will be implemented in each incremental release.
After completing this module, you will be able to:
- Define the components of the use case model
- Model a use case diagram using actors, use cases, systems, and associations
- Build a use case
- Write a use case narrative
- Find use case scenarios
In the next lesson, the use case model will be discussed.