Details
Model samples
The complete modelling guidelines document can be retrieved from here.
This page provides some sample models discussed in the guidelines:
Machine state model, depicting the structure of a machine type (including sensors), some of its instances and defects.
Typical links to be set for non-visual relations (in object notebook):
- from defect to machine type (Details->For types)
- from defect to sensors (Details->Defect description->Sensor)
- from defect to process model prepared to handle the defect (Details->Recommended approach)
- from defect to skills/knowledge (in Business and Org. structure) required to handled it (Details->SkillsKnowledge->Element)
- from role/performer (in Business and Organisation structure) to the defect or machine type it can handle (Relations->SkillsKnowledge->Element)
What this sample depicts on visual level:
- A printer type decomposed in several parts, with some sensors or actuators attached to some of the parts (e.g. Toner)
- Two instances of this printer type
- Two defects (for which maintenance processes have been prepared)
Business and Organisation structure model, depicting the roles, performers and skills involved in the business.
Typical links to be set for non-visual relations (in object notebook):
- from activity (in Process models) to role or performer for which they are responsible (Relations->Assigned role)
- from business entity/role to the value they can contribute, from Value structure models (Relations->Business capabilities->Provided value)
- from business entity/performer to the role they can fulfil (Relation->fulfils)
- from role/performer to the defect or machine type they can handle or to the skill/knowledge they have (Relations->SkillsKnowledge->Element)
What this sample depicts on visual level:
- A hierarchy of business roles (supplier companies)
- A hierarchy of human roles
- Four candidate companies that can fulfil some of the business roles
- Three performers that can fulfil the human roles (in company Shirt producer A)
- Two skills that can be linked to the roles/performers
Value structure model, depicting the value decomposition of a product, a service or a mix of those.
Typical links to be set for non-visual relations (in object notebook):
- from value (configuration) to the value it is a configuration of (Relations->Configuration of)
- from value to a value that it implies (Relations-> implies)
- from value to a value that it prohibits (Relations->prohibits)
- from a business entity/role (in Business and Organisation structure) to the value it provides (Relations->Business capabilities->Provided value)
- from an activity (in a Process model) to the value it influences (Relations->Influences->Value)
What this sample depicts on visual level:
- A base product (shirt) with two customization options (material and color) and one optional part (Embroidery) which prohibits the Black colorprinter type decomposed in several parts, with some sensors or actuators attached to some of the parts (e.g. Toner)
- The customer is provided with the options of deciding on material, color and embroidery (hence the orange arrows)
- Tencel and Local product are abstract characteristics that are competitive (focus of advertising), hence the orange value symbols
Process model (app requirements), depicting the business process and required apps
Typical links to be set for non-visual relations (in object notebook):
- from activity to responsible role/performer (Relations->Assigned role)
- from activity to another process model (e.g. an interaction process) (Relations->Referenced process)
- from activity to app support from the Resource pool (Relations->Mobile IT support)
- from activity to the value it influences (Details->Influences->Value)
- from a defect (in Machine state models) to the process that can handle it (Details->Recommended approach)
What this sample depicts on visual level:
- A collaborative business process with required apps attached to most of its activities and four responsible roles (also suggested by swimlanes)
Process model (interaction process) and Mobile IT support model, depicting the interaction steps required to interact with an app
Typical links to be set for non-visual relations (in object notebook):
- from (interaction) activity to the POI (point of interaction) needed to perform the step, from a Mobile IT support model (Interaction flow attrs.-> Used POIs->POI)
- from (interaction) activity to required abstract capability from the Resource pool (Interaction flow attrs.->Required capabilities->Capability)
- from business activity (of an app requirements Process model) to the (interaction) process model that depicts its interaction with the app (Relations->Referenced process)
What this sample depicts on visual level:
- An app with one screen containing 3 POIs - one readable (e.g. a label) and two interactive (e.g. buttons)
- The flow of interacting with this screen
Orchestration model, depicting the app usage precedence.
These models are typically generated automatically for every role involved in an (app requirements) Process model. The precondition is that both roles and apps have been linked to the process model.
