Design flow management in the NELSIS CAD framework

Abstract

In this paper a new approach for design jlow management is presented.We describe how the inputlouput relations between tools can be defined in a j%nwnap. For this, several concepts are introduced, such as defiing activities for tools, run-time activity identification, hierarchical jlow graphs, modijkation versus extension, and the possibility to have loops in the j?owmap.We also address tool scheduling and the integration of design Jow management in the architecture of afiarne-bared &sign system.

Design Flow Management: More than Convenient Tool Invocation

“…For this, we introduce the activity construct. (see also [2]). Several different activities may be defined for one design tool.…”

“…The design How model should be extended with a construct to denote data access or production. We use the term design object for a unit of design data for which the access and production is administered by the CAD framework and extend the How model with a port construct (see also [2]) to describe access to design objects. A port is either an input port, describing read access to a design object, or an output port, describing the production of a design object.…”

Past, present and future of information and knowledge sharing in the construction industry: Towards semantic service-based e-construction?

“…When combined with the increasing ubiquity of electronic networking and the Internet, this allowed many companies to collaborate and share building information and data which in turn lead to new ways of communicating and working [15] [10]. The opportunities presented by the move towards collaborative working and information sharing encouraged a number of research projects in the early 1990's, which aimed to facilitate and provide frameworks to encourage the migration from document centred approaches towards model based, integrated systems: CONDOR [51]; COMMIT [57] being examples.…”

A User Model Supporting Communication in High-Level Design Systems

“…Secondly, while working together on a design, users are bound to work with tools that handle the same design data. Several approaches exist that address this kind of issue ([3], [1]). Our approach supports cooperation not just in respect of data management but on a more global scale.…”