Friday, September 25, 2009
Principle 12
(Metropolitan Development as a Complex System: A New Approach to Sustainability, Judith E. Innes and
Principles 11
"As for aesthetic value, I would bet on the architect whose project reflects enduring human values in architecture" (Catesby Leigh, Guest lecture for ESD.34, 2009).
Sunday, September 13, 2009
Principles 6-10
6. "If you cannot explain it in five minutes, either you do not understand it or it does not work." (Darcy McGinn 1992, David Jones).
7. "All the serious mistakes are made on the first day" (R.Spinrad,1988).
8. "If it cannot wait it will" (Murphy's Law).
9. Development Process is useful for the following reasons (Ulrich K.T., Eppinger S.D., Product Design and Development, McGraw-Hill Inc. New York, NY, 2007.):
- Quality assurance,
- Coordination,
- Planning,
- Management,
- Improvement.
10. The Five Phases of Generic Development process are (Ulrich K.T., Eppinger S.D., Product Design and Development, McGraw-Hill Inc. New York, NY, 2007.):
"...
- Concept Development - single concept is chosen from a list of alternatives. The concept is described in form, function and features, accompanied by specifications.
- System Level Design - definition of the product architecture, division of the product into subsystems (and their functional specifications), creation of geometrical layout of the product.
- Detail Design - complete specification of the geometry, materials, and tolerances of all of the unique parts in the product. A process plan is established and control documentation is delivered.
- Testing and Refinement - construction and evaluation of multiple pre-production version of the product. Alpha and Betta prototypes.
- Production ramp-up - product is made using the intended production system..."
Principles 1-5
1. "There are no such things as good companies, bad companies or tired companies. There are good leaders, bad leaders and tired leaders" (Shalom Saada Saar, from ESD.930 lecture).
The four Heuristic from The Art of System Architecture (Rechtin E., Maier M.W., 2009):
2. Do not assume that the original statement of the problem is necessary the best, or even the right one.
3. In partitioning, choose the element so that they are as independent as possible; that is elements with low external complexity and high internal complexity.
4. Simplify, Simplify, Simplify.
5. Build in and maintain options as long as possible in the design and implementation of complex systems.
Subscribe to:
Posts (Atom)