Tracker: PLCS templates  :—Issues approved by CCB and in work

[Index] [Process] [All issues] [CCB issues] [Open NoRes issues]

Export date: 2012-10-15 09:46:35

Row Id Category Summary Details Priority Status Resolution Release Submitter Assignee Closer
1 3527862 Incorrect use of OCL element allInstance() We have incorrectly used the OCL element allInstance() instead of the correct allInstances() in developing Uniqueness constraints. This needs changing in the help file and all using templates. 5 Open Accepted philsp philsp nobody
2 3558982 OASIS:PersonInOrganization needs re-structuring The current template creates a collection of PersonInOrganization relationship objects and returns a single (arbitrary?) one from the output port. There are no characterizations specified such as effectivities on the relationship or associated addresses etc. The mechanism for creating person means the same information has to be provided for a number of PIO templates. It would seem much better to have a Person template that would include characterizations of person such as Date of Birth used by most Defence organizations to uniquely identify people and use that template in the PersonInOrganization template. 5 Open Accepted philsp philsp nobody
3 3559801 OASIS:Observation fails to assign basic information The OASISObservation template currently only assigns a descriptor to the observation block, other attributes such as observedBy, observedDuring and inContext are not supported by the template meaning these cannot be assigned. 5 Open Accepted philsp philsp nobody
4 3559803 OASIS:ActualActivity - create There are no Activity templates currently defined in the OASIS context. As a result the other contexts are building their own activity templates leading to possible confusion. 5 Open Accepted philsp robbod nobody
5 3567402 OASIS:SystemElement - create Create the template OASIS:SystemElement 5 Open Accepted robbod robbod nobody
6 3571954 All Templates - Functional constraint clarification At present constraint blocks used to define functional capabilities do not clearly identify which of the ports the result(s) of te function are available on. For code generation from the template specification this is a fundamental requirement. All ports that are assigned to by OCL constraints in functional constraint blocks should be marked as ReadOnly to signify they carry the results of the OCL and should not be assigned to. 7 Open Accepted philsp nobody nobody
7 3571962 OASIS:Identification redundant context port The identification template requires a public property "context" which is assigned into the private identifier block. This is then assigned back out to a public port. Firstly this output port is redundant since the public property that is assigned into the identifier is visible in all usages of the template. Secondly the output port is identified as providing an optional context, when the template demands that the context is always present. Recommend removal of the context port and use of public property in other using templates. 5 Open Accepted philsp philsp nobody
8 3573368 OASIS:PlannedActivity - create create thePlanned Activity template properties Ids Classification plannedStartDate plannedEndDate Status Approval Creator methodPlanned Inputs 5 Open Accepted robbod robbod nobody
9 3573369 OASIS: Scheme - create Create the Scheme template 5 Open Accepted robbod robbod nobody
10 3573370 OASIS: SchemeElement - create Create the SchemeElement template 5 Open Accepted robbod robbod nobody
11 3573371 OASIS: SystemBreakdownStructure - create Create SystemBreakdownStructure template Note - in Dexlib it was called SystemStructure. In AP239e2 we have System Blocks. hence SystemStructure should be used to represent an assembly of systems 5 Open Accepted robbod emlarsson nobody
12 3573445 OASIS: ProductConfiguration - create Need a ProductConfiguration template to represent Family/Variant/etc .. of a product. 5 Open Accepted phoubaux phoubaux nobody
13 3573446 OASIS: ProductConfigurationStructure - create Need to represent product configuration structure i.e. Product Family/Variant/Options hierarchy 5 Open Accepted phoubaux phoubaux nobody
14 3573759 OASIS: ProductConfigurationOptionRelationship - create This template will represent for instance the concept of having a product configuration as an option for another product configuration. i.e.: - A gun configuration can be mounted on a vehicle configuration - A protection kit configuration can be mounted on a vehicle configuration 5 Open Accepted phoubaux phoubaux nobody
15 3573760 OASIS: Applicability - create This template will indicate that an item is valid (applicable) to another item. Will use ConditionalEffectivity for that. 5 Open Accepted phoubaux phoubaux nobody
16 3573786 OASIS: DatedEffectivity - create This template is needed to avoid repeating the same pattern all over again and to avoid mistakes. 5 Open Accepted phoubaux phoubaux nobody
17 3574157 OASIS:Justification - create Create the template It should include: Justification JustificationAssignment JustificationSupportAssignment 5 Open Accepted robbod robbod nobody
18 3574165 OASIS: Catalog - create Need generic template to represent a catalog of a product that could be used by business contexts to represent any business catalog (for instance Spare parts catalog). Will use Breakdown template for that. 5 Open Accepted phoubaux phoubaux nobody
19 3574166 OASIS: CatalogItem - create Need a generic template to represent an item in a Catalog 5 Open Accepted phoubaux phoubaux nobody
20 3574167 OASIS: CatalogItemStructure - create Need a template to represent a generic catalog item structure relationship 5 Open Accepted phoubaux phoubaux nobody
21 3574168 OASIS: CatalogItemRealization - create Need a generic template to represent a generic Catalog item realization relationship 5 Open Accepted phoubaux phoubaux nobody
22 3574403 OASIS:DirectedActivity - create Now that we have removed DirectedActivity from workorder template – on strong insistence from Patrick – I presume that we need the following templates: PlannedActivity – an activity that is planned but not controlled by a workorder ActualActivity – an actual activity that may point back a directed activity or an activity DirectedActivity – a directed activity controlled by a work order I would also suggest that we add PlannedProductUsage – to cover an activity that is planned to be performed by a product – e.g. running the engine ActualProductUsage – to cover an activity that is has to be performed by a product – e.g. sortie flown by a plane 5 Open Accepted robbod robbod nobody
23 3574404 OASIS:ActualProductUsage - create Now that we have removed DirectedActivity from workorder template – on strong insistence from Patrick – I presume that we need the following templates: PlannedActivity – an activity that is planned but not controlled by a workorder ActualActivity – an actual activity that may point back a directed activity or an activity DirectedActivity – a directed activity controlled by a work order I would also suggest that we add PlannedProductUsage – to cover an activity that is planned to be performed by a product – e.g. running the engine ActualProductUsage – to cover an activity that is has to be performed by a product – e.g. sortie flown by a plane 5 Open Accepted robbod robbod nobody
24 3574405 OASIS:BreakdownStructure - create As we have SystemBreakdownStructure - we should have BreakdownStructure 5 Open Accepted robbod robbod nobody
25 3574414 OASIS:WorkOrder - review comments 1) Work order should not be forced to create a directed activity - move the directed activity to the template directed activity 2) Why is teh State Assignment for status classified as "Status"? Is this necessary? If so we woudl need to do this consistently and will probably need a "Status" template 5 Open Accepted robbod robbod nobody
26 3574425 OASIS: BreakdownElementRealization - create Need a generic template for BreakdownElementRealization with support for identification, classification and dated effectivity 5 Open Accepted phoubaux phoubaux nobody
27 3574429 OASIS:Contract - create Create the tempate - Contract 5 Open Accepted robbod phoubaux nobody
28 3574732 OASIS:WorkRequest Uniqueness constraint not needed The Uniqueness constraint specified in the template is not required. Since, by definition, the identifiers are all unique and since all identifiers are encapsulated when used as id having a cardinality of 1 - meaning they cannot be used anywhere else. 4 Open Accepted philsp robbod nobody
29 3574736 OASIS:WorkDone - review comments 1) change the name of property "predictedWork" to directedActivity as that is more meaningful 2) change the name of property "performedMethod" to "methodUsed" as it is more meaningful and in line with template ActivityActual 3) Add location, contract, project, resourceUsed 5 Open Accepted robbod robbod nobody
30 3574746 OASIS:TaskStructure - create For initial use in the SwedishDefence context. TaskInvocation relating TaskMethodVersions. 5 Open Accepted emlarsson emlarsson nobody
31 3574748 OASIS:PhysicalBreakdownElement - create For initial use in the SwedishDefence context 5 Open Accepted emlarsson emlarsson nobody
32 3574749 OASIS:PhysicalBreakdown - create For initial use in the SwedishDefence context 5 Open Accepted emlarsson emlarsson nobody
33 3574750 OASIS:FunctionalBreakdownElement - create For initial use in the SwedishDefence context 5 Open Accepted emlarsson emlarsson nobody
34 3574751 OASIS:FunctionalBreakdown - create For initial use in the SwedishDefence context 5 Open Accepted emlarsson emlarsson nobody
35 3574752 OASIS:FaultMode - create For initial use in the SwedishDefence context. StateDefinition (classified as FaultMode) + StateDefinitionRelationShip (classified as CausedBy) to OASIS::Templates::FaultCause 5 Open Accepted emlarsson emlarsson nobody
36 3574753 OASIS:FaultEffect - create For initial use in the SwedishDefence context. OASIS::Templates::Faultmode + StateDefinitionAssignment (classified as FaultCause) 5 Open Accepted emlarsson emlarsson nobody
37 3574754 OASIS:FaultCause - create StateDefinition classified as FaultCause. May be included in OASIS::Templates::Faultmod 5 Open Accepted emlarsson emlarsson nobody
38 3574800 Invalid use of DateTimeStringProxy as public properties DateTimeStringProxy is only present due to limitations in UML. Therefore it should not be used as a public property and the more meaningful DateTimeString should be used. The proxy, if required to support a select type, should be created 'on the fly' on the parametric diagram. 5 Open Accepted philsp nobody nobody
39 3574825 Version id context needs constraining in templates. OASIS:Part and a number of other templates use version identification. We need to constrain the version identifiers so they use the identifiers as their contexts. We should also allow multiple version identifiers since they can be checked if this constraint is specified. 6 Open Accepted philsp nobody nobody