what's the difference between studying architectural design and engineering design?
December 30th, 2008
except the houses and buldings that architect design…. what i mean is, it is still design,.right?? i'm not good at architectural design,..so does it mean that i'm not good also at engineering design?? …. that's bothering me to take up BSEE……. what should i do?? any advice would be much appreciated,….tnx…
Perhaps the best way to describe it is that Architects design around Form while Engineers design around Function.
For an architect, how things 'look' is as important as how they are put together. Frank L. Wright wanted his buildings to look like they belonged at that location and were part of it.
G. Eiffel didn't care as much about that as making sure that his Tower was strong and tall.. A fellow named Roebling only wanted to build a bridge near Brooklyn and it was just a plain bridge held up by cables.
At Thirteen you have more then a few years ahead of you to decide if you like form more then function, so kick back and enjoy your life. As you decide what you enjoy you will find your answer about which road to choose.
good luck on your journey.
Posted in architectural engineering
Perhaps the best way to describe it is that Architects design around Form while Engineers design around Function.
For an architect, how things 'look' is as important as how they are put together. Frank L. Wright wanted his buildings to look like they belonged at that location and were part of it.
G. Eiffel didn't care as much about that as making sure that his Tower was strong and tall.. A fellow named Roebling only wanted to build a bridge near Brooklyn and it was just a plain bridge held up by cables.
At Thirteen you have more then a few years ahead of you to decide if you like form more then function, so kick back and enjoy your life. As you decide what you enjoy you will find your answer about which road to choose.
good luck on your journey.
References :
Engineers build weapons, architects build targets.
References :
really no difference, but learn trade any why and get a job on a construction site this way you can help in the process with out designing.
References :
BSEE?…..electrical engineering…how do go from engineering design the EE?……Im in engineering design…I cant drawn worth a darn, but I can take the pretty drawings that and architect drew for a high rise building design and design the steel frame, the precast concrete skin that will cover it, the foundation it sits on, and all the necessary components that make it work. So it all depends…do you want to draw pictures, or make it work….then again…some programs offer architecural engineering……a mix of both, I suppose…..but at most schools, architects and engineers dont mix….
References :
1. “Architecture is concerned with the selection of architectural elements, their interaction, and the constraints on those elements and their interactions…Design is concerned with the modularization and detailed interfaces of the design elements, their algorithms and procedures, and the data types needed to support the architecture and to satisfy the requirements.”
2. Software architecture is “concerned with issues…beyond the algorithms and data structures of the computation.”
3. “Architecture…is specifically not about…details of implementations (e.g., algorithms and data structures.)…Architectural design involves a richer collection of abstractions than is typically provided by OOD” (object-oriented design).
In suggesting typical “architectures” and “architectural styles,” existing definitions consist of examples and offer anecdotes rather than providing clear and unambiguous notions. In practice, the terms “architecture,” “design,” and “implementation” appear to connote varying degrees of abstraction in the continuum between complete details (“implementation”), few details (“design”), and the highest form of abstraction (“architecture”). But the amount of detail alone is insufficient to characterize the differences, because architecture and design documents often contain detail that is not explicit in the implementation (e.g., design constraints, standards, performance goals). Thus, we would expect a distinction between these terms to be qualitative and not merely quantitative.
The ontology that we provide below can serve as a reference point for these discussions.
The Intension/Locality Thesis
To elucidate the relationship between architecture, design, and implementation, we distinguish at least two separate interpretations for abstraction in our context:
1. Intensional (vs. extensional) design specifications are “abstract” in the sense that they can be formally characterized by the use of logic variables that range over an unbounded domain. For example, a layered architectural pattern does not restrict the architect to a specific number of layers; it applies equally well to 2 layers or 12 layers.
2. Non-local (vs. local) specifications are “abstract” in the sense that they apply to all parts of the system (as opposed to being limited to some part thereof).
Both of these interpretations contribute to the distinction among architecture, design, and implementation, summarized as the “intension/locality thesis”:
1. Architectural specifications are intensional and non-local
2. Design specifications are intensional but local
3. Implementation specifications are both extensional and local
References :