This week's book giveaway is in the OCPJP forum. We're giving away four copies of OCA/OCP Java SE 7 Programmer I & II Study Guide and have Kathy Sierra & Bert Bates on-line! See this thread for details.
people are investing a lot of time in learning things like uml , patterns etc . it is steep learning curve . learning one more modelling technique will be once again invest of time . how mush productivity can be gained by model driven artchitectures ? what is the learning curve ? what are the prerequisites ? shailesh.
Hi Sailesh, I thnk Learning UML and Patterns is like learning alphabets and words of language. Architecture is like writing a paper using those alphabets and words. So, i think we should see both of them in a different perrspective. While developing architectures we apply patterns and use UML to represent them visually. Ultimately all the patterns and UML usage boils down to laying down a architecture for the requirement. Please comment!
Ram Dhan Yadav (SCJP, SCWCD, SCJA-I, IBM EC(483))
"We are what we repeatedly do. Excellence, then, is not an act, but a habit."
how mush productivity can be gained by model driven artchitectures ?
Model driven architecture can improve productivity in many ways. Model driven architecture ensures that you , the developer, have a clear vision of system functionality before you begin to code. A model can serve as a common view of the system between the developer and the user. Therefore, misunderstandings between what the user wants and what you think they want can be corrected before the system is coded. Correcting an error in a model is almost allways simpler than correcting an error in your code. Trying to correct these problems after coding and entire system can be very time consuming and therefore productivity will be lossed. These are just a couple of benefits of having a model driven architecture. There are many other benefits but these stand out as my personal reasons for using a model based architecture.
Hi everyone, Many UML tool has a capability to generate source code from diagrams. I think it is also an advantage. So the designer can hand in the skelton of each java files with the diagram. I make a lot of mistakes. I am grad that I can visualize my idea so I can get some clitique on it before the coding. It's not absolutely necessary. I agree that learning the standard like UML is a big investment for a company or individual programmer. As far as I have heard, programmers who plactice those standards pays off the investment pretty first. Personally, I like the idea, and I intend to keep studying for a while. Shin Hashitani