Recursive Design

Part I: Graphical Model

Graphical Model

Part II: Objects and Attributes

101. PROJECT (RD_P)

Project ( Arbitrary ID, Name, Notation, Location, Location Format, Description )

Identifiers:
Arbitrary ID

101.1. Project.Arbitrary ID (A)

Data Type: Project ID

101.2. Project.Name

Data Type: Name

101.3. Project.Notation

Data Type: Notation

101.4. Project.Location

Data Type: Project Location

101.5. Project.Location Format

Data Type: Project Location Format

101.6. Project.Description

Data Type: Description

102. DOMAIN (RD_D)

Domain ( Project, Name, Order, Domain Category, Mission Statement, Information Model )

Identifiers:
Project + Name
Project + Order

102.1. Domain.Project (R)

References:
Project.Arbitrary ID (across R101)

102.2. Domain.Name

Data Type: Name

102.3. Domain.Order (A)

Data Type: Domain Order

102.4. Domain.Domain Category

Data Type: Domain Category

102.5. Domain.Mission Statement

Data Type: Description

102.6. Domain.Information Model (R)

References:
Information Model.Arbitrary ID (across R102)

103. BRIDGE (RD_B)

Bridge ( Project, Order, Bridge ID, Client Domain, Server Domain, Client Assumptions, Server Requirements )

Identifiers:
Project + Order
Project + Bridge ID
Project + Client Domain + Server Domain

103.1. Bridge.Project (R)

References:
Project.Arbitrary ID (across R103)
Domain.Project (across R104)
Domain.Project (across R104)

103.2. Bridge.Order (A)

Data Type: Bridge Order

103.3. Bridge.Bridge ID (M)

Data Type: Bridge ID

103.4. Bridge.Client Domain (R)

References:
Domain.Name (across R104)

103.5. Bridge.Server Domain (R)

References:
Domain.Name (across R104)

103.6. Bridge.Client Assumptions

Data Type: Description

103.7. Bridge.Server Requirements

Data Type: Description

104. TASK (RD_T)

Task ( Project, Name, Order, Description )

Identifiers:
Project + Name
Project + Order

104.1. Task.Project (R)

References:
Project.Arbitrary ID (across R105)

104.2. Task.Name

Data Type: Name

104.3. Task.Order (A)

Data Type: Task Order

104.4. Task.Description

Data Type: Description

105. ACTIVITY (RD_A)

Activity ( Project, Task, Row, Column, Short Note, Long Note )

Identifiers:
Project + Task + Column

105.1. Activity.Project (P)

105.2. Activity.Task (P)

105.3. Activity.Row (M)

Data Type: Positive Integer

105.4. Activity.Column (M)

Data Type: Positive Integer

105.5. Activity.Short Note

Data Type: Description

105.6. Activity.Long Note

Data Type: Description

106. DOMAIN ACTIVITY (RD_DA)

Domain Activity ( Project, Task, Domain, Activity )

Identifiers:
Project + Task + Domain
Project + Task + Activity

106.1. Domain Activity.Project (R)

References:
Activity.Project (across R106)
Task.Project (across R107)
Domain.Project (across R107)

106.2. Domain Activity.Task (R)

References:
Activity.Task (across R106)
Task.Name (across R107)

106.3. Domain Activity.Domain (R)

References:
Domain.Name (across R107)

106.4. Domain Activity.Activity (R)

References:
Activity.Column (across R106)

107. SUBSYSTEM ACTIVITY (RD_SA)

Subsystem Activity ( Project, Task, Information Model, Subsystem, Activity )

Identifiers:
Project + Task + Information Model + Subsystem
Project + Task + Activity

107.1. Subsystem Activity.Project (R)

References:
Activity.Project (across R106)
Task.Project (across R108)

107.2. Subsystem Activity.Task (R)

References:
Activity.Task (across R106)
Task.Name (across R108)

107.3. Subsystem Activity.Information Model (R)

References:
Subsystem.Information Model (across R108)

107.4. Subsystem Activity.Subsystem (R)

References:
Subsystem.Name (across R108)

107.5. Subsystem Activity.Activity (R)

References:
Activity.Column (across R106)

Part III: Relationships

R101.Project DEFINES Domain (1:Mc)
Domain IS DEFINED BY Project

Formalization:
Domain.Project→Project.Arbitrary ID

R102.Domain DEFINES Information Model (1:1c)
Information Model IS DEFINED BY Domain

Formalization:
Domain.Information Model→Information Model.Arbitrary ID

R103.Project DEFINES Bridge (1:Mc)
Bridge IS DEFINED BY Project

Formalization:
Bridge.Project→Project.Arbitrary ID

R104.Domain ASSUMES CAPABILITIES PROVIDED BY SERVER Domain (Mc:Mc)
Domain PROVIDES CAPABILITIES REQUIRED BY CLIENT Domain
Bridge SATIFIES ASSUMPTIONS OF CLIENT Domain USING CAPABILITIES PROVIDED BY SERVER Domain 1-(Mc:Mc)

Formalization:
Bridge.Project→Domain.Project
Bridge.Client Domain→Domain.Name
Bridge.Project→Domain.Project
Bridge.Server Domain→Domain.Name

R105.Project DEFINES Task (1:Mc)
Task IS DEFINED BY Project

Formalization:
Task.Project→Project.Arbitrary ID

R106.Activity IS A (SUPERTYPE OF) Domain Activity
Activity IS A (SUPERTYPE OF) Subsystem Activity

Domain Activity IS A (SUBTYPE OF) Activity
Subsystem Activity IS A (SUBTYPE OF) Activity

Formalization:
Domain Activity.Project→Activity.Project
Domain Activity.Task→Activity.Task
Domain Activity.Activity→Activity.Column
Subsystem Activity.Project→Activity.Project
Subsystem Activity.Task→Activity.Task
Subsystem Activity.Activity→Activity.Column

R107.Task IS PERFORMED TO DELIVER Domain (Mc:Mc)
Domain DELIVERED BY PERFORMING Task
Domain Activity CAPTURES NOTES REGARDING PERFORMANCE OF Task DELIVERING Domain 1-(Mc:Mc)

Formalization:
Domain Activity.Project→Task.Project
Domain Activity.Task→Task.Name
Domain Activity.Project→Domain.Project
Domain Activity.Domain→Domain.Name

R108.Task IS PERFORMED TO DELIVER Subsystem (Mc:Mc)
Subsystem DELIVERED BY PERFORMING Task
Subsystem Activity CAPTURES NOTES REGARDING PERFORMANCE OF Task DELIVERING Subsystem 1-(Mc:Mc)

Formalization:
Subsystem Activity.Project→Task.Project
Subsystem Activity.Task→Task.Name
Subsystem Activity.Information Model→Subsystem.Information Model
Subsystem Activity.Subsystem→Subsystem.Name