Readings
|
|
I confess that I do not know where to
draw the line between Requirements, System Analysis, System Architecture,
Software Engineering, Development, and Quality Assurance. I have
interests in each and I call myself a system architect. For now, I see
System Architecture as including concerns for requirements identification and
system formulation through verification of requirements satisfaction.
System architecture includes architecture of system delivery as well as
architecture of sustaining operation. This is a broad view, and essential to
achievement of coherence and conceptual integrity -- system architecture done on
purpose. I will settle for that now, and factor off parts that seem to
be too far below or above the architectural abstraction as it becomes useful
to do so.
I will stop short of internal architecture, the kind that
compartments functions underneath the covers of configurable units. (It
is unclear to me why functions are supposed to live in boxes and I have little
patience for it.)
The
ceiling on system architecture is far enough into the world of users to
include the confirmable articulation of those key values that set the context for the
system. Meanwhile, as my associate Bill Anderson is prone to say,
"It is turtles all the way down."
-- Dennis E. Hamilton
Seattle, Washington
2002 June 8
updated: 2002 June 10
You are navigating Orcmid's Lair |
created 2000-07-18-18:21 -0700 (pdt) by orcmid |
Home