Parent Class(es): |
|
|---|---|
Instances: |
|
Subclasses: |
|
Principles help guide development team decisions as they aid in evaluating the pros and cons of various options. Principles are much like building codes created by cities and towns that regulate choices and construction methods.
| Attribute Definitions | |||||
|---|---|---|---|---|---|
| Name | Documentation | Type | Values Allowed | Number Allowed | Assumed Value |
| Principle_for | The are the items for which this is a principle. |
Instance VTYPE | Principled_Item | 0:* | |
| Description | A Documented Item is an item that requires descriptive text above and beyond what the reader may gain from looking at the other attributes individually. |
String VTYPE | 0:1 | ||
| Item_Source | This is the source for the information in this item. |
Instance VTYPE | Source | 0:* | |
| Aliases | These are all of the other names by which this item goes. |
Instance VTYPE | Alias | 0:* | |
| Name | This is an item that readers can identify for one another by referring to a single word, or phrase. |
String VTYPE | 1:1 | ||
| Attributes | ||||
|---|---|---|---|---|
| Name | Documentation | Type | Value | |
| Item_Source | This is the source for the information in this item. |
Instance | Constructing Blueprints for Enterprise IT Architectures |
|
| Aliases | These are all of the other names by which this item goes. |
Instance | Philosophy Rule of Thumb Guideline |
|
| Modeling Value | This is value of including this item in the Enterprise Architecture. |
String | Just like CEO's issue business objectives that cut across the business landscape, architects typically need to communicate architectural values that cut across the technical landscape. The Principle connect these statements to this technical landscape. |
|
| Examples | These are examples of instances of this class. |
String | ||