: A reactive object model is defined to control the design process of evolving objects in concurrent engineering environments. The goal is to support engineers in controlling the result of their design decisions, using a software automaton as a plug-in addition to computer-aided design platforms that support concurrent engineering. The automaton implements a reactive design specification for composite objects with multiple representations. The synchronous language ARGOS is used to implement the automaton. ARGOS is an imperative language for the specification and verification of reactive systems. It is based on the parallel and hierarchical composition of automata. Key-words: specification, verification, automata, reactive systems, concurrent engineering, design objects, CAD applications. Topics: Information Systems for Engineering Applications, Active Database/Knowledge base systems. 1. Motivations The design of integrated concurrent engineering platforms has received much attentio...

In this paper, we propose a novel software interoperability framework, termed "agent-based", that addresses many important issues critical to effective concurrent engineering. We demonstrate how concurrent engineering is supported using Designworld, an environment for total product engineering built using the agent-based framework. 1.0 Introduction Today's software infrastructures are inadequate to support concurrent engineering effectively. Heterogeneous software tools typically do not interoperate well. As a result, many interoperability standards are beginning to emerge from the industry. CORBA (Common Object Request Broker Architecture from OMG consortium) aims at making data format independent across platforms and service location transparent to the user. BMS (Broadcast Message Server from Hewlett-Packard) provides a basic message brokering service based on message types. CFI (CAD Framework Initiative) provides common presentation and management services. However, these standards...

SEED is an acronym for Software Environment to Support the Early Phases in Building Design. The overall architecture of SEED is based on a division of the preliminary design process into phases, each of which addresses a specific task. SEED intends to support each phase by an individual support module based on a shared logic and architecture. The modules envisioned for the first SEED prototype support the following phases: architectural programming, schematic layout design, and schematic configuration design. This document presents a requirements analysis of database related issues for the above and anticipated modules. SEED Database Requirements 7/19/94 Page ii Table of Contents 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1.1 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1.2 Scope . . . . . ...

Abstract not found

Abstract not found