Quality-Driven Database System Development Within MDA Approach

Quality-Driven Database System Development Within MDA Approach

Iwona Dubielewicz, Bogumila Hnatkowska, Zbigniew Huzar, Lech Tuzinkiewicz
DOI: 10.4018/978-1-5225-5643-5.ch019
(Individual Chapters)
No Current Special Offers


The chapter presents an extended version of a quality-driven, MDA-based approach for database system development. The extension considers the relationship between successive models in the MDA approach. In particular, it gives rise to the introduction of domain ontology as a model preceding the CIM model as well as allows assessment of the extent to which the successive model is conformant with the preceding model. The chapter consists of four parts. The first part gives a short presentation of quality models and basic MDA concepts. The second one discusses the specific relationships between software development and quality assessment processes. The third part presents the Q-MDA framework and the proposal of a new quality characteristic (model conformance) with some measures for assessing the quality of a specific model in the context of other models. The last part contains an example of the framework application limited to the proposed quality model extension.
Chapter Preview


As a software system is a kind of a product which is developed in a production process therefore its quality may be considered in two perspectives: the product quality and the development process quality. The perspectives are strongly interrelated, for example, in shipbuilding industry, which is more matured discipline compared to software engineering, the controlled quality over the design and building process is necessary to guarantee the quality of a ship – the final product. In software engineering the quality of software development process also influences positively on a quality of a software product but does not guarantee expected quality of the product. The software development process may be considered as a sequence of activities that deliver different artifacts. At the beginning of the process software requirements, both functional and nonfunctional, are defined usually on the base of the business model. At the end a final software product is delivered. Other activities deliver intermediate artifacts. The quality of the intermediate artifacts influence the quality of the final software product. The chapter abstracts from the quality of software development process, and concentrates on the quality of the software product and its relationship to the quality of intermediate artifacts.

Complete Chapter List

Search this Book: