Monday, April 28, 2008

INTENT

Intent relates to the intended meaning of a communication. It is the attempt to get someone to share your thoughts by having intellectual arrangements of features and dimensions of design. Design intent tends to govern the relationship between features in part and parts in assemblies. This means that for a design to work as a solution there has to be intent of each component to answer the design problem.

Within a presentation we try to use body language which tends to provide clues to the meaning and intent of communication from others that we get from gesture, facial expression, posture and everything else that is non-verbal. Non-verbal communication amounts to a second source of human communication that is often more reliable or essential to understanding what is really going on than the words themselves. While verbally when we talk to someone it is essential to bare in mind that others share the same sphere of experience would understand the content of a presentation. In the architecture environment there needs to be a high-level framework that can be used to develop unified communications environments that can provide significant productivity and cost benefits. Intelligent presenters should be able to communicate with each other using an extensible, expressive language.

REFERENCE

http://hbswk.hbs.edu/archive/3123.html

Monday, April 21, 2008

KNOWLEDGE

Architectural knowledge enables architects to create humane environments that emerges from and responds to societal, cultural and environmental needs. The humane environment is all about reason, emotion and intuition where architects have to resolve with the ability and knowledge to conceptualize, coordinate, and execute the idea of building. Like any other distinctive branches of education in design, architecture requires the development of creative capabilities to produce three dimensional spaces and form that accommodates for related human activities.

Knowledge in architecture can be regarded as a prerequisite to knowledge sharing within an infrastructure that combines people, content and technology all together.

Knowledge sharing often requires people to do a proper job in the case of assig ning job content to the right people to make sure that information flows to the right departments at the right time. This can be done by assigning people authority and responsibility for specific kinds of knowledge content and knowledge delivery. This avoids departments to become territorial in a typical organization fighting over budget or over the control of sensitive processes, and ensures departments to be cooperative and ready to share knowledge. The necessary knowledge transfer between people and technology involves capturing implied knowledge from experts, storing it in knowledge base, and making it available to people for solving complex problems.

Design studios are directed to practical ends and that knowledge cannot substitute for architectural imagination yet inadequate knowledge would handicap the general level of design. The architectural design process is knowledge intensive which requires a sequence of design decisions to be made. In our team it is expected that every one of us are at the same knowledge level with computer skills so it becomes easy to communicate to one another without much explanation.

REFERENCE

www.humiliationstudies.org/documents/SalamaICHH-05.pdf

http://www.ds.arch.tue.nl/Research/publications/henri/am97ha.htm

http://turing.une.edu.au/~comp292/Lectures/HEADER_KM_2004_LEC_NOTES/node17.html

Thursday, April 10, 2008

RECORD

To record is to make a permanent or official note of evidences accumulated in an investigation that are intended for future use and it can be in forms of written or electronic such as databases in Excel or Access with archived CAD files. The recording method varies according to the complexity of a project. In preservation and restoration projects for instance, they require careful documentation of their work like investigation reports and notes which are then made into a permanent file record. Either planned or unplanned architecture reports will always be of value to future researchers or owners of the building. An architectural record system tends to contain description of the original structure and changes made over time, the results of all investigations, a record of current conditions or problems, of past repairs and treatments, and recommendations for current and future action. An effective records management system is critical to managing procedures consistently across an organization, minimizing possibilities of having different rules and procedures from department to department. Many architectural firms tend to keep documents for less than 7 years except for leases which require record-keeping for building area measurements to be accomplished differently than normal architectural project-file record keeping.

To make a record we need to create and identify unique information that are then stored and retrieved with authorized access to others as a form of secondary use. It should be renewed constantly every time something new has been proposed on the project. The most frequently used form of record in our group is email. Email allows individuals and groups to communicate with one another. Once we have established contact within ourselves, we can gather and share information as well as elicit reactions to on-going proposals through email rather than face-to-face meetings or repetitive telephone calls. Unlike telephone and face-to-face conversations, email conversations provide a built-in record of what is asked for and what information is received. Via continuous emailing we could find out about someone else’s progress towards achieving the same goal, as well as setting a timeframe for each one of our tasks. Having an accurate internal system of records management would avoid our work to be overlapped.

REFERENCE

http://architecture.about.com/library/bl-preservationbrief-investigate08.htm

http://www.standards.org.au/cat.asp?catid=44&contentid=310&News=1

http://www.buildingareameasurement.com/faq.htm#q30

http://www.caldeson.com/RIMOS/barry2.html

Saturday, April 5, 2008

WK 3 - DISCIPLINE

A discipline refers to a system of rules of conduct or method of practice. In the architectural field, a disciplinary design team can develop designs that satisfy the needs and demands of all concerned. It was very difficult In the past when data were not exchangeable between different systems, but as buildings became more complex like the emergence of high rise and underground structures there became a need for establishing design teams so as to relief the burden of having just one person assigned to a project. Good teamwork in collaborative design produces good quality work as well as a having to generally reduce the cost. I seems therefore a good idea for stake holders to design the concept together from the start so that they can acknowledge their specialized knowledge into a project to prevent the design from starting on the wrong foot. A basic team consists of an architect, a structural advisor, an installation advisor and a cost advisor, all of which are experienced in practice.

The fabrication of our project requires a similar collaborative system, dividing roles amongst ourselves in order to achieve the best possible outcome. We had sessions discussing our areas of expertise and we were then able to assign one another with specific tasks. These sessions were held not only in group meeting but also by other communicative mediums that we have chosen, such as MSN and email, and as far as I know we are going to set up a forum later on. Even though sometimes we are not exactly sure of what to do but we can support and back up each other’s weaknesses with our own knowledge via these communicative mediums. As everyone’s not familiar with the new software (UT3) we might organize sometime to work it out together later. I took on the role to model the building in 3DMax not that I am good at it but its probably the only software I can use for now, and it would by all means reduce time and effort in going through tutorials of other software. We have divided the task into eleven streams, with everyone having a similar workload. The diagram below shows how we have divided the tasks.



REFERENCE


http://www.wordnet-online.com/discipline.shtml