Please enable JavaScript.
Coggle requires JavaScript to display documents.
Civil versus Large Gov Acquisition Architectures (Similarities ("…
Civil versus Large Gov Acquisition
Architectures
Similarities
"concept" used in both
"context" used in both
In some product development, what something looks like is closely tied to marketing and form (usually tied in civil as well)
system may have to do something it wasn't designed to do
"elegant design" (from SI4021) in engineering incorporates many of the principles he mentioned from the civil realm
Similar approach starting with main concepts and then drilling down
Usually a team effort in both realms - never a 1 person show
details are important in both
Differences
Will rarely hear "circulation, character and magic" when hearing about DoD systems
The products we design/field can be thought of as opposites to artifacts
Artifacts are open ended systems
Life beyond design intent
Civil incorporates art and nature much more than DoD engineering typically does
Maybe that's what we are missing?
Engineers not likely to think of the emotional response their designs will evoke
Civil is more abstract and "soft", using more metaphors while engineering is more detail oriented and analytical with cold hard facts
designers can influence context about a product
Form/function...cart or horse
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
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
Upstream Influences
client
what is most important to the client
nature
emotions of the public who will experience their work
local regulations
Some Architectural Principles
(from our class that I felt fit with what he discussed)
Primary function is paramount
Big items located first
His example had him starting with the "centerpiece" and working the details and outward from there
Comfort & well-being of passengers & crew are high priority
Benefit in finding where (hull) form fits the function
Designer should always try to imagine (the ship or component) in service
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.
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.
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.