ECAP(ID:3048/eca001)Electronic Circuit Analysis ProgramRelated languages
Samples: References: in [ACM/IEEE] Proceedings of the SHARE Design Automation Project Annual ACM IEEE Design Automation Conference 1965 view details in [ACM/IEEE] Proceedings of the SHARE Design Automation Project Annual ACM IEEE Design Automation Conference 1965 view details in [ACM/IEEE] Proceedings of the SHARE Design Automation Project Annual ACM IEEE Design Automation Conference 1965 view details in [ACM/IEEE] Proceedings of the SHARE Design Automation Project Annual ACM IEEE Design Automation Conference 1965 view details in [ACM/IEEE] Proceedings of the SHARE Design Automation Project Annual ACM IEEE Design Automation Conference 1965 view details By contrast. NET-I and SCEPTRE (nonlinear programs) and NASAP (a symbolic flow diagram approach) are confined to a general discussion of the respective programs, with little or no information on program capabilities and limitations. Also, these articles lack coding information and accompanying programming examples. To summarize, with the exception of ECAP, the book treats all of the programs in a general fashion suitable only for readers interested in a cursory introduction to the subject. Furthermore, the book suffers considerably from its failure to compare these programs with one another to the point where a potential user could make an intelligent choice among them. in ACM Computing Reviews 11(02) February 1970 view details in [ACM] CACM 15(07) (July 1972) view details Types of Existing Systems We can divide CAD software into three general areas: data structure and data management techniques, computational techniques, and user interface techniques. Examples, are described which are effective in each of these areas. Architecture is a design area in which data structure and data management techniques predominate. These systems typically have a rather large data base,.but only modest requirements-for complex computations. There are single architectural systems which have subsystems for the design and checking of space utilization, structural details, architectural aesthetics, bills of materials, and building codes. A variety of subsystems are required to support the multitude of overlapping considerations which influence such a design. The architectural designer may change rapidly from one design aspect to another in this way. For example, he may change a room, then check the new space utilization and view a perspective drawing; change some structural details, then see how costs are affected and check for compliance with the building codes. To support this switching from one subsystem to another, the overall architectural CAD system must be modular and it must have a very general data structure and data management facility. The predominant type of CAD systems are those which are used for their analytic capacity. Examples of such systems are NASTRAN, for structural analysis, TRANSPORT, for accelerator magnet design, and SPICE, for electronic circuit design. These systems operate on modest amounts of data (from a data management point of view), so they have tended to use data structures formulated to facilitate the required computation. Another characteristic of these systems is that they are very specific; they concentrate very thoroughly on a very small problem area. The algorithms used by these computational systems show that they have a good theoretical framework. Nevertheless, they recognize a large number of special cases, often at substantial cost in software. NASTRAN, for example, recognizes beams, plates, cylinders, and many other shapes. Interactive CAD systems are rapidly moving from an academic to an industrial environment. While the data capacity and the computational capacity of these systems has been-modest, industry is finding that in many cases an interactive facility is cost effective. The GMS described in this work, together with one of the analysis routines forms a cost effective combination for many problems. While the ease of use of such a system will often encourage more analysis and hence more computing, the time saved by the user will usually more than compensate for the added computation cost. in [ACM] CACM 15(07) (July 1972) view details |