- Learning new or existing MDSD techniques, and all forms of rapid development and code reuse.
- Connection between MDSD and other disciplines (like AOP, Code Generation and Component-based systems)
- Networking with other MDSD professionals, opinion leaders and decision-makers in the industry
My experience of Model Driven Software Development:
- Studying Rapid Development techniques for several years
- Developing a new Model-Driven Software Engineering methodology (ABSE) and its implementation through a dedicated IDE (AtomWeaver)
"Per, I am developing a "general, all purpose, MDSD tool" like you classify it on your profile. Having such experience, can you elaborate more on this and explain to me (us all) why you "don't like / don't want / don't…"
Thank you for your kind words and for purchasing the book ;-) We tried to make the book practical and included there 5 easy to understand languages too. Feel free to comment and tell how you found it.
I noticed that you have an interest in IDE development. Using my temporal approach in an IDE would be an ideal way to advance the technology. I have several different designs if you would like to take a look. I can put the screen shots into a PDF and send it to you.
I understand the threat to programmers. But as technology advances the need to "code" as we have since the 50's is going to go away. I look forward to the better productivity and not having to code.
In my previous I tried to upload a couple of diagrams from the book. Let me know if the PDF came through.
I have been resisent to get involved in any discussions because the book is in the printing process. My publisher says it should be available on line and in stores by the end of Feb if not sooner (ISBN: 978-1-4327-3215-8). Dr. Aynur Unal is now living in Istanbul and can be reached at . My 4,847,755 patent is also very interesting if you are into Multi-Core and Hyper-Threading architectures.
What if you could reduce the size of applications by 50 percent, while cutting code complexity by a factor of three? Breaking the Time Barrier, from renowned inventor and programming expert Gordon E. Morrison, can help you do all that while dramatically increasing software reliability. The secret is COSA, Coherent Object System Architecture. This revolutionary new paradigm in software engineering, keeps control-flow and data-flow separate, and brings breakthrough time savings where it counts. The resulting applications are easier to trace, debug, validate, and reuse⎯and are free of the scourge of modern software engineering: “spaghetti code.”
Promising a Moore’s Law for software—in which software decreases in size while increasing in performance—Breaking the Time Barrier allows the technology to be consistent from the top of the model down to the binary code at the bottom. This happens through changing the architectural paradigm from the way specifications are created to the automated manufacture of the application. Breaking the Time Barrier is chock full of programming examples and clear instructions that will make it among a software engineer’s most referenced technical works.
“This technique is so powerful and adaptive that it has the potential to develop into a complete, model driven architecture and holds the possibility of eliminating programmers as we know them.”
⎯Dr. Aynur Anul, Silicon Valley, 2005