USE CASE DIAGRAM & USE CASE GLOSSARY

Comments (0)

Transcript of USE CASE DIAGRAM & USE CASE GLOSSARY

USE CASE DIAGRAM & USE CASE GLOSSARYWhat is UML (Unified Modeling Language)?The Unified Modeling Language (UML) is a general-purpose modeling language in the field of software engineering, which is designed to provide a standard way to visualize the design of a system.What is Use Case Diagram?A use case diagram at its simplest is a representation of a user's interaction with the system and depicting the specifications of a use case. A use case diagram contains four components.

The boundary, which defines the system of interest in relation to the world around it.The actors, usually individuals involved with the system defined according to their roles.The use cases, which are the specific roles played by the actors within and around the system.The relationships between and among the actors and the use cases.What are its purpose?Used to gather requirements of a system.

Used to get an outside view of a system.

Identify external and internal factors influencing the system.

Show the interacting among the requirements are actors.Use Case Sample DiagramAbogado, Viron P.Abueva, Kizza D.Liguan, Earl John Y.Sac, Timothy John G.What is Use Case?A use case is a methodology used in system analysis to identify, clarify, and organize system requirements. The use case is made up of a set of possible sequences of interactions between systems and users in a particular environment and related to a particular goal. Users (known in Unified Modeling Language (UML) as an "actor") can be a human, an external system, or time.Use Case Sample DiagramWhat are the rules in User Case Diagram?Think from end user’s perspective - It is clear that you need to know users’ expectation in order to build a software system that works, and this principle is particular important in use case modeling.Actor is a role, not a real person.Model detailed system flow with sequence diagram - Sequence diagram allows you to model the system behavior by representing the communication and interchange of messages between objects over time.

Apply same width on use cases when appropriate - Since the names of use cases are different in length, it is normal to have the use cases in different width. To make the diagram more pretty and easier to read, it would be nice to resize them to same width.

Position actors and use cases in a meaningful way - A use case diagram with randomly placed actors and use cases is definitely a nightmare for readers. Model scenario with flow of events, not directly on diagramMake good use of stereotype for categorizationAvoid long use case nameModel exceptional behavior with <<extend>>Model common use case with <<include>> relationshipUse Case Glossary