[Index] [Process] [All issues] [In work issues] [Open NoRes issues]
Export date: 2012-11-19 06:32:58
Row | Id | Category | Summary | Details | Priority | Status | Resolution | Release | Submitter | Assignee | Closer | Date raised | Date Closed |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | 3582235![]() |
Missing characterization of Environment Assignments | The environment blocks have not been fully characterized in AP239ed2 The following Blocks: EnvironmentAssignment, EnvironmentViewDefinitionRelationship, ObservedEnvironmentAssignment, ObservedEnvironmentToDefinition, ObservedEnvironmentToDefinitionVersion, ObservedEnvironmentToDefinitionView, ObservedEnvironmentViewDefinitionRelationship, ObservationAssignment, should be added to the select below: ApprovalAssignmentSelect, CollectionMemberSelect, ConditionEvaluationAssignmentSelect ConditionEvaluationParameterSelect ConditionAssignmentSelect ConditionParameterSelect DateTimeAssignmentSelect DocumentAssignmentSelect EffectivityAssignmentSelect EvidenceSelect JustificationAssignmentSelect ObservationAssignmentSelect OrganizationOrPersonInOrganizationAssignmentSelect RequirementSourceSelect RiskPerceptionSourceAssignmentSelect SecurityClassificationAssignmentSelect TimeIntervalAssignmentSelect WorkRequestAssignmentSelect | 5 | Pending | Accepted | robbod | nobody | robbod | 2012-10-31 02:29:22 | 2012-11-12 03:36:59 | ||
2 | 3518772![]() |
PLCS PSM Model | Two types of ActivityMethodAssignment | AP239 and hence the PSM has two entities for assigning an activity method. PSM: ActivityMethodAssignment <==>AP239: Activity_method_assignment and PSM: AppliedActivityMethodAssignment <==> AP239: Applied_activity_method_assignment PSM ------------------------ ENTITY ActivityAssignment SUBTYPE OF (AssignmentObject); assignedActivity : Activity; assignedTo : SET[1:?] OF ActivityAssignmentSelect; END_ENTITY; ENTITY AppliedActivityMethodAssignment SUPERTYPE OF (ONEOF (RiskEvent, SchemeEntryAssignment, SchemeSubjectAssignment, SchemeVersionAssignment, TaskElementAssignment, TaskMethodAssignment, TaskMethodVersionAssignment)) SUBTYPE OF (AssignmentObject); assignedActivityMethod : ActivityMethod; assignedTo : SET[1:?] OF AppliedActivityMethodAssignmentSelect; END_ENTITY; ENTITY AppliedActivityMethodAssignment SUPERTYPE OF (ONEOF (RiskEvent, SchemeEntryAssignment, SchemeSubjectAssignment, SchemeVersionAssignment, TaskElementAssignment, TaskMethodAssignment, TaskMethodVersionAssignment)) SUBTYPE OF (AssignmentObject); assignedActivityMethod : ActivityMethod; assignedTo : SET[1:?] OF AppliedActivityMethodAssignmentSelect; END_ENTITY; AP239 ---------- ENTITY Activity_method_assignment; relation_type : STRING; assigned_method : Activity_method; associated_request : Work_request; END_ENTITY; ENTITY Applied_activity_method_assignment; assigned_activity_method : Activity_method; items : SET[1:?] OF activity_method_item; role : STRING; END_ENTITY; We shoudl only have one entity | 5 | Pending | Accepted | robbod | nobody | robbod | 2012-04-17 12:19:20 | 2012-10-29 03:52:38 | |
3 | 3577994![]() |
PLCS PSM Model | Simplify RequiredResource/ ManagedResource Model | The model around RequiredResource is over complicated for not a lot of added value. All following blocks can be removed and the model simplified: - RequiredResourceByRequirement - RequiredResourceByResourceItem - RequireResourceByReference - RequiredResourceRequirement - ResourceAsRealizedByResourceItem - ResourceAsRealizedByReference - ManagedResourceByReference - ManagedResourceByResourceItem Changes: - RequiredResource : non Abstract - ManagedResource : non Abstract - ResourceItem : subtype of ResourceItemSelect - RequiredResource : Add property \"item\" [1] of type ResourceItemSelect - ResourceAsRealized: Add property \"item\"[1] of type ResourceItemSelect - ManagedResource: Add property \"item\" [1] of type ResourceItemSelect See attachment: 20121018_PSM_RequiredResource_ManagedResource_changes.jpg | 5 | Pending | Accepted | phoubaux | robbod | robbod | 2012-10-18 04:55:44 | 2012-10-29 04:41:19 | |
4 | 3578091![]() |
PLCS PSM Model | Extend Select: ContractAssignmentSelect | Add the following to ContractAssignmentSelect: - WorkRequest - WorkOrder | 5 | Pending | Accepted | phoubaux | robbod | robbod | 2012-10-18 12:54:23 | 2012-10-22 08:18:16 | |
5 | 3580098![]() |
PLCS PSM Model | Extend Select: PropertyAssignmentSelect | Add the following to PropertyAssignmentSelect: - Contract - Project - Observation | 5 | Pending | Accepted | phoubaux | nobody | robbod | 2012-10-25 11:07:58 | 2012-10-29 04:41:39 | |
6 | 3580453![]() |
PLCS PSM Model | Extend select: ActivityAssignmentSelect | Add the following: - DocumentAssignment Actually all AssignmentObject should be in this select so why not adding AssignmentObject directly? | 5 | Pending | Accepted | phoubaux | robbod | robbod | 2012-10-26 07:57:58 | 2012-10-29 04:41:26 | |
7 | 3582248![]() |
PLCS PSM Model | SecurityClassificationAssignmentSelect shoudl contain produc | SecurityClassificationAssignmentSelect should contain product, productversion, productviewdefnition, observation | 5 | Pending | Accepted | robbod | robbod | robbod | 2012-10-31 03:45:36 | 2012-11-12 03:36:52 | |
8 | 3582287![]() |
PLCS PSM Model | Extend Select: EffectivityAssignmentSelect | Add the following to EffecitivtyAssignmentSelect: - CollectionMembership - CollectionAssignment | 5 | Pending | Accepted | phoubaux | robbod | robbod | 2012-10-31 06:30:55 | 2012-11-12 06:42:28 | |
9 | 3586167![]() |
PLCS PSM Model | ConditionRelationship not required | I do not think that ConditionRelationship is required. Its definition is: A ConditionRelationship is a relation between two conditions. NOTE The ConditionRelationship normally represents a logical combination of conditions. The logical type is identified by the classification of the ConditionRelationship by an ExternalOwlClass. EXAMPLE "If the engine has been running for 10000 hours AND the engine is fitted with a clog-up-quick Oil filter then change the oil filter" is an example of two conditions related by a logical AND. Right now the ConditionRelationship is used as condition parameters to a conditions It is not possible to have a Condition as a condition parameters to a condition So you have to use ConditionRelationship to represent complex logical conditions. It would be much simpler if a condition could be the input parameter to a Condition - not the ConditionRelationship This would make it more straightforward to represent boolean logic and remove ambiguity between Condition and ConditionRelationship In fact this would make Condition reflect standard programming If/Then Else constructs If I need to represent: IF A AND B THEN I can either represent this with one condition classified as an AND condition with A and B condition parameters OR I can either represent this with Three conditions. One condition with A as condition parameter and the other condition with B as condition pararmeter. These two conditions are related by a ConditionRelationship classified as an AND relationship, the ConditionRelationship is then the condition parameter to the third condition. I propose changing the definition of the ConditionRelationship to make it clear that is just a relationship. I.e. delete the NOTE Removing ConditionRelationship from ConditionParameterSelect and ConditionEvaluationParameterSelect Adding Condition to ConditionParameterSelect and ConditionEvaluationParameterSelect Changing the reference data so that the condition is classified NOT the ConditionRelationship | 5 | Pending | Accepted | robbod | robbod | robbod | 2012-11-11 07:49:45 | 2012-11-12 09:00:07 |