[Index] [Process] [All issues] [CCB issues]
Export date: 2012-10-08 12:18:02
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 | 3573370![]() |
OASIS: SchemeElement - create | Create the SchemeElement template | 5 | Open | Accepted | robbod | nobody | nobody | ||
10 | 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 | robbod | nobody |