UML CASE Tools
At the end of the 1980s and the beginning of the 1990s the software engineering community had high hopes for CASE tools. „If we can automate everything, why not software creation itself?" Enter Computer Aided Software Engineering (CASE). James Martin even put the use of a CASE tool as a pillar in his Rapid Application Development method.
However, how it often goes with silver bullets, the tools didn't bring the much needed rise in productivity and quality. In mainstream software engineering it went silent on the CASE tools. But not for long…
The intoduction of UML (Unified Modeling Language) brought a couple of your ago new life into the CASE tools. Computer Aided Software Engineering covers the entire process from requirements determination to the actual coding, and all intermediate steps. CASE tools offer many benefits for programmers coding. As user requirements continue to drive system complexity to new hights, the CASE tools enable us to abstract away from the entanglement of source code, to a level where architecture and design become more apparent and easier to understand and modify.
The use of UML in the tools have made it possible to exchange between different tools, and have created a proper foundation for CASE in general. The popularity of enviroments like Rational Rose indicate that this time the tools may deliver what they promise.
Related links
No comments yet. Be the first.
Leave a reply
Subscribe to my blog by email and you will receive bi-weekly a summary of my postings. As sign of my gratitude you receive the first part of my book "
Bas de Baar, blogging as "The Project Shrink", is taking his message to the International Project Management community with a vengeance: "Projects Are About Humans. Now Deal With That!" ... 
