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

Bach, James. 1997. "Good Enough Quality: Beyond the Buzzword." IEEE Computer Society , August, p. 97.

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

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

” ” ”. 1988. "A Spiral Model of Software Development and Enhancement." IEEE Computer 21(5), pp. 61 “72.

Boehm, Barry W., and Philip N. Papaccio. 1988. "Understanding and Controlling Software Costs." IEEE Transactions on Software Engineering 14(10), pp. 1462 “1473.

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

Brooks, Frederick P., Jr. 1975. The Mythical Man Month: Essays on Software Engineering . Reading, MA: Addison-Wesley.

Cockburn, Alistair. 2002. Agile Software Development . Boston, MA: Addison-Wesley.

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

” ” ”. 1995. 201 Principles of Software Development . New York: McGraw-Hill.

” ” ”. 1999. "Achieving Quality in Software Requirements." Software Quality Professional 1(3), pp. 37 “44.

Dorfman, Merlin, and Richard H. Thayer. 1990. Standards, Guidelines, and Examples of System and Software Requirements Engineering . Los Alamitos, CA: IEEE Computer Society Press.

European Software Process Improvement Training Initiative. 1995. User Survey Report .

FDA (Food and Drug Administration). 1996. "Medical Devices; Current Good Manufacturing Practice (CGMP) Final Rule; Quality System Regulation." Federal Register 61(195) (7 October), Subpart C, pp. 52657 “52658.

” ” ”. 1998. "Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices." Final version (May 29).

Fisher, Roger, William Ury, and Bruce Patton. 1983. Getting to Yes: Negotiating Agreement without Giving In , 2nd ed. New York: Penguin Books.

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

Grady, Robert B. 1992. Practical Software Metrics for Project Management and Process Improvement . Englewood Cliffs, NJ: Prentice-Hall.

Heumann, James. 2001. "Generating Test Cases from Use Cases." Cupertino, CA: Rational Software Corporation. Available online (February 2003) at

Humphrey, Watts S. 1989. Managing the Software Process . Reading, MA: Addison-Wesley.

IEEE. 1994. IEEE Standards Collection, Software Engineering . New York: IEEE.

INCOSE (International Council on Systems Engineering). 1993. "An Identification of Pragmatic Principles ”Final Report." INCOSE WMA Chapter. Available online (February 2003) at http://

” ” ”. 2003. "What Is Systems Engineering?" Available online (February 2003) at

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

Jacobson, Ivar, Magnus Christerson, Patrik Jonsson, and Gunnar –vergaard. 1992. Object-Oriented Software Engineering: A Use Case Driven Approach . Harlow, U.K.: Addison-Wesley.

Jacobson, Ivar, Maria Ericsson, and Agneta Jacobson. 1995. The Object Advantage: Business Process Reengineering with Object Technology . Wokingham, U.K.: Addison-Wesley.

Jones, Capers. 1994. "Revitalizing Software Project Management." American Programmer 6(7), pp. 3 “12.

Karat, Claire-Marie. 1998. "Guaranteeing Rights for the User." Communications of the ACM 41(12), p. 29.

Kruchten, Philippe. 1995. "The 4+1 View of Architecture." IEEE Software 12(6), pp. 45 “50.

” ” ”. 1999. The Rational Unified Process: An Introduction . Reading, MA: Addison-Wesley.

Moore, Geoffrey A. 1991. Crossing the Chasm: Marketing and Selling Technology Products to Mainstream Customers . New York: HarperCollins.

Rational Software Corporation. 2002. "Rational Unified Process 2002." Cupertino, CA: Rational Software Corporation.

Rechtin, Eberhardt, and Mark W. Maier. 1997. The Art of Systems Architecting . Boca Raton, FL: CRC Press.

Royce, Walker. 1998. Software Project Management: A Unified Approach . Reading MA: Addison-Wesley.

Royce, Winston W. 1970. "Managing the Development of Large Software Systems: Concepts and Techniques." In WESCON Technical Papers , Vol. 14. Los Angeles: WESCON. Reprinted in Proceedings of the Ninth International Conference on Software Engineering , 1987, pp. 328 “338.

Rumbaugh, James, Ivar Jacobson, and Grady Booch. 1998. The Unified Modeling Language Reference Manual . Reading, MA: Addison-Wesley.

Scharer, Laura. 1981. "Pinpointing Requirements." Originally published as an article in Datamation . Reprinted in Merlin Dorfman and Richard H. Thayer (eds), Software Requirements Engineering . Los Alamitos, CA: IEEE Computer Society Press, 1990.

Schneider, Geri, and Jason P. Winters. 1998. Applying Use Cases: A Practical Guide . Reading, MA: Addison-Wesley.

SEI (Software Engineering Institute). 1993. Capability Maturity Model for Software . Version 1.1, Document No. CMU/SEI-93-TR-25, ESC-TR-93-178. Pittsburgh, PA: Carnegie-Mellon University Software Engineering Institute.

Shaw, Mary, and David Garlan. 1996. Software Architecture: Perspective on an Emerging Discipline . Upper Saddle River, NJ: Prentice-Hall.

Snyder, Terry, and Ken Shumate. 1992. "Kaizen Project Management." American Programmer 5(10), pp. 12 “22.

The Standish Group. 1994. "Charting the Seas of Information Technology ”Chaos." West Yarmouth, MA: The Standish Group International.

Weinberg, Gerald. 1971. The Psychology of Computer Programming . New York: Van Nostrand Reinhold.

” ” ”. 1995. "Just Say No! Improving the Requirements Process." American Programmer 8(10), pp. 19 “23.

Wood, Bill J., and Julia W. Ermes. 1993a. "Applying Hazard Analysis to Medical Devices" (Part I). Medical Device & Diagnostic Industry Magazine 15(1), pp. 79 “83.

” ” ”. 1993b. "Applying Hazard Analysis to Medical Devices" (Part II). Medical Device & Diagnostic Industry Magazine 15(3), pp. 58 “64.


Managing Software Requirements[c] A Use Case Approach
Managing Software Requirements[c] A Use Case Approach
ISBN: 032112247X
Year: 2003
Pages: 257 © 2008-2017.
If you may any questions please contact us: