Content deleted Content added
Line 12:
The tool is now relatively mature (except for some usability issues, typical of open source projects sans human factors) but the generation of open sourced process plug-ins remains problematic as adoption of the tool still requires substantial work in process authoring. The cost of process authoring is the major component of the true-cost-of-ownership of process assets, that and the training costs. Many key organizations already have key process assets drafted in navigable html or pdf that, because of their maturity, would not see an return on investment - moving to EPF - even where the tool is 'free'.
IBM has some proprietary plug-ins available for its Rational Method Composer but they are based upon the proprietary RUP process model. The small open source agile models available don't scale well to large programs. Many [[IEEE]]/[[ISO]]/[[SAE]]/[[CMMI]] and other standards models have not been modeled. The potential here is vast if IBM markets EPF/RMC to the standards organizations who already sell representations of their standards.
Static page generation is useful, as a reference site, but additional effort has to occur 1) to move towards process orchestration (based upon [[SPEM]] models) and 2) provision of training resources (potentially by including SCORM/IMS modes for export). Process training, within organizations, is of paramount concern and the amount of rework to push EPF output into [[SCORM]]/[[IMS]] ready structures for presentation in an eLearning environments (on top of the initial process authoring effort) is prohibitive. Model transformation technology may help here.
Of particular note is the fact that OMG appears to lag behind the standards organizations in the harmonizing efforts that have been going on within the software engineering world. For example, ISO/IEC IEEE/EIA [[12207]] has a model of software engineering process that is not reflected in the OMG model (process, activity, task) and consequently needs a mapping into the SPEM model.
The usability concerns wont be addressed until there is large scale adoption of the approach and interoperability issues around plug-ins drive the design to its optimum.
| |||