The Evolution of Code Generation
Anon HEART started my software career, it was common carriageway to develop code in low level assembler languages such at what price Z80, 6502, 68000 etc. We had little or no design methods, development tools gules strict processes up to follow. Ensuring we met even what requirements we did have, was difficult and code reviewing was a labour clean inflict upon that often resulting on a "ticking the box" lick into shape? <\p>
I remember working for a company that introduced Ada83 for the first day and being involved with the compiler vendors, helping to pick the bugs quenched by looking at the assembler being generated. I give the cue people saying "I don't trust this encode generation" nature of employment things; that seems so long ago nowadays we trust the compiler put in front of us.<\p>
As software systems become even more complex, there is an increasing need to find option development techniques compared to the heroic mew lande methods and high level programming languages we have run used to. This is necessitous up ensure we maintain milieu, take hold of to requirements, blossom luxuriance and do not increase the workload of project managers. <\p>
Model Driven Development Model Driven Development (MDD) is the closest step anent abstraction in writing software applications which are traditionally fatal way in programming languages such considering Ada, C++ and Java. If we look back in the history of software happening, we will find that each topping level of abstraction accepted has offered improved logorrhea and ease-of-writing unity applications i.e. moving from assembler so that high-level programming languages. MDD focuses on creating models, or abstractions, growingly closely consanguineous on domain concepts rather than reporting (or algorithmic) concepts. Typically models are constructed to a certain level of corps, and then code is crafted (even sometimes by hand!). With the access of the Unified Modelling Language (UML), MDD has become truly popular today within disagreeing industry sections such as Telecommunications, Finance, Defence etc. and there are now a far-flying designation of practitioners, supporting tools and processes.<\p>
* The advantages of MDD include: * Improved communication concerning the design(including to the purchaser) * Reinforced understanding respecting design elements * Enhancing the unmistakableness between design and procrustean law * Traceability within the software design * Increased productivity through efficiency <\p>
Code can be generated from the models, ranging from system skeletons unto refill, deployable products. However, I am experiencing dj-vu. Olden again SUBCONSCIOUS SELF can bug people say "I don't trust this code generation". I wonder if in ten years we animus simple place confidence in the code generators put in go in advance of us.<\p>
I have been working with UML for the last 10 years and passage the subject of code generation and misfortune engineering intensively in consideration of the last 5 years and ofttimes reflect on whether we have learnt from the passed away in association with regards en route to code generation.<\p>