 |
Page History
| Wiki Markup |
|---|
h1. Meeting |
...
Time
Information | *Time* \\ | 9:00 - 10:00 |
...
Date
AM \\ | | *Date* \\ | 05/24/2010 |
...
Location
...
telecon
| | *Location* \\ | telecon | Moderator/Facilitator: Beate Mahious |
...
Attendees
Beate Mahious | SemanticBits |
Rick Kiefer | Mayo Clinic |
Alan Blair | SemanticBits |
Patrick McConnell | SemanticBits |
Baris Suzek | Georgetown |
Shantanu Deshpande | Persistent |
Zoran Milosevic | Deontik |
Apologies
Meeting Agenda
1.Re-organization of use cases into levels
A, Wiki page with descriptions (Patrick)
B, UML model (Patrick)
C, Wiki page with use cases in levels as text links (Shantanu)
D, table with some additional elements based on ODP and UML (Zoran)
2. Service Taxonomies
Meeting Minutes
1. Re-organization of use cases into levels
A, Wiki page with descriptions
We reviewed the wiki page with level descriptions as a group and agreed that it is good the way it is.
B, UML model
Patrick presented the UML model that he created for 8 out of about 30 use cases and their sub use cases that he has developed. The visual representation is useful and the group think it is a good way to structure all the use cases.
Shantanu and Patrick will move forward with this approach for all use cases.
C, Wiki page with use cases in levels as text links
We quickly reviewed Shantanu's levels in text format and he will take these and turn them into UML models.
D, table with some additional elements based on ODP and UML
Zoran gives an overview and walks the group through his draft document "Formalisation of use cases". This document will be shared with the group after the meeting for everyone to review.
2. Service Taxonomies
We review the definitions and decide to use this week to think about approaches on how to map the con op requirements to these four service taxonomies:
- Business/Process - Arbitrarily complex services that utilize the other three service types to carry out business functionsBusiness Capability
- Services that provide "business atoms", the data most business processes utilize
- Core - Services that provide information components to capability and business services
- Infrastructure/Utility - Services that are required or utilized by virtually all other services (most of the SI services will be seen by others as fitting into this category in order for them to build their Business Process Services)
Action Items
...
Name Responsible
...
Action Item
...
Date Due
...
Notes
...
Shantanu and Patrick
...
create UML models such as Patrick's for all use cases
...
6/1/2010
...
Patrick
...
upload and share UNL model and send out link to EA as a viewer
...
5/18/2010
...
done
...
Bea
...
share Zoran's document "Formalisation of use cases" with entire group
...
5/17/2010
...
done
...
Everyone
...
review Zoran's document "Formalisation of use cases"
...
5/24/2010
...
Everyone
...
think about approaches on how to map the con op requirements to these four service taxonomies
...
h2. Attendees
| Beate Mahious | SemanticBits |
| Rick Kiefer | Mayo Clinic |
| Alan Blair | SemanticBits |
| Patrick McConnell | SemanticBits |
| Baris Suzek | Georgetown |
| Shantanu Deshpande \\ | Persistent \\ |
| Zoran Milosevic \\ | Deontik \\ |
h2. Apologies
h1. Meeting Agenda
<!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:1; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:variable; mso-font-signature:0 0 0 0 0 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin-top:0in; margin-right:0in; margin-bottom:10.0pt; margin-left:0in; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} p.MsoNoSpacing, li.MsoNoSpacing, div.MsoNoSpacing {mso-style-priority:1; mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} .MsoPapDefault {mso-style-type:export-only; margin-bottom:10.0pt; line-height:115%;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} /* List Definitions */ @list l0 {mso-list-id:1293050125; mso-list-type:hybrid; mso-list-template-ids:497707052 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;} @list l0:level1 {mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in;} @list l0:level2 {mso-level-number-format:alpha-lower; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in;} ol {margin-bottom:0in;} ul {margin-bottom:0in;} -->
1. Re-organization of use cases into levels
A, Shantanu to present his UML model
B, Patrick to present his UML model
2. Discussion of visual representation (bubbles, stick figures,...)
3. Discussion of Community Concept
Zoran presents chart from his paper to group and group discusses the community concept.
4. Taxonomies
Mapping use cases to taxonomies can be done in UML. Levl 3 and 4 use cases can be linked to taxonomies.
Zoran will take lead on this effort with the support of Patric, who will be traveling in the next months.\\
SI Workflow:
Zorana nd Patrick will think about adding actors while working on mapping use cases to taxonomies.
h1. Meeting Minutes
1. Re-organization of use cases into levels
A, Shantanu to present his UML model
Shantanu presents his UML model and the group provides the following feedback:
Same levels should be horizontally aligned.
Some of the levels need to be adjusted.
Shantanu will make a few adjustments until next meeting.
\\
B, Patrick to present his UML model
2. Discussion of visual representation (bubbles, stick figures,...)
3. Discussion of Community Concept
4. Taxonomies
h2. Action Items
|| Name Responsible || Action Item || Date Due \\ || Notes \\ ||
| Shantanu \\ | adjustments to UML model based on feedback from group \\ | 6/1/2010 | \\ |
| Patrick \\ | \\ | 6/1/2010 | \\ |
| \\ | \\ | \\ | \\ |
| \\ | \\ | \\ | \\ |
| \\ | \\ | \\ | \\ | |
