SegmentDefinitionProcess

Version: 
1
Is Abstract: 
no
Is Pattern: 
no
Definition: 

Describes how the design of the segment definition is used to meet the goal of the segment definition.

Property: 
NameCardinalityDatatypeDescription
overview
0..1
A high level summary of this process of defining segments
Relationship: 
NameTarget ObjectDescriptionSource cardinalityTarget cardinalityRelationship type
isDiscussedIn
External materials that describe or discuss the process.
0..n
0..n
Neither
hasDesign
Informs the specific process by providing the underlying rationale, rules and general preconditions for the segment definition process.
0..1
0..1
Neither
hasPrecondition
Any condition that must be met prior to the process being implemented.
0..n
0..n
Aggregation
hasProcessSequence
The process step(s) that initiate the detailed process.
0..1
0..n
Neither
hasResults
The end result of the process of segment definition.
0..n
0..n
Neither
implementsAlgorithm
An implementation and/or execution of an algorithm which is associated with the design of the segment definition process.
0..n
0..n
Neither
realizes
Takes the role of a process for segment definition.
0..n
1..1
Neither
definesSegments
The process produces location specifications for a set of segments
0..n
0..1
Neither

Stage:

Is extendable: 
Is property: 
0
RDF Mapping: 

Comments

Doesn't hasResults and definesSegments mean the same thing? This may just be a leftover from earlier process and methodology patterns. Should be reviewed.