NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0
Wiki Markup
{scrollbar:icons=false}
h1. {
Scrollbar
iconsfalse
page-info

...

Time

:title}

|| *Time* \\ | 9:00 - 10:00

...

Date

 AM \\ |
|| *Date* \\ | 05/17/2010

...

Location

...

telecon

 |
|| *Location* \\ | telecon |
Moderator/Facilitator: Beate Mahious

...

Attendees

Team Member

Organization

Beate Mahious

SemanticBits

Rick Kiefer

Mayo Clinic

Alan Blair

SemanticBits

Patrick McConnell

SemanticBits

Baris Suzek

Georgetown

Shantanu Deshpande

Persistent

Zoran Milosevic

Deontik

Apologies

None

Meeting||Team Member || Organization ||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

5/24/2010

---

...



h2. Attendees

||Team Member || Organization ||
| Beate   Mahious | SemanticBits |
| Rick   Kiefer | Mayo   Clinic |
| Alan Blair | SemanticBits |
| Patrick McConnell | SemanticBits |
| Baris Suzek | Georgetown |
| Shantanu Deshpande \\ | Persistent \\ |
| Zoran Milosevic \\ | Deontik \\ |

h2. Apologies

None

h2. Meeting||Team Member || Organization ||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

h2. 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)
\\

h2. 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 \\ | 5/24/2010 | ---\\ |
\\
{scrollbar:icons=false}