Wednesday, November 18, 2009

References









































References




Alexander, Ian F., and Neil Maiden, eds. 2004. Scenarios, Stories, Use Cases: Through the Systems Development Life-Cycle. Chichester, UK: John Wiley & Sons, Ltd.





Alexander, Ian F., and Richard Stevens. 2002. Writing Better Requirements. London: Addison-Wesley.





Ambler, Scott W., and Larry L. Constantine. 2000a. The Unified Process Inception Phase: Best Practices in Implementing the UP. Lawrence, KS: CMP Books.





Ambler, Scott W., and Larry L. Constantine. 2000b. The Unified Process Elaboration Phase: Best Practices in Implementing the UP. Lawrence, KS: CMP Books.





Armour, Frank, and Granville Miller. 2001. Advanced Use Case Modeling: Software Systems. Boston: Addison-Wesley.





Basili, Victor R., and H. Dieter Rombach. 1988. "The TAME Project: Towards Improvement-Oriented Software Environments." IEEE Transactions on Software Engineering 14(6): 758–773.





Beck, Kent. 2000. Extreme Programming Explained: Embrace Change. Reading, MA: Addison-Wesley Longman.





Beck, Kent, and David West. 2004. "User Stories in Agile Software Development." In Scenarios, Stories, Use Cases: Through the Systems Development Life-Cycle, ed. Ian F. Alexander and Neil Maiden, 265–279. Chichester, UK: John Wiley & Sons, Ltd.





Beyer, Hugh, and Karen Holtzblatt. 1998. Contextual Design: Defining Customer-Centered Systems. San Francisco: Morgan Kaufmann Publishers, Inc.





Bittner, Kurt, and Ian Spence. 2003. Use Case Modeling. Boston: Addison-Wesley.





Blackburn, Joseph D., Gary D. Scudder, and Luk N. Van Wassenhove. 1996. "Improving Speed and Productivity of Software Development: A Global Survey of Software Developers." IEEE Transactions on Software Engineering 22(12): 875–885.





Boehm, Barry W. 1981. Software Engineering Economics. Englewood Cliffs, NJ: Prentice-Hall.





Boehm, Barry W., et al. 1975. "Some Experience with Automated Aids to the Design of Large-Scale Reliable Software." IEEE Transactions on Software Engineering 1(1): 125–33.





Booch, Grady, James Rumbaugh, and Ivar Jacobson. 1999. The Unified Modeling Language User Guide. Reading, MA: Addison-Wesley.





Brians, Paul. 2003. Common Errors in English Usage. Wilsonville, OR: William, James & Company.





Cockburn, Alistair. 2001. Writing Effective Use Cases. Boston: Addison-Wesley.





Cohn, Mike. 2004. User Stories Applied: For Agile Software Development. Boston: Addison-Wesley.





Cooper, Alan. 1999. The Inmates Are Running the Asylum: Why High-Tech Products Drive Us Crazy and How to Restore the Sanity. Indianapolis, IN: Sams.





Costello, Rita J., and Liu, Dar-Biau. 1995. "Metrics for Requirements Engineering." J. Systems Software 29(1): 39–63.





Davis, Alan M. 1993. Software Requirements: Objects, Functions, and States. Englewood Cliffs, NJ: PTR Prentice Hall.





Davis, Alan M. 1995. 201 Principles of Software Development. New York: McGraw-Hill.





DeMarco, Tom. 1979. Structured Analysis and System Specification. Englewood Cliffs, NJ: Prentice-Hall.





DeMarco, Tom. 2001. Slack: Getting Past Burnout, Busywork, and the Myth of Total Efficiency. New York: Broadway Books.





DeMarco, Tom, and Timothy Lister. 1999. Peopleware: Productive Projects and Teams, Second Edition. New York: Dorset House Publishing.





Derby, Esther. 2004. "Building a Requirements Foundation Through Customer Interviews." Insights 2(1): 1–4.





Fairley, Richard E., and Mary Jane Willshire. 2005. "Iterative Rework: The Good, the Bad, and the Ugly." IEEE Computer 38(9): 34–41.





Gause, Donald C., and Brian Lawrence. 1999. "User-Driven Design." Software Testing & Quality Engineering 1(1): 22–28.





Gause, Donald C., and Gerald M. Weinberg. 1989. Exploring Requirements: Quality Before Design. New York: Dorset House Publishing.





Gilb, Tom. 2005. Competitive Engineering: A Handbook for Systems Engineering, Requirements Engineering, and Software Engineering Using Planguage. Oxford: Elsevier Butterworth-Heinemann.





Gilb, Tom, and Dorothy Graham. 1993. Software Inspection. Wokingham, UK: Addison-Wesley.





Goldstein, Harry. 2005. "Who Killed the Virtual Case File?" IEEE Spectrum 42(9): 24–35.





Grady, Robert B. 1999. "An Economic Release Decision Model: Insights into Software Project Management." In Proceedings of the Applications of Software Measurement Conference, 227–239. Orange Park, FL: Software Quality Engineering.





Hall, Tracy,Sara Beecham, and Austen Rainer. 2002. "Requirements Problems in Twelve Software Companies: An Empirical Analysis." IEE Proceedings—Software, 149(5): 153–60.





Hofmann, Hubert F., and Franz Lehner. 2001. "Requirements Engineering as a Success Factor in Software Projects." IEEE Software 18(4): 58–66.





Hooks, Ivy F., and Kristin A. Farry. 2001. Customer-Centered Products: Creating Successful Products Through Smart Requirements Management. New York: AMACOM.





Humphrey, Watts. 1998. "Your Date or Mine?" news@sei (September): Software Engineering Institute. http://www.sei.cmu.edu/news-at-sei/columns/watts_new/1998/September/watts-sep98.pdf.





IEEE. 1990. IEEE Std. 610.12-1990: "IEEE Standard Glossary of Software Engineering Terminology." Los Alamitos, CA: IEEE Computer Society Press.





IEEE. 1998. IEEE Std 830-1998: "IEEE Recommended Practice for Software Requirements Specifications." Los Alamitos, CA: IEEE Computer Society Press.





International Function Point Users Group (IFPUG). 2002. Function Point Counting Practices Manual, Version 4.1.1. Princeton Junction, NJ: International Function Point Users Group.





Jacobson, Ivar, Grady Booch, and James Rumbaugh. 1999. The Unified Software Development Process. Reading, MA: Addison-Wesley.





Jeffries, Ron, Ann Anderson, and Chet Hendrickson. 2001. Extreme Programming Installed. Boston: Addison-Wesley.





Jones, Capers. 2000. Software Assessments, Benchmarks, and Best Practices. Boston: Addison-Wesley.





Karner, Gustav. 1993. "Resource Estimation for Objectory Projects." http://www.bfpug.com.br/Artigos/UCP/Karner%20-%20Resource%20Estimation%20for%20Objectory%20Projects.doc.





Kulak, Daryl, and Eamonn Guiney. 2004. Use Cases: Requirements in Context, Second Edition. Boston: Addison-Wesley.





Lauesen, Soren. 2002. Software Requirements: Styles and Techniques. London: Addison-Wesley.





Leffingwell, Dean. 1997. "Calculating the Return on Investment from More Effective Requirements Management." American Programmer 10(4): 13–16.





Leffingwell, Dean, and Don Widrig. 2003. Managing Software Requirements, Second Edition: A Use Case Approach. Boston: Addison-Wesley.





McConnell, Steve. 1998. Software Project Survival Guide. Redmond, WA: Microsoft Press.





McConnell, Steve. 2006. Software Estimation: Demystifying the Black Art. Redmond, WA: Microsoft Press.





Morgan, Tony. 2002. Business Rules and Information Systems: Aligning IT with Business Goals. Boston: Addison-Wesley.





Nejmeh, Brian A., and Ian Thomas. 2002. "Business-Driven Product Planning Using Feature Vectors and Increments." IEEE Software 19(6): 34–42.





Ribu, Kirsten. 2001. "Estimating Object-Oriented Software Projects with Use Cases." Master of Science Thesis, University of Oslo. http://www.bfpug.com.br/Artigos/UCP/Ribu-Estimating_O-O_SW_Projects_with_Use_Cases.pdf.





Robertson, James. 2002. "Eureka! Why Analysts Should Invent Requirements." IEEE Software 19(4): 20–22.





Robertson, James, and Suzanne Robertson. 1994. Complete Systems Analysis: The Workbook, The Textbook, The Answers. New York: Dorset House Publishing.





Robertson, Suzanne, and James Robertson. 1999. Mastering the Requirements Process. Harlow, UK: Addison-Wesley.





Rodrigues, Alexandre. 2001. "Project Goals, Business Performance, and Risk." Cutter Consortium e-Project Management Advisory Service Executive Update 2(7).





Ross, Ronald G. 2003. Principles of the Business Rule Approach. Boston: Addison-Wesley.





Sheldon, F., et al. 1992. "Reliability Measurement from Theory to Practice." IEEE Software 9(4): 13–20.





Sommerville, Ian, and Pete Sawyer. 1997. Requirements Engineering: A Good Practice Guide. Chichester, UK: John Wiley & Sons.





The Standish Group. 2003. "What Are Your Requirements?" West Yarmouth, MA: The Standish Group International, Inc.





von Halle, Barbara. 2002. Business Rules Applied: Building Better Systems Using the Business Rules Approach. New York: John Wiley and Sons.





Whitmire, Scott A. 1995. "An Introduction to 3D Function Points." Software Development, 3(4): 43–53.





Wiegers, Karl E. 1996. Creating a Software Engineering Culture. New York: Dorset House Publishing.





Wiegers, Karl E. 1999. "Software Process Improvement in Web Time." IEEE Software 15(4): 78–86.





Wiegers, Karl E. 2000. "Stop Promising Miracles." Software Development 8(2): 49–54.





Wiegers, Karl E. 2001. "Measuring Requirements Management: Getting to Know Your Requirements Data." http://www.StickyMinds.com, May 21, 2001.





Wiegers, Karl E. 2002a. Peer Reviews in Software: A Practical Guide. Boston: Addison-Wesley.





Wiegers, Karl E. 2002b. "Success Criteria Breed Success." http://www.TheRationalEdge.com (February). http://www.128.ibm.com/developerworks/rational/library/2950.html.





Wiegers, Karl E. 2002c. "Saving for a Rainy Day." http://www.TheRationalEdge.com (April). http://www.128.ibm.com/developerworks/rational/library/content/RationalEdge/apr02/RainyDayApr02.pdf.





Wiegers, Karl E. 2003a. Software Requirements, Second Edition. Redmond, WA: Microsoft Press.





Wiegers, Karl E. 2003b. "See You in Court." Software Development 11(1): 36–40.





Wilson, Peter B. 1995. "Testable Requirements—An Alternative Sizing Measure." The Journal of the Quality Assurance Institute 9(4): 3–11.






































Posted by at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)