1. Business Process and Functional Modeling

2. OOP Review Object-oriented development approaches are
Driven by use-cases
Architecture-centric
Iterative
Incremental

3. Introduction There are two intertwined parts to this lecture
You will learn the purpose of and how to create UML use-case and activity diagrams so as to model the function facets of business processes
You will see how to use the .NET tools to create these diagrams

4. UML Diagrams (.NET)

5. Functional UML Diagrams
Use-case diagrams depict the functional parts of an application
Activity diagrams depict the actions that occur for each use-case
So we would have one activity diagram for each use-case
I’ll go through each in turn

6. Use-cases: Introduction
Depict how users interact with a system
Depict the relationships between users
There is a graphical and narrative form
It’s a high-level interaction overview rather than a low-level detailed implementation depiction
We have other UML diagrams for that
They depict how users see the process rather than internal mechanism of how the process works
This is left to the structural and behavioral models discussed later
They are not always precise

7. Use-case: Narrative Use-case name Primary actor Stakeholders
Description
Trigger (s)
Normal flow of events
Sub-flows
Alternative flows

8. Use-cases: Elements Actors Use cases Subject boundary Relationships
Association
Include
Extend
Generalization

9. Actors Actors are depicted by stick figures
Caption contains the business name
Actors can be users or a more generalized role (business function)
Actors might provide inputs and / or receive outputs
Actors might be other systems that interact with this system
Use <<actor>> when the actor is another system
Actors can be associated with other actors

10. Use-cases A major part of system functionality
Is placed inside the system boundary
The name should be a verb-noun phrase
Manage appointments
Issue purchase order
Receive goods
Depict with a oval containing the verb-noun phrase

11. Subject Boundary
The subject boundary defines the scope of a process or system
Depict with a box surrounding use-cases
The title depicts the system or system purpose
The subject boundary might have several use-cases

12. Use Case: Example 1
Place an OFBiz sales order

13. Use Case: Example 2 From your book (an appointment system)
Manage appointments
Produce schedules
Availability

14. Use-case: Relationships
If we elaborate, there are
different kinds of relationships between actors and use cases
Relationships between actors and use-cases
Association
Include
Extend
Generalization

15. Relationships: Association
An association depicts a relationship between an actor and a use-case
A purchasing clerk issues purchase orders
Patients make appointments
A line is drawn between a use-case and an actor
An arrow appears if the information flow is one-way
A cardinality indicator appears at each end of the line

16. Relationships: Association (Example)
A CSR interacts with various use-cases via a simple association

17. Relationships: Include
An invocation of one use case by another one
Also known as a “uses” relationship
Conceptually similar to calling a function in programming
Use the <<include>> stereotype between the line connecting the use case
Common functions used by other use-cases
Verify available credit used by sales order process

18. Relationships: Include (Example)
The Billing processes uses (includes) the Verify Credit process

19. Relationships: Extend
Called an extend dependency in UML
Think of the relationship as a
Alternate course of action
Ordinary use case to issue purchase order
Alternate use-case to require supervisor approval
Alternate use-case to reevaluate suppliers

20. Relationships: Extend
Best practices tell us to use extend relationships sparingly to avoid undue complexity
For some actors, perform another process task in addition to
Depict with a dashed line and the notation <<extend>>
Arrowhead points to the base relationship

21. Relationships: Extend (Example)

22. Relationships: Generalization
From the OOP world, we are depicting an inheritance relationship between actors
An “IS-A” relationship from class diagram
Examples
A student is a person
An employee is a person
Depict with a line from inheriting actor to the inherited actor

23. Relationships: Generalization (Example)
The CSR Manager is a specialized form of a CSR

24. General Steps There are no hard and fast rules |
Define and draw the use-cases
Define and draw actors
Draw subject boundary
Add associations

25. Activity Diagrams: Introduction
Activity diagrams are similar to BPMN diagrams
The symbols roughly correspond to each other
They are similar to OOP data flow diagrams or flowcharts
Through an activity diagram, we model a business process and capture its internal logic
Usually for a specific use-case

26. Activity Diagrams: Notation
Initial node
A filled circle indicating the starting point of the activity
Use is optional but suggested to improve clarity
Final Activity node
A filled circle with an outer surrounding circle
Marks the end of the activity or object flow

27. Activity Diagrams: Notation
Depict with a rounded rectangle containing text that describes the activity
Might be physical or electronic
Control flow
Depict with a solid line from one activity to another

28. Activity Diagrams (Example 1)
Even the most simple process has an starting point, action, and an ending point

29. Activity Diagrams: Notation
Decision
A two or three way decision
A diamond symbol with one flow entering and two or more flows leaving
Merge
A diamond symbol with one many flows entering and one flow leaving
Where the decisions merge back together
These are optional

30. Activity Diagram (Decision)
A decision is made based on the results of an automated credit check

31. Activity Diagrams: Notation
Fork
A black bar with one flow entering and multiple flows leaving
A parallel fork in BPMN
Join
The close of a fork
A black bar with many flows entering and one flow leaving

32. Activity Diagrams: Notation (Example)
Parallel mixing of wet and dry ingredients

33. Activity Diagrams: Notation
Conditions
Are shown as notes attached to an activity
The condition must be true for the activity to proceed
Order is complete and verified for example
Partition
These are the swim lanes of BPMN
.NET does not support these

34. Activity Diagrams: Notation
Flow final
The process steps
Depict with a circle having an X through it
It depicts the end of an activity path but not the activity itself
Note
The UML standard note