Page History
Wiki Markup |
---|
h1. Meeting |
...
Time
Information | *Time* \\ | 9:00 - 10:00 |
...
Date
AM \\ | | *Date* \\ | 05/17/2010 |
...
Location
...
telecon
| | *Location* \\ | telecon | Moderator/Facilitator: Beate Mahious |
...
Attendees
Denise Warzel | NCI CBIIT |
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. CDISC meeting and preparation meeting (5 minutes)
2. Google spreadsheets (10 minutes)
3. Re-organization of use cases into levels (45 minutes)
Meeting Minutes
1. CDISC meeting and preparation meeting
We decide to have an internal preparation meeting this week with Margaret Haber and Dianne Reeves.
Our plan is to meet next week we will meet with Rhonda for an interview led by Patrick regarding CDISC.
...
h2. Attendees | Denise Warzel \\ | NCI CBIIT | | 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:0; mso-generic-font-family:roman; mso-font-pitch:variable; mso-font-signature:-1610611985 1107304683 0 0 159 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, 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 h1. Meeting Minutes 1. CDISC meeting and preparation meeting We decide to have an internal preparation meeting this week with Margaret Haber and Dianne Reeves. Our plan is to meet next week we will meet with Rhonda for an interview led by Patrick regarding CDISC. 2. Google spreadsheets Discussion of B2B item's category. Can it be labeled transformation or not. The definition of "transformation" is looked up at [https://wiki.nci.nih.gov/display/EAWiki/Candidate+NCI+Enterprise+Services] and it is decided to label this requirement with "transformation". |
...
Baris shares the news that he is now the primary contact for caB2B, which is moving to Georgetown. |
...
The third column is now final and can be updated in the master list by Rick Kiefer. |
...
3. Re-organization of use cases into levels |
...
Our overall plan is to complete the following steps: |
...
1. Mapping to Candidate NCI Enterprise Services (Periodic Table) |
...
2. Organize requirements via Use Case "leveling" (using the agile levels: |
...
Summary Goals: (White) |
...
\- Cloud - Very high level, involve multiple user goals "Operate a Biospecimen Repository" |
...
\- Kite - High level, a process that takes place over several hours, days or weeks involving many steps "Find Usable Samples |
...
User Goals: (Blue) |
...
\- Sea Level - User Goal, something the actor is trying to get done - "one person, one sitting", involves several underwater or clam level |
...
\- Subfunction Goals: (Indigo or Black) |
...
\- Underwater - needed to accomplish user goals, typically can be used and reused - "Save as a File" |
...
\- Clam |
...
These should be combined with caEHR's descriptions of 'levels" that Patrick will share with the team.
The goal is to create a new wiki page with a description of each level and link to sub-use cases within each level. Many of the use case templates contain more than one use case and each one of these might be on a different level. They will be linked from this new wiki page.
...
- not usually written out in detail as a use case, "insert record into database" These should be combined with caEHR's descriptions of 'levels" that Patrick will share with the team. The goal is to create a new wiki page with a description of each level and link to sub-use cases within each level. Many of the use case templates contain more than one use case and each one of these might be on a different level. They will be linked from this new wiki page. 3. Mapping requirements to NCI Service Taxonomy Categories (Business Process, Business Capability, Core, Infrastructure/Utility). See top of: [https://wiki.nci.nih.gov/display/EAWiki/Candidate NCI Enterprise |
...
Services|https://wiki.nci.nih.gov/display/EAWiki/Candidate+NCI+Enterprise+Services#CandidateNCIEnterpriseServices-Infrastructure] - Business/Process - Arbitrarily complex services that utilize the other three service types to carry out business functions |
...
- Business 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) |
...
4. Hand-off business requirements to the architects and high priority use cases that address the gaps in SI |
...
Action Items
...
Name Responsible
...
Action Item
...
Date Due
...
Notes
...
Rick
...
update categories in master list
h2. Action Items || Name Responsible || Action Item || Date Due \\ || Notes \\ || | Rick \\ | update categories in master list \\ | 5/14/2010 |
...
done
...
Patrick
...
| done \\ | | Patrick \\ | send caEHR's descriptions of 'levels" to |
...
team \\ | 5/10/2010 |
...
done
...
Analysts
...
get use cases organized by levels
| done \\ | | Analysts \\ | get use cases organized by levels \\ | 5/17/2010 | \\ | |