Elements
Elements have unique IDs which are automatically generated when they are created. It is possible to edit element IDs in tables as long as each ID remains unique within the model.
In diagrams, element IDs are displayed in a small box to the upper left of the element itself.
Elements can have one of the following metatypes:
- Annotation: a short note annotating another element
- Component: a physical component of the system of interest
- Milestone: a progress milestone
- Requirement: a need or desire that the system of interest must fulfill
- Stakeholder: a person or organization with an interest or concern in another element
Annotations can have one of the following types:
- Action: There is an action to be taken.
- Assumption: There is an assumption that has been made.
- Lesson: There is a lesson to be learnt.
- Opportunity: There is an opportunity that could be exploited.
- Risk: There is a risk that should be avoided.
Components can have one of the following types:
- Data: a data item
- Facility: a building or other structure in which a system is housed
- Hardware: a hardware item
- Organization: a company or other group of people that works together for a particular purpose
- Person: a person who performs a function of, and therefore forms a part of, the system of interest
- Product: an article that is the result of an action or process
- Project: an undertaking with pre-specified objectives, magnitude and duration
- Service: a service provided by a service provider
- Software: a software item
- System: a system (either a black box or built from other elements)
Requirements can have one of the following types:
- CDRL
- Design
- Environmental
- External Interface
- Functional
- Non-System
- Other Qualities
- Performance
- Physical
- Resource
- States / Modes