C++ Final Analysis Workflow and Activity Diagrams

• collection of transitions
• transitions between those activities

• represents actions
• should be a verb and a noun

used to partition activity diagrams

when modeling concurrent flows, you can split these using a fork and put them back together using a join

used to model complex business processes as a workflow

When state finishes it’s work, transition out of this state into the next one

• Captures the big picture
• tells a story about the desired system

• analysis classes
• use case realizations

• 50 to 100 analysis classes
• only include classes that model the vocabulary of the problem domain
• do no make implementation decisions
• focus on classes and associations
• use inheritance
• keep it simple!

• conceptual
• specification
• implementation

a diagram that represents the concepts in the domain under study

diagrams that focus on the interfaces of the software not the implementation

diagrams with classes that are going to be implemented as diagrammed