20230720105151_Session 9 - COMP6798001 - Business Process and Functional Modeling

Page 1: Title Slide

• Title: BINUS HIGHER EDUCATION BUSINESS PROCESS AND FUNCTIONAL MODELING

• Session 9

• Subject Matter Expert: Muhammad Amien Ibrhaim, S.Kom., M.Sc.

Page 2: Sub Topics

• Introduction

• Business Process Identification using Use Case Diagram

• Business process Modeling using Activity Diagram

• Business Process Documentation: use case Description

• Verifying and validating functional Model

• Applying the concepts

• Data Flow Diagram

Page 3: Acknowledgment

• Adapted from:

  • Alan Dennis, Barbara Haley Wixom, David Tegarden (2015).

  • Title: Systems Analysis and Design_ An Object-Oriented Approach with UML, 5th ed.

  • ISBN: 978-1-118-80467-4, Chapter 4

Page 4: Learning Outcomes

• At the end of this lecture, students are able to:

  • LO3: To analyze the requirement of a system

Page 5: Introduction to Object-Oriented Systems Development

• Use-case driven, architecture-centric, iterative and incremental approaches.

• Use Case: Represents interaction between business system and its environment.

• Provides a high-level overview of business processes.

• Supporting the creation of an external or functional view of a business process.

Page 6: Introduction Continued

• Object-oriented systems are developed incrementally and iteratively.

• Activity Diagrams:

  • Used to enhance understanding of business processes.

  • Useful for any process-modeling activity.

  • Logical model that describes activities without suggesting execution methods.

Page 7: Introduction to Business Process Modeling

• Steps:

  • Identifying business processes using use cases and diagrams.

  • Modeling processes with activity diagrams.

  • Creating use-case descriptions, their elements, and guidelines.

  • Verification and validation of processes and functional models.

Page 8: Use-Case Diagrams

• Elements of Use-Case Diagrams:

  • Actor:

    • External person/system benefiting from the subject.

    • Depicted as a stick figure or rectangle for non-human actors.

    • Labeled with their role and can indicate specialization.

  • Use Case:

    • Represents major functionality, can extend/include other use cases.

    • Labeled descriptively and placed inside the system boundary.

  • Subject Boundary:

    • Scope inclusion (name inside/on top).

Page 9: Relationships in Use-Case Diagrams

• Association Relationship: - Links actors with use cases.

• Include Relationship:

  • Functionality inclusion of one use case in another.

• Extend Relationship:

  • Extension to include optional behavior; denoted with arrows.

• Generalization Relationship:

  • Specialization to generalized use cases.

Page 10: Example Use Case Diagram for Appointment System

• Actors:

  • Patient

  • Doctor

  • Management

• Use Cases:

  • Manage Appointments

  • Produce Schedules

  • Record Availability

Page 11: Association in Use-Case Diagrams

• Use cases are connected to actors through association relationships representing two-way communication.

• One-way communication indicated by a solid arrowhead.

• Multiplicity of associations can be represented.

Page 12: Reinforcement of Key Concepts in Use Cases

• Association use cases and actor connections emphasized.

Page 13: Specialized Actor Use Case

• Use Case: Appointment System

  • Manage Appointments, Patient interaction.

  • Produce Schedules

  • Management's role and involvement in recording.

Page 14: Include and Extend Relationships Example

• Use Case Diagram: Appointment System with

  • Manage Appointments, Make Payment Arrangements, etc.

Page 15: Mini Case: Campus Housing

• Overview:

  • Campus housing helps students find rental units.

  • Owners submit unit info, students search via web.

  • Apartment listings updated accordingly.

Page 16: Campus Housing System Diagram

• Key interactions include:

  • Maintain Available Rental Unit Information

  • Search Available Rentals - Student and Owner roles highlighted.

Page 17: Use Case Development Steps

• Process for requirements:

  1. Review Requirements Definition

  2. Identify Subject Boundaries

  3. Identify Primary Actors & Goals

  4. Identify Business Processes & Major Use Cases

  5. Review Current Set of Use Cases.

Page 18: Steps to Create Use Case Diagram

• 1. Place & Draw Use Cases

• 2. Place & Draw Actors

• 3. Draw Subject Boundary

• 4. Add Associations

Page 19: Elements of Activity Diagram

• Action: Nondecomposable behavior, labeled by name.

• Activity: Set of actions, also labeled.

• Control Flow: Sequence of execution.

• Object Flow: Flow between activities/actions.

• Nodes: Initial, final, decision, merge, fork, join, swimlane, etc. explained.

Page 20: Activity Diagram Node Functions

• Decision Node: Represents conditions determining control flow paths.

• Fork Node: Splits behavior into concurrent flows; Join Node brings them back together.

• Swimlane: Organizes responsibilities within an activity diagram.

Page 21: Example Activity Sequence

• Activities Include:

  • Get Patient Information

  • Create New Patient Appointment

  • Make Payment Arrangements

  • Change or Cancel Appointments.

Page 22: Guidelines for Creating Activity Diagrams

• Set the scope and context for modeling.

• Identify activities, control flows, and object flows.

• Recognize decision-making points and potential parallelism in processes.

Page 23: Steps to Create Activity Diagram

• 1. Choose a Business Process

• 2. Identify Activities

• 3. Identify Control Flows & Nodes

• 4. Identify Object Flows & Nodes

• 5. Create Diagram Layout.

Page 24: Mini Case: Activity Diagram (Campus Housing)

• Activities: Adding/removing rental units.

  • Owners provide details and notify removals.

Page 25: Campus Housing Activities Detailed

• Actions for Rental Units:

  • Capture Location, Bedrooms, Monthly Rent, etc.

  • Manage Add/Delete Processes via the service.

Page 26: Business Process Documentation with Use Cases

• Types of Use Cases:

  • Overview Use Case: Basic info laid out early.

  • Detail Use Case: Comprehensive necessary details.

  • Essential Use Case: Core functionalities only.

  • Real Use Case: Specific steps outlined.

Page 27: Elements of a Use Case Description

• Components include: Name, Actors, Overview, Stakeholders, Trigger, Relationships, Flows, Sub Flows, Exceptions.

Page 28: Guidelines for Writing Use-Case Descriptions

• Clearly express actions from an observer's perspective.

• Maintain consistent abstraction level and logical action sequences.

Page 29: Verification and Validation

• Walkthrough: Peer review process identifying errors, does not fix them.

• Functional Model Verification includes ensuring consistency among activity diagrams, use-case descriptions, and diagrams.

Page 30: Data Flow Diagrams (DFD)

• Graphical representation of data flow with several characteristics such as supporting analysis stage and describing activities/processes.

Page 31: DFD Symbols

• Key elements: External Entity, Process, Data Flow, Data Store.

Page 32: DFD Types

• Context Diagram: Highest abstraction, shows scope and interactions.

• Level 0: Major processes and data flows; further decomposed subsequently.

Page 33: Context Diagram Example

• Depicts relationships between customer orders and kitchen processes.

Page 34: Level 1 DFD Breakdown

• Details the system’s major components and information flows.

Page 35: Context Diagram and Decomposition Framework

• Representation of the hierarchical system structure.

Page 36: References

• Alan Dennis, Barbara Haley Wixom, David Tegarden (2015).

• Systems Analysis and Design_ An Object-Oriented Approach with UML, 5th ed.

• ISBN: 978-1-118-80467-4.