Page info
title title

...

Lead: Denise Warzel

Moderator/Facilitator: Beate Mahious

Attendees

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.

None

Meeting Agenda

1. Update on ISO 11179 (Joshua 5 min)
2. Update on caEHR (Denise 5min)
3. Simple User Stories (30 50 min)
3.a. Presentation to leadership
3.b. Preparation for software developers

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:
https://cabig-kc.nci.nih.gov/Vocab/KC/index.php/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*

...

Update on ISO 11179
Our basic technical approach remains unchanged. ISO 11179 is not part of our requirements.

Q: Is "value domain" a 11179 term?
A: Yes, it is, but we can still use it as a domain for a particular property.

2.Update on caEHR

Dave Hau has been assigned with ca EHR ( = cancer Electronic Health Record). This week we will find out more about it and whether or not there might be another analyst involved on the caEHR side, or whether one of our analysts will take on the caEHR use cases.

3.Simple User Stories

We reviewed and discussed the following two pages:

• Patrick's simple user stories : User Story Drafts

• Rick's matrix with list of user stories and what functional profiles they address: Semantic Infrastructure Services User Story Matrix

The idea is that user story titles from the second link will link to user stories in format as displayed in the first link.

Each user story has three parts to it: Domain Description, Technical Description, and Cross Reference.

User stories need to be reviewed and if possible further consolidated to come up with the shortest list of use cases which will cover all of Initiative 1 requirements. Those will be pesented to leadership and then entered into the matrix by Alan Blair (Second link above) with an "x" in the appropriate column of functional profile that is addressed in the user stories.

Baris will take on the domain description for workflow/ pipeline.

For traceability each user story has a list of links to requirements from the master list in its "cross reference" section.

3.a.Presentation to leadership

The domain stories are fit for presentation to members of CBIIT leadership.

3.b.Preparation for software developers

The matrix is for internal use of the team to easily keep track of which user story covers with functional profile.

Action Items