The activity of developing a document specification, including graphical and textual layout and formatting.

name (O, K, I: ndt_name)

The name or label given to the activity. Inherited from activity.


ref_existence_kind (M, K, I: ref_existence_kind)

The lifecycle kind of the activity e.g. actual, planned, required or predicted. Inherited from activity.


typical_activity (O, K, I: typical_activity(activity))

Gives the typical activity which acts as the template or design for this activity. Each compose_document_specification may be an occurrence of one typical_activity. Inherited from activity.


containing_activity (O, K, I: activity(contained_activity))

Specifies the containing activity. The containing activity indicates the activity for which this activity is a component sub-activity. Constrains the time of the contained activity to be during the containing activity. Each compose_document_specification may be contained by one activity. Inherited from activity.


cost (O, I: ndt_money)

The cost of the activity. Inherited from activity.


description (O, I: ndt_comment)

A description of the activity. Inherited from activity.


duration (O, I: ndt_time)

The duration of the activity. Inherited from activity.


end_time (O, I: ndt_date_tod)

The end time of the activity. Inherited from activity.


start_time (O, I: ndt_date_tod)

The start time of the activity. Inherited from activity.


activity_classification (I, V: SET[0:?] activity_classification(activity))

This activity can be classified as one or more activity classes via the activity classification association. Each compose_document_specification may classified by one or more activity_classification. Inherited from activity.


business_associate_activity_role (I, V: SET[0:?] business_associate_activity_role(activity))

These are the roles of the business associates for the activity. For example, a service activity may have one business associate in the role of client and another in the role of vendor. Each compose_document_specification may be characterized by one or more business_associate_activity_role. Inherited from activity.


caused (I, V: SET[0:?] activity_cause_and_effect(caused_by)) (0639)

This is the association that defines those activities that this activity caused to happen. Each compose_document_specification may caused one or more activity_cause_and_effect. Inherited from activity.


cause_association (I, V: SET[0:?] transient_association(caused_by))

Indicates the various transient associations that are established as a result of this activity. For example, the movement of a material into a storage facility would cause a transient association to be established. Each compose_document_specification may cause one or more transient_association. Inherited from activity.


constrained_by (I, V: SET[0:?] schedule_constraint(constraint_for))

Gives the schedule constraints where this activity is constrained by the other activity related to this schedule constraint. Each compose_document_specification may be the activity constrained by one or more schedule_constraint. Inherited from activity.


constraint_for (I, V: SET[0:?] schedule_constraint(constrained_by))

This activity acts as a constraint, via the schedule constraint, upon the other activity related to this schedule constraint. Each compose_document_specification may constrain one or more schedule_constraint. Inherited from activity.


contained_activity (I, V: SET[0:?] activity(containing_activity))

Specifies the contained activities. Containment means that the contained activities must occur during the time of the containing activity. Each compose_document_specification may contain one or more activity. Inherited from activity.


contract (I, V: SET[0:?] contract(activity))

These are the contracts that provide specifications, requirements, or other information about this activity. For example, a contract may describe the manner in which this activity is performed. Each compose_document_specification may be a subject of one or more contract. Inherited from activity.


contractual_obligation (I, V: SET[0:?] contractual_obligation(contractual_obligation_activity))

This instance of an activity satisfies the contractual obligation. Each compose_document_specification may satisfy one or more contractual_obligation. Inherited from activity.


create_schedule (I, V: SET[0:?] schedule(create_activity))

Defines the schedules which were created by this activity. Each compose_document_specification may create one or more schedule. Inherited from activity.


data_collection (I, V: SET[0:?] data_collection(collection_content))

Indicates the data collections that include this instance of E and P data. Each compose_document_specification may be a member of one or more data_collection. Inherited from e_and_p_data.


describing_schedule (I, V: SET[0:?] schedule(described_activity))

The set of schedules that describe this activity. Each compose_document_specification may be described by one or more schedule. Inherited from activity.


document_specification (V: SET[0:?] document_specification(compose_document_specification))

Indicates the document specifications which were produced through this activity. Each compose_document_specification may produce one or more document_specification.


facility (O, I: SET[0:?] facility(activity))

Defines the facilities which were used by the activity. Each compose_document_specification may utilize one or more facility. Inherited from activity.


fulfill (I, V: SET[0:?] activity_fulfillment(fulfillment))

This defines the associations with the activities that are fulfilled by this activity. Each compose_document_specification may fulfills one or more activity_fulfillment. Inherited from activity.


fulfillment (I, V: SET[0:?] activity_fulfillment(fulfill))

This is the association that defines the activities that fulfill this activity. Each compose_document_specification may is fulfilled by one or more activity_fulfillment. Inherited from activity.


graphical_element (I, V: SET[0:?] graphical_element(depicted_object))

Specifies one or more graphical elements which are depicting this data item. Each compose_document_specification may be depicted by one or more graphical_element. Inherited from e_and_p_data.


guideline_or_privilege (I, V: SET[0:?] guideline_or_privilege(activity_subject_to_guideline)) (1223)

These are the guidelines, limitations, regulations or privileges that are specifically defined for this activity. Other general guidelines, etc., that apply to this activity are defined via the typical and class relationships (if any) defined for this activity. Each compose_document_specification may be the subject of one or more guideline_or_privilege. Inherited from activity.


guideline_or_privilege_compliance (I, V: SET[0:?] guideline_or_privilege_compliance(activity))

This describes the guidelines, limitations, regulations or privileges for which compliance information is kept for this activity. Each compliance instance defines a specific guideline, limitation, regulation or privilege and states the status of this activity with respect to it over a period of time. Each compose_document_specification may be the subject of one or more guideline_or_privilege_compliance. Inherited from activity.


populate (I, V: SET[0:?] data_collection(populated_by))

Defines the data collections whose contents were assembled from existing instances by this activity. Each compose_document_specification may populate one or more data_collection. Inherited from activity.


process_data (I, V: SET[0:?] process_data(activity))

Defines the set of instances created by this activity. Each compose_document_specification may result in values for one or more process_data. Inherited from activity.


process_data_item (I, V: SET[0:?] process_data_item(activity))

Defines the set of data used by this activity. Each compose_document_specification may use one or more process_data_item. Inherited from activity.


ref_transient_period (O, I: ref_transient_period) (1222)

The type of period over which the property applies, such as day, month, quarter, cumulative, etc. Inherited from activity.


result_of (I, V: BAG[0:1] activity_cause_and_effect(result)) (0639)

This is the association that defines the activities that caused this activity to occur. Each compose_document_specification may result of one activity_cause_and_effect. Inherited from activity.


schedule_activity (I, V: SET[0:?] schedule_activity(activity))

Shows how this activity is ordered within a schedule and, possibly with respect to other activities within the same schedule. Each compose_document_specification may be scheduled as one or more schedule_activity. Inherited from activity.


symbol_library (O: SET[0:?] symbol_library(compose_document_specification))

Indicates the usage of catalogs of symbols, patterns, and styles by this document preparation activity. Each compose_document_specification may utilize one or more symbol_library.


terminate_association (I, V: SET[0:?] transient_association(terminated_by))

Indicates the transient associations terminated by the activity. For example, transferring materials from a storage facility terminates the storage association between the material and the storage facility. Each compose_document_specification may terminate one or more transient_association. Inherited from activity.


update_collection (I, V: SET[0:?] data_collection(updated_by))

The data pointed to by this data collection was updated or created by this activity. Each compose_document_specification may updates or creates the instances contain one or more data_collection. Inherited from activity.


utilize_equipment (O, I: equipment_item(utilized_in_activity))

Defines a piece of equipment used by the activity without stating the functional usage of the equipment. This is useful for legacy data where there is knowledge about a piece of equipment but there is not enough knowledge to define a facility. Each compose_document_specification may use one equipment_item. Inherited from activity.


utilize_material (O, I: SET[0:?] material(used_by_activity)) (1223)

Indicates various materials which are utilized by this activity, such as consumables, agents, catalysts, or in other roles. Each compose_document_specification may utilize one or more material. Inherited from activity.

Local rules:

Uniqueness Constraint
name, ref_existence_kind, typical_activity, containing_activity
[I: activity] Different Related Instance
An instance of ACTIVITY cannot contain itself.
[I: activity] Different Related Instance
An instance of ACTIVITY cannot be contained by itself.
[I: activity] Instance Value Constraint
If REF_TRANSIENT_PERIOD is EVENT, then both START_TIME and END_TIME must either be blank or be identical.
[I: activity] Instance Value Constraint
If REF_TRANSIENT_PERIOD is either YEAR TO DATE, MONTH TO DATE or CUMULATIVE, then END_TIME must be instantiated.
[I: activity] Instance Value Constraint
If REF_TRANSIENT_PERIOD is ANNUAL, SEMIANNUAL, QUARTER, MONTHLY, DAILY, or HOURLY, then either both START_TIME and END_TIME are blank or both must be instantiated.
Supertype path(s):
e_and_p_data > activity > compose_document_specification.

Entity projects as table CMPS_DOC_SPEC.

Referenced in Diagrams:

• AC3: Activity Subtypes
• DMG1: Specification and Rendering