9
« on: December 18, 2002, 05:42:55 pm »
Dear all:
I been researching MDA, UML and EA to define my company standard for software development.
Here is my understanding:
- MDA is the concept for software development by means of modeling. I like the concept. It promised that after the model is completed, it can deliver system in the next best thing platform or language without having to recode much.
- UML is language the currently been accepted to define requirements, logics of the software. I can understand some the notation can described in use cases, state diagram, collaboration diagram etc..
So... If I adopted MDA and UML using the best tools around say EA. I can model a requirement and can generate the software in the different language available.
Now, I came to a stumbling block. How much code generation can the tools out there do? From EA, it appeared only the class structure with the method name and variables. You can also generate table scripts.
To complete coding of the class means, I would have to decide on a language and add in the programming logics of the stubs generated from EA. Moving to different language mean big time reprogramming? This is not what MDA promised.
After some thoughts, I came up with the following on software development process/approach:
1. Obtain requirments
2. Jump into Class Diagram Modeling (generate class stubs)
3. Create table schema diagram (generate ddl scripts)
4. Create tables in the database (from script in 3)
5. Programs the methods in the stub (generated in 2)
6. Do user interface programming outside of the tool but use only the methods developed in (5) to access the class.
Can any of your wise ladies and gentlemen comment on my thoughts/approachs?
Peter Cheung