[PDF][PDF] Using difference information to reuse software cases
J Ebert, D Bildhauer, H Schwarz, V Riediger - 2007 - dl.gi.de
J Ebert, D Bildhauer, H Schwarz, V Riediger
2007•dl.gi.deThe goal of the ReDSeeDS12 (Requirements-Driven Software Development System) project
is to support reuse of software development artifacts and code in a model driven
development context. The set of all artifacts that are produced during the development of a
software product together with all their interconnections is called a software case in the
context of ReDSeeDS. A software case contains (at least) a set of requirements, an
architectural model, several detailed design models, the produced code and some …
is to support reuse of software development artifacts and code in a model driven
development context. The set of all artifacts that are produced during the development of a
software product together with all their interconnections is called a software case in the
context of ReDSeeDS. A software case contains (at least) a set of requirements, an
architectural model, several detailed design models, the produced code and some …
The goal of the ReDSeeDS12 (Requirements-Driven Software Development System) project is to support reuse of software development artifacts and code in a model driven development context.
The set of all artifacts that are produced during the development of a software product together with all their interconnections is called a software case in the context of ReDSeeDS. A software case contains (at least) a set of requirements, an architectural model, several detailed design models, the produced code and some transformational information–the latter describing potential model-to-model and/or model-to-code transformations. Based on similarity of new requirements to those stored in former software cases partial solutions shall become reusable. Figure 1 (taken from the ReDSeeDS website) sketches this approach.
dl.gi.de
Showing the best result for this search. See all results