Java Developer view system from "problem space"(i.e business)
- Aim: create system with objects in system to represent elements in real world
Manager/ System Analyst view system from "solution space" (i.e computer)
- Aim: assume java developer to code using the least time without understand OO
Therefore, Java Developer receive requirement in words, and requirement is tweak from the "problem space" to "solution space". For java developer to achieve his/her aim, a mapping OO design (e.g. UML) from requirements in words is a must to be carried out, however time is not given enough for this since the assumption from Manager/System Analyst without considering OO.
Maintenance problem keep arise since the code is not flexible, what Java Developer should do in this situation ?
The problem is always the same. You have managers and modelers selecting modeling tools which are not java oriented and then let the team code in Java.
The generated code from the UML tool is so mediocre that the java integration team spend more time to fix the code that to work on requirements. Once the code is fixed it is not anymore compatible with the first requirement and architecture so the modeling stage is finished
My answer is there is no answer, sorry about that
Lee Kian Giap
Joined: Jan 23, 2008
A lot of people focus to much on the function of code generating from UML , it is just a small portion , and this portion of code generating can't be mix as part of UML , it is just tool for you to auto create the code from modelled Class Diagram. So, lot of people blame that , but blame on the wrong side , is not UML fault.
The main point of using UML is it help you on analysis and design, and communicate between business and system ... and with UML, you modeling on problem space , and there is MDA to help you on architecture.
Joined: Dec 28, 2002
The problem is code generation from models which has been transformed !!
Model manipulation and transformation is today the reason of the UML mess.
UML as a language is really fantastic but EMF, GMF, other Eclipse frameworks integration is a real disaster
Actually, the Eclipse Modeling Framework (EMF) is very robust tool for building applications based on a data model.
I highlighted the key point above. If you don't have a structured data model, then you shouldn't attempt to use EMF. If you
don't know this, then you most likely will not be able to apply the EMF properly.
Aside, the EMF is a complex framework and requires an expert level knowledge of Object technology. Programmers struggling with
JSP/servlets and Googling as they go will most likely fail to comprehend the EMF.