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

Slides:



Advertisements
Similar presentations
EU funds’ evaluation plan , Latvia
Advertisements

Getting to We! Consensus Decision-Making. What is Consensus?
what is it and why do we use it?
Campus Improvement Plans
1 Vendor ITB - Sourcing User Guide. 2 Minimum System Requirements Internet connection - Modem, ISDN, DSL, T1. Your connection speed determines your access.
Monitoring and Evaluation for HES Activities
Systems Analysis and Design 9th Edition
Conversation Form l One path through a use case that emphasizes interactions between an actor and the system l Can show optional and repeated actions l.
Use-case Modeling.
Chapter 14 Requirements and Specifications. Copyright © 2005 Pearson Addison-Wesley. All rights reserved Software Engineering The implementation.
1.1 Dr. Honghui Deng Associate Professor MIS Department UNLV MIS 746 IS Project Management.
UNDERSTANDING DATA AND INFORMATION FLOW Session 4.
UML Activity Diagram. Activity Diagram  The main reason to use activity diagrams is to model the workflow behind the system being designed.  Activity.
© 2005 course technology1 1 1 University Of Palestine UML for The IT Business Analyst A practical guide to Object Oriented Requirement Gathering Hoard.
Internal Auditing and Outsourcing
Systems Development Life Cycle Dirt Sport Custom.
1 © 2005 course technology University Of Palestine Chapter 6 Storyboarding the User’s Experience.
IAEA International Atomic Energy Agency. IAEA Outline Learning Objectives The Mission Report Purpose and objectives What is not needed? Evolution of the.
Software engineering lec4 Requirements. Developing requirements Start thinking about particular problem Understand the problem  Domain analysis Gather.
© 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 1 University Of Palestine UML for The IT Business Analyst A practical guide to Object Oriented Requirement Gathering Hoard Podeswa.
1.  Describe an overall framework for project integration management ◦ RelatIion to the other project management knowledge areas and the project life.
1 UML for The IT Business Analyst A practical guide to Object Oriented Requirement Gathering Hoard Podeswa Instructor: Mrs. Eman ElAjrami 2008 University.
© 2005 course technology1 1 1 University Of Palestine UML for The IT Business Analyst A practical guide to Object Oriented Requirement Gathering Hoard.
Policy Influencing strategies & Tactics. What is Public policy? Public policy: It is a guideline to the actions of the governments in addressing societal.
Interaction Models (2): Sequence Diagrams Extracted from textbook: Object Oriented Modeling and Design with UML M. Blaha, J. Rumbaugh 1.
1 © 2005 course technology1 1 1 University Of Palestine Chapter 5 (Cont.) Scoping the IT Project with System Use Cases.
1 © 2005 course technology University Of Palestine Chapter 6 (cont.) Storyboarding the User’s Experience.
Participate in a Team to Achieve Organizational Goal
Conceptual Modelling – Behaviour
Systems Analysis and Design 8 th Edition Chapter 2 Analyzing the Business Case.
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
1 Chapter 4 Analyzing End-to-End Business Processes (cont.)
© 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 1 1 University Of Palestine UML for The IT Business Analyst A practical guide to Object Oriented Requirement Gathering Hoard.
1 Chapter 4 Analyzing End-to-End Business Processes.
1 Chapter 4 Analyzing End-to-End Business Processes.
© 2005 course technology1 1 1 University Of Palestine UML for The IT Business Analyst A practical guide to Object Oriented Requirement Gathering Hoard.
1 Capturing Requirements As Use Cases To be discussed –Artifacts created in the requirements workflow –Workers participating in the requirements workflow.
Use Case Driven Analysis Requirements Use Case Use Case Description System Sequence Diagram Chapter 5.
Chapter 4 Requirements Engineering (3/3) Yonsei University 2 nd Semester, 2015 Sanghyun Park.
Systems Accreditation Berkeley County School District School Facilitator Training October 7, 2014 Dr. Rodney Thompson Superintendent.
CS 151: Object-Oriented Design August 29 Class Meeting Department of Computer Science San Jose State University Spring 2012 Instructor: Ron Mak
Proving and Ruling a Journal Accounting 1 Chapter 3 Section 4.
Systems Analysis and Design in a Changing World, Fourth Edition
P.i.M.P.S One Brick Volunteer Retention 1. About One Brick… 2.
Lecture 14 22/10/15. The Object-Oriented Analysis and Design  Process of progressively developing representation of a system component (or object) through.
7-1 © Prentice Hall, 2007 Topic 7: Analysis Classes Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey.
Regional Dental Consultants’ Meeting Presented by Emerson Robinson, DDS, MPH Region II and V Dental Consultant.
Systems Accreditation Berkeley County School District Accreditation Team Chair Training October 20, 2014 Dr. Rodney Thompson Superintendent.
The Polling Process in Uganda.. Learning outcome (LO) The ability to explain the importance of voting, Identify polling day officials and their duties,
Prepared by Amira Selim 31 st October 2009 Revised by Dahlia Biazid Requirements Analysis.
Session 2: Developing a Comprehensive M&E Work Plan.
 Problem Analysis  Coding  Debugging  Testing.
Activity Diagrams.
The ADDIE Instructional Design Process
Sequence Diagrams.
Objectives of the Training
Object-Oriented Analysis Principles using UML
Sequence Diagrams.
The Process of Object Modeling
Activity Diagrams.
Accountability Court Certification and Peer Review
GMP Inspection Process
Chapter 13: Systems Analysis and Design
Systems Analysis and Design
Digital Stewardship Curriculum
Project Management Process Groups
Technology Assessment
Chapter 10 Problem-Solving in Groups
Presentation transcript:

© 2005 course technology1 1 1 University Of Palestine UML for The IT Business Analyst A practical guide to Object Oriented Requirement Gathering Hoard Podeswa Instructor: Mr. Ahmed Al Astal Chapter 4(Cont.) Analyzing End-to-End Business Processes

© 2005 course technology2 University Of Palestine 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.

© 2005 course technology3 University Of Palestine Activity diagram With Partitioning See Book Page 78

© 2005 course technology4 University Of Palestine Case Study D2: Business Use-Case Activity Diagram 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.

© 2005 course technology5 University Of Palestine 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.

© 2005 course technology6 University Of Palestine Case Study D2: Business Use-Case Activity Diagram with Partitions ( Cont.) 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.

© 2005 course technology7 University Of Palestine Case Study D2: Business Use-Case Activity Diagram with Partitions ( Cont.) [ 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].

© 2005 course technology8 University Of Palestine Case Study D2: Business Use-Case Activity Diagram with Partitions ( Cont.) 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”.

© 2005 course technology9 University Of Palestine Case Study D2: Business Use-Case Activity Diagram with Partitions ( Cont.) 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

© 2005 course technology10 University Of Palestine Case Study D2: Business Use-Case Activity Diagram with Partitions ( Cont.) 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.).

© 2005 course technology11 University Of Palestine Manage Case Activity diagram With Partitioning See Book Page 82

© 2005 course technology12 University Of Palestine Case Study D2: Business Use-Case Activity Diagram with Partitions ( Cont.) 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.

© 2005 course technology13 University Of Palestine Case Study D2: Business Use-Case Activity Diagram with Partitions ( Cont.) 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.

© 2005 course technology14 University Of Palestine Administer Payments Activity diagram With Partitioning See Book Page 82