Using formal metamodels to check consistency of functional views in information systems specification

UML notations require adaptation for applications such as Information Systems (IS). Thus we have defined IS-UML. The purpose of this article is twofold. First, we propose an extension to this language to deal with functional aspects of IS. We use two views to specify IS transactions: the first one is defined as a combination of behavioural UML diagrams (collaboration and state diagrams), and the second one is based on the definition of specific classes of an extended class diagram. The final objective of the article is to consider consistency issues between the various diagrams of an IS-UML specification. In common with other UML languages, we use a metamodel to define IS-UML. We use class diagrams to summarize the metamodel structure and a formal language, B, for the full metamodel. This allows us to formally express consistency checks and mapping rules between specific metamodel concepts. (C) 2007 Elsevier B.V. All rights reserved

Ontology-based modelling of architectural styles

The conceptual modelling of software architectures is of central importance for the quality of a software system. A rich modelling language is required to integrate the different aspects of architecture modelling, such as architectural styles, structural and behavioural modelling, into a coherent framework. Architectural styles are often neglected in software architectures. We propose an ontological approach for architectural style modelling based on description logic as an abstract, meta-level modelling instrument. We introduce a framework for style definition and style combination. The application of the ontological framework in the form of an integration into existing architectural description notations is illustrated

Towards Verification of UML Class Models using Formal Specification Methods: A Review

Abstract In today s world many elements of our lives are being affected by software and for that we are in greater need of high-quality software The Unified Modeling Language UML is considered the de facto standard for object-oriented software model development UML class diagram plays an important role in the design and specification of software systems A class diagram provides a static description of system component

Water and environmental issues

Water is a precious and finite part of the environment which is vital for socioeconomic development, sustainability of the environment and survival. Malaysia is fortunate that it is located in a humid tropical area rich in rainfall and water resources. The rapid economic growth of Malaysia in the past decades is also mainly attributed to its ability to exploit abundant natural resources including water. The exploitation of water resources is an important catalyst of economic growth but continuous exploitation without proper management and conservation may cause the depletion of water supplies, rendering water resources unsustainable. In recent years, water problems have escalated in Malaysia due to climate change, urbanization and population explosion. Therefore, effective water conservation, efficient waste water and sewage management integrated with recent technologies are important for fostering the tandem development of economic growth and the sustainability of environmental resources

Model evolution and system evolution

In this paper we define an evolution mechanism with formal semantics using the metamodeling methodology [Geisler et al.98] based on dynamic logic. A remarkable feature of the metamodeling methodology is the ability to define the relation of intentional and extensional entities within one level, allowing not only for the description of structural relations among the modeling entities, but also for a formal definition of structural\nconstraints and dynamic semantics of the modeled entities. While dynamic semantics on the extensional level means run-time behavior, dynamic semantics on intentional level describes model evolution in the system life cycle

Managing Requirement Volatility in an Ontology-Driven Clinical LIMS Using Category Theory. International Journal of Telemedicine and Applications

Requirement volatility is an issue in software engineering in general, and in Web-based clinical applications in particular, which often originates from an incomplete knowledge of the domain of interest. With advances in the health science, many features and functionalities need to be added to, or removed from, existing software applications in the biomedical domain. At the same time, the increasing complexity of biomedical systems makes them more difficult to understand, and consequently it is more difficult to define their requirements, which contributes considerably to their volatility. In this paper, we present a novel agent-based approach for analyzing and managing volatile and dynamic requirements in an ontology-driven laboratory information management system (LIMS) designed for Web-based case reporting in medical mycology. The proposed framework is empowered with ontologies and formalized using category theory to provide a deep and common understanding of the functional and nonfunctional requirement hierarchies and their interrelations, and to trace the effects of a change on the conceptual framework.Comment: 36 Pages, 16 Figure

Foundations of the Unified Modeling Language.

Object-oriented analysis and design is an increasingly popular software development method. The Unified Modeling Language (UML) has recently been proposed as a standard language for expressing object-oriented designs. Unfortunately, in its present form the UML lacks precisely defined semantics. This means that it is difficult to determine whether a design is consistent, whether a design modification is correct and whether a program correctly implements a design. Formal methods provide the rigor which is lacking in object-oriented design notations. This provision is often at the expense of clarity of exposition for the non-expert. Formal methods aim to use mathematical techniques in order to allow software development activities to be precisely defined, checked and ultimately automated. This paper aims to present an overview of work being undertaken to provide (a sub-set of) the UML with formal semantics. The semantics will facilitate the use of the UML in the software development process by allowing development steps to be defined and checked