TABLE OF CONTENTS This chapter provides essential rules, principles, and style guidelines for composing UML use-case or user models within the context of the road-map, including use-case diagrams and their elements. Use-case modeling is concerned with modeling the functional dimension of a system what functionality the system provides to its users and is used for system, subsystem, and class conceptualization within the roadmap to capture in a conceptualization model what requirements the construct must satisfy and what functionality it provides to its users. A conceptualization model consists of use-case diagrams and their model elements. Our goal, in this chapter, is to gain more depth in understanding the UML notation and the roadmap concerning conceptualization models.
A use-case diagram depicts the functionality of an entity using actors, use cases, and their relationships. An entity is a classifier, for example, a system, subsystem, or class.
An actor is a set of roles outside of an entity that users of the entity can play when interacting with the entity, including human users and other systems. An actor instance is a specific instance of an actor or a specific user that conforms to the actor and plays a specific role. An actor is depicted as a class stereotyped with the "actor" keyword or a "stick figure" icon.
Figure 5.1 shows a Project Management System with its actors and use cases, including four actors: Manager, System Administrator, Database, and Backup System. There are two types of managers, project managers and resource managers. The Manager...
