Вигерс Карл. Разработка требований к программному обеспечению

Подождите немного. Документ загружается.

Keith, Norman

2001. Project Retrospectives: A Handbook for Team

Reviews. New York: Dorset House Publishing.

Kosman, Robert J. 1997. A Two-Step Methodology to Reduce Require-

ment Defects.

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

Kulak,

Daryl

и Eamonn Guiney. 2000. Use Cases: Requirements in Con-

text. New York: ACM Press.

Larman, Craig. 1998. The Use Case Model: What Are the Processes? Ja-

va 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

Coui

theyn. 2001. A Formal Process for Evaluating COTS Software

Product:;;.

IEEE 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.

997.

Calculating the Return on Investment from More

Effective Requirements Management. American Programmer 10(4}:13-16.

Leffingwell, Dean и Don Widrig. 2000. Managing Software Require-

ments: A Unified Approach. Reading, MA: Addison-Wesley.

Leishman,

Theron

R. и David A. Cook. 2002. Requirements Risks Can

Drown Software Projects.

CrossTalk

5(4):4-8.

Leveson, Nancy.

1995.

Safeware: System Safety and Computers.

Read-

ing, MA: Addison-Wesley.

Lilly,

Susan. 2000. How to Avoid Use-Case Pitfalls. Software Develop-

ment

8(1

):40-44.

Martin, James. 1991. Rapid Application Development. New York: Mac-

millan Publishing.

Martin, Johnny и W. T. Tsai. 1990.

N-fold

Inspection: A Requirements

Analysis Technique. Communications of the ACM 33{2):225-232.

Библиографический список 547

McCabe, Thomas J.

1982.

Structured Testing: A Software Testing Meth-

odology Using the

Cyclomatic

Complexity Metric. National Bureau of Stan-

dards Special

Publication

500-599.

McConnell, Steve. 1993. Code Complete: A Practical Handbook of Soft-

ware Construction. Redmond, WA: Microsoft Press.

Те же авторы. 1996. Rapid Development: Taming Wild Software Sched-

ules.

Redmond,

WA: Microsoft Press.

Те

же авторы. 1998. Software Project Survival Guide. Redmond, WA: Mi-

crosoft Press.

McGraw, Karen L. и Karan Harbison. 1997. User-Centered Require-

ments: 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

High-Tech Products to Mainstream Customers.

New

York: HarperBusiness.

Morgan, Tony, 2002. Business Rules and Information Systems: Aligning

IT 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 Reli-

ability: Measurement, Prediction, Application.

New

York: 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.

IEEE

Software 19(6):34-42.

Nelsen, E. Dale. 1990. System Engineering and Requirement Allocation.

In System and Software Requirements Engineering, Richard H.

Thayer

and

Merlin

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.

New

York: Dorset House Publishing,

Paulk,

Mark, et

al.

1995. The Capability Maturity Model: Guidelines for

Improving the Software Process. Reading, MA: Addison-Wesley.

548 Библиографический список

Pfleeger,

Shart

Lawrence.

2001.

Software Engineering: Theory and Prac-

tice,

2d ed.

Englewood

Cliffs, NJ: Prentice Hall.

Porter,

Adam

A.,

Lawrence G.

Votta,

Jr. и Victor R. Basili. 1995. Compar-

ing Detection Methods for Software Requirements Inspections: A Replicat-

ed Experiment.

IEEE

Transactions on Software Engineering

21(6):563-57S.

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 Test-

ing. 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

Managi3-

ment

Institute.

Putnam, Lawrence H. и Ware Myers. 1997. Industrial Strength Software:

Effective Management Using Measurement. Los Alamitos, CA: IEEE Com-

puter 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 Require-

ments. 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 Pro-

grammer

10(8):27-32.

Robertson, Suzanne и James Robertson. 1999. Mastering the Require-

ments Process. Harlow, England: Addison-Westey.

Библиографический список 549

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

Newsletter

3(1).

Rubin, Howard. 1999. The 1999 Worldwide Benchmark Report: Software

Engineering and IT Findings for

998

and

999,

Part

IT Metrics Strategies

Schneider, G. Michael, Johnny Martin

nW.

TTsai.

1992. An Experimental

Study of Fault Detection in User Requirements Documents. ACM Transac-

tions on Software Engineering and Methodology

1(2):

188-204.

Schneider,

Gerin

Jason 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: Specify-

ing, 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,

18-125.

LosAlamitos,

CA: IEEE Com-

puter 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.

Pro-

ceedings of the Third International Conference on Requirements Engineer-

ing,

41-50.

LosAlamitos,

CA: IEEE Computer Society Press.

550 Библиографический список

Sorensen, Reed. 1999.

CCB—An

Acronym for

'Chocolate

Chip Brown-

ies'? 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

Soft-

ware 19(3):88-89.

Stevens, Richard, Peter Brook, Ken Jackson и Stuart Arnold. 1998. Sys-

tems 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 Evolv-

ing Enterprises. Software Development 3(2):34-44.

Voas, Jeffrey.

1999.

Protecting Against What? The Achilles Heel of

Infor-

mation Assurance. IEEE Software

16{

1 ):28-29.

von Halle, Barbara. 2002. Business Rules Applied: Building Better Sys-

tems Using the Business Rules Approach.

New

York: John Wiley & Sons.

Votta, Lawrence G., Jr. 1993. Does Every Inspection Need a Meeting?

Proceedings of the First ACM SIGSOFT Symposium on Software Develop-

ment Engineering,

107-114.

New

York: ACM Press.

Wallace, Dolores R. и Laura M. Ippolito. 1997, Verifying and Validating

Software Requirements Specifications. In Software Requirements Engi-

neering, 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

Requiremenls

Process. American

Programmer8(10}: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.

Библиографический список

55Л

Те

же авторы, 1996b. Reducing Maintenance with Design Abstraction.

Software Development 4(4):47-50.

Те же авторы,

1998a.

The Seven

Deadly

Sins of Software Reviews. Soft-

ware Development 6{3):44-47.

Те же авторы. 1998b. Know

Your

Enemy: Software Risk Management.

Software

Development

6(10):38-42.

Те же авторы. 1998с. Improve Your Process With Online

'Good

Practic-

es'.

Software

Development

6(12):45-50,

Те

же авторы. 1999а. A Software Metrics Primer. Software

Development

7(7)i39-42.

Те

же авторы. 1999b. Software Process Improvement

Web Time. IEEE

Software 15(4}:78-86.

Те же авторы. 2000. The Habits of Effective Analysts. Software

Develop-

ment8(10):62-65.

Те же авторы.

2001.

Requirements When the Field Isn't Green. STQE

3(3):30-37.

Те же авторы. 2002а. Peer Reviews in Software: A Practical Guide. Bos-

ton, MA: Addison-Wesley.

Те же авторы. 2002b. Promises, Promises. The Rational Edge 2{

(http://www.therationaledge.com).

Те же авторы. 2002с. Success Criteria Breed Success. The Rational

Edge 2(2)

(http://www.therationaledge.com).

Те же авторы. 2002d. Saving for a Rainy Day. The Rational Edge 2(4)

(http://www.

therationaledge.

com).

Те же авторы. 2003. See You In Court. Software Development

):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

Under--

standing. 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 и

Audrey

J. 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.

552 Библиографический список

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

Software Prototyping

(CMU/SEI-92-TR-013).

Pittsburgh,

PA: Software En-

gineering Institute, Carnegie Mellon University.

Wood, Jane и Denise Silver.

1995.

Joint Application Development, 2d ed

New

York: 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.

Библиографический список

553

Об авторе

Карл И. Вигерс -- главный специалист компании Process Impact

(Портланд, Орегон), которая занимается консультированием и

подго-

товкой специалистов в области разработки ПО. Сейчас он проводит

обучающие семинары во многих компаниях, расположенных в

различ-

ных странах мира. А ранее почти

лет Карл работал в Eastman Kodak

Company, где занимался исследованием фотографического

процесса

разработкой и управлением ПО, а также руководил процессом улучше-

ния качества продукта. Карл получил степень бакалавра химии в Boise

State College, магистра и доктора органической химии в Университете

Иллинойса. Он является членом IEEE, IEEE Computer Society и ACM.

Вигерс — автор книг «Peer Reviews in Software: A Practical Guide» (Ad-

dison-Wesley,

2002) и отмеченной наградой Software Development Pro-

ductivity Award «Creating a Software Engineering Culture

(Dorset House,

1996).

Помимо этого он написал около 160 статей на различные темы:

компьютеры, химия, военная история. Некоторое время Карл работал

редакторе

м-составителем

журнала «Software

Development»

и трудился

в редколлегии журнала «IEEE Software».

Когда Карл не перед компьютером или не в классе, он с удовольст-

вием бренчит на гитарах — Gibson Les Paul, Fender Stratocaster и Guild

D40, катается на мотоцикле Suzuki

VX800,

изучает военную историю,

готовит и потягивает вино с женой Крис Замбито. Вы найдете Карла на

ttp://www.processimpact.

com.

554

Вигерс Карл

Разработка требований к программному обеспечению

Практические приемы сбора требований

и управления ими при разработке

программного продукта

Перевод с английского под общей редакцией Ю.

П.Леоновой

Переводчики Е. А, Широчкова, Е. В.

Брезгин

Технический редактор

Н.Г.Тимченко

Компьютерная верстка Е. Е. Сярая

Дизайнер обложки Е. В. Козлова

TypeMarketFoHfLibrary

Главный редактор А. И. Козлов

Подготовлено к печати издательством

«Русская

Редакция*

123317,

Москва, ул. Антонова-Овсеенко, д.

тел.:

(095)

256-5120,тел./факс:

(095) 256-4541

e-mail:

info@rusedit.ru,

http://www.rusedit.ru

В1.РШШ

РЕШШ

Подписано в печать

03.12.03

г. Тираж 2500

экз.

Формат60x90/16.

Фиэ.п.

л.

Отпечатано в ОАО

"Типография

"Новости"»

105005, Москва,

-ул.

Фр. Энгельса, 46

ад,

Прани.чыю

rio,..Tpt.x:Hi

ад

ГГ-иггфрастригпра

комл-гмин

lajioryciieaiHoro

itoHuypcwTHsjcn

ильного

биаж-са

еягадоге

преуктамлеш

детальная

-,ш-

формлцш

тхж'.'ншх

новинках

мир!.-

программного

(Ххчгпечения,

приведены

(>ii:«)p

чие

ci-атьи.

примеры

успе11шоп)п!1едреиия

рамкюбрлзные-пшовые^кгения.

Эта

инфорча»

иия

поможет

нам

сделать

[грапилшыГ;

выбор.

Йыбйриге

кагаясс,

««гарый

язм

куж^н,

рисшищге

время

выпускается

несколько

nepo-fi

1.-.1ТЯЛ01-ОВ

SoftfJne*-(Urei4

pii,-j

ITJCHH

тычков

(Micrfjsott,

Linux,

Novell.

Appk-j.

Оп-говмой

каталог

Soft!

inc-'-dir^c?

прсдстаа'К'»

к 5

рсхакцимх:

pjBijjihHoft

Mi"i'«(j-'KH-int

лицензирования

ПО

ортшгааций

fcistenubs;

biiji/n

•

кат^юг'лтдаыхреикчшй

Среди

них,

часпюс"П1:

мсч\>

1еиия

cejx:»oil

ппфрасфукчуры.

бсзопаакчть,

рсжршии;

ьчтир^тание,

у.'и

ила,гешУНЛ1

йлк-а'!|]длц!1яссрш|Х111

1р--гс.усф.^шя.

бесирлк

да!ы<;

лги,

мобильнмс

nMi»iOHJT(^;n

др.

Ka'cuor

дргдидзыачеи

дли

рукг

>водо)Т(:лей

Г'илне-сл.

р>-коцод|

•

лей

ГГ-

подразделений

кимпаинй

чиодом

компькпхров

бшсс

50.