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
Hits 1 to 20 of 127
Reformat results as: short short into frame detailed detailed into frame
This paper will give a short history of IGES, discuss its reason for being, list its strengths and weaknesses, examine its inner workings, and introduce the current effort of the IGES committee: a total "Product Design Exchange Specification", PDES (and internationally as STEP). It will also discuss the techniques used by the PDES application committees to model their various products, and give a case study of the effort of the AEC committee in modeling an architectural "product".
The paper will conclude with the opinions on the future of IGES by the author (a four year member of the IGES/PDES organization).
An interview technique was developed to address three main concerns: (1) how computers are and should be utilized in areas--i.e., research, course preparation, lecture delivery, computer-aided instruction, grading and monitoring, and student exercises; (2) what kinds of applications are and should be utilized--i.e., word processing, statistics, graphics, drafting, modeling, audio-visual, database, etc.; and (3) what problems or concerns stand in the way of achieving the desired levels of computer usage.
The twenty-three full-time faculty surveyed (96% participation) represent 65 curriculum courses varying in format from design studio and labs to lecture. This paper outlines the methods of the study and presents the findings via graphs of current and desired computer usage by both area and application along with a graphic summary of statistics and trends. Also presented are a summary of root problems and concerns noted during the interview process and conclusions and limitations of study.
It is the view of the author that a student can obtain much more from her or his first course in CAADD if some fundamental concepts are covered specifically and dramatically, rather than assumed or conveyed by osmosis. On the other hand, one does not want to significantly delay the teaching of he principal objective: how to use a computer as a partner in design and production. The answer to meeting these two divergent objectives is two-fold: (1) careful organization with computer based tutorials, and (2) integration of architectonic lessons during the introduction.
The objectives of he initial five weeks are (1) to demystify computers, (2) teach the fundamental concepts of computer systems relating to hardware (disks, cpu, memory, display), and software (programs, data, files), (3) illustrate programming and program design, and (4) convey the concept of discrete symbol manipulation and its relation to graphics and text.
For more results click below: