| |
| |
Prologue | |
| |
| |
| |
Science and Technology | |
| |
| |
| |
In the Tradition | |
| |
| |
| |
The Underlying Thesis | |
| |
| |
| |
Going Beyond Programming | |
| |
| |
| |
An Engineering Discipline of Software | |
| |
| |
| |
The Philosophy of Science | |
| |
| |
| |
Why Study the Philosophy of Science? | |
| |
| |
| |
Science in the Early Twentieth Century | |
| |
| |
| |
Popper's Correction to Logical Positivism | |
| |
| |
| |
Epistemological Refinements | |
| |
| |
| |
Science in a Historical Context | |
| |
| |
| |
Some Other Contributions | |
| |
| |
| |
The Structure of Science | |
| |
| |
| |
Discovery and Design | |
| |
| |
| |
The Relationship Between Science and Technology | |
| |
| |
| |
Comparing the Engineer and the Scientist | |
| |
| |
| |
Technological Knowledge | |
| |
| |
| |
Modeling Reality | |
| |
| |
| |
Scientific and Technological Models | |
| |
| |
| |
Science and Free Phenomena | |
| |
| |
| |
A Short Coda | |
| |
| |
| |
Ecological Design | |
| |
| |
| |
A Foundation for Design | |
| |
| |
| |
The Foundation, So Far | |
| |
| |
| |
The Rejection of Technical Rationality | |
| |
| |
| |
Heidegger's Being-in-the-World | |
| |
| |
| |
An Ecological Study of Design | |
| |
| |
| |
Problem Solving | |
| |
| |
| |
The Chapter's Unifying Theme | |
| |
| |
| |
Human Problem Solving | |
| |
| |
| |
Human Problem Solving in the Real World | |
| |
| |
| |
The Nature of Expertise | |
| |
| |
| |
Scientific Expertise | |
| |
| |
| |
Complex Problem Solving | |
| |
| |
| |
Activity, Reflection, Context | |
| |
| |
| |
A Check Point | |
| |
| |
| |
Activity Theory | |
| |
| |
| |
Reflection in Practice | |
| |
| |
| |
Closing the Circle | |
| |
| |
| |
Reason, Bias, and Error | |
| |
| |
| |
The Design Process | |
| |
| |
| |
Finally, an Examination of Design | |
| |
| |
| |
Design Practice | |
| |
| |
| |
Architectural and Industrial Design | |
| |
| |
| |
Engineering and System Design | |
| |
| |
| |
The Individual Designer | |
| |
| |
| |
The Challenge | |
| |
| |
| |
Participatory Design | |
| |
| |
| |
Evolving Models of Design | |
| |
| |
| |
Human Factors and the Interface | |
| |
| |
| |
User-Centered Design | |
| |
| |
| |
The Scandinavian Approach | |
| |
| |
| |
A Model of Computer Technology Adaptation | |
| |
| |
| |
A Closing Observation | |
| |
| |
| |
Software Design | |
| |
| |
| |
The Software Process | |
| |
| |
| |
A Foundation for Software Design | |
| |
| |
| |
Software Engineering, a Historical Overview | |
| |
| |
| |
The Traditional Technological Perspective | |
| |
| |
| |
The Essential Software Process | |
| |
| |
| |
Looking to the Future | |
| |
| |
| |
Exploiting Software's Unique Properties | |
| |
| |
| |
Design Methods | |
| |
| |
| |
Adaptive Design in Context | |
| |
| |
| |
Methodological Dilemmas | |
| |
| |
| |
A Taxonomy of Design Methods | |
| |
| |
| |
A Brief Survey of Design Methods | |
| |
| |
| |
The Design Method Taxonomy | |
| |
| |
| |
Adaptive Design | |
| |
| |
| |
A Personal Preface | |
| |
| |
| |
Exploiting Software's Unique Capabilities | |
| |
| |
| |
Introduction to TEDIUM | |
| |
| |
| |
Application Database Representation | |
| |
| |
| |
Representing Knowledge in TEDIUM | |
| |
| |
| |
Family Knowledge | |
| |
| |
| |
The TEDIUM Window into Design | |
| |
| |
| |
Some Final Observations | |
| |
| |
| |
A Case Study | |
| |
| |
| |
Issues in Evaluation | |
| |
| |
| |
The Oncology Clinical Information System | |
| |
| |
| |
Characterizing the Project | |
| |
| |
| |
Evaluating the Environment | |
| |
| |
| |
The Representation as a Specification | |
| |
| |
| |
The Representation as a Conceptual Model | |
| |
| |
| |
Characterizing the Software Process | |
| |
| |
| |
Characterizing the Product | |
| |
| |
| |
What the Case Study Tells Us | |
| |
| |
Epilogue | |
| |
| |
References | |
| |
| |
Index | |