Download Model-Driven Software Migration: A Methodology: by Christian Wagner PDF
By Christian Wagner
Today, trustworthy software program structures are the root of any company or corporation. the continual additional improvement of these structures is the crucial part in software program evolution. It calls for an immense period of time- guy energy- in addition to monetary assets. The demanding situations are dimension, seniority and heterogeneity of these software program structures. Christian Wagner addresses software program evolution: the inherent difficulties and uncertainties within the approach. He provides a model-driven strategy which results in a synchronization among resource code and layout. accordingly the version layer often is the relevant half in additional evolution and resource code turns into a derivative. For the 1st time a model-driven approach for upkeep and migration of software program platforms is defined. The strategy consists of a model-driven reengineering and a model-driven migration part. the applying and effectiveness of the strategy are proven with a reference implementation utilized to 4 exemplary systems.
Read or Download Model-Driven Software Migration: A Methodology: Reengineering, Recovery and Modernization of Legacy Systems PDF
Similar machine theory books
Mathematical Structures for Computer Science: A Modern Treatment of Discrete Mathematics
Re-creation of the vintage discrete arithmetic textual content for computing device technological know-how majors.
Argumentation offers instruments for designing, imposing and reading subtle kinds of interplay between rational brokers. It has made a great contribution to the perform of multiagent dialogues. software domain names comprise: felony disputes, enterprise negotiation, hard work disputes, crew formation, clinical inquiry, deliberative democracy, ontology reconciliation, danger research, scheduling, and logistics.
The two-volume set LNAI 9119 and LNAI 9120 constitutes the refereed lawsuits of the 14th foreign convention on man made Intelligence and gentle Computing, ICAISC 2015, held in Zakopane, Poland in June 2015. The 142 revised complete papers provided within the volumes, have been conscientiously reviewed and chosen from 322 submissions.
- Mathematics for the analysis of algorithms
- Reinforcement Learning and Dynamic Programming Using Function Approximators (Automation and Control Engineering)
- 50 Years of Artificial Intelligence - Essays Dedicated to the 50th Anniversary of Artificial Intelligence
- Parallel Processing and Applied Mathematics: 10th International Conference, PPAM 2013, Warsaw, Poland, September 8-11, 2013, Revised Selected Papers, Part I
- Theoretische Informatik: Eine kompakte Einführung
- Programmieren für Ingenieure und Naturwissenschaftler: Grundlagen
Extra resources for Model-Driven Software Migration: A Methodology: Reengineering, Recovery and Modernization of Legacy Systems
Sample text
2). 2. It was developed in the 80s in response to problems with the linearity in the waterfall model. 2, 1st quadrant) to test different aspects of the software as well as to evaluate risks. 1 Software Life Cycle 13 of a risk-based methodology. 2, 2nd quadrant). To summarize, the development of software should change from an open process towards a closed loop with user feedback [Mil76, p. 266]. Boehm also discusses the applicability of his model in the operation/maintenance phase: The iterations in the model are solely used as preliminary risk assessment for the actual software development process.
3, the demand do maintain the system and its inherent business logic, especially from an economic point of view, is very high for old systems. Because of the central importance of the systems they can not be shut down or redeveloped. 2). 1 Definition of Software Migration In this book, software migration is defined as splitting and transferring software to a new platform or technology (transformation) – with the goal to meet new requirements and to improve future maintainability. The existing functionality is to be preserved in order to prevent the loss of business knowledge.
In this context Seacord et al. [SPL03] defined this as black-box modernization. Merely knowledge of the external interfaces is required. Unfortunately, this method has solely a short term solution character. Since the basic problems are not necessarily solved. Further steps, such as the replacement of the wrapped components, are strictly necessary.