This wiki has undergone a migration to Confluence found Here
Difference between revisions of "HL7 - Tooling & Electronic Services alignment"
Jump to navigation
Jump to search
Line 20: | Line 20: | ||
** ESWG is responsible for '''"collaboration tooling"''', eg. conference calls, wiki's, website, list-serves, balloting desktop | ** ESWG is responsible for '''"collaboration tooling"''', eg. conference calls, wiki's, website, list-serves, balloting desktop | ||
** Project Services is responsible for project management, i.e. project insight | ** Project Services is responsible for project management, i.e. project insight | ||
− | ** Tooling is responsible for '''"artifact design tooling"''' | + | ** Tooling is responsible for '''"artifact design tooling"''', project support, eg Gforge and source control, and publication tooling (in concert with v3 Publishing WG) |
** PIC is responsible for recommending best practices for '''"Work Group process artifact tooling"''' | ** PIC is responsible for recommending best practices for '''"Work Group process artifact tooling"''' | ||
** coordinate requests at the Steering Division level | ** coordinate requests at the Steering Division level |
Revision as of 20:19, 19 November 2009
- Objectives
- Work to crate a common understanding of information architecture
- Work to create a common understanding of infrastructure & technical architecture
- Work to create a common application architecture
- Work to reduce the tools used to meet members needs to a common uniform set
- Develop best practices for using tools
- Issues
- Multiple places to store "stuff"
- Tooling map for members to be able to do what they need to do
- Members don't know who to go to to get needs met
- Protect HL7 intellectual property and assets
- Disaster recovery - backup & restore - future proof
- Multiple tools used to do the same thing
- Insight/GForge/Wiki/Webpage used to "store artifacts"
- Solutions
- Understand which group is responsible for what sorts of information
- List of tools and what tools can be used and what they are most useful for
- Understand what purposes for which we use tools
- Understand what process to use to get tooling requirements met
- ESWG is responsible for "collaboration tooling", eg. conference calls, wiki's, website, list-serves, balloting desktop
- Project Services is responsible for project management, i.e. project insight
- Tooling is responsible for "artifact design tooling", project support, eg Gforge and source control, and publication tooling (in concert with v3 Publishing WG)
- PIC is responsible for recommending best practices for "Work Group process artifact tooling"
- coordinate requests at the Steering Division level
- see Platform Function Lists on T3SD Wiki site