Process Redesign Stages

1. Process Redesign Stages Developing Business Vision Understanding the Existing Business Designing the New Business Installing the New Business

2. 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

3. Activities of Reengineering Business Development Reversing the Existing Business Envisioning Engineering theNew Business Installing the New Business ReengineeringDirective The Reengineered Corporation

4. Envisioning Model of the Existing Business Understanding the Existing Business Strategy Reengineering Directive Objective Specification Benchmarking CustomerDemands

5. Business Modeling • Business Process (use case) • Internal Process (business object) • Deliverables (object) • Work Flow

6. Use Case Model • External Model • Satisfies the external customer • The Business System • The Actors • The Use Cases

7. 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

8. 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

9. 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.

10. 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.

11. 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

12. 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.

13. Characteristics of a Use Case • Primary Actor or actors • Goal • Scenarios used

14. Characteristics of Scenario • Primary actor • Goal • Conditions under which scenario occurs • Scenario result or outcome (goal delivery or failure)

15. 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

16. 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)

17. 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)

18. Example – Use Case • System under discussion: the insurance company • Primary actor: the claimant • Goal: Get paid for car accident • Steps: • Claimant submits claim with substantiating evidence • Insurance company verifies claimant owns a valid policy • Insurance company assigns agent to examine case • Agent verifies all details are within policy guidelines • Insurance company pays the claimant

19. Example – Use Case contd. • Extensions • Submitted data is incomplete • Insurance company requests missing information • Claimant supplies missing information • Claimant does not own a valid policy • Insurance company denies claim, notifies claimant, records information, terminates proceedings

20. Example – Use Case contd. • No agents are available at this time • (Where have they all gone?) • Accident violates basic policy guidelines • Insurance company denies claim, notifies claimant, records, terminates proceedings • Accident violates some minor policy guidelines • Insurance company begins negotiation with claimant for payment

21. Example – Use Case contd. • Variations • Claimant • Person • Another company • Government • Payment • Check • Inter-bank transfer

22. 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

23. Goal refinement Strategic-scopeSummary Goal Strategic-scopeUser Goal System-scopeSummary Goal System-scopeUser Goal System-scopeSubfunction

24. Structure of Use Cases Summary Goal Summary Goal Summary Goal User Goal User Goal User Goal Subfunction Subfunction

25. Objects of Business • Three types of objects • Interface objects • Control objects • Entity objects

26. Interface Object • Represent set of operations • Each performed by one & same resource • Communicates with external environment • Participate in several use cases • Has coordinating responsibility

27. Control Object • Represent set of operations • Life span similar to use case • Represent special tasks • Participate in several use cases • Has no coordinating responsibility

28. Entity Object • Represent occurrences of products and things • Exists throughout the life span of business • E.g., Product, Invoice, Order