Abran, Alain и JamesW. Moore., eds. 2001. Guide to the Software Engineer-ling Body of Knowledge, Trial Version. LosAlamitos, CA: lEEEComputer Society Press.
Alexander, Ian F. и Richard Stevens. 2002. Writing Better Requirements. London: Addison-Wesley.
Ambler, Scott. 1995. Reduce Development Costs with Use-Case Scenario Testing. Software Development 3(7):53-61.
Теже авторы. 1999. TraceYour Design. Software Development7(4):48-55.
Andriole, Stephen J. 1996. Managing Systems Requirements: Methods, Tools, and Cases. NewYork: McGraw-Hill.
Arlow, Jim. 1998. Use Cases, UML Visual Modeling and the Triviati sation
of Business Requirements. Requirements Engineering 3(2);150-152.
Armour, Frank и Granville Miller. 2001. Advanced Use Case Modeling: Software Systems. Boston, MA: Addison-Wesley.
Arnold, Robert S. и Shawn A. Bohner. 1996. Software Change Impact Analysis. Los Alamitos, CA: IEEE Computer Society Press.
Bass, Len, Paul Clements и Rick Kazman. 1998. Software Architecture in Practice. Reading, MA: Addison-Wesley.
iBeck, Kent. 2000. Extreme Programming Explained: Embrace Change. Boston, MA: Addison-Wesley.
Beizer, Boris. 1990. Software Testing Techniques. 2d ed. New York: Van, INostrand Reinhold.
Теже авторы. 1999. Bestand Worst Testing Practices: A Baker's Dozen. Cutter IT Journal 12{2):32-38.
Beyer, Hugh и Karen Holtzblatt 1998. Contextual Design: Defining Customer-Centered Systems. San Francisco, CA: Morgan Kaufmann Publishers, Inc.
Blackburn, Joseph D, Gary D. Scudder и 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.
Те же авторы. 1988. A Spiral Model of Software Development and Ел hancement. IEEE Computer 21 (5):61 -72.
Те же авторы. 2000. Requirements that Handle IKIWISI, COTS, and Rap-iid Change. IEEE Computer33(7):99-102.
Boehm, BarryW. и Philip N. Papaccio. 1988. Understanding and Controlling Software Costs. IEEE Transactions on Software Engineering 14(10):1462-1476.
Boehm, Barry, J. R. Brown и M. Lipow. 1976. Quantitative Evaluation of Software Quality. Second IEEE International Conference on Software Engineering, 592-605. Los Alamitos, CA: IEEE Computer Society Press.
iBoehm, BarryW., et al. 2000. Software Cost Estimation with Cocomo II.
Upper Saddllnternational Conference on Software Engineering, 592-605.. Los Alamitos, CA: IEEE Computer Society Press.
Boehm, BarryW., etal. 2000. Software Cost Estimation with Cocomo II. Upper Saddle River, NJ: Prentice Hall PTR.
Booch. Grady, James Rumbaugh и Ivar Jacobson. 1999. The Unified Modeling Language User Guide. Reading, MA: Addison-Wesley.
IBrooks, Frederick P.. Jr. 1987. No Silver Bullet: Essence and Accidents of Software Engineering. С River, NJ: Prentice Hall PTR.
Booch, Grady, James Rumbaugh и Ivar Jacobson. 1999. The Unified Modeling Language User Guide. Reading, MA: Addison-Wesley. •
|
|
iBrooks, Frederick P., Jr. 1987. No Silver Bullet: Essence and Accidents of Software Engineering. Computer 20(4): 10-19.
Brown Norm. 1996. Industrial-Strength Management Strategies. IEEE Software 13(4}:94~103.
Те же авторы. 1999. High-Leverage Best Practices: What Hot Companies Are Doing to Stay Ahead. Cutter П Journal 12(9):4-9.
Business Rules Group. 1993. « Defining Business Rules: What Are They Really?» https://www.husinessrulesgroup.org.
Caputo, Kim. 1998. CMM Implementation Guide: Choreographing Software Process Improvement. Reading, MA: Addison-Wesley.
Carnegie Mellon University/Software Engineering Institute. 2000a. CMMI for Systems Engineering/Software Engineering, Version 1.02: Staged Representation. Technical ReportCMU/SEI-2000-TR-018. Pittsburgh, PA: Carnegie Mellon University/Software Engineering Institute.
Те же авторы. 2000b CMMI for Systems Engineering/Software Engineering, Version 1.02: Continuous Representation. Technical Report CMU/ SEI-2000-TR-029. Pittsburgh, PA: Carnegie Mellon University/ Software 'Engineering Institute,
Carr, Marvin J., Suresh L Konda, Ira Monarch, F. Carol Ulrich и Clay F. Walker. 1993. Taxonomy-Based Risk Identification (CMU/ SEI-93-TR-6). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University.
Cavano, J. P. и J. A. McCall. 1978. A Frameworkforthe Measurement of Software Quality. ACM SIGSOFTSoftware Engineering Notes 3(5): 133-139,
Charette, Robert N. 1990. Applications Strategies for Risk Analysis. New York: McGraw-Hill.
Christel, Michael G. и KyoC. Kang. 1992. Issues in Requirements Elicita-tion (CMU/SEI-92-TR-12). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University.
Cockburn, Alistair. 2001. Writing Effective Use Cases. Boston, MA: Addison-Wesley.
Те же авторы. 2002. Agile Software Development. Boston, MA: Addison-Wesley.
Cohen, Lou. 1995. Quality Function Deployment: Howto MakeQFDWork forYou. Reading, MA: Addison-Wesley,
Collard; Ross. 1999. Test Design. Software Testing ^.Quality Engineering 1{4):30-37.
Constantine, Larry. 1998. Prototyping from the User's Viewpoint. Software Development 6(U):51 -57.
Constantine, Larry L. и LucyA. D. Lockwood. 1999. Software for Use: A Practical Guide to the Models and Methods of Usage-Centered Design. Reading, MA: 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.
Covey, Stephen R. 1989. The 7 Habits of Highly Effective People. New York: Simon & Schuster.
Davis, Alan vi. 1993. Software Requirements: Objects, Functions and States. Englewood Cliffs, NJ: Prentice Hall PTR.
|
|
Те же авторы. 1995. 201 Principles of Software Development. New York: McGraw-Hill.
DeGrace, Peter и Leslie HuletStahl. 1993. The Olduvai Imperative: CASE.and the State of Software Engineering Practice. Englewood Cliffs, NJ: V don Press/Prentice Hall.
DeMarco, Tom. 1979. Structured Analysis and System Specification. Englewood Cliffs, NJ: Prentice Hall.
DeMarco, Tom и Timothy Lister. 1999. Peopleware: Productive Projects and Teams, 2d ed. NewYork: Dorset House Publishing.
Drabick, Rodger D. 1999. On-Track Requirements. Software Testing & Quality Engineering 1(3}:54-60.
Dutta. Soumitra, Michael Lee и LukVanWassenhove. 1999. Software Engineering in Europe: A Study of Best Practices. IEEE Software 16(3):82-90.
ESPITI. 1995. European Software Process Improvement Training Initiative. User Survey Report.
Fagan, Michael E. 1976. Design and Code Inspections to Reduce Errors in Program Development. IBM Systems Journal 15(3): 182-211.
Ferdinandi, Patricia L. 2002. A Requirements Pattern: Succeeding in the Internet Economy. Boston, MA: Addison-Wesley.
Fisher, Roger, William Ury и Bruce Patton. 1991. Getting toYes: Negotiating Agreement Without Giving In. NewYork: Penguin USA.
Florence, Al. 2002. Reducing Risks Through Proper Specification of Software Requirements. CrossTalk 15(4}:13-15.
Fowler, Floyd J. 1995. Improving Survey Questions: Design and Evaluation. Thousand Oaks, CA: Sage Publications.
Fowler, Martin. 1999. Refactoring: Improving the Design of Existing Code. Boston, MA: Addison-Wesley.
Freedman, Daniel P. и Gerald M.Weinberg. 1990. Handbook of Walkthroughs, Inspections, and Technical Reviews: Evaluating Programs, Projects, and Products, 3d ed. NewYork: Dorset House Publishing.
Gainer, Jeff. 1999. The Cutter IT E-Mail Advisor, August 11, 1999.
Gause, DonaldС. и Brian Lawrence. 1999. User-Driven Design. Software Testing & Quality Engineering 1(1):22-28.
Gause, Donald С. и Gerald M. Weinberg. 1)9. Exploring Requirements:
Quality Before Design. York: Dorset House Publishing.
Gilb. Tom. 1988. Principles of Software Engineering Management. Har-'low, England: Addison-Wesley.
Те же авторы. 1997 Quantifying the Qualitative: Howto Avoid Vague Requirements by Clear Specification Language. Requirenautics Quarterly 12:9-13.
Gilb, Tom и Dorothy Graham. 1993. Software Inspection. Wokingharr England: Addison-Wesley.
Glass, Robert L. 1 Э92. Building Quality Software. Englewood Cliffs, NJ: Prentice Hall.
Те же авторы. 1999. Inspections-Some Surprising Findings, Communications of the ACM 42(4): 17-19.
Gotel, О. и A. Finkelstein. 1994. An Analysis of the Requirements Trace-ability Problem. In Proceedings of the First International Conference on Requirements Engineering, 94-101. LosAlarr itos, CA: IEEE Computer Society Press.
|
|
Gottesdiener, Ellen. 20l Decide Howto Decide. Software Development 9(1);65-70.
Те же авторы. Requirements by Collaboration: Workshops for Defining Needs. Boston, MA: Addison-Wesley,
Grady, Robert B. 1999. An Economic Release Decision Model: Insights linto Software Project Management. In Proceedings of the Applications of Software Measurement Conference, 227-239. Orange Park, FL: Software Quality Engineering.
Grady, RobertВ. и Tom Van Slack. 1994. Key Lessons in Achieving Widespread Inspection Use. lEEESoftware 11(4):46-57.
Graham, Dorothy. 2002. Requirements and Testing: Seven Missing-Link Myths. IEEE Software 19(5): 15-17.
Ham, Gary A. 1998. Four Roads to Use Case Discovery: There Is a Use (and a Case) for Each One. CrossTalk 11 (12): 17-19.
Hatley, Derek, Peter Hruschka и Imtiaz Pirbhai. 2000. Process for System Architecture and Requirements Engineering. NewYork: Dorset House Publishing.
Highsmith, James A., III. 2000. Adaptive Software Development: A Collaborative Approach to Managing Complex Systems. New York: Dorset House Publishing.
Hofmann, Hubert F. и Franz Lehner. 2001. Requirements Engineering as a Success Factor in Software Projects. IEEE Software 18(4):58-66.
Hohmann, Luke. 1997. Managing Highly Usable Graphical User Interface Development Efforts, https://members.aol.com/lhohmann/papers.htm.
Hooks, Ivy F. и Kristin A. Farry. 2001. Customer-Centered Products: Creating Successful Products Through Smart Requirements Management, NewYork: AMACOM.
Hsia, Pei, David Kung и Chris Sell. 1997. Software Requirements and Acceptance Testing. In Annals of Software Engineering, Nancy R. Mead, ed, 3:291-317.
Humphrey, Watts S. 1989. Managing the Software Process. Reading, MA: Addison-Wesley.
Теже авторы. 1997. Managing Technical People: Innovation, Teamwork, and the Software Process. Reading, MA: Addison-Wesley.
IEEE. 1990. lEEEStd 610.12-1990: IEEE Standard Glossary of Software Engineering Terminology. LosAlamitos, CA: IEEE Computer Society Press.
Те же авторы. 1992, IEEE Std 1061-1992: IEEE Standard for a Software Quality Metrics Methodology. Los Alamitos, CA: IEEE Computer Society Press.
Те же авторы. 1998а. IEEE Std 1362-1998: IEEE Guide for Information Technology—System Definition—Concept of Operations (ConOps) Document. Los Alamitos, CA: IEEE Computer Society Press.
Те же авторы. 1998b. lEEfc Std 830-1998: IEEE Recommended Practice for Software Requirements Specifications. Los Alamitos, CA: IEEE Computer Society Press.
Те же авторы. 1998с. IEEE Std 1233-1998: IEEE Guide for Developing System Requirements Specifications. Los Alamitos, CA: IEEE Computer Society Press.
International Function Point Users Group. 2002. Function Point Counting Practices Manual, Version 4.1.1. Princeton Junction, NJ: International Function Point Users Group.
Jackson, Michael. 1995. Software Requirements & Specifications: A Lexicon of Practice, Principles, and Prejudices. Harlow, England: Addison-Wes-ley.
Jacobson, Ivar, Magnus Christerson, Patrik Jonsson и Gunnar LJver-gaard. 1992. Object-Oriented Software Engineering: A Use Case Driven Approach. Harlow, England: Addison-Wesley.
Jacobson, Ivar, Grady Booch и James Rumbaugh. 1999. The Unified Software Development Process. Reading, MA: Addison-Wesley,
Jarke, Matthias. 1998. Requirements Tracing. Communications of the ACM41{12):32-36.
Jeffries, Ron, Ann Anderson и Chet Hendrickson. 3001. Extreme Programming Installed. Boston, MA: Addison-Wesley.
Jones, Capers. 1994. Assessment and Control of Software Risks. Engle-wood Cliffs, NJ: Prentice HallPTR.
Те же авторы. 1996а. Strategies for Managing Requirements Creep. IEEE Computer 29(6}:92-94.
Те же авторы. 1996b. Applied Software Measurement, 2d ed. NewYork: McGraw-Hill.
Те же авторы. 1997. Software Quality: Analysis and Guidelines for Success. Boston, MA: International Thomson Computer Press.
Jones, David Donald M.York, John F. Nallonи Joseph Simpson. 1995. Factors Influencing Requirement Management Toolset Selection. In Proceedings of the Fifth Annual Symposium of the National Council on Systems Engineering, vol. 2 33-58. Seattle, WA: International Council on Systems Engineering.
Jung, Ho-Won. 1998. Optimizing Value and Cost in Requirements Analysis. IEEE Software 15(4):74-78.
Karlsson, Joachim и Kevin Ryan. 1997. A Cost-Value Approach for Prioritizing Requirements. IEEE Software 14(5):67-74.
Keil, Mark и Erran Carmel. 1995. Customer-Developer Links in Software Development. Communications of the ACM 38(5):33-44.
Kelly, John C, Joseph S. Sherif и Jonathon Hops. 1992. An Analysis of Defect Densities Found During Software Inspections. Journal of Systems and Software 17(2):111-117.
Keith, Norman L. 2001. Project Retrospectives: A Handbook for Team Reviews. New York: Dorset House Publishing.
Kosman, Robert J. 1997. A Two-Step Methodology to Reduce Requirement Defects. In Annals of Software Engineering, Nancy R. Mead, ed. 3:477-494.
Kovitz, Benjamin L. 1999. Practical Software Requirements: A Manual of Content and Style. Greenwich, CT: Manning Publications Co.
Kruchten, Philippe. 1996. A Rational Development Process. CrossTalk 9(7}:11-16.
Kulak, Daryl и Eamonn Guiney. 2000. Use Cases: Requirements in Context. New York: ACM Press.
Larman, Craig. 1998. The Use Case Model: What Are the Processes? Java Report 3(8):62-72.
Lauesen, Soren. 2002. Software Requirements: Styles and Techniques. London: Addison-Wesley.
Lawlis, Patricia K., Kathryn E. Mark, Deborah A. Thomas и Terry Com-theyn. 2001. A Formal Process for Evaluating COTS Software Products. IIEEE Computer 34(5):58-63.
Lawrence, Brian. 1996. Unresolved Ambiguity. American Programmer ■9(5}:17-22.
Те же авторы. 1997. Requirements Happens... American Programmer 10(4}:3-9.
Leffingwell, Dean. 1 997. Calculating the Return on Investment from More Effective Requirements Management. American Programmer 10(4}:13-16.
Leffingwell, Dean и Don Widrig. 2000. Managing Software Requirements: A Unified Approach. Reading, MA: Addison-Wesley.
Leishman, Theron R. и David A. Cook. 2002. Requirements Risks Can Drown Software Projects. CrossTalk 1 5(4):4-8.
Leveson, Nancy. 1995. Safeware: System Safety and Computers. Reading, MA: Addison-Wesley.
Lilly, Susan. 2000. How to Avoid Use-Case Pitfalls. Software Development 8(1):40-44.
Martin, James. 1991. Rapid Application Development. New York: Mac-imillan Publishing.
Martin, Johnny и W. T. Tsai. 1990. N-fold Inspection: A Requirements Analysis Technique. Communications of the ACM 33{2):225-232.
McCabe, Thomas J. 1982. Structured Testing: A Software Testing Methodology Using the Cyclomatic Complexity Metric. National Bureau of Standards Special Publication 500-599.
McConnell, Steve. 1993. Code Complete: A Practical Handbook of Software Construction. Redmond, WA: Microsoft Press.
Те же авторы. 1996. Rapid Development: Taming Wild Software Schedules. Redmond.WA: Microsoft Press.
Те же авторы. 1998. Software Project Survival Guide. Redmond, WA: Microsoft Press.
McGraw, Karen L. и Karan Harbison. 1997. User-Centered Requirements: The Scenario-Based Engineering Process. Mahwah, NJ: Lawrence Erlbaum Associates.
McMenamin, Stephen M. и John F. Palmer. 1984. Essential Systems Analysis. Englewood Cliffs, NJ: Prentice Hall.
Moore, Geoffrey A. 1991. Crossing the Chasm: Marketing and Selling IHigh-Tech Products to Mainstream Customers. NewYork: HarperBusiness.
Morgan, Tony, 2002. Business Rules and Information Systems: Aligning IIT with Business Goals. Boston, MA: Addison-Wesley.
Musa, John D. 1996. Software-Reliability-Engineered Testing. IEEE Computer 29(11):61-68.
Musa, John, Anthony lannino и Kazuhira Okumoto. 1987. Software Reliability: Measurement, Prediction, Application. NewYork: McGraw-Hill..
Myers, Glenford J. 1979, The Art of Software Testing. New York: John Wiley & Sons.
Nejmeh, Brian А. и Ian Thomas. Business-Driven Product Planning Using.Feature Vectors and Increments. II ЕЕ Software 19(6):34-42.
Nelsen, E. Dale. 1990. System Engineering and Requirement Allocation. In System and Software Requirements Engineering, Richard H. Thayerand IMerlin Dorfman, eds. Los Alamitos, CA: IEEE Computer Society Press.
Nielsen, Jakob. 2000. Designing Web Usability. Indianapolis, IN: New Riders Publishing.
Pardee, William J. 1996. To Satisfy & Delight Your Customer: How to Manage for Customer Value. NewYork: Dorset House Publishing,
Paulk, Mark, et al. 1995. The Capability Maturity Model: Guidelines for Improving the Software Process. Reading, MA: Addison-Wesley.
Pfleeger, Shari Lawrence. 2001. Software Engineering: Theory and Practice, 2d ed. Englewood Cliffs, NJ: Prentice Hall.
Porter, Adam A., Lawrence G. Votta, Jr. и Victor R. Basili. 1995. Comparing Detection Methods for Software Requirements Inspections: A Replicated Experiment. lEEETransactions on Software Engineering 21(6):563-575.
Porter-Roth, Bud. 2002. Request for Proposal: A Guide to Effective RFP Development. Boston, MA: Addison-Wesley.
Poston, Robert M. 1996. Automating Specification-Based Software Testing. Los Alamitos, CA: IEEE Computer Society Press.
Potter, Neil S. и Mary E. Sakry. 2002. Making Process Improvement Work: A Concise Action Guide for Software Managers and Practitioners. Boston, MA; Addison-Wesley.
Project Management Institute. 2000. A Guide to the Project Management 'Body of Knowledge, 2000 Edition. Newtown Square, PA: Project Management Institute.
Putnam, Lawrence H. и Ware Myers. 1997. Industrial Strength Software: Effective Management Using Measurement. Los Alamitos, CA: IEEE Computer Society Press.
Radice, Ronald A, 2002. High Quality Low Cost Software Inspections. An-dover, MA: Paradoxicon Publishing.
Ramesh, Bala, Curtis Stubbs, Timothy Powers и Michael Edwards. 1995. Lessons Learned from Implementing Requirements Traceability. CrossTalk 8(4): 11-15,20.
Ramesh, Balasubramaniam. 1998. Factors Influencing Requirements Traceability Practice. Communications of the ACM41(12):37-44.
Rettig, Marc. 1994. Prototyping for Tiny Fingers. Communications of the ACM37(4):21-27.
Robertson, James. 2002. Eureka! Why Analysts Should Invent Requirements. IEEE Software 19(4):20-22.
Robertson, James и Suzanne Robertson. 1994. Complete Systems Analysis: The Workbook, The Textbook, The Answers. New York: Dorset 'House Publishing.
Те же авторы. 1997. Requirements: Made to Measure. American Programmer 10(8):27-32.
Robertson, Suzanne и James Robertson. 1999. Mastering the Requirements Process. Harlow, England: Addison-Westey.
Ross. Ronald G. 1997. The Business Rule Book: Classifying, Defining, and Modeling Rules, Version 4.0, 2d ed. Houston: Business Rule Solutions, LLC.
Те же авторы. 2001. The Business Rules Classification Scheme. DataTo-Knowledge Newsletter 29(5).
Rothman, Johanna. 2000. Reflections Newsletter3(1).
Rubin, Howard. 1999. The 1999 Worldwide Benchmark Report: Software Engineering and IT Findings for 1 998 and 1 999, Part II. IT Metrics Strategies 5(3):1-13.
Schneider, G. Michael, Johnny Martin nW.T.Tsai. 1992. An Experimental Study of Fault Detection in User Requirements Documents. ACM Transactions on Software Engineering and Methodology l(2): 188-204.
Schneider, Gen nJason P. Winters. 1998.Applying Use Cases: A Practical
Guide. Reading, MA: Addison-Wesley.
Schulmeyer, G. Gordon и James I. McManus, eds. 1996. Total Quality Management for Software. London: International Thomson Computer Press.
Sibbet, David. 1994. Effective Facilitation. San Francisco, CA: The Grove Consultants International.
Simmons, Erik. 2001. From Requirements to Release Criteria: Specifying, Demonstrating, and Monitoring Product Quality. In Proceedings of the 2001 Pacific Northwest Software Quality Conference, 155-165. Portland, OR: Pacific Northwest Software Quality Conference.
Smith, Larry W. 2000. Project Clarity Through Stakeholder Analysis. CrossTalk13(12):4-9.
Smith, R. Craig. 1998. Using a Quality Model Framework to Strengthen the Requirements Bridge. In Proceedings of the Third International Confer-ence on Requirements Engineering, 1 18-125.LosAlamitos,CA: IEEE Computer Society Press.
Sommerville, Ian и Pete Sawyer. 1997. Requirements Engineering: A Good Practice Guide. Chichester, England: John Wiley & Sons.
Sommerville, Ian и Gerald Kotonya. 1998. Requirements Engineering: Processes and Techniques. Chichester, England: John Wiley & Sons.
Song, Xiping, Bill Hasling, Gaurav Mangla и Bill Sherman. 1998. Lessons Learned from Building a Web-Based Requirements Tracing System. In Proceedings of the Third International Conference on Requirements Engineering, 41-50. LosAlamitos, CA: IEEE Computer Society Press.
Sorensen, Reed. 1999. CCB—An Acronym for 'Chocolate Chip Brownies'? A Tutorial on Control Boards. CrossTalk 12(3):3-6.
The Standish Group. 1995. The CHAOS Report. Dennis, MA: The Standish Group International, Inc.
Steven, John. 2002. Putting Software Terminology to the Test. IEEE Software 19(3):88-89.
Stevens, Richard, Peter Brook, Ken Jackson и Stuart Arnold. 1998. Systems Engineering: Coping with Complexity, London: Prentice Hall.
Thayer, Richard H. 2002. Software System Engineering: A Tutorial. IEEE Computer 35(4);68-73.
Thayer, Richard H. и Merlin Dorfman, eds. 1997.Software Requirements Engineering, 2d ed. Los Alamitos, CA: IEEE Computer Society Press.
Thompson, Bruce и Karl Wiegers. 1995. Creative Client/ Server for Evolving Enterprises. Software Development 3(2):34-44.
Voas, Jeffrey. 1999. Protecting Against What? The Achilles Heel of Information Assurance. IEEE Software 16(1):28-29.
von Halle, Barbara. 2002. Business Rules Applied: Building Better Systems Using the Business Rules Approach. NewYork: John Wiley & Sons.
Votta, Lawrence G, Jr. 1993. Does Every Inspection Need a Meeting? Proceedings of the First ACM SIGSOFT Symposium on Software Development Engineering, 107-114. NewYork: ACM Press.
Wallace, Dolores R. и Laura M. Ippolito. 1997, Verifying and Validating Software Requirements Specifications. In Software Requirements Engineering, 2d ed Richard H. Thayerand Merlin Dorfman, eds., 389-404. Los Alamitos, CA: IEEE Computer Society Press.
Wasserman. Anthony I. 1985. Extending State Transition Diagrams for the Specification of Human-Computer Interaction. IEEE Transactions on Software Engineering SE-11(8):699-713.
Weinberg, Gerald M. 1995. Just Say No! Improving the Requirements Process. American Programmer 8(10y.19-23.
Whitmire, Scott A. 1995. An Introduction to 3D Function Points. Software Development 3(4):43-53.
Те же авторы. 1997. Object-Oriented Design Measurement. New York: John Wiley &Sons.
Wiegers, Karl E. 1996a. Creating a Software Engineering Culture. New York: Dorset House Publishing.
Те же авторы, 1996b. Reducing Maintenance with Design Abstraction. Software Development 4(4):47-50.
Те же авторы, 1998a.The Seven Deadly Sins of Software Reviews. Software Development 6{3):44-47.
Те же авторы. 1998b. KnowYour Enemy: Software Risk Management. Software Development 6(10):38-42.
Те же авторы. 1998с. Improve Your Process With Online Good Practices. Software Development 6(12):45-50.
Те же авторы. 1999а. A Software Metrics Primer. Software Development 7(7):39-42.
Те же авторы. 1999b. Software Process Improvement inWeb Time. IEEE
Software 15(4):78-86.
Те же авторы. 2000. The Habits of Effective Analysts. Software Development 8(10):62-65.
Те же авторы. 2001. Requirements When the Field Isn't Green. STQE 3(3):30-37.
Те же авторы. 2002а. Peer Reviews in Software: A Practical Guide. Boston, MA: Addison-Wesley.
Те же авторы. 2002b. Promises, Promises. The Rational Edge 2(1) (https://www.therationaledge.com).
Те же авторы. 2002с. Success Criteria Breed Success. The Rational Edge 2(2) (https://www.therationaledge.com).
Те же авторы. 2002d. Saving for a Rainy Day. The Rational Edge 2(4) (https://www. thera tionaledge. com).
Те же авторы. 2003. See You In Court. Software Development 11(1):36-40,
Wiegers, Karl и Johanna Rothman. 2001. Looking Back, Looking Ahead, Software Development 9(2};65-69.
Wieringa, R. J. 1996. Requirements Engineering: Frameworks for Understanding. Chichester, England: John Wiley & Sons.
Wiley, Bill. 2000. Essential System Requirements: A Practical Guide to Event-Driven Methods. Reading, MA: Addison-Wesley.
Williams, Ray C, Julie A. Walker и AudreyJ. Dorofee. 1997. Putting Risk
Management into Practice. IEEE Software 14(3):75-82.
Wilson, Peter B. 1995, Testable Requirements—An Alternative Sizing Measure. The Journal of the Quality Assurance Institute 9(4):3- 11.
Wirfs-Brock, Rebecca. 1993. Designing Scenarios: Making the Case for ■a Use Case Framework. Smalltalk Report 3(3).
Wood, David P. и Куо С Kang. 1992. A Classification and Bibliography of Software Prototyping (CMU/SEI-92-TR-013). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University.
Wood, Jane и Denise Silver. 1995. Joint Application Development, 2d ed NewYork: John Wiley & Sons.
Young, Ralph R. 2001. Effective Requirements Practices. Boston, MA: Addison-Wesley.
Zultner, Richard E. 1993. TQM for Technical Teams. Communications of theACM36(10):79-91.
Об авторе
Карл И. Вигерс — главный специалист компании Process Impact (Портланд, Орегон), которая занимается консультированием и подготовкой специалистов в области разработки ПО. Сейчас он проводит обучающие семинары во многих компаниях, расположенных в различных странах мира. А ранее почти 18 лет Карл работал в Eastman Kodak Company, где занимался исследованием фотографического процесса разработкой и управлением ПО, а также руководил процессом улучшения качества продукта. Карл получил степень бакалавра химии в Boise State College, магистра и доктора органической химии в Университете Иллинойса. Он является членом IEEE, IEEE Computer Society и ACM.
Вигерс — автор книг «Peer Reviews in Software: A Practical Guide» (Addison-Wesley, 2002) и отмеченной наградой Software Development Productivity Award «Creating a Software Engineering Culture (Dorset House, 1996) Помимо этого он написал около 160 статей на различные темы: компьютеры, химия, военная история. Некоторое время Карл работал редактором-составителем журнала «Software Development» и трудился в редколлегии журнала «IEEE Software».
Когда Карл не перед компьютером или не в классе, он с удовольствием бренчит на гитарах — Gibson Les Paul, Fender Stratocaster и Guild D40, катается на мотоцикле Suzuki VX800, изучает военную историю, готовит и потягивает вино с женой Крис Замбито. Вы найдете Карла на https://www.processimpactjcom.
О книге и ее авторе
Когда мы начинали, способность вовремя выпускать качественные продукты имела решающее значение для нашего стратегического успеха. В этой книге кратко описана модель создания программного обеспечения в NuMega. Лежащие в ее основe принципы и методы — плод нелегкого опыта, но они обеспечили нам возможность выпуска замечательных программ вовремя и вопреки различным обстоятельствам.