Page History

{scrollbar:icons=false}
h1. {page-info:title}

|| *Time* \\ | 9:00 - 10:00 AM \\ |
|| *Date* \\ | 04/12/2010 |
|| *Location* \\ | telecon |
Lead: Denise Warzel

Moderator/Facilitator: Beate Mahious

h2. Attendees

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

h2. Apologies

Baris Suzek - Baris' update:
- Drafted the requirement gathering/use case development process as per action items from last meeting
- Provide recommendations around handling the use cases around "cyclic references" in models.

h2. Meeting Agenda

1. Review simple stories
2. Periodic table
3. Analysts present use cases
4. Assignments for this week

h2. Meeting Minutes

*1. Review simple stories*
Patrick McConnell presents the work he has done with Ram, Joshua, Alan and Tom in a brainstorming session last Thursday to come up with a "short list" of simple user stories that represent the requirements for Initiative 1 (Knowledge Repository project)

Question: Should these user stories be oriented around a feature or around scenarios?
Answer: We decide that it is more useful to write them scenario/ action oriented.

Question: Are these user stories still worded too technical?
Answer: There are two main audiences for these user stories:
a. technical modelers
b. clinician
Stories around clinician related scenarios / actions that a clinician wants to perform need to be worded less technical language.

Question: How do we ensure traceability of the user stories back to the requirements/ forum entries/...?
Answer: Each user story may relate to more than one requirement, and each requirement may relate to more than one user story. A matrix can be developed for traceability.

Question: Are the user stories we have so for all related to Init 1 (Knowledge Repository project)?
Yes, but others will be added for RE purposes.

Next steps on User stories:
\-> Look though other initiatives to add and create more complete list. (All analysts)
\-> Baris can contribute user stories related to ICR
\-> Shantanu can contribute user stories about imaging

*2. Periodic table*
Review of the [latest version of the periodic table|Semantic Infrastructure Services]

Suggestions:
- add another blue box for "transformations" in the bottom part "semantic profiles"
- some visual indication which of the items in "semantic profiles" are ISO 11179 standards?
- show rules differently?

*3. Analysts present use cases*
- postponed until next Monday

*4. Assignments for this week*
- postponed until next Monday

h2. Action Items

|| Name Responsible || Action Item || Date Due \\ || Notes \\ ||
| Patrick | place list of user stories on wiki | 4/12/2010 |--- |
| Baris | add user stories related to ICR | 4/19/2010 |--- |
| Shantanu | add user stories related to imaging | 4/19/2010 |--- |
| All Business Analysts | look through use cases and requirements of initiatives 2 through 7 for important user stories that are not covered yet | 4/19/2010 |--- |
\\
{scrollbar:icons=false}