| Name | Activity Diagram |
| Abbreviation | ACT |
| Learning Cost | 100 |
| Playing Cost | 200 |
| Suggested Phases | 1,2 |
Engineers
| Mechanical Engineer | Industrial Design | System Engineer | Electrical Engineer | Production Engineer | Software Engineer |
| ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Technique and Issue Views
| BusinessNeeds | Stakeholder | Stakeholder Needs | System Requirements | System Structure Architecture |
| ✗ | ✗ | ✔ | ✔ | ✗ |
| System Functional Architecture | Detail Hardware Design | Detail Service Design | Detail Software Design | Manufacturing Operations |
| ✔ | ✗ | ✔ | ✗ | ✔ |
Technique Traits
| Identify Stakeholders | Elicit Needs | Remove Ambiguity | Layman's Terms | Technical Terms | Teamworkings |
| 1 | 2 | 2 | 2 | 3 | 2 |
| Traceability | Prioritizing | Exploring Breadth | Inside the Box | Outside the box | V&V |
| 0 | 0 | 0 | 0 | 0 | 0 |
Verification and Validation
| Analysis | Calculus | Inspection | Demonstration | Test |
| ✗ | ✗ | ✗ | ✗ | ✗ |
Created to allow better communication within people and departments of different expertise, activity diagrams are graphical representations of workflows of stepwise activities and actions with support for choice, iteration and concurrency. [1] Nowadays, they are mostly used in UML (unified Modelling Language) to demonstrate the logic of an algorithm. [2] This helps developers better understand how the program will flow as well as the root causes of certain events. As an activity diagram conveys a lot of information in a clear and concise way, it is also useful to ease communication with people from the business/marketing (or other) departments, that might otherwise not be able to understand the technicalities of a certain software/program.
