Introduction to OMG UML. Updated July 2005 to reflect formal adoption of UML 2.0 Superstructure. Large enterprise applications - the ones that execute core business applications, and keep a company going - must be more than just a bunch of code modules. They must be structured in a way that enables scalability, security, and robust execution under stressful conditions, and their structure - frequently referred to as their architecture - must be defined clearly enough that maintenance programmers can (quickly!) Find and fix a bug that shows up long after the original authors have moved on to other projects. That is, these programs must be designed to work perfectly in many areas, and business functionality is not the only one (although it certainly is the essential core). Of course a well-designed architecture benefits any program, and not just the largest ones as we've singled out here. Modeling is the designing of software applications before coding. Models vs. What can you Model with UML?
UML, BPMN and Database Tool for Software Development. UML and MDA (Model Driven Architecture) Google. 2001-mda-omg-tech-drilldown-01-01-01. What is the place for MDA and UML? Chris Young:In our company we don't even get the time to make an analysis modell....Someone talked that MDA contains a platform independent language. We already have that: Java. So what do you suggest? Leaving Java and learning that MDA programming language?
Of course there are differences, but basically I think that trading Java for MDA language is just the same thing in pink color. Perhaps if you did spend more time on the analysis and you used MDA principals, then you would spend less time hand coding, then have more time for analysis on the next project :-) Actually, you make a good point about Java being platform independent already. Sure it is, if you already have written a java application you expect it will run independent of the hardware you choose (as long as there is a JVM or Application Server for that platform).
There is some up front work to write your PSM transformations, but this is akin to spending time building an assembly line for a Car factory. Model-driven architecture. Model-driven architecture (MDA) is a software design approach for the development of software systems. It provides a set of guidelines for the structuring of specifications, which are expressed as models.
Model-driven architecture is a kind of domain engineering, and supports model-driven engineering of software systems. It was launched by the Object Management Group (OMG) in 2001.[1] Overview[edit] The model-driven architecture approach defines system functionality using a platform-independent model (PIM) using an appropriate domain-specific language (DSL)[citation needed]. Then, given a platform model corresponding to CORBA, .NET, the Web, etc., the PIM is translated to one or more platform-specific models (PSMs) that computers can run. The PSM may use different DSLs or a general purpose language. The OMG organization provides rough specifications rather than implementations, often as answers to Requests for Proposals (RFPs). Related standards[edit] Trademark[edit] MDA approach[edit]