...

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.Zoran Milosevic

Meeting Agenda

1. Introduction of three new Business Analysts Alan Blair, Zoran Milosevic, and Baris Suzek (5 minutes)
2. Updates to Requirement Gathering Template (5 min)
3. Review of Periodic Table ( Denise 10 minutes)
4. Presentation of use cases (Patrick - 15 min, Shantanu - 15 min)
5. Assignments for new business analysts (Denise 10 min)
6. Meeting schedule ( Beate 5 min)

Meeting Minutes

*1. Introduction of three new Business Analysts Alan Blair and Baris Suzek*

Alan and Baris share their background and experiences. Clarification of flow: Storyboard -> requirement -> use case -> sub use cases  Discussion of 5 viewpoints of RM-ODP:

1.       Business/Enterprise viewpoint
2.      Information viewpoint
3.      Computational viewpoint
4.      Engineering viewpoint
5.      Technology viewpoint

*2. Updates to Requirement Gathering Template*
Bea Mahious shows requested and implemented changes to the Requirement Statement template:

• additional line for revised statement
• additional line for link to use case
• added note to business analysts to keep "watch" on a requirement while writing a use case for it.
  Question about template titles clarified.
  New requests for changes are:
• delete "by reviewer"
• move the Statement up higher (right under the "Requirement #)
• move all descriptions from 2nd column over to first column

*3. Review of Periodic Table*
Denise presents the ppt of the periodic table and group discusses changes in layout and labeling.

*4. Presentation of use cases*
shortened due to time constraints.
Patrick has worked on:

• Medidata - revisit with Christo's feedback
• caIntegrator
• Automate
• No questions
  Denise brings up idea of placing requirement statement directly on master list to lessen the problem of incorrect or incomplete names for Forum Topics such as "Automate".

Shantanu has worked on:

• Content Browser
• No questions

*5. Assignments for new business analysts*
Alan Blair will be focusing on caDSR
Baris Suzek tbd

*6. Meeting schedule*
The group determines that a daily 15 minute meeting is not feasible for this group, because 3 analysts are not able to take part in these meetings. We decide to meet once or twice a week for one hour with the architect (Tom Digre) which will allow for a more in-depth review. Each analyst needs to be aware of what others are working on in order to determine inter-dependencies, conflicts and and to avoid duplications.
Bea Mahious presents a chart with the four time zones that the team works in. It becomes clear that some team members will have to work outside of regular business hours in order to get the entire group together.
We decide to set up a doodle poll to try and find one common time for everyone.

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

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.

Question: Does it make sense for the new Knowledge Repository Team to focus only on Initiative 1 and not include requirements regarding rules? This is how the contract is written, but can these topics be separated?
Need to follow up with Joshua Phillips on SOW.

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: https://cabig-kc.nci.nih.gov/Vocab/KC/index.php/Semantic_Infrastructure_Services^{Image Added}

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

Action Items