Cumincad : CUMINCAD Papers : Search Results

CumInCAD is a Cumulative Index about publications in Computer Aided Architectural Design
supported by the sibling associations ACADIA, CAADRIA, eCAADe, SIGraDi, ASCAAD and CAAD futures

PDF papers
References

Hits 1 to 4 of 4

Reformat results as: short short into frame detailed detailed into frame

_id	0e5e
authors	Kociolek, A.
year	1986
title	CAD in Polish Building
source	Computer-Aided Architectural Design Futures [CAAD Futures Conference Proceedings / ISBN 0-408-05300-3] Delft (The Netherlands), 18-19 September 1985, pp. 235-245
summary	There is little CAAD in Polish architectural design offices, and only recently have practising architects discovered the computer. On the other hand, CAAD has been used for some time in research and development based at universities or in large design organizations. This chapter gives a broad picture of the computerization of building design in Poland, a complex process which concerns planning and financing, hardware, software, CAD practice, standardization, training, education, etc. Here architectural applications are treated on an equal basis, together with other applications representing design disciplines involved in design, such as structural and mechanical engineering. The underlying philosophy of this chapter is a belief that proper and well-balanced computerization of design in building which leaves creative work to human beings should result in better design and eventually in improvements in the built environment. Therefore integration of the design process in building seems more important for design practice than attempts to replace an architect by a computer, although the intellectual attraction of this problem is recognized.
series	CAAD Futures
last changed	1999/04/03 17:58

_id	8312
authors	Rasdorf, William J. and Wang, TsoJen E.
year	1986
title	CDIS: An Engineering Constraint Definition and Integrity Enforcement System for Relational Databases
source	Computers in Engineering International Conference Proceedings. 1986. American Society of Mechanical Engineers, vol. 2: pp. 273-280. CADLINE has abstract only
summary	Database management systems (DBMS) are an essential component of the computer integrated manufacturing (CIM) environment. A database management system provides a powerful functionality for the storage, management, and use of engineering data. It is lacking, however, in its ability to deal with engineering constraints. In the past, constraint checking was performed by application programs. More recently DBMS's have been incorporating into their structure specifications for enforcing a limited set of integrity constraints and the mechanisms for invoking them automatically. To ensure the correctness of engineering data, an effective constraint management capability must be incorporated into any proposed engineering DBMS. This paper demonstrates how this can be done, proposes a systematic way to classify constraints so that integrity can be maintained efficiently, and discusses a prototype called CDIS which implements the concepts. This paper uses the relational database model to represent both engineering data and engineering constraints. Data integrity is defined and its enforcement through the use of engineering constraints is described. Existing methods for handling constraints are discussed. A new model that enables the engineer to associate design constraints with a relational database is presented and an example is given that demonstrates the model. Extensions to a DBMS to implement the concepts presented are described. No currently available DBMS provides the much needed capabilities proposed here
keywords	civil engineering, relational database, constraints management
series	CADline
last changed	2003/06/02 13:58

_id	c3ca
authors	Rasdorf, William J. and Watson, Bruce R.
year	1986
title	ADI : An Adaptive Database Interface for Dynamic Databases
source	ASME Symposium Proceedings on Knowledge based Expert Systems for Manufacturing. Anaheim, CA: American Society of Mechanical Engineers, Production Engineering Division, December, 1986. pp. 119-130. CADLINE has abstract only
summary	The operation of a manufacturing organization often depends on its underlying design and manufacturing databases. In a manufacturing environment, many users, both individuals and application programs, must have access to one or more of the organization's databases to provide, use, or modify data, to control information flow, and to facilitate information management. Such databases routinely undergo dynamic changes in both their content and their structure. These changes commonly result from the design of new products, the introduction of new materials, and the introduction of new machines and processes on the shop floor. Such continuing changes must be reflected in the database schemas and subsequently require that application programs be updated and that online users be educated on a continuous basis. The problem addressed in this paper is that it is difficult for users and application programs to get the information that they need, when they need it, from the multiple heterogeneous database management system (DBMS) environments that have evolved in design and manufacturing organizations. The solution proposed here is to build a general, extendable interface between database users and the many sources of data available to them. This in itself is not a new suggestion; a number of researchers have addressed portions of this problem. In general, the interfaces that they have developed to date are best suited to environments where the structure of the database is static and does not change over time. One of the things that this paper proposes that is different from existing work is an interface which handles the dynamic restructuring nature of manufacturing databases, enabling a user to obtain the most accurate and up to date information as the structure and content of the underlying databases change. Another unique aspect of the DBMS interface proposed herein is that the interface attempts to capture the knowledge that an experienced human user incorporates in his search for data in a database, i.e., it seeks to identify and use the generic knowledge needed to operate a DBMS. This knowledge is used by the interface to enable both the online users and the application programs to request data without knowing the data's location or precisely how to ask for it. Further, the interface makes use of mechanisms that allow the user to request data without knowing the exact identity of the required entities that are stored in the database
keywords	engineering, database, manufacturing, user interface
series	CADline
last changed	2003/06/02 10:24

_id	02c6
authors	Wheeler, B.J.Q
year	1986
title	A Unified Model for Building
source	Computer-Aided Architectural Design Futures [CAAD Futures Conference Proceedings / ISBN 0-408-05300-3] Delft (The Netherlands), 18-19 September 1985, pp. 200-231
summary	It is commonly recognized that the time-honoured procedure for preparing an architectural design for building on site is inefficient. Each member of a team of consultant professionals makes an independently documented contribution. For a typical project involving an architect and structural, electrical, mechanical and public services engineers there will be at least five separate sets of general- arrangement drawings, each forming a model of the building, primarily illustrating one discipline but often having to include elements of others in order to make the drawing readable. For example, an air-conditioning duct-work layout is more easily understood when superimposed on the room layout it serves which the engineer is not responsible for but has to understand. Both during their parallel evolution and later, when changes have to be made during the detailed design and production drawing stages, it is difficult and time consuming to keep all versions coordinated. Complete coordination is rarely achieved in time, and conflicts between one discipline and another have to be rectified when encountered on site with resulting contractual implications. Add the interior designer, the landscape architect and other specialized consultants at one end of the list and contractors' shop drawings relating to the work of all the consultants at the other, and the number of different versions of the same thing grows, escalating the concomitant task of coordination. The potential for disputes over what is the current status of the design is enormous, first, amongst the consultants and second, between the consultants and the contractor. When amendments are made by one party, delay and confusion tend to follow during the period it takes the other parties to update their versions to include them. The idea of solving this problem by using a common computer-based model which all members of the project team can directly contribute to is surely a universally assumed goal amongst all those involved in computer-aided building production. The architect produces a root drawing or model, the 'Architect's base plan', to which the other consultants have read-only access and on top of which they can add their own write-protected files. Every time they access the model to write in the outcome of their work on the project they see the current version of the 'Architect's base plan' and can thus respond immediately to recent changes and avoid wasting time on redundant work. The architect meanwhile adds uniquely architectural material in his own overlaid files and maintains the root model as everybody's work requires. The traditional working pattern is maintained while all the participants have the ability to see their colleagues, work but only make changes to those parts for which they are responsible.
series	CAAD Futures
last changed	1999/04/03 17:58

No more hits.