This wiki has undergone a migration to Confluence found Here
Difference between revisions of "20080819 ARB Jump Start"
Jump to navigation
Jump to search
| Line 25: | Line 25: | ||
* 30 Minutes - Tooling - It is not sufficient to simply rely on automated tooling (but we should def leveraged where we can). | * 30 Minutes - Tooling - It is not sufficient to simply rely on automated tooling (but we should def leveraged where we can). | ||
* 30 Minutes - Capacity and Capability - We need to identify the "how to" as well as the phase transitions that are _easier_ and properly granulated. | * 30 Minutes - Capacity and Capability - We need to identify the "how to" as well as the phase transitions that are _easier_ and properly granulated. | ||
| − | + | 15 Minutes Break | |
| + | |||
== Empower the feedback loop from implementation back to specification development.(30 Minutes )== | == Empower the feedback loop from implementation back to specification development.(30 Minutes )== | ||
== Roles of HL7 Groups (60 Minutes) (including ArB) in | == Roles of HL7 Groups (60 Minutes) (including ArB) in | ||
Revision as of 22:10, 14 August 2008
Minutes of the 20080819 August out-of-cycle Day 1
Contents
Tuesday Morning 0800 - 1200
Review of Bernd Bobel's Document (30 minutes)
Artifacts for SOA
- (I think this is a bit of a misnomer, esp in light of BB's work - this is the intersection of MDA, SOA, RM-ODP, a software engineering process, and HL7)
Review of FW Presentation(75 Minutes )
- How SOA artifacts are diffferent, how they map to the FW, how they map to the FW
- Traceability from Requirements to Design to Implementation (Traceability across artifacts)
- 15 Minutes - Break
Cross Functional Teams and SOA Artifacts (90 Minutes)
Real World Example: NCI COPPA Information Model work / Constraint Pattern (30 minutes)
HDF is not very affected by services per se (60 minutes)
- need to show in S4 how unique SOA Artifacts support different aspects of the HDF, are created by different groups, etc.
Tuesday 1300 - 1700
Summary from above (30 minutes)
- Different groups need to expose XYZ artifacts to appropriately utilize/ support / give back to the HL7 Capability list. It is a QA issue when standards are in process.
ISCS (45 minutes)
- Detailed Structure
- Relation to Conformance Statements
- Ties from Groups
tbBAM - Structure of HL7 delivers support for customers to craft ISCS
- 30 Minutes - Tooling - It is not sufficient to simply rely on automated tooling (but we should def leveraged where we can).
- 30 Minutes - Capacity and Capability - We need to identify the "how to" as well as the phase transitions that are _easier_ and properly granulated.
15 Minutes Break
Empower the feedback loop from implementation back to specification development.(30 Minutes )
== Roles of HL7 Groups (60 Minutes) (including ArB) in
- Conformance and Compliance
- Process Mentoring
- QA
