Page 26 - Software and Systems Requirements Engineering in Practice

Acknowledgments

ince requirements engineers work across the entire development
life cycle, they must interface with engineers working on
Sspecialized project tasks. We’re fortunate to have had the
experience of working with many talented software and systems
architects, testing experts, project managers, and requirements
engineers. Some of these experts have also collaborated with us on
this book project as contributing authors. We acknowledge the
contributions of these authors here as well as in the chapters they
have written: Sascha Konrad, Raghu Sangwan, Hans Ros, Xiping
Song, Bea Hwong, Marlon Vieira, Bill Hasling, Gilberto Matos, Bob
Schwanke, and Brad Wehrwein.
Like software system development, writing a book can be done
using a very iterative process. Once the author puts the first words to
paper, there is an iterative (seemingly endless) process of review and
rewrite, until we either become comfortable with the work or run out
of time. We’d like to acknowledge the contributions of our review
team: Capers Jones, Manfred Broy, John Worl, John Nallon, Stephan
Storck, and Mark Sampson.
We’d like to acknowledge the contributions of our cartoonist,
Johnol Jones, who helped to insert some humor into a usually serious
subject, and our intern, Lindsay Ivins, who developed the figures and
helped keep us organized when the page counts started to grow.
Finally, we’d like to acknowledge the support of our editor,
Wendy Rinaldi, and the staff at McGraw-Hill and International
Typesetting and Composition. Sometimes, just knowing that someone
has confidence in us to complete the project is enough motivation to
keep us working toward a successful completion.
Brian Berenbach
Daniel J. Paulish
Juergen Kazmeier
Arnold Rudorfer
Princeton, NJ 08540 USA

xxv