Information Technology Reference
In-Depth Information
not pay sufficient attention to the lessons that can be learned from non-
software fields.
For designers and architects, there are other “soft” aspects that they
need to understand and implement. A point that should be remembered
is that complex systems, similar to large and successful companies, are
built around “proven” value systems and processes. Certain things are
done a certain way in good companies because that is the right thing to
do even if it costs a little more or takes a little longer. It is not all altruism:
the right thing to do may lower long-term costs and increase return on
investment. One must adhere to such value systems if one is convinced
that it is the right thing to do as a professional.
As with any topic, this one is just one view of the software world
based on our thinking, reading, and experience in software systems design,
development, and implementation. We hope to contribute to the larger
body of knowledge in the software and systems domain through this topic
and the SEE approach to building software.
In a wide-ranging topic such as this, there is a limit to the depth to
which one can take each topic. There is a wide body of literature on
systems development and we have not covered basic material. Some
experience in the software field is assumed on the part of our readers.
We hope we have provided some fresh approaches and creative thinking
to familiar issues, with some stress on the cross-domain and cross-func-
tional aspects of the topics we discuss.
Through the hustle and bustle of daily work commitments, try to step
back and “understand” that experience. Write down why something
worked and others did not. Add to your personal repository of good
solutions. Build your library of good design concepts and management
techniques. And, at all times, look at other systems, beyond software.
Wish you all success in building better software.
