Presentation on theme: "Process Redesign Stages Developing Business Vision Understanding the Existing Business Designing the New Business Installing the New Business."— Presentation transcript:
Process Redesign Stages Developing Business Vision Understanding the Existing Business Designing the New Business Installing the New Business
Case for Action Elements The Company’s Environment The Customer’s Expectations The Competitors’ Responses The Companies Business Difficulties The Company Diagnostics The Risk of Inaction
Activities of Reengineering Envisioning Reversing the Existing Business Engineering the New Business Installing the New Business Business Development Reengineering Directive The Reengineered Corporation
Envisioning Strategy Understanding the Existing Business Customer Demands Benchmarking Model of the Existing Business Reengineering Directive Objective Specification
Business Modeling Business Process (use case) Internal Process (business object) Deliverables (object) Work Flow
Use Case Model External Model –Satisfies the external customer The Business System The Actors The Use Cases
Use Case Model Good, comprehensive picture of what the business should do. Does not show internal structures needed to support Does not explain how to realize the activities
Use Case Collection of possible interactions between the system under discussion and its external actors, related to a particular goal. Clause 1 –All the interactions relate to the same goal Clause 2 –Interactions start at the triggering event and end when the goal is delivered or abandoned, and the system completes its responsibilities with respect to the interaction
Use Case redefined A collection of possible scenarios between the system under discussion and external actors, characterized by the goal the primary actor has toward the system’s declared responsibilities, showing how the primary actor’s goal might be delivered or might fail.
Scenarios A sequence of interactions happening under certain conditions, to achieve the primary actor’s goal, and having a particular result with respect to that goal. The interactions start from the triggering action and continue until the goal is delivered or abandoned, and the system completes whatever responsibilities it has with respect to the interaction.
Actors Primary actor –Has a goal requiring assistance of the system Secondary actor –One from which the system needs assistance to satisfy its goal. One is designated system under design
Interaction model Each actor has a set of responsibilities Sets goals to fulfill responsibilities Reach goals through actions Action triggers interaction with actor Interactions invoke a hierarchy of goals, responsibilities, actions, etc.
Characteristics of a Use Case Primary Actor or actors Goal Scenarios used
Characteristics of Scenario Primary actor Goal Conditions under which scenario occurs Scenario result or outcome (goal delivery or failure)
Example - Scenario System under discussion: the insurance company Primary actor: me, the claimant Goal: I get paid for my car accident Conditions: Everything is in order Outcome: Insurance company pays claim
Example – Scenario contd. Insurance company verifies claimant owns a valid policy (failure may mean goal failure) Insurance company assigns agent to examine case Agent verifies all details are within policy guidelines (interaction between agent and secondary actors) Insurance company pays claimant (implies all preceding goals succeeded)
Controlling Scenario Explosions Variations –Often a section of use case text Payment types (cash, check, credit card) Subordinate use cases –Each step is a use case. Apply hierarchical decomposition Extensions –Alternate use cases ( to handle failures)
Example – Use Case System under discussion: the insurance company Primary actor: the claimant Goal: Get paid for car accident Steps: 1.Claimant submits claim with substantiating evidence 2.Insurance company verifies claimant owns a valid policy 3.Insurance company assigns agent to examine case 4.Agent verifies all details are within policy guidelines 5.Insurance company pays the claimant
Example – Use Case contd. Extensions 1.Submitted data is incomplete 1.Insurance company requests missing information 2.Claimant supplies missing information 2.Claimant does not own a valid policy 1.Insurance company denies claim, notifies claimant, records information, terminates proceedings
Example – Use Case contd. 3.No agents are available at this time 1.(Where have they all gone?) 4.Accident violates basic policy guidelines 1.Insurance company denies claim, notifies claimant, records, terminates proceedings 2.Accident violates some minor policy guidelines 1.Insurance company begins negotiation with claimant for payment
Example – Use Case contd. Variations 1.Claimant 1.Person 2.Another company 3.Government 5.Payment 1.Check 2.Inter-bank transfer
Use Case Levels of goals Level 1: Strategic & Systems Scope –Benefits project sponsor, organization Level 2: User goal –Summary goals, user goals, subfunctions Level 3: Interaction details –Semantic interface
Goal refinement Strategic-scope Summary Goal Strategic-scope User Goal System-scope Summary Goal System-scope User Goal System-scope Subfunction
Structure of Use Cases Summary Goal Subfunction User Goal Summary Goal
Objects of Business Three types of objects Interface objects Control objects Entity objects
Interface Object Represent set of operations Each performed by one & same resource Communicates with external environment Participate in several use cases Has coordinating responsibility
Control Object Represent set of operations Life span similar to use case Represent special tasks Participate in several use cases Has no coordinating responsibility
Entity Object Represent occurrences of products and things Exists throughout the life span of business E.g., Product, Invoice, Order
Your consent to our cookies if you continue to use this website.