New PDF release: Model-driven software engineering in practice

By Marco Brambilla

ISBN-10: 1608458830

ISBN-13: 9781608458837

This booklet discusses how model-based ways can increase the day-by-day perform of software program execs. this is often referred to as Model-Driven software program Engineering (MDSE) or, easily, Model-Driven Engineering (MDE). MDSE practices have proved to extend potency and effectiveness in software program improvement, as proven by way of a variety of quantitative and qualitative experiences. MDSE adoption within the software program is foreseen to Read more...

content material: 1. creation --
1.1 goal and use of versions --
1.2 Modeling for software program improvement --
1.3 tips on how to learn this ebook --
2. MDSE rules --
2.1 MDSE fundamentals --
2.2 misplaced in acronyms: the MD* jungle --
2.3 review of the MDSE technique --
2.4 MDSE adoption in --
2.5 instrument help --
2.6 Criticisms of MDSE --
three. MDSE use circumstances --
3.1 Automating software program improvement --
3.2 approach interoperability --
3.3 opposite engineering --
four. Model-driven structure (MDA) --
4.1 MDA definitions and assumptions --
4.2 The modeling degrees: CIM, PIM, PSM --
4.3 Mappings --
4.4 General-purpose and domain-specific languages in MDA --
4.5 Architecture-driven modernization --
five. Integration of MDSE on your improvement technique --
5.1 Introducing MDSE on your software program improvement technique --
5.2 conventional improvement procedures and MDSE --
5.3 Agile and MDSE --
5.4 Domain-driven layout and MDSE --
5.5 Test-driven improvement and MDSE --
6. Modeling languages at a look --
6.1 Anatomy of modeling languages --
6.2 General-purpose vs. domain-specific modeling languages --
6.3 General-purpose modeling: the case of UML --
6.4 UML extensibility: the center means among GPL and DSL --
6.5 assessment on DSLs --
6.6 Defining modeling constraints (OCL) --
7. constructing your individual modeling language --
7.1 Metamodel-centric language layout --
7.2 instance DSML: sWML --
7.3 summary syntax improvement --
7.4 Concrete syntax improvement --
eight. Model-to-model ameliorations --
8.1 version alterations and their category --
8.2 Exogenous, out-place changes --
8.3 Endogenous, in-place alterations --
8.4 studying version modifications --
nine. Model-to-text ameliorations --
9.1 fundamentals of model-driven code iteration --
9.2 Code new release via programming languages --
9.3 Code new release via M2T transformation languages --
9.4 getting to know code new release --
9.5 Excursus: code iteration via M2M differences and TCS --
10. coping with types --
10.1 version interchange --
10.2 version endurance --
10.3 version comparability --
10.4 version versioning --
10.5 version co-evolution --
10.6 international version administration --
10.7 version caliber --
10.7.1 Verifying types --
eleven. precis --
Bibliography --
Authors' biographies.
summary: This ebook discusses how model-based techniques can enhance the day-by-day perform of software program execs. this is often often called Model-Driven software program Engineering (MDSE) or, easily, Model-Driven Engineering (MDE). MDSE practices have proved to extend potency and effectiveness in software program improvement, as established via a variety of quantitative and qualitative reports. MDSE adoption within the software program is foreseen to develop exponentially within the close to destiny, e.g., because of the convergence of software program improvement and company research

Show description

Read or Download Model-driven software engineering in practice PDF

Similar systems analysis & design books

New PDF release: Practical Guide to Enterprise Architecture, A

In a pragmatic advisor to company structure, six major specialists current crucial technical, method, and company perception into each point of firm structure. you can find start-to-finish advice for architecting potent approach, software program, and service-oriented architectures; utilizing product strains to streamline firm software program layout; leveraging strong agile modeling ideas; extending the Unified method to the entire software program lifecycle; architecting presentation degrees and person event; and using the technical course of the full firm.

Read e-book online Project Management for Information Systems (5th Edition) PDF

Cadle and Yeates' venture administration for info platforms is acceptable for undergraduate scholars learning undertaking administration in the IT surroundings. This finished and functional e-book is a wonderful place to begin for any scholars of undertaking administration for info structures, whether or not they are from a computing or a enterprise historical past, at undergraduate or masters point.

Crystal Reports 2008 Official Guide by Neil Fitzgerald PDF

CRYSTAL experiences® 2008 legitimate consultant even if you’re a DBA, facts warehousing or company intelligence specialist, reporting professional, or developer, this e-book has the solutions you would like. via hands-on examples, you’ll systematically grasp Crystal reviews and Xcelsius 2008’s strongest beneficial properties for growing, allotting, and supplying content material.

Extra resources for Model-driven software engineering in practice

Example text

Drawing tools. On the other hand, many drawing tools are not modeling tools. , the tool does not deal with just shapes, lines, and arrows, but understands that they represent classes, associations, and other modeling concepts. , check that the model is a correct instance of its metamodel. ClassA * . 10: Wrong model defined with a drawing tool. The icons and shapes may be the ones defined in a given language (in the example, the UML notation) but the model may have no meaning at all, because the way elements are used breaks the language rules.

Notice that a technical space can either span both the problem and solution domains or cover only one of these aspects. 3: Technical spaces examples and coverage. 3. , through model interpretation techniques); XML and the Java framework, more oriented to implementation. During the software development process it is possible to move from one technical space to another (as represented by the arrows in the figure). This implies the availability of appropriate software artifacts (called extractors) that are able to extract knowledge from a technical space and of others (called injectors) that are able to inject such knowledge in another technical space.

There are other benefits of bringing MDSE into the development process. , by facilitating tracing back the code to the original requirements). Overall, the most direct benefits of MDE can be summarized as: increase of communication effectiveness between the stakeholders and increase in the productivity of the development team thanks to the (partial) automation of the development process. As a side effect, this automation reduces also the number of defects in the final code that could be inadvertently introduced by the developers.

Download PDF sample

Model-driven software engineering in practice by Marco Brambilla

by Steven

Rated 4.18 of 5 – based on 28 votes