![]() The participation of an actor in a use case is shown by connecting an actor to a use case by a solid link.Each Actor must be linked to a use case, while some use cases may not be linked to actors.System function (process - automated or manual).Actor has a responsibility toward the system (inputs), and Actor has expectations from the system (outputs).Similar to the concept of user, but a user can play different roles.Someone interacts with use case (system function).Developed by analysts together with domain expertsĪ standard form of use case diagram is defined in the Unified Modeling Language as shown in the Use Case Diagram example below:.Drive implementation and generate test cases. ![]() Use case diagrams are typically developed in the early stage of development and people often apply use case modeling for the following purposes: In 1992 his co-authored book Object-Oriented Software Engineering - A Use Case Driven Approach helped to popularize the technique for capturing functional requirements, especially in software development.In 1986, Ivar Jacobson first formulated textual and visual modeling techniques for specifying use cases.These days use case modeling is often associated with UML, although it has been introduced before UML existed. ![]() Other requirements such as business rules, quality of service requirements, and implementation constraints must be represented separately, again, with other UML diagrams.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |