Aug 29, 2019 - Use Case Working Group
- Stephen White (Unlicensed)
Date
29 Aug 2019
Previous Meeting - Next Meeting
Agenda
Item / Topic | Presenter | Description |
|---|---|---|
| Discuss sub-data element issue | Stephen White (Unlicensed) | Look at options and vote on approach |
| Continue review of proposed extensions to Item /wiki/spaces/BPMPLUS/pages/420970781 | Stephen White (Unlicensed) | Walk through metamodel proposal |
| Review some notational /wiki/spaces/BPMPLUS/pages/420937838 | Stephen White (Unlicensed) | Walk through example diagrams |
Participants
Goals
List goals for this meeting (e.g., Set design priorities for FY19):
- Address any Situational Data Requirements from the Field Guide and OMG Meetings
Discussion all comments on the Item Definition update proposal
- Update document as appropriate
- Identify next steps
Notes (raw)
Everyone should look at and comment on the /wiki/spaces/BPMPLUS/pages/524419095.
We reviewed the current notation proposals on /wiki/spaces/BPMPLUS/pages/420937838 page.
Regarding Semantic References, we don't have a mechanism to insure consistency across the model elements that are similar and could have the same reference.
We discussed the Order Set items, which we are calling prototypes right now.
We could use the normal item definition unary tests to constrain the prototypes with the appropriate values. However, this needs to be context specific.
Thus the prototypes need to inherit the structures of the main item definitions, but still include their own unary tests.
Just copying Data Items in the model is not sufficient, since you would have to independently maintain all the prototypes and the source item definition if there are any changes.
We'll look at metamodel mechanism for inheritance across classes.
Chat Log
No chat log this time.
Action items
Add action items to close the loop on open questions or discussion topics:
- enter action item