Lech Tuzinkiewicz

Feasibility Analysis of MDA-based Database Design

MDA is a modern approach to software system development. The paper proposes how database design may be embedded into such development process. It is shown how database models are associated with MDA models, and next qualitative analysis of problems that are concerned with transformation of databases models along with transformation of non-functional requirements is presented

Problems of SUMO-Like Ontology Usage in Domain Modelling

Ontologies are increasingly used, especially in the early stages of software development. It is widely believed that the use of ontologies has positive impact on the quality of the final software product. The aim of the paper is an introductory analysis of possible mapping between SUMO-like ontologies and domain models expressed in UML as a commonly accepted modelling language in software development. The main contribution of the paper is identification of basic problems within this mapping.

Evaluation of MDA/PSM database model quality in the context of selected non-functional requirements

Conceptual, logical, and physical database models can be regarded as PIM, PSM1, and PSM2 data models within MDA architecture, respectively. Many different logical database models can be derived from a given conceptual database model by applying a set of transformations rules. To choose a logical database model for further transformation (to physical database model at PSM2 level) some selection criteria based on quality demands, e.g. database efficiency, easy maintainability or portability, should be established. To evaluate quality of the database models some metrics should be provided. We present metrics for measuring two selected, conflicted quality characteristics (efficiency and maintainability), next we analyse correlation between the metrics, and finally propose how to assess quality of logical database models.

Development of Domain Model Based on SUMO Ontology

Domain model is the first model in the scope of interests of software developers. Its creation, especially for complex domain, can be very costly and time consuming, as it extensively involves domain experts. On the other side, domain knowledge could be included in existing ontologies, and can be extracted, with the support of domain experts, from them. That way of knowledge extraction should lead to better model quality, preventing from misunderstandings between business analysts and domain experts. The paper presents an approach to business model development on the base of SUMO ontologies. The approach is explained with the use of simple, but real example. The results are promising. Domain models, created using this approach, could be perceived as valuable input for further development.

Domain Modeling in the Context of Ontology

Abstract The domain knowledge represented by ontology should be widely used in the design process of information system. The aim of the paper is to outline a systematic approach of developing a CIM model (domain model, precisely) on the basis of a selected domain ontology. There are presented some hints how ontology concepts can be expressed in domain model. Elaborated example realizes some difficulties in proposed approach, e.g. the domain knowledge is spread over many ontologies, some facts are defined at very general level (their interpretation is more difficult), ontology may contain many irrelevant elements. Nevertheless, we are believed that applying ontology in conscious way can help to achieve higher compliance of the domain model with the application domain.

An Approach to Software Quality Specification and Evaluation (SPoQE)

The paper discusses how to carry evaluation of software product quality within software development process. The evaluation process bases on a quality model being an instance of a quality model Quality model, elaborated basing on ISO quality standards, may be used both for specification of quality requirements and quality assessment. The evaluation process is presented in terms of activity diagrams. It is generic and may be concretized for two perspectives of software product quality, i.e. external, and internal quality. Simple example illustrates the proposed approach.