This wiki has undergone a migration to Confluence found Here
Difference between revisions of "MnM SWOT"
Jump to navigation
Jump to search
| Line 9: | Line 9: | ||
====Weaknesses==== | ====Weaknesses==== | ||
| − | * | + | *Core members have other primary interests and/or responsibilities within HL7 |
*Difficulty getting all (or even most) facilitators together to form true consensus | *Difficulty getting all (or even most) facilitators together to form true consensus | ||
| − | *Lack of bandwidth | + | *Lack of bandwidth to train new participants and Facilitators |
| + | *Lack of new participants to pass on the methodology | ||
*Difficult to track, monitor and maintain active communication with the organizations breadth of Work Groups and projects | *Difficult to track, monitor and maintain active communication with the organizations breadth of Work Groups and projects | ||
Revision as of 16:27, 6 May 2014
SWOT
Strengths, Weaknesses, Opportunities, and Threats for Modeling and Methodology Work Group (MnM)
Strengths
- Active members with strong knowledge of Methodology and its foundations
- Active members with a passion for a functional methodology
- Solid foundation in RIM and Methodology
- The HL7 membership trusts the work group to lead
Weaknesses
- Core members have other primary interests and/or responsibilities within HL7
- Difficulty getting all (or even most) facilitators together to form true consensus
- Lack of bandwidth to train new participants and Facilitators
- Lack of new participants to pass on the methodology
- Difficult to track, monitor and maintain active communication with the organizations breadth of Work Groups and projects
Opportunities
- Opening for outreach and collaboration with "non-messaging" V3
- Chance to improve collaboration with Vocabulary, SOA and Structured Documents
- Change to re-think and refactor artifacts and methodology as part of SAIF and FHIR work
- Engage w/ OMG and others to seek incorporation of key methodology constructs (design by constraint, terminology binding, etc.) into "standard" methodologies such as UML.
Threats
- Losing credibility due to inability to respond to key issues in timely fashion
- Transition to FHIR (if it occurs) could be very disruptive to the organization, creating a negative perception of MnM
- Demands of a FHIR transition may place demands on MnM the committee doesn't have the bandwidth to handle
- FHIR is consuming resources that would otherwise be directed to other responsibilities, slowing delivery times
