Year-end Sale % OFF 
Abstract
Faculty, researchers, and graduate students in academic settings produce a multitude of software programs for architecture. These tool builders are attempting to transform existing paradigms into computer-based tools for academia and the profession. Although the number of serious attempts at developing software is increasing dramatically and software authoring tools are continuing to improve, the successful integration of new software into teaching and practice often remains a problem. Inexperience in software development is causing many of these projects to be unsuccessful. This article represents a compendium of the common pitfalls in architectural software development that serves as a preliminary checklist. Pitfalls are found in deciding what software to make, the effects of computation, the nature of design, the process of transformation and implementation, and organization.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
