Design Data Object (DDO)
A Design Data Object represents a development artifact, such as a function or requirement whose data is summarized in the form of design data attributes. The purpose context of the attributes is defined by an Project Unique Identifier (PUID) that is associated with each object.
It consists of the actual data, which is represented in the form of attributes and administrative information, such as the creation or modification date and the design data object type. The PUID defines the context of the attributes and thus the information contained in the data.
Without the context, the intended use of the data can neither be determined nor its plausibility can be checked. For example, the following attributes 'description', 'justification', 'source' can contain any data imaginable, but it is by determining the context, in this case as a requirement, that the meaning of the attributes and their interrelationship becomes clear.
Project Unique Identifier (PUID)
The Project Unique Identifier or PUID is used for the unique identification of a Design Data Objectand consists of object type and an identifier, e.g. RT-42.
- Type - Identifies the Design Data Object's type (context), e.g. RT for Requirement;
- ID - unique identifier assigned by the RePoSyD's database system.
The PUID is displayed in various places of the user interface, as well as in the documents generated from RePoSyD.
DesignData Attribute
An individual set of attributes is defined for each Design Data Object. All design data objects, their attributes as well as the design data links are defined via the meta model stored in RePoSyD and can be adapted to the respective requirements of a project.
| Name | Description | Type | Access Mode |
|---|---|---|---|
| Number | Alphanumeric number with a maximum length of 255 characters | Number | Read/Write |
| Title | Short name of the element with a length of maximum 255 characters | String | Read/Write |
| Descrption | Contains the description of the element, e.g. a requirement or function | Text | Read/Write |
| Rationale | Rationale why this requirement exists | Text | Read/Write |
| Type | Type of requirements (e.g. functional, non-functional,…) | Enumeration | Read/Write |
| Maturity Level | Maturity of requirements (e.g. initial, defined, managed,…) | Enumeration | Read/Write |
Attribute Types
- boolean: 'boolean',
- choice
- date
- datetime
- enumeration
- enumerationwithforms
- id
- number
- properties
- string
- text
- url
- useraccount
- value