• Skip to primary navigation
  • Skip to content
  • Skip to primary sidebar
  • Skip to footer
  • Core Java
  • Design Patterns
  • JSP
  • Servlets
  • Building Tools
  • jQuery
  • Spring
  • Hibernate
  • Mongo DB
  • More
    • HTML
    • SCJP
    • AJAX
    • UML
    • Struts
    • J2EE
    • Testing
    • Angular JS

J2EE Reference

  • Home
  • About Us
    • Java Learning Centers
  • Contact Us

UML- Use Case Diagram

May 24, 2011 By j2eereference 1 Comment

1. Use Case Diagram describes interaction between user and the system.

2. Use Case Diagram doesn’t tell detailed information about individual feature of the system, it is used to describe the complete functionality of the system.

3. Use Case Diagram is suited to describe high level functionality of the system, it is not recommended to use where we have to capture the entire flow of the system like number of hits to a particular module or exceptions etc.

4. Use Case Diagram has four major elements

• Actors:  A role that a user plays with respect to the system,including human users and other systems. e.g.,inanimate physical objects (e.g. robot); an external system that needs some information from the current system.

• Use Case: A set of scenarios that describing an interaction  between a user and a system, including alternatives.

• System boundary :A rectangle diagram representing the boundary between the actors and the system.

• Relationships: The lines between the elements

5. How to identify actors in Use Case Diagram?

Elements whose behavior appears in actors actions column are actors, it may be humans or system interacting with other system example: cronjob interacting with a database for updating user information here cronjob is a process which is actor in Use Case Diagram because it interacts with the other system which is database here other example for humans online banking here humans are actors because they are interacting with the banking system to get there work done by sending a request to the system.

6. how to identify systems in Use Case Diagram?

Elements whose behavior appears in System responses column are components in the system, system box contains use cases one for each service that the system provide to the actors, any internal behavior of the system that the other parts of the system uses should not appear in system box

Filed Under: UML

Reader Interactions

Comments

  1. Rohit says

    May 27, 2011 at 6:02 pm

    Excellent

    Reply

Leave a Reply Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Primary Sidebar

FOLLOW US ONLINE

  • View J2eereference-166104970118637’s profile on Facebook
  • View j2eereference’s profile on Twitter
  • View j2eereference’s profile on LinkedIn

Subscribe by email

Recent posts

  • Java Buzzwords
  • Anonymous Inner Class in Java
  • Network Programming – java.net Package
  • Java Regular Expressions
  • Method Local Inner Class in Java
  • URL Processing in Java
  • Iterator Design Pattern Implementation using Java
  • Strategy Design Pattern Implementation using Java
  • Decorator Design Pattern
  • Adapter Design Pattern Implementation using Java
  • JSF Composite Components
  • JSF UI Components
  • What is JavaServer Faces (JSF)?
  • GOF Design Patterns
  • History and Need for Design Patterns

Footer

Core Java
Design Patterns
JSP
Servlets
HTML
Building Tools
AJAX
SCJP
jQuery
Testing
Spring
UML
Struts
Java Centers
Java Training
Home
About Us
Contact Us
Copyright © j2eereference.com. All right reserved.