Eclipse Process Framework (EPF) Project, SPARX Enterprise Architect (EA), and ALM Enablement
This article points out a problem that I see with a lot of process instances (RUP, OpenUP, etc.). The templates provided are static word documents. I know that has been par for course over the years, but SPARX EA gives us a better option for Application Lifecycle Management (ALM) Enablement.
Using SPARX EA Profiles (PLE Example here), Templates, and Artifact Exports in conjunction with EPF custom process plug-ins and guidelines allows for the mapping of artifacts to SPARX predefined or custom templates.
A major problem we found with the RUP is that it pointed to all IBM tools to get the job done. We do not use IBM tools. We have to change all the toolset language to SPARX, VSTS, VSS, and TFS.
A major problem with TFS is it has no architecture or design tools to generate useful artifacts. The process guidance is completely static. The tools to customize the MSF process are way too immature to be considered usable.
Creating an Eclipse Process Framework Project (EPF) plug-in we can point to a toolset to help get the job done, not word templates. SPARX EA has proved time and time again to be a great time saver when creating project artifacts and later keeping them up to date.
In the past I have heard the term "living document" used over and over again as an excuse for artifacts being out of date. Using a tool that dynamically creates a set of artifacts at any given time, and that is part of the daily development environment, allows living documents to actually be living documents that are up to date.
_
Using SPARX EA Profiles (PLE Example here), Templates, and Artifact Exports in conjunction with EPF custom process plug-ins and guidelines allows for the mapping of artifacts to SPARX predefined or custom templates.
A major problem we found with the RUP is that it pointed to all IBM tools to get the job done. We do not use IBM tools. We have to change all the toolset language to SPARX, VSTS, VSS, and TFS.
A major problem with TFS is it has no architecture or design tools to generate useful artifacts. The process guidance is completely static. The tools to customize the MSF process are way too immature to be considered usable.
Creating an Eclipse Process Framework Project (EPF) plug-in we can point to a toolset to help get the job done, not word templates. SPARX EA has proved time and time again to be a great time saver when creating project artifacts and later keeping them up to date.
In the past I have heard the term "living document" used over and over again as an excuse for artifacts being out of date. Using a tool that dynamically creates a set of artifacts at any given time, and that is part of the daily development environment, allows living documents to actually be living documents that are up to date.
_
posted by tadanderson at 8:02 AM
0 Comments:
Post a Comment
<< Home