Parent Class(es): |
|
|---|---|
Instances: |
|
Subclasses: |
|
This is a behavioral or non-behavioral requirement of the implementation that is necessary to successfully complete the activity.
| Attribute Definitions | |||||
|---|---|---|---|---|---|
| Name | Documentation | Type | Values Allowed | Number Allowed | Assumed Value |
| Requirement_Type | This is the specific type of requirement. |
Symbol VTYPE | Availability, Efficiency, Flexibility, Interoperability, Configurability, Legal, Maintainability, Managability, Scalability, Reliability, Space, Functional | 0:1 | |
| 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:* | |
| Required_by | These are all of the implementations for which this is an feature. |
Instance VTYPE | Implementation | 0:* | |
| Comment | Some supporting documentation. |
String VTYPE | 0:* | ||
| Precondition | The state of the enterprise before the triggered use of the feature. |
String VTYPE | 0:* | ||
| Item_Categories | These are all of the categories for this item. |
Instance VTYPE | Category | 0:* | |
| Post_Conditions | The state of the enterprise after the triggered use of the feature. |
String VTYPE | 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 | ||
| Item_Review_Status | This is the review status of the item. |
Instance VTYPE | Review_Status | 0:1 | |
| Satisfied_by | These are all of them items for which this is a feature. |
Instance VTYPE | Implementation_Item | 0:* | |
| Attributes | ||||
|---|---|---|---|---|
| Name | Documentation | Type | Value | |
| Item_Source | This is the source for the information in this item. |
Instance | Writing Effective Use Cases |
|
| Aliases | These are all of the other names by which this item goes. |
Instance | Business Problem Business Requirement Non-Behavioral Requirement Non-Functional Requirement Use Case User Story |
|
| Modeling Value | This is value of including this item in the Enterprise Architecture. |
String | Requirements are very useful when users are considering changing an underlying implementation in order to more effectively or efficiently accomplish a activity. Often, business users can tell you about the messy mix of business applications and manual processes they use accomplish their activities, but can't really tell you what business problem there try to solve. The requirement class captures the problem. |
|
| Examples | These are examples of instances of this class. |
String | Must enable users to track appointment 'No Shows' Must enable users to see all their current prospects |
|