© 2005 course technology1 1 1 University Of Palestine UML for The IT Business Analyst A practical guide to Object Oriented Requirement Gathering Hoard

©2005 course technology1 ©2005 course technology1 ©2005 course technology1

University Of Palestine

UML for The IT Business Analyst

A practical guide to Object Oriented Requirement GatheringHoard Podeswa

Instructor: Mr. Ahmed Al Astal

Chapter 4(Cont.)

Analyzing End-to-EndBusiness Processes

©2005 course technology2


Activity Diagrams for Describing Business Use Cases (Cont.)

Activity Diagram with Partitions:• To indicate who performs each activity, you add partitions

to the activity diagram.• A partition is a column on an activity diagram.• Each partition represents a stakeholder (business actor or

worker) that carries out some activity.• Position every activity in the partition of the object that

performs it. Name each partition at the top of the column, according to the participating object.



Activity diagram With Partitioning

See Book Page 78



Case Study D2: Business Use-Case ActivityDiagram with Partitions

• The following case study walks you through the next evolution of the CPP project.

• During this case study, you meet with stakeholders to discuss the workflow for two business use cases.

• During the meeting, you draw and revise activity diagrams in order to help stakeholders work toward a consensus regarding workflow.



Case Study D2: Business Use-Case Activity Diagram with Partitions ( Cont.)

Problem Statement:• You’ve met individually with stakeholders involved in the

business use cases, Manage case and Administer payments, in order to discuss workflow for these processes.

• Not too surprisingly, everyone has a slightly different view of how best to sequence activities, so you decide to convene a meeting to reach a consensus.

• In preparation for the meeting, you plan to create activity diagrams with partitions to summarize your best understanding of the workflow for these business processes.




Business Use Case: Manage Case (Dispute)• This example uses two sections found in the formal

template, preconditions and postconditions.• A precondition is something that must be true before the

use case begins. In the following example, a Peace Committee must already have been set up before the CPP can manage a case.

• A postcondition is something that will be true after the use case ends.




• [A postcondition on success is something that will be true after the use case ends, but only if the goal (expressed in the name of the use case) is accomplished. In the example, the postcondition on success is that a case

report has been prepared for the case being managed during the business use case].

• [A postcondition on failure (not shown in the example) is a condition that will be true after the use case is over, if it ends with abandonment of the goal].




• Precondition: “A Peace Committee has been established in the township”.

• Postcondition on success (what is true after the use case completes successfully): “A case report has been prepared”.




Flow: 1. The Peace Committee in the area initiates a Peace Gathering.2. The Peace Committee prepares an individual interview report

for each party to the dispute.3. Once all reports have been taken, the Facilitator summarizes the

reports to the Peace Gathering.4. The Facilitator verifies the facts in the reports with those

present.5. The Facilitator solicits suggestions from the gathering.6. The Facilitator solicits a consensus for a plan of action.7. If the gathering has decided to refer the case to the police, the

Facilitator escorts the parties to the police station, after which the Convener prepares a case report as per Step 10.6




Flow (Cont.): 8. If, on the other hand, a consensus has been reached, the

Facilitator appoints a Monitor.9. The Monitor performs ongoing monitoring of the case to

ensure its terms are being met.10.When the deadline for monitoring has been reached, the

ongoing monitoring immediately ends. At this time, if the conditions of the case have been met, the Convener prepares a case report. If the conditions have not been met, then the process begins again (return to Step 1.).



Manage Case Activity diagram With Partitioning

See Book Page 82




Business Use Case: Administer Payments

• Precondition (what must be true before the use case begins): A case report has been submitted.

• Postcondition on success(what is true after the use case completes successfully): Payments have been made to funds and to accounts of Peace Committee members involved in the case.




Flow: 1. The Convener reviews the case report to determine whether rules and

procedures have been followed.2. If rules and procedures have been followed:

a. The Convener marks the case as payable.b. The Convener then disburses payments to the various funds

and to the accounts of Peace Committee members who worked on the case.

c. The existing Accounts Payable system actually applies the payments.

(Constraint: The AP system must continue to be used for this purpose when the project is implemented.)

3. If the rules and procedures have not been followed, the Convener marks the case as non-payable.



Administer Payments Activity diagram With Partitioning

See Book Page 82

Documents

© 2005 course technology1 1 1 University Of Palestine UML for The IT Business Analyst A practical guide to Object Oriented Requirement Gathering Hoard