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.

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.

No abstract

No abstract

No abstract

By ontology, we understand a knowledge structure which well reflects the complexity of a real world. Ontologies are built to store and process knowledge about objects and dependencies between them. Thus, ontologies not only structure raw data, but also contain the meaning of those data. So far, ontology developers have been forced to provide the semantics of modeled objects and relations between them manually. The goal of this paper is to address some still unresolved problems related to providing meanings in ontologies. A typical ontology consists of concepts with attributes, relations between them, and instances. In our research, we focus on concepts level where attributes must be interpretable because they are the primary carriers of the meaning of the entire ontology. In other words, we need to assign semantics for each attribute within a concept. For this purpose, we have proposed a semi-automatic method for defining attribute semantics based on WordNet. The attribute semantics designated by human experts and based on WordNet does not affect the integration result. However, the developed method allows reducing the time for preparing an ontology to the integration process. What is more, it is less sensitive to the subjective evaluations done by experts.

No abstract

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.