| Name | State Transition Diagram |
| Abbreviation | STD |
| 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 |
| 0 | 1 | 3 | 0 | 4 | 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 |
| ✗ | ✗ | ✗ | ✗ | ✗ |
A state diagram is a type of diagram used in computer science and related fields to describe the behaviour of systems. The base assumption is that the system can only take a finite number of states, which are represented together with the path (usually an action) needed to reach that state. These diagrams are usually used for representing object-based systems where each diagram usually represents objects of a single class and track the different states of its objects through the system [1]. State-transition diagrams describe all of the states that an object can have, the events under which an object changes state (transitions), the conditions that must be fulfilled before the transition will occur (guards), and the activities undertaken during the life of an object (actions). [2]
