This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

SAIF Pilot Coordination Project Closed Deliverables

From HL7Wiki
Revision as of 15:43, 10 February 2014 by Rick haddorff (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

02-10-2014:- Rick Haddorff Project Services

Return to SAIF Pilot Coordination main wiki page

Return to Main Page - SAIF Architecture Program wiki page - Work Group main page

Closed Issues / Deliverables

GForge ItemDescriptionDeliverableNotes/Links
1868Determine how to actually get the EA Software to the modelersThe process is documented in the Managing Sparx Enterprise

Architect License Distribution (via GForge > Tooling Documenation >

Files). Also Tracker 1865 is continuing work regarding this topic
Managing Sparx Enterprise Architect License Distribution
1868Pilot Coordination Deliverable: For Orders and Observations Behavioral Framework tooling selection (Enterprise Architecture): Document the relationships for who needs to be involved so the next tool we need we know who to go to and what steps to complete to obtain the software.RASCI chartRASCI OO EA Tool
N/ACan the OO CO project ballot before the SAIF IG is available? If so, can it still be within the SAIF AP umbrella?SAIF AP meeting - 08-31-2011 Yes - OO will move forward with balloting artifacts available today; Will add SAIF artifacts as they become available
2037, 2038Validation of target dates for OO Projects 797 (BF), 38 (CO), and 587 (Lab Order Template)SAIF AP meeting - 08-31-2011 Dates updated in schedule
1865Determine what steps needs to be completed to acquire the EA softwareLorraine Constable will document what steps they took to acquire EA software for the OO project and report to the team
NACreate Concept Map to document dependencies between pilot projectsRick Haddorff will create first draft of Concept Map document to be reviewed at the January 2012 WGM in San Antonio