Business Analysis with For PG MDI, Gurgaon Kamna Malik, Ph.D.

Nov 29 09Dr. Kamna Malik2 A Primitive model of Software Development Requirement Specifications Design Model Source Code

Nov 29 09Dr. Kamna Malik3 Rational Unified Process

Nov 29 09Dr. Kamna Malik4...What is an Iteration

Nov 29 09Dr. Kamna Malik5 4+1 View Model - Philip Krutchen Logical View Process View Deployment View Implementation View Use case View Actors Use cases Classes Collaborations Objects Classes Collaborations Interactions Categories Module Subroutine Tasks Subsystems Task Thread Process Interactions Nodes Modules Main Program

Nov 29 09Dr. Kamna Malik6 What is UML? UML stands for Unified Modeling Language The UML combines the best of the best from –Data Modeling concepts (Entity Relationship Diagrams) –Business Modeling (work flow) –Object Modeling –Component Modeling The UML is the standard language for visualizing, specifying, constructing, and documenting the artifacts of a software-intensive system It can be used with all processes, throughout the development life cycle, and across different implementation technologies

Nov 29 09Dr. Kamna Malik7 UML 2.0 Diagrams

Nov 29 09Dr. Kamna Malik8

Nov 29 09Dr. Kamna Malik9

Nov 29 09Dr. Kamna Malik10 How to Create UML Diagrams? White Board Use a white board (free-form diagram) to draw and then capture with a digital camera if you wish. Word Processor Use a word processor for text Microsoft Visio This is a very popular tool. UML Tools –IBM’s Rational Rose –many other free downloads e.g. UML Let, Visual Paradigm, Magic Draw and

Nov 29 09Dr. Kamna Malik11 Use Case Analysis is a technique to capture business process from user’s perspective Use Case Modeling

Nov 29 09Dr. Kamna Malik12 Documenting Use Cases A flow of events document is created for each use case –Written from an actor point of view Details what the system must provide to the actor when the use case is executed Typical contents –How the use case starts and ends –Normal flow of events –Alternate flow of events –Exceptional flow of events

Nov 29 09Dr. Kamna Malik13 Uses and Extends Use Case Relationships As the use cases are documented, other use case relationships may be discovered –A uses relationship shows behavior that is common to one or more use cases –An extends relationship shows optional behavior Register for courses > Logon validation > Maintain curriculum

Nov 29 09Dr. Kamna Malik14 USE CASE DIAGRAMS Helps to specify system requirements. Steps of Execution: Use case Diagrams Use Case Descriptions Class Diagrams

Nov 29 09Dr. Kamna Malik15 Use Case Diagram- Example (Point of Sales Terminal) Steps to execute: –Identify actors and Use cases –Write Use cases in high level format –Draw a Use-case Diagram –Relate Use cases –Write expanded Use cases –Rank Use cases –Identify Concepts

Nov 29 09Dr. Kamna Malik16 Step1 (Example: POST) Primary ActorUse Cases CashierLog in,Cash Out CustomerBuy Items, Refund-Items ManagerStart up, Shutdown System Admin.Add new user, Manage user

Nov 29 09Dr. Kamna Malik17 Step 2:(Example: POST) High Level Use Case Document Use Case:Buy Items Actors:Customer (Initiator), cashier Type:Primary Overview:A customer arrives at a checkout with items to purchase. The cashier records the purchase items and collects the payment. On completion, the customer leaves with the items.

Nov 29 09Dr. Kamna Malik18 Step 3 (Example POST): Create Use Case Diagram

Nov 29 09Dr. Kamna Malik19 Step 4 (Example: POST) Relate Use Cases

Nov 29 09Dr. Kamna Malik20 Step 5 (Example: POST) Expanded Use Case Use Case:Buy Items Actors:Customer (Initiator), Cashier Type:Primary Overview: Typical Course of events.....

Nov 29 09Dr. Kamna Malik21....Step 5 (Example: POST) Typical Course of events Actor Action 1.This use case begins when a customer arrives at POST checkout with items to purchase 2. The cashier records each item System Action 3. Determines the item price and adds description to the running sales transaction.

Nov 29 09Dr. Kamna Malik22....Step 5 (Example: POST) Typical Course of events Actor Action 4. On completion of item entry, the cashier indicates the sale is complete. 6. Cashier tells total to customer System Action 5. Calculates and displays sales total

Nov 29 09Dr. Kamna Malik23....Step 5 (Example: POST) Typical Course of events Actor Action 7. Customer chooses payment type: a. If cash Payment, Initiate Pay by Cash b. If Credit Payment, Initiate Pay by Credit c. If Check Payment, Initiate Pay by Check System Action 8. Logs the completed sale.

Nov 29 09Dr. Kamna Malik24....Step 5 (Example: POST) Typical Course of events Actor Action 10. Cashier gives receipt to customer 11. Customer leaves with the items purchased. System Action 9. Prints a receipt

Nov 29 09Dr. Kamna Malik25....Step 5 (Example: POST) Typical Course of events Alternative Courses (Secondary Scenarios): Invalid Item Identifier entered. Display error. Customer could not pay, cancel sale transaction. Related Use cases: Uses Pay by Cash Uses Pay by Credit Uses Pay by Check

Nov 29 09Dr. Kamna Malik26 Step 6 (Example - POST) Rank the Use cases Allocate priorities to the use cases to begin further expansion of analysis and design. E.g. We can rank them in this order (high to low): 1Buy Items5. Start up 2. Cash Out6. Shut Down 3. Refund Items7. Add Users 4. Log in8. Manage Users

Nov 29 09Dr. Kamna Malik27 Get Together … Consider Cab Dispatch System –Draw a high level use case diagram using UML notations

Nov 29 09Dr. Kamna Malik28 Example: Cab Dispatch System

Nov 29 09Dr. Kamna Malik29 Use Case Description Interaction diagrams describe how use cases are realized as interactions among societies of objects Multiple types of interaction diagrams Sequence Diagrams Interaction overview (activity + sequence diagram) Timing (state + Sequence) Communication (Collaboration)

Nov 29 09Dr. Kamna Malik30 Notation: Sequence Diagrams object1object2object3object4 Notes on what’s happening Event Event (number) constraints Event Outside the scope

Nov 29 09Dr. Kamna Malik31 Example: Sequence Diagram for sales order processing Ram: SalesPerson :Accounting:Inventory Order# 101 Selects new order Order information sent Enters customer details Items entered Item availability checked Item availability established Order information sent

Nov 29 09Dr. Kamna Malik32 Control Structures: Sequence Diagrams ADCB x {y-x<3s} Y z-y < 1s z t

Nov 29 09Dr. Kamna Malik33 …. Control Structures AB While X Loop End Loop Message *[X] Message

Nov 29 09Dr. Kamna Malik34 …. Control Structures AB If X End if Message else C [X]Message [non X] Message

Nov 29 09Dr. Kamna Malik35 Concurrent Messages AB C 1: 3: 2: Message 1 and 2 are synchronous Message 1 and 3 are asynchronous There is a transmission delay in message 3

Nov 29 09Dr. Kamna Malik36 Get Together … Revisit Cab Dispatch System –Describe any one use case scenario using sequence diagram

Nov 29 09Dr. Kamna Malik37 Activity Diagram-Example CustomerStock room Sales Request service Pay Collect Order Take Order Deliver Order Fill Order Order [Placed] Order [Entered] Order [Filled] Order [Delivered]

Nov 29 09Dr. Kamna Malik38 Communication diagrams A representation of objects and links Represents a context / scenario Has static and dynamic parts Static: Organized around the object roles Dynamic: Shows time sequence

Nov 29 09Dr. Kamna Malik39 Communication Diagrams :class name 1: event 2: event Class role Association

Nov 29 09Dr. Kamna Malik40 Communication Diagrams: Example Ram: SalesPerson :Accounting :Inventory Order# 101 1: EnterID 2: SendItem details 3: SendOrder details

Nov 29 09Dr. Kamna Malik41 Interaction Overview Diagram

Nov 29 09Dr. Kamna Malik42 UML Diagrams for Physical View Package Diagrams Component Diagrams Deployment Diagrams

Nov 29 09Dr. Kamna Malik43 Package diagram - Example

Nov 29 09Dr. Kamna Malik44 Component Diagrams Component Interface

Nov 29 09Dr. Kamna Malik45 Deployment Diagrams