Abstract
Since unified definitions and methods applicable to architectural programming does not yet exist in Japan, often the contents of the architectural programs and design requirements have submitted before being well clarified. Then designers and their clients have to spend their times before they can finally define the prerequisites and design requirements through repetitious studies relying on preliminarily submitted drawings in the design process. One of the reasons for programming implementation remains in the part may be that its effectiveness of programming works not yet be clarified. This Study examined the effectiveness and its mechanism of “Problem Seeking Method” by researching and analyzing disturbing factors of process issues in project examples that applied this Method. At the research and analysis in this Study based on 56 programming case analysis of the project to which the “Problem Seeking Method” was applied, it identified the process issues and disturbing factors that occurred from the stage of programming proposal to the stage of program hand-off, then it was discussed about the effectiveness of “Problem Seeking Method” by revealing the mechanism to solve occurred issues. In the analysis, eliminating processes of disturbing factors and effective functions of the “Problem Seeking Method” at each programming phases were extracted, then there were clarified relations between disturbing factors and effective functions of “Problem Seeking Method” by organizing relation information at the chart. As a result, the Study concluded, as the followings, (1) In order to establish such architectural programs as to reflect owner's requirements precisely in the projects such as workplace projects which are drawing social attentions today, the “Problem Seeking Method” may function well, as a tool to or as a body of knowledge to support the best planning and implementation by improving insufficient knowledge and poor experiences of project team staffs. (2) The “Problem Seeking Method” has necessary and sufficient structure, mechanism and tools, consisting of 1) principle of separation between programming and design, 2) framework of programming, 3) method and tools to promote decision making and consensus building, including their combined functions, which may enable ones to treat effectively and flexibly and solve any challenging issue occurred during the programming process from the stage of proposal to program hand-off. (3) The structure and system of the Method, especially, “3) method and tools to promote decision making and consensus building” above can be said that these are the results of continuous up-dating though accumulation and reviews of experienced many cases in the past, and therefore, the Method can function efficiently even in the environment of current architectural projects. It can also be said that the Method can provide practical approach based on the accumulation of actual implementations and related experiences.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
More From: Journal of Architecture and Planning (Transactions of AIJ)
Disclaimer: 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.