Difference between revisions of "Tpso:Arc"
Megankatsumi (talk | contribs) |
Megankatsumi (talk | contribs) |
||
| Line 8: | Line 8: | ||
subClassOf [[accessesComplex]] only [[TransportationComplex]] | subClassOf [[accessesComplex]] only [[TransportationComplex]] | ||
| − | |||
| − | |||
subClassOf containsArc only [[tpso:Arc]] | subClassOf containsArc only [[tpso:Arc]] | ||
| Line 16: | Line 14: | ||
subClassOf supportsMode min 1 Mode | subClassOf supportsMode min 1 Mode | ||
| + | |||
| + | subClassOf associatedComplexLength exactly 1 length | ||
subClassOf hasControl only AccessRestriction | subClassOf hasControl only AccessRestriction | ||
Revision as of 17:06, 17 April 2020
Pattern
This class has been associated with the following pattern:
Subclass Of
Description
An English description of the definition (what distinguishes this sense of the term?).
A tpso:Arc is distinct from the concepts that describe the physical infrastructure in a transportation network. An Arc represents the abstract constraints and attributes that exist independent of the physical characteristics. A tpso:Arc is a kind of Manifestation; it represents an Arc at a specific moment in time. To support a representation of change over time, the same Arc object (an Arc_TimeVariant) have multiple tpso:Arc Manifestations, as depicted in the simplified example below.
<uml> @startuml
title Example Arc Manifestations
object Arc1_t1 object Arc1_t2 object Arc1_TimeVariant
Arc1_TimeVariant --> Arc1_t1 : hasManifestation
Arc1_TimeVariant --> Arc1_t2 : hasManifestation
Arc1_t1 : speed = 80kmph
Arc1_t2 : speed = 100kmph
@enduml
</uml>
Class Diagram Description
Required by Use Case(s)
(why is this specialized definition needed?)
CDM References
What other classes or properties reference this term?
Interface Specification References
This class has been associated with the following interface specification items:
Sources
Sources considered when developing the class:
Status
Pending Approval
Has Subclass(es)