Civil versus Large Gov Acquisition Architectures (Some Architectural…
Civil versus Large Gov Acquisition
Some Architectural Principles
(from our class that I felt fit with what he discussed)
Balance: Many factors influence and act on the conception, design, implementation, and operation of a system. One must find a balance among the factors that satisfies the most important stakeholders.
He did not specifically state this, but I feel some themes were there: the role of the architect is to resolve ambiguity, focus creativity, and simplify complexity.
This other Ambiguity applies a bit more: The early phase of a system design is characterized by great ambiguity. The architect must resolve this ambiguity to produce (and continuously update) goals for the architect's team.
He mentioned duality in a different context but we have discussed that as well: all built systems inherently and simultaneously exist in the physical domain and in the informational domain.
Designer should always try to imagine (the ship or component) in service
Benefit in finding where (hull) form fits the function
Comfort & well-being of passengers & crew are high priority
Big items located first
His example had him starting with the "centerpiece" and working the details and outward from there
Primary function is paramount
emotions of the public who will experience their work
what is most important to the client
Form/function...cart or horse
Seems like form followed function in a lot of cases for them
Civil knows they need something to hold up the building (function) and then they pick creative forms to do it that are emotionally appealing
Seems to be easier for function to follow form in a lot of cases for us
We might start with the main level function, but then it is easier to zig zag between function and form to complete the architecture
designers can influence context about a product
Civil is more abstract and "soft", using more metaphors while engineering is more detail oriented and analytical with cold hard facts
Engineers not likely to think of the emotional response their designs will evoke
Civil incorporates art and nature much more than DoD engineering typically does
Maybe that's what we are missing?
The products we design/field can be thought of as opposites to artifacts
Life beyond design intent
Artifacts are open ended systems
Will rarely hear "circulation, character and magic" when hearing about DoD systems
details are important in both
Usually a team effort in both realms - never a 1 person show
Similar approach starting with main concepts and then drilling down
"elegant design" (from SI4021) in engineering incorporates many of the principles he mentioned from the civil realm
system may have to do something it wasn't designed to do
In some product development, what something looks like is closely tied to marketing and form (usually tied in civil as well)
"context" used in both
"concept" used in both