Functional Specifications of Object Oriented Systems: A Model Driven Framework

Traceability-centric model-driven object-oriented engineering

“…Furthermore, there are a lot of works to integrate MDD with various development paradigms: web application development [12][13][14], general software system development [8][9][10][11], feature-oriented development [15,16], aspect-oriented development [17], and service-oriented development [18][19][20]. However, by observing the gap between our work and related model-based OO approaches such as [8][9][10], we can find the necessity of our work.…”

“…However, by observing the gap between our work and related model-based OO approaches such as [8][9][10], we can find the necessity of our work. The work such as [8] focuses on traceability link itself rather than transformation and does not consider human engineering part though it is important.…”

“…Many works on MDD such as [8][9][10][11][12][13][14][15][16][17][18][19][20] use models to represent different levels of abstraction and propose (semi-) automatic transformations between them in order to keep the complexity of software development manageable. And some of them [8,11,17] also consider the traceability as a key feature in the development.…”

“…Model-driven OO approaches are proposed [8][9][10], but their applicability in industry projects is largely limited. We observe two reasons behind this limitation; (1) lack of complete analysis of traceability and (2) lack of effective treatment on the development part which can only be engineered by human developers.…”

“…The work such as [8] focuses on traceability link itself rather than transformation and does not consider human engineering part though it is important. The work such as [10] focuses on functional specification without handling neither traceability (which is a basis for transformation) nor the meta-model of the artifacts. In work [9], there is no explicit treatment on OO artifacts, nor suggestion on traceability.…”