Content deleted Content added
Line 10:
==Issues to Resolve==
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, and because of their maturity, would not see an return on investment - moving to EPF - even where the tool is 'free'. One notable example is the [[V-Modell]].
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.
| |||