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 of 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
Recommend
More recommend
