Representing relational database designs in the UML.

Database Reverse Engineering (DBRE) refers to mapping relational schemas into semantically enriched models. Most of researches on DBRE map relational databases into the ER or EER models. They differ in input requirements and output. Unlike previous DBRE approaches, this thesis provides a methodology for mapping relational databases into an object-oriented designs in the UML. A distinct advantage of our approach is that it unifies objected oriented application designs and relational database designs. In this thesis, we first provide the Unified Modeling Language (UML) representations for basic relation schemas, with rigorous definitions for relational model concepts given by the UML metamodel and Object Constraint Language (OCL). Then, the paper classifies relational databases based on the types and number of inclusion dependencies. Finally, a general approach for mapping relational databases into object-oriented designs in the UML is specified.Dept. of Computer Science. Paper copy at Leddy Library: Theses & Major Papers - Basement, West Bldg. / Call Number: Thesis2001 .Z53. Source: Masters Abstracts International, Volume: 40-06, page: 1562. Adviser: Liwu Li. Thesis (M.Sc.)--University of Windsor (Canada), 2001

rCOS: A refinement calculus for object systems

This article presents a mathematical characterization of object-oriented concepts by defining an observation-oriented semantics for a relational objectoriented language with a rich variety of features including subtypes, visibility, inheritance, type casting, dynamic binding and polymorphism. The language is expressive enough for the specification of object-oriented designs and programs. We also propose a calculus based on this model to support both structural and behavioral refinement of object-oriented designs. We take the approach of the development of the design calculus based on the standard predicate logic in Hoare and He’s Unifying Theories of Programming (UTP). We also consider object reference in terms of object identity as values and mutually dependent methods

Generic unified modelling process for developing semantically rich, dynamic and temporal models

Models play a vital role in supporting a range of activities in numerous domains. We rely on models to support the design, visualisation, analysis and representation of parts of the world around us, and as such significant research effort has been invested into numerous areas of modelling; including support for model semantics, dynamic states and behaviour, temporal data storage and visualisation. Whilst these efforts have increased our capabilities and allowed us to create increasingly powerful software-based models, the process of developing models, supporting tools and /or data structures remains difficult, expensive and error-prone. In this paper we define from literature the key factors in assessing a model’s quality and usefulness: semantic richness, support for dynamic states and object behaviour, temporal data storage and visualisation. We also identify a number of shortcomings in both existing modelling standards and model development processes and propose a unified generic process to guide users through the development of semantically rich, dynamic and temporal models

Two Case Studies of Subsystem Design for General-Purpose CSCW Software Architectures

This paper discusses subsystem design guidelines for the software architecture of general-purpose computer supported cooperative work systems, i.e., systems that are designed to be applicable in various application areas requiring explicit collaboration support. In our opinion, guidelines for subsystem level design are rarely given most guidelines currently given apply to the programming language level. We extract guidelines from a case study of the redesign and extension of an advanced commercial workflow management system and place them into the context of existing software engineering research. The guidelines are then validated against the design decisions made in the construction of a widely used web-based groupware system. Our approach is based on the well-known distinction between essential (logical) and physical architectures. We show how essential architecture design can be based on a direct mapping of abstract functional concepts as found in general-purpose systems to modules in the essential architecture. The essential architecture is next mapped to a physical architecture by applying software clustering and replication to achieve the required distribution and performance characteristics

DESIGNING AN OBJECT RELATION MAPPING SYSTEM IN PHP

Object Relational Mapping is a programming technique used by software developers to convert data between incompatible systems. This technique is used in object-oriented programming languages, hence the “Object” in Object Relational Mapping. Often times we see ORM systems being used by developers when interacting with relational database management systems. ORM is about creating classes that mimic the tables in the database but in a more business oriented manner rather than the normalized form used by the RDBMS.ORM, object, relational, mapping, class, business model, normalization, primary key, foreign key, methods, properties