Parent Class(es): |
|
|---|---|
Instances: |
|
Subclasses: |
|
The Situation is some set of circumstances under which the implementation or data source is valid. In other words, the item is dependent on a specific situation, where the circumstances describe the facets of the situation.
| Attribute Definitions | |||||
|---|---|---|---|---|---|
| Name | Documentation | Type | Values Allowed | Number Allowed | Assumed Value |
| 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 | ||
| Similar_Circumstances | These are all of the circumstances similar to this one. |
Instance VTYPE | Circumstance | 0:* | |
| Circumstance_for_Situation | These are all of the situations for which this circumstance is a key aspect. |
Instance VTYPE | Situation | 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 | ||
| Aliases | These are all of the other names by which this item goes. |
Instance | Exception Path |
|
| Modeling Value | This is value of including this item in the Enterprise Architecture. |
String | Very few businesses have well defined processes that work the exact same way for all their customers in all situations. Typically, business people will say something like "well, in order to accomplish this activity we will use business application X, but whenever a premium customer comes then will we will use manual process Y." In this case, the circumstance would be something like "Premium Customer." |
|
| Examples | These are examples of instances of this class. |
String | Phone Fax Middle Market Satalite Patient |
|