Bibliography [Agile Alliance2001] Agile Alliance, Principles: The - - PDF document

Bibliography [Agile Alliance2001] Agile Alliance, “Principles: The Agile Alliance” (2001),

http://www.agilealliance.org/.

[Alexander2002]

• I. Alexander, “Initial Industrial Experience of Misuse Cases in Trade-Off Analysis”, pp. 11–13 in Proceed-

ings of the IEEE Joint International Requirements Engineering Conference (RE’02), IEEE Computer Society Press, Essen, Germany (2002). [Alford1977] M.W. Alford, “A Requirements Engineering Methodology for Realtime Processing Requirements”, IEEE Transactions on Software Engineering SE-3(1), pp. 60–69 (1977). [Bergman2002] M.B. Bergman, J.L. King, and K. Lyytinen, “Large-Scale Requirements Analysis Revisited: The need for Understanding the Political Ecology of Requirements Engineering”, Requirements Engineering Journal 7(3),

• pp. 152–171 (2002).

[Berry1980] D.M. Berry and O. Berry, “The Programmer-Client Interaction in Arriving at Program Specifications: Strong Typing, Abstract Data Typing, and Jewish Motherhood”, in Proceedings of the Third International Winter Seminar on Computer Science, Santiago, Chile (August 1980). [Berry1983] D.M. Berry and O. Berry, “The Programmer-Client Interaction in Arriving at Program Specifications: Guidelines and Linguistic Requirements”, in Proceedings of IFIP TC2 Working Conference on System Description Methodologies, ed. E. Knuth, Kecskemet, Hungary (May 1983). [Berry1995] D.M. Berry, “The Importance of Ignorance in Requirements Engineering”, Journal of Systems and Software 28(2), pp. 179–184 (February 1995). [Berry1998] D.M. Berry, “Software and House Requirements Engineering: Lessons Learned in Combating Requirements Creep”, Requirements Engineering Journal 3(3&4), pp. 242–244 (1998). [Berry2003] D.M. Berry, E. Kamsties, and M.M. Krieger, “From Contract Drafting to Software Specification: Linguistic Sources of Ambiguity”, Technical Report, University of Waterloo, Waterloo, ON, Canada (2003),

http://se.uwaterloo.ca/˜dberry/handbook/ambiguityHandbook.pdf.

[Berry2004a] D.M. Berry and E. Kamsties, “Ambiguity in Requirements Specification”, pp. 7–44 in Perspectives on Requirements Engineering, ed. J.C.S.P. Leite and J. Doorn, Kluwer, Boston, MA (2004). [Berry2004b] D.M. Berry, K. Daudjee, J. Dong, I. Fainchtein, M.A. Nelson, and T. Nelson, “User’s Manual as a Require- ments Specification: Case Studies”, Requirements Engineering Journal 9(1), pp. 67–82 (February 2004). 1

[Beyer1998]

• H. Beyer and K. Holtzblatt, Contextual Design, Morgan Kaufman, San Francisco, CA (1998).

[Boehm1988a]

• B. Boehm, “Process Architectures in a COTS-Oriented World”, Workshop Presentation, Software Engineer-

ing Institute, Pittsburgh, PA (May 1988). [Boehm1981] B.W. Boehm, Software Engineering Economics, Prentice-Hall, Englewood Cliffs, NJ (1981). [Boehm1988b] B.W. Boehm, “A Spiral Model of Software Development and Enhancement”, IEEE Computer 21(5), pp. 61–72 (May 1988). [Boehm2003] B.W. Boehm and L.G. Huang, “Value-Based Software Engineering: A Case Study”, IEEE Computer 36(3),

• pp. 33–41 (March 2003).

[Bohner1996] S.A. Bohner and R.S. Arnold, Software Change Impact Analysis, IEEE Computer Society Press, Los Alami- tos, CA (1996). [Borgida1985]

• A. Borgida, S. Greenspan, and J. Mylopolous, “Knowledge Representation as the Basis for Requirements

Specifications”, Computer 18(4), pp. 82–91 (April 1985). [Bowers1994]

• J. Bowers and J. Pycock, “Talking Through Design: Requirements and Resistance in Cooperative Prototyp-

ing”, pp. 299–305 in Proceedings of the 1994 Computer-Human Interaction Conference (CHI’94), ACM SIGCHI, New York, NY (1994). [Breen2005]

• M. Breen, “Experience of Using a Lightweight Formal Specification Method for a Commercial Embedded

System Product Line”, Requirements Engineering Journal (to appear 2005). [Brooks1987] F.P. Brooks, Jr., “No Silver Bullet”, Computer 20(4), pp. 10–19 (April 1987). [Brooks1995a] F.P. Brooks, Jr., “Keynote Address”, in Seventeenth International Conference on Software Engineering, IEEE Computer Society, Seattle, WA (1995). [Brooks1995b] F.P. Brooks, Jr., The Mythical Man-Month: Essays on Software Engineering, Second Edition, Addison Wes- ley, Reading, MA (1995). [Bubenko1995] J.A. Bubenko, Jr., “Challenges in Requirements Engineering”, pp. 2–8 in Proceedings of the Second IEEE International Symposium on Requirements Engineering, IEEE Computer Society Press, York, UK (March 1995). 2

[Burgess-Yakemovic1990] K.C. Burgess-Yakemovic and J. Conklin, “Report on Development Project Use of an Issue-Based Informa- tion System”, in Proceedings of the ACM Conference on CSCW, Los Angeles, CA (October 1990). [Burstin1984] M.D. Burstin and M. Ben-Bassat, “A User’s Approach to Requirements Analysis if a Large Software Sys- tem.”, in Proceedings of ACM National Conference, Seattle, WA (October 1984). [Carmel1993]

• E. Carmel, R.D. Whitaker, and J.F. George, “PD and Joint Application Design: A Transatlantic Com-

parison”, Communications of the ACM 36(4), pp. 49–48 (June 1993). [Carroll1998]

• J. Carroll, M.B. Rosson, G. Chin, and J. Koenemann, “Requirements Development in Scenario-Based

Design”, IEEE Transactions on Software Engineering SE-24(12), pp. 1156–1170 (December 1998). [Carter1984]

• R. Carter, J. Martin, B. Mayblin, and M. Munday, Systems, Management and Change: A Graphic Guide,

Kluwer Academic, Boston (1984). [Cerf2003] V.G. Cerf, “Requirements for the Internet”, pp. 3–4 in Proceedings of the 11th IEEE International Require- ments Engineering Conference, IEEE Computer Society Press, Monterey, CA (September 2003). [Cheheyl1981] M.H. Cheheyl, M. Gasser, G.A. Huff, and J.K. Millen, “Verifying Security”, Computing Surveys 13(3), pp. 279–340 (September 1981). [Coad1991]

• P. Coad and E. Yourdon, Object-Oriented Analysis, Yourdon Press, Englewood-Cliffs, NJ (1991).

[Dardenne1993]

• A. Dardenne, A. van Lamsweerde, and S. Fickas, “Goal-Directed Requirements Acquisition”, Science of

Computer Programming 20, pp. 3\n50 (1993). [Daugulis1998]

• A. Daugulis, “Time Aspects in Requirements Engineering or ‘Every Cloud has a Silver Lining’”, Technical

Report, Royal Institute of Technology, KTH, Department of Industrial Control Systems, Stockholm, Sweden (1998). [Davis1992]

• A. Davis, “Operational Prototyping: A New Development Approach”, IEEE Computer 9(5), pp. 70–78

(1992). [Davis1993]

• A. Davis, Software Requirements: Objects, Functions, and States, Prentice-Hall, Englewood Cliffs, NJ

(1993). [Davis1990] A.M. Davis, Software Requirements: Analysis and Specification, Prentice-Hall, Englewood Cliffs, NJ (1990). 3

[Drake1994] J.M. Drake and W.T. Tsai, “System Bounding Issues for Analysis”, pp. 24–31 in Proceedings of the IEEE International Conference on Requirements Engineering, IEEE Computer Society Press, Colorado Springs, CO (1994). [Dupre ´1998]

• L. Dupre

´, Bugs in Writing: A Guide to Debugging Your Prose, Second Edition, Addison-Wesley, Reading, MA (1998). [Dzida1999]

• W. Dzida and R. Freitag, “Documentation of Prototypes in Terms of Use Scenarios: Nice to Have to

Indispensable?”, pp. 905–908 in Human-Computer Interaction, Volume I, ed. H.-J. Bullinger and J. Ziegler, Lawrence Erlbaum Associates, Mahwah, NJ (August 1999). [Easterbrook1993]

• S. Easterbrook, “Domain Modelling with Hierarchies of Alternative Viewpoints”, pp. 65–72 in Proceedings
• f the IEEE International Symposium on Requirements Engineering, IEEE Computer Society Press, San

Diego, CA (January 1993). [Easterbrook1995]

• S. Easterbrook and B. Nuseibeh, “Managing Inconsistencies in an Evolving Specification”, pp. 48–55 in

Proceedings of the Second IEEE International Symposium on Requirements Engineering, IEEE Computer Society Press, York, UK (March 1995). [Easterbrook1996]

• S. Easterbrook and B. Nuseibeh, “Using ViewPoints for Inconsistency Management”, Software Engineering

Journal 11(1), pp. 31–43 (January 1996). [Eberlein2002]

• A. Eberlein and J.C.S.P Leite, “Proceedings of the International Workshop on Time Constrained Require-

ments Engineering (TCRE)”, Essen Germany (September 2002),

http://www-di.inf.puc-rio.br/˜julio/tcre-site/tcre-2.htm.

[El Aman1996] K El Aman, S. Quintin, and N.H. Madhavji, “User Participation in the Requirements Engineering Process: An Empirical Study”, Requirements Engineering Journal 1(1), pp. 4–27 (1996). [Finkelstein1993] A.C.W. Finkelstein, “Report of the Inquiry Into The London Ambulance Service”, Original ISBN No: 0 905133 70 6, Report to The Communications Directorate, South West Thames Regional Health Authority (February 1993), http://www.cs.ucl.ac.uk/staff/A.Finkelstein/las/lascase0.9.pdf. [Finkelstein1996] A.C.W. Finkelstein and J. Dowell, “A Comedy of Errors: the London Ambulance Service Case Study”, pp. 2–4 in Proceedings of Eighth International Workshop on Software Specification and Design, IWSSD-8, IEEE Computer Society Press (1996). [Finkelstein2001] A.C.W. Finkelstein and M. Shattock, “CAPSA and its implementation Report to the Audit Committee and the Board of Scrutiny University of Cambridge”, Cambridge University Reporter CXXXII(6), pp. 153–208 (2 November 2001). 4

[Forsberg1997]

• K. Forsberg and H. Mooz, “System Engineering Overview”, in Software Requirements Engineering , Second

Edition, ed. R.H. Thayer and M. Dorfman, IEEE Computer Society Press, Washington (1997). [Gause1989] D.C. Gause and G.M. Weinberg, Exploring Requirements: Quality Before Design, Dorset House, New York, NY (1989). [Gause1990] D.C. Gause and G.M. Weinberg, Are Your Lights On? How to Figure Out What the Problem REALLY Is?, Dorset House, New York, NY (1990). [Goguen1993] J.A. Goguen and C. Linde, “Techniques for Requirements Elicitation”, pp. 152–164 in Proceedings of the IEEE International Symposium on Requirements Engineering, IEEE Computer Society Press, San Diego, CA (January 1993). [Goguen1994a] J.A. Goguen, “Requirements Engineering as the Reconciliation of Technical and Social Issues”, pp. 165–199 in Requirements Engineering: Social and Technical Issues, ed. J.A. Goguen and M. Jirotka, Academic Press, London, UK (1994). [Goguen1994b] J.A. Goguen and M. Jirotka, Requirements Engineering: Social and Technical Issues, Academic Press, Lon- don, UK (1994). [Goldin1994]

• L. Goldin and D.M. Berry, “AbstFinder: A Prototype Abstraction Finder for Natural Language Text for Use

in Requirements Elicitation: Design, Methodology, and Evaluation”, pp. 84–93 in Proceedings of the IEEE International Conference on Requirements Engineering, IEEE Computer Society Press, Colorado Springs, CO (April 1994). [Gotel1994] O.C.Z. Gotel and A.C.W. Finkelstein, “An Analysis of the Requirements Traceability Problem”, pp. 94–101 in Proceedings of the IEEE International Conference on Requirements Engineering, IEEE Computer Society Press, Colorado Springs, CO (1994). [Highsmith2001]

• J. Highsmith and A. Cockburn, “Agile Software Development: The Business of Innovation”, IEEE Com-

puter 34(9), pp. 120–122 (September 2001). [Holtzblatt1990]

• K. Holtzblatt and S. Jones, “Contextual Inquiry: Principles and Practice”, Technical Report DEC-TR 729,

Digital Equipment Corporation (October 1990). [Holtzblatt1995]

• K. Holtzblatt and H. Beyer, “Requirements Gathering: The Human Factor”, Communications of the ACM

23(5), pp. 279–295 (May 1995). 5

[Hooper1982] J.W. Hooper and P. Hsia, “Scenario-Based Prototyping for Requirements Identification”, SOFTWARE ENGINEERING NOTES 7(5), pp. 88–93 (December 1982). [Hunter1997]

• A. Hunter and B. Nuseibeh, “Analysing Inconsistent Specifications”, pp. 78–86 in Proceedings of the Third

IEEE International Symposium on Requirements Engineering, IEEE Computer Society Press, Annapolis, MD (January 1997). [IEEE1998] IEEE, “IEEE Recommended Practice for Software Requirements Specifications”, in ANSI/IEEE Standard 830-1998 , Anonymous, IEEE Computer Society, Los Alamitos, CA (1998). [Jackson1998]

• M. Jackson, “Formal Methods and Traditional Engineering”, Journal of Systems and Software 40(3), pp.

191–194 (March 1998). [Jackson1994] M.A. Jackson, “The Role of Architecture in Requirements Engineering”, pp. 241 in Proceedings of the IEEE International Conference on Requirements Engineering, IEEE Computer Society Press, Colorado Springs, CO (April 18–22 1994). [Jackson1995] M.A. Jackson, “Problems and Requirements”, pp. 2–8 in Proceedings of the Second IEEE International Symposium on Requirements Engineering, IEEE Computer Society Press, York, UK (March 1995). [Jacobson1992]

• I. Jacobson, Object-Oriented Software Engineering, Addison Wesley, Reading, MA (1992).

[Kaindl1993]

• H. Kaindl, “The Missing Link in Requirements Engineering”, ACM SIGSOFT Software Engineering Notes

18(2), pp. 30–39 (April 1993). [Kamsties1998]

• E. Kamsties, K. H¨
• rmann, and M. Schlich 1998, “Requirements Engineering in Small and Medium Enter-

prises”, Requirements Engineering Journal 3, pp. 84–90 (1998). [Kang1990]

• K. Kang, S. Cohen, J. Hess, W. Novak, and A. Peterson, “Feature Oriented Domain Analysis (FODA) Feasi-

bility Study”, Technical Report, CMU/SEI-90-TR-21, DTIC: ADA235785, Software Engineering Institute (November 1990). [Kantorowitz1997]

• E. Kantorowitz, A. Guttmann, and L. Arzi , “The Performance of the N-Fold Requirement Inspection

Method”, Requirements Engineering Journal 2(3), pp. 152–164 (1997). [Karlsson1997a]

• J. Karlsson, S. Olsson, and K. Ryan, “Improved Practical Support for Large-Scale Requirements Prioritiz-

ing”, Requirements Engineering 2(1), pp. 51–60 (1997). 6

[Karlsson1997b]

• J. Karlsson and K. Ryan, “Prioritizing Requirements Using a Cost-Value Approach”, IEEE Software 14(5),
• pp. 67–74 (September-October 1997).

[K¨

• sters1996]
• G. K¨
• sters, H.W. Six, and J. Voss, “Combined Analysis of User Interface and Domain Requirements”, pp.

199–207 in Proceedings of the Second IEEE International Conference on Requirements Engineering, IEEE Computer Society Press, Colorado Springs, CO (1996). [Knuth1989] D.E. Knuth, T.L. Larrabee, and P.M. Roberts, Mathematical Writing, MAA Notes, No. 14, Mathematical Association of America, Washington, D.C. (1989). [Krogstie1998]

• J. Krogstie, “Using Quality Function Deployment in Software Requirements Specification”, Technical

Report, Anderson Consulting and IDI, NTNU, Oslo, Norway (1998). [Lehman1980] M.M. Lehman, “Programs, Life Cycles, and Laws of Software Evolution”, Proceedings of the IEEE 68(9),

• pp. 1060–1076 (September 1980).

[Leiner2000] B.M. Leiner, V.G. Cerf, D.D. Clark, R.E. Kahn, L. Kleinrock, D.C. Lynch, J. Postel, L.G. Roberts, and S. Wolff , “A Brief History of the Internet”, Internet Society (ISOC), Reston, VA (2000),

http://www.isoc.org/internet/history/brief.shtml.

[Leite1987] J.C.S.P. Leite, “A Survey on Requirements Analysis.”, Advanced Software Engineering Project Technical Report RPT-071, Department of Information and Computer Science, University of California, Irvine, CA (June 1987). [Leite1993] J.C.S.P. Leite and A.P.M. Franco, “A Strategy for Conceptual Model Acquisition”, pp. 243–246 in Proceed- ings of the IEEE International Symposium on Requirements Engineering, IEEE Computer Society Press, San Diego, CA (January 1993). [Leveson1986] N.G. Leveson, “Software Safety: What, Why, and How”, Computing Surveys 18(2), pp. 125–164 (June 1986). [Leveson1995] N.G. Leveson, Safeware: System Safety and Computers, Addison Wesley, Reading, MA (1995). [Leveson1997] N.G. Leveson, “Intent Specifications: An Approach to Building Human-Centered Specifications”, Technical Report, Computer Science and Engineering, University of Washington, Seattle, WA (1997). [Linger1998] R.C. Linger, N.R. Mead, and H.F. Lipson, “Requirements Definition for Survivable Network Systems”, pp. 14–23 in Proceedings of the Third IEEE International Conference on Requirements Engineering, IEEE Computer Society Press, Colorado Springs, CO (1998). 7

[Loucopoulos1995]

• P. Loucopoulos and V. Karakostas, System Requirements Engineering, McGraw-Hill, New York, NY

(1995). [Lubars1993]

• M. Lubars, C. Potts, and C. Richter, “A Review of the State of Practice in Requirements Modeling”, pp.

2–14 in Proceedings of the IEEE International Symposium on Requirements Engineering, IEEE Computer Society Press, San Diego, CA (January 1993). [Luqi1992] Luqi, “Computer-Aided Prototyping for a Command-and-Control System Using CAPS”, IEEE Software 9(1), pp. 56–67 (January-February 1992). [Lutz2003] R.R. Lutz and I.C. Mikulski, “Resolving Requirements Discovery in Testing and Operations”, pp. 33–44 in Proceedings of the 11th IEEE International Requirements Engineering Conference, IEEE Computer Society Press, Monterey, CA (September 2003). [Maarek1989] Y.S. Maarek and D.M. Berry, “The Use of Lexical Affinities in Requirements Extraction”, in Proceedings of the Fifth International Workshop on Software Specification and Design, Pittsburgh, PA (May 1989). [Maiden2001]

• N. Maiden and A. Gizkis, “Where Do Requirements Come From?”, IEEE Software 18(5), pp. 10–12

(September-October 2001). [Maiden2004] N.A.M. Maiden, A. Gizikis, and S. Robertson, “Provoking Creativity: Imagine What your Requirements Could Be Like”, IEEE Software 21(5), pp. 68–75 (September-October 2004). [Martin1988]

• J. Martin and W.T. Tsai, “An Experimental Study in Upstream Software Development”, Technical Report,

University of Minnesota, Minneapolis, MN (1988). [Mich2000]

• L. Mich and R. Garigliano, “Ambiguity Measures in Requirements Engineering”, in Proceedings of the

International Conference on Software Theory and Practice (ICS2000), Sixteenth IFIP World Computer Conference, Beijing, China (21–24 August 2000). [Mich2001]

• L. Mich, “On the use of Ambiguity Measures in Requirements Analysis”, in Applications of Natural

Language to Information Systems, Sixth International Workshop NLDB’01, ed. A.M. Moreno and R.P. van de Riet, Madrid, Spain (28–29 June 2001). [Mylopoulos1992]

• J. Mylopoulos, L. Chung, and B. Nixon, “Representing and Using Non-Functional Requiremements: A

Process-Oriented Approach”, IEEE Transactions on Software Engineering SE-18(6), pp. 483–497 (June 1992). 8

[Neumann1986] P.G. Neumann, “Risks to the Public”, Software Engineering Notes (1986), Column in nearly every issue since January 1986. [Neumann1999] P.G. Neumann, “Risks to the Public in Computers and Related Systems: The Bloatware Debate (Edupage)”, Software Engineering Notes 24(1) (January 1999). [Nuseibeh2000]

• B. Nuseibeh and S. Easterbrook, “Requirements Engineering: A Roadmap”, in The Future of Software

Engineering 2000, ed. A. Finkelstein, ACM, Limerick, Ireland (June 2000). [Parnas1994] D.L. Parnas, “Software Aging”, pp. 279–287 in Proceedings of the Sixteenth International Conference on Software Engineering , Invited Plenary Talk, Sorrento, Italy (May 1994). [Posner1993] M.I. Posner, Foundations of Cognitive Science, MIT Press, Cambridge, MA (1993). [Potts1993]

• C. Potts and K. Takahashi, “An Active Hypertext Model for System Requirements”, Technical Report, Col-

lege of Computing, Georgia Institute of Technology (1993). [Ramos2002]

• I. Ramos, D.M. Berry, and J.A. Carvalho, “The Role of Emotion, Values, and Beliefs in the Construction of

Innovative Work Realities”, pp. 300–314 in Procedings of First International Conference, Soft-Ware 2002: Computing in an Imperfect World, ed. D. Bustard, W. Liu, R. Sterritt, Eds., Springer, LNCS 2311, Belfast, Northern Ireland (April 2002). [Ramos2005]

• I. Ramos, D.M. Berry, and J.A. Carvalho, “Requirements Engineering for Organizational Transformation”,

Journal of Information and Software Technology (to appear 2004 or 2005). [Ross1977a] D.T. Ross, “Structured Analysis (SA): A Language for Communicating Ideas”, IEEE Transactions on Software Engineering SE-3(1), pp. 16–33 (January 1977). [Ross1977b] D.T. Ross and K.E. Schoman, Jr., “Structured Analysis for Requirements Definition”, IEEE Transactions on Software Engineering SE-3(1), pp. 6–15 (January 1977). [Rost2004]

• J. Rost, “Political Reasons for Failed Software Projects”, IEEE Software 21(6), pp. 104–103 (November-

December 2004). [Royce1970] W.W. Royce, “Managing the Development of Large Software Systems: Concepts and Techniques”, in Proceedings of WesCon (August 1970). 9

[Ryan1993]

• K. Ryan, “The Role of Natural Language in Requirements Engineering”, pp. 240–242 in Proceedings of the

IEEE International Symposium on Requirements Engineering, IEEE Computer Society Press, San Diego, CA (January 1993). [Saeki1987]

• M. Saeki, H. Horai, K. Toyama, N. Uematsu, and H. Enomoto, “Specification Framework Based on Natural

Language”, pp. 87–94 in Proceedings of the Fourth International Workshop on Software Specification and Design, Monterey, CA (April 1987). [Salton1983]

• G. Salton and M.J. McGill, Introduction to Modern Information Retrieval, McGraw-Hill, New York, NY

(1983). [Santos1998]

• I. Santos and J.A. Carvalho, “Computer-Based Systems that Support the Structural, Social, Political and

Symbolic Dimensions of Work”, Requirements Engineering 3(2), pp. 138–142 (1998). [Santos2002]

• I. Santos and J.A. Carvalho, “Creating Work Realities Supported by Computer-Based Systems: A Construc-

tionist Perspective”, in REFSQ’02: Eighth International Workshop on Requirements Engineering: Founda- tion for Software Quality (9-10 September 2002). [Schach1992] S.R. Schach, Software Engineering, Second Edition, Aksen Associates & Irwin, Boston, MA (1992). [Sharp1999]

• H. Sharp, A. Finkelstein, and G. Galal, “Stakeholder Identification in the Requirements Engineering Pro-

cess”, in Proceedings of the 1999 Workshop on Requirements Engineering Process (REP’99), Florence, Italy (September 1999). [Shneiderman1984]

• B. Shneiderman, Designing the User Interface: Strategies for Effective Human-Computer Interaction,

Addison Wesley, Reading, MA (1984). [Sindre2000]

• G. Sindre and A.L. Opdahl, “Eliciting Security Requirements by Misuse Cases”, pp. 120–131 in Proceed-

ings of TOOLS Pacific 2000 (20–23 November 2000). [Smith1993] T.J. Smith, “READS: A Requirements Engineering Tool”, pp. 94–97 in Proceedings of the IEEE Interna- tional Symposium on Requirements Engineering, IEEE Computer Society Press, San Diego, CA (January 1993). [Some ´1996]

• S. Some

´, R. Dssouli, and J. Vaucher, “Toward an Automation of Requirements Engineering Using Scenarios”, Journal of Computing and Information 2(1), pp. 1110–1132 (1996). [Strand1982] E.M. Strand and W.T. Jones, “Prototyping and Small Software Projects”, ACM SIGSOFT Software Engineering Notes 7(5), pp. 169–170 (December 1982). 10

[Teichroew1977]

• D. Teichroew and E.A. Hershey, III, “PSL/PSA: A Computer-Aided Technique for Structure Documentation

and Analysis of Information Processing Systems”, IEEE Transactions on Software Engineering SE-3(1), pp. 41–48 (January 1977). [Tichy1985]

• W. Tichy, “RCS—A System for Version Control”, Software—Practice and Experience 15(7), pp. 637–654

(July 1985). [Tomayko2002] J.E. Tomayko, “A Comparison of Pair Programming to Inspections for Software Defect Reduction”, Com- puter Science Education 12(3), pp. 213–222 (September 2002). [van Lamsweerde2000]

• A. van Lamsweerde, “Requirements Engineering in the Year 00: A Research Perspective”, in Proceedings
• f 22nd International Conference on Software Engineering, ACM, Limerick, Ireland (June 2000).

[von Neumann1944]

• J. von Neumann and O. Morgenstern, Theory of Games and Economic Behavior, Princeton University

Press, Princeton, NJ (1944). [Wasserman1984] A.I. Wasserman, “Developing Interactive Information Systems with the User Software Engineering Metho- dology”, in Proceedings, First Conference on Human-Computer Interaction, London, UK (September 1984). [Wasserman1986a] A.I. Wasserman, P.A. Pircher, and D.T. Shewmake, “Building Reliable Interactive Information Systems”, IEEE Transactions on Software Engineering SE-12(1) (January 1986). [Wasserman1986b] A.I. Wasserman, P.A. Pircher, D.T. Shewmake, and M.L. Kirsten, “Developing Interactive Information Sys- tems with the User Software Engineering Methodology”, IEEE Transactions on Software Engineering SE- 12(1), pp. 147–156 (January 1986). [Winchester1982]

• J. Winchester and G. Estrin, “Requirements Definition and Its Interface to the SARA Design Methodology

for Computer-Based Systems”, AFIPS Conference Proceedings 51, pp. 369–379 (June 1982). [Wood1994] D.P. Wood, M.G. Christel, and S.M. Stevens, “A Multimedia Approach to Requirements Capture and Modeling”, in Proceedings of the IEEE International Conference on Requirements Engineering, IEEE Com- puter Society Press, Colorado Springs, CO (April 1994). [Wood1995]

• J. Wood and D. Silver, Joint Application Development, John Wiley (1995).

[Zahniser1993] R.A. Zahniser, “Design by Walking Around”, Communications of the ACM 36(10), pp. 115–123 (October 1993). 11

[Zave1982]

• P. Zave, “An Operational Approach to Requirements Specification for Embedded Systems”, IEEE Trans-

actions on Software Engineering SE-8(3), pp. 250–269 (May 1982). [Zave1997]

• P. Zave, “Classification of Research Efforts in Requirements Engineering”, ACM Computing Surveys 29(4),
• pp. 315–321 (1997).

[Zucconi1993]

• L. Zucconi, “I Never Realized My Requirements Were Object-Oriented Until I Talked to My Analyst”, pp.

230 in Proceedings of the IEEE International Symposium on Requirements Engineering, IEEE Computer Society Press, San Diego, CA (January 1993). 12