Model Transformation

Abstract

In a classic approach to software development, the requirements and analysis stages are a largely informal and iterative process. At a certain point in time, specifications are considered to be (more or less) finalised and they are handed over to the implementation team, which proceeds with the technical design, coding and testing. Also the sequence of technical design, coding and testing is actually an iterative process. If problems are discovered during coding and/or testing, one will return to the previous stage to take corrective actions. It is, however, rare that the analysis documents are updated accordingly. Surely, discovered errors may lead to some extra requirements elicitation and analysis activities during the implementation phase, but the results of these will be immediately incorporated into the code rather than documenting them first via updated models and requirements documentation. Figure 11.1 represents this way of working.