The document discusses use case diagrams in UML modeling. It defines what UML is, which is a standard modeling language used to visualize how a system is designed. UML diagrams include use case diagrams, which capture a system's functionality through actors and use cases. The document provides guidelines for creating use case diagrams, such as using meaningful names and annotations. It also gives tips, like keeping diagrams simple and complete. Examples of use case diagrams for an online shopping system and home security system are provided.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
24 views13 pages
3 Usecase
The document discusses use case diagrams in UML modeling. It defines what UML is, which is a standard modeling language used to visualize how a system is designed. UML diagrams include use case diagrams, which capture a system's functionality through actors and use cases. The document provides guidelines for creating use case diagrams, such as using meaningful names and annotations. It also gives tips, like keeping diagrams simple and complete. Examples of use case diagrams for an online shopping system and home security system are provided.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 13
LAB 3
To perform the user‘s view analysis for the suggested system:
Use case diagram UML What is UML? Unified Modeling Language (UML) is a general purpose modeling language. The main aim of UML is to define a standard way to visualize the way a system has been designed. It is quite similar to blueprints used in other fields of engineering.
UML is not a programming language, it is rather a visual
language. We use UML diagrams to portray the behavior and structure of a system.
UML helps software engineers, businessmen and system
architects with modeling, design and analysis. WHY WE NEED UML? Graphical Notations:-Clearer than the natural language and Coding Languages.
help acquiring of overview of system.
A lot of time is saved down the line when teams are able to visualize processes, user interactions and static structure of the system.
UML moves NOT dependent on any one language or
technology.
It simples software design process.
DIAGRAMS IN UML CAN BE BROADLY CLASSIFIED AS: Structural Diagrams – Capture static aspects or structure of a system. Behavior Diagrams – Capture dynamic aspects or behavior of the system. USE CASE DIAGRAM Use Case Diagram captures the system’s functionality and requirements by using actors and use cases. Use Cases model the services, tasks, function that a system needs to perform Use cases represent high-level functionalities and how a user will handle the system. Use-cases are the core concepts of Unified Modelling language modeling. FOLLOWING RULES MUST BE FOLLOWED WHILE DRAWING USE-CASE FOR ANY SYSTEM:
The name of an actor or a use case must be
meaningful and relevant to the system. Interaction of an actor with the use case must be defined clearly and in an understandable way. Annotations must be used wherever they are required. If a use case or an actor has multiple relationships, then only significant interactions must be displayed. TIPS FOR DRAWING A USE-CASE DIAGRAM
A use case diagram should be as simple as
possible. A use case diagram should be complete.
A use case diagram should represent all
interactions with the use case. If there are too many use cases or actors, then only the essential use cases should be represented. A use case diagram should describe at least a single module of a system. If the use case diagram is large, then it should be generalized. USE CASE DIAGRAM FOR ONLINE SHOPPING SYSTEM. USE-CASE DIAGRAM FOR THE SAFEHOME SYSTEM