UML For Project


Published on

UML for E commerce: Use case

1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

UML For Project

  1. 1. Introduction toUML andPatterns foreffective Usecase
  2. 2. What is UML?•UML means Unified Modeling language.•UML is a standard language for designing and documenting a system.•UML is language use to define what system going to perform and how to perform .•Its is not pictorial representation but its graphical representation about system.•It is not a methodology, it is a language Modeling language or Model•Model means the final representation of product.•For example if you are building house or Bridge or something civil engineer first makemodel and taking model works make final output. Same way in software we can use thisModel much before coding and execution.• UMl is language by which a technical architect can communication with developer
  3. 3. Structural Diagrams:•Structural diagrams illustrate the static features of a model.•Static features include classes and association, objects and links, and collaborations. Thesestatic features provide the framework in which the dynamic elements of the model execute.For example •A Class defines the behaviors that types of objects can provide. •An association defines the type of relationship that objects can participate in. •A Deployment diagram models pieces of hardware (and people) that can perform work.•Components define pieces of software and procedures that need to be deployed to processors.
  4. 4. Behavioral Diagrams:•Behavioral diagrams describe how the resources modeled in the Structural diagramsinteract and how they each execute their capabilities.•The behavioral diagram puts the resources in motion, in contrast to the structural view,which provides a static definition of the resources.
  5. 5. Use Case diagram:The Use Case diagram models the users expectation for using the system. The peopleand systems that interact with the target system are called actors.The features of the system that the actors use are called use cases. Some use casesinteract with other use cases, a relationship modeled using dependency arrows.The goal of the Use Case diagram is to identify all the features that the clients expect thesystem to support, but it does not reveal any details about the implementation of thesefeatures.Use cases can be written many different ways but the most common is to represent a viewof the system from outside the system. OverviewThe Use Case diagram is a unique graphical element, in that it is a diagram used to modelhow people expect to use a system. The diagram describes who the relevant users willbe, the services they require of the system, and the services they need to provide to thesystem.
  6. 6. Use Case Elements: So use case diagrams are consists of actors, use cases and their relationships. Actors:•Now as we have to discuss that the use case diagram is dynamic in nature there shouldbe some internal or external factors for making the interaction.•Actors can be defined as something that interacts with the system. Use Cases:•A single use case diagram captures a particular functionality of a system. Relationships:Include, Extend and Generalization
  7. 7. Include:•Must relationship•Within an include relationship, one use case explicitly includes the behavior of another usecase at a specified point within a course of action.•The included use case doesnt stand alone; it has to be connected with one or more base usecases. Add To Watch list Login Checkout
  8. 8. Extend:•Optional Relationship•You generally use this construct to factor out behavior thats optional or that occurs onlyunder certain conditions Check <<EXTEND>> Cancel Order Order Status
  9. 9. Case Study: CRUD OperationsBrief Description:•This use case explains the process of Create, update ,Delete and Search of any Userin the system.Often called as Manage Users Actors: Use Cases Relationship: Pre-conditions Create <<INCLUDE>> Only Administrator User <<EXTEND>> Update Admin User Manage User Delete User Search User
  10. 10. Basic Flow of Events:Create User:•Admin will go to the User creation form of the system•Admin will fill all the required information in the form•Admin will submit the form•Acknowledgement will shown to user about success/failure of the requestUpdate User:•Admin will go to the User lookup (for search) form of the system•System will display a list of User based on the criteria filled by the user.•Admin Updates the User information•System validated the data sent by AdminDelete User: •Admin will go to the User lookup (for search) form of the system •System will display a list of User based on the criteria filled by the user. •Admin Delete the User information •System validated the data sent by Admin
  11. 11. Manage User Admin: CRUD Operations System Boundary Manage <<INCLUDE>> Create User User Admin Update User Search User Delete User
  12. 12. Post Conditions:•User details will be created/updated and reflected everywhere in the system•An successful operation message would be displayed to administratorExceptions:If user don’t have sufficient permission then he will not be able to create/update User
  13. 13. Defining the Use Case Approach:You need to answer questions such as the following:•What functionality do we need to include and exclude?•How does this system relate to other systems in our architecture?•Who will use the system?•Who or what does the system depend on?•What products and/or results does the system provide?•Why do the users/other systems need the specific set of features that this system provides?
  14. 14. Advantages OF Use CaseIndependent Of programming language.•Communication with programmers and outside contractors will be more efficient•The right decisions are made before you are given poorly written code.•Easy to understand and provide overall grip on project.
  15. 15. Ecommerce Case Study Flow Diagram Use Case
  16. 16. Add Item to Cart End TransactionYES Add More Items NO NO Item In Check Out Basket ? YES New NO Enter Login Details Custom er? YES Account Enter Account Details Create Account Register Confirmation NO Account Details Correct? YES Confirm Order Make Payment Confirm Payment
  17. 17. Invoice Create Invoice Invoice End Transaction Place Order Order
  18. 18. Use Cases forCustomer,Merchant andAdmin
  19. 19. Search Products System Boundary Buy <<INCLUDE>> Send Product Notification Authenticate Update User/Login Database Write Customer Product Review Search Product View Product Search Product Use Case
  20. 20. Use Case Merchant Account System Boundary Add/Delete Product View Product Upload Images Update Merchant Add/Dele Database te Image Edit Personal Profile Change Password Authenticate Login <<INCLUDE>> User Merchant Account
  21. 21. Use Case Admin Account System Boundary Add/Delete Product Send Notification Add/Delete Merchant Account Add/Delete Update Merchant Ac. Database Admin Add/Delete Reviews. Add/Delete Customer Account. Add/Delete Upload Image Image Send mail/ Newsletter Backup Write Database Backup File Admin Account
  22. 22. Thank you!!