TransformingSoftwareDevelopmentAnMDARoadMap

TransformingSoftwareDevelopmentAnMDARoadMap - COVER FEATURE...

Info iconThis preview shows pages 1–2. Sign up to view the full content.

View Full Document Right Arrow Icon
COVER FEATURE Transforming Software The Model Driven Architecture initiative shifts the focus of software development from writing code to building models. At appropriate abstraction levels, such models can help customers and development teams translate their understanding of the problem domain into more reliable working code more quickly. Thonzas O. he comedian Steven Wright once quipped Meservy (www.contrih.andrew.cni~~.eci~~/-norm/ Kurt D. I SteveQuotes.html): "I have a map of the ' 1 United States ... Ithat'sI actual size. It says, Fensterrnacher , Universiry of Arizona i 'Scale: 1 mile = 1 mile.' I spent last sum- rncr tolding it." A map is a model that represents a geographic area by preserving only its relevant details in an cnsy-to-usc form; obviously, this woi~ld not be characteristic of an actual-size map. While c~lrtogrnphers create different kinds of maps in varying detail to model different geo- graphical aspects, software developers have tradi- tionally focused on a single model: code, which is the map equivalent of a photograph, displayed actual size. Models are con~monly used to flexibly represent complex systerns. Models can he viewed at many levels of abstraction, and complementary model views can he comhincd to give a morc intelligible, accurate view of a system than a single model alone. Many software development experts have long advocated using models to understand the prob- lenls that a system seeks to address,' yet develop- ment teams conlmonly employ models only in the early stages of modeling. Often, once construction begins, the teams leave the model behind and never update it to reflect their changing conceptions of the project. Most software developers would agree that mod- eling should play a role in every project. However, there is no clear consensus on what that role should be, how developers sho~~ld integrate modeling with other development activities, and who should par- ticipate in the modeling process. In 2001, the Object Management Group launched the Model Driven Architecture initiative (www. omg.orghndal) with the an~bitious goal of shifting the focus of software development from writing code to modeling. MDA is part of a larger trend within the software industry to carefully layer addi- tional levels of abstraction onto the underlying hard- ware: High-level lang~~ages have replaced assemhly language, libraries and frameworks are replacing isolated code segments in reuse, and design patterns are replacing project-specific code. Working code will always be the ultimate goal of sofrware development. MDA faces the substantial challenge of carrying models through to imple- mentation, arid current technology cannot imple- ment models as well as seasoned programmers. Nevertheless, MDA can help software development teams concentrate their efforts on modeling and generating much of the perfunctory code needed, enabling skilled developers to transform the most demanding model elements. MDA IN A NUTSHELL As the "Modeling in MDA" sidebar describes, MDA makes modeling the primary focus of the software development process. After first generat-
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 2
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 09/06/2009 for the course CIS 12414 taught by Professor Deloach,scotta during the Fall '09 term at Kansas State University.

Page1 / 7

TransformingSoftwareDevelopmentAnMDARoadMap - COVER FEATURE...

This preview shows document pages 1 - 2. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online