Tracker: PLCS PSMmodel  :—Issues for CCB decision

[Index] [Process] [All issues] [In work issues]

Export date: 2012-09-03 06:58:20

Row Id Category Summary Details Priority Status Resolution Release Submitter Assignee Closer
1 3562456 PLCS PSM Model AnalysisModelObject should be classifiable AnalysisModelObject should be classifiable 5 Open Remind robbod robbod nobody
2 3562459 PLCS PSM Model RequirementSatisfiedBy should be classifiable RequirementSatisfiedBy shoudl be classifiable 5 Open Remind robbod robbod nobody
3 3562460 PLCS PSM Model RiskPerceptionContext must be classifiable The RiskPerceptionContext has no properties. It should be the same as: AnalysisRepresentationContext and have at least a description, sameAs and classifiedAs 5 Open Remind robbod robbod nobody
1 3558882 PLCS PSM Model StateAssignmentSelect does not include DocumentDefinition The current capability allows us to identify states for Digital and Physical document definitions but not the more general DocumentDefinition. Since DocumentDefinition is an instantiable supertype of PhysicalDocumentDefinition and DigitalDocumentDefinition I would sugesst removing these two and adding DocumentDefinition. 4 Pending Accepted R2.0 philsp robbod robbod
2 3558997 PLCS PSM Model Allowable units on propertydefinition It is possible to assign a property definition to a part with no value. This is used to make statements like .. all part should have these properties defined. For example an OEM could send a list of part numbers to a supplier to design the parts and a set of assigned property definitions that specify teh properties that are to be be provided. It should also be possible to specify the allowable units that are to be used for the properties. This is available in AP242. Add allowedUnits property to ExternalPropertyDefinition 5 Pending Accepted R2.0 robbod robbod robbod