Материал: Руководство по стилю программирования и конструированию по

ГЛАВА 35 Где искать дополнительную информацию
839
отнести путаный, сложный для восприятия стиль некоторых авторов. Хорошая проявляется в том, что он содержит наиболее передовую информацию, которая не попадет с годами в низкопробные издания.
Специализированные публикации
Часть периодики более глубоко рассматривает специальные темы.
Профессиональные издания
Компьютерная ассоциация IEEE выпускает специализирован- ные журналы по следующим вопросам: проектирование ПО,
безопасность и защита информации, компьютерная графи- ка и анимация, Интернет-технологии, мультимедиа, интеллектуальные системы,
история вычислительной техники и др. Подробнее см. по адресу
www.computer.org.
ACM также публикует специальные выпуски по таким раз- делам, как искусственный интеллект, взаимодействие чело- века и компьютера, базы данных, встроенные системы, гра- фика, языки программирования, ПО для математических задач, построение сетей,
проектирование ПО и др. Подробнее см. по адресу
www.acm.org.
Популярные коммерческие издания
Темы следующих журналов следуют из названий.
«The C/C++ Users Journal»,
www.cuj.com.
«Java Developer’s Journal»,
www.sys-con.com/java/.
«Embedded Systems Programming»,
www.embedded.com.
«Linux Journal»,
www.linuxjournal.com.
«Unix Review»,
www.unixreview.com.
«Windows Developer’s Network»,
www.wd-mag.com.
35.4. Список литературы для разработчика ПО
В этом разделе предлагается план чтения, позволяющий разработчику ПО стать полноценным специалистом в моей компании, Construx Software. Этот план является предмет- ным базовым курсом и рассчитан на тех, кто уже работает в области ПО и желает уделить особое внимание теме разработки. Наше методическое пособие дает воз- можность перестраивать базовую программу с учетом индивидуальных интере- сов. В рамках программы Construx предусматривается также повышение квали- фикации и обмен опытом работы по конкретным вопросам.
Вводный курс
Чтобы пройти «начальный» уровень по методике Construx, необходимо прочесть следующие книги.
Adams, James L.
Conceptual Blockbusting: A Guide to Better Ideas, 4th ed. Cambridge,
MA: Perseus Publishing, 2001.
http://cc2e.com/3551
http://cc2e.com/3558
http://cc2e.com/3565
http://cc2e.com/3507

840
ЧАСТЬ VII Мастерство программирования
Bentley, Jon.
Programming Pearls, 2d ed. Reading, MA: Addison-Wesley, 2000.
Glass, Robert L.
Facts and Fallacies of Software Engineering. Boston, MA: Addison-Wesley,
2003.
McConnell, Steve.
Software Project Survival Guide. Redmond, WA: Microsoft Press, 1998.
McConnell, Steve.
Code Complete, 2d ed. Redmond, WA: Microsoft Press, 2004.
Курс практической подготовки
Далее предлагаются дополнительные источники, которые должен освоить програм- мист, чтобы соответствовать «промежуточному» уровню в Construx.
Berczuk, Stephen P. and Brad Appleton.
Software Configuration Management Patterns:
Effective Teamwork, Practical Integration. Boston, MA: Addison-Wesley, 2003.
Fowler, Martin.
UML Distilled: A Brief Guide to the Standard Object Modeling Language,
3d ed. Boston, MA: Addison-Wesley, 2003.
Glass, Robert L.
Software Creativity. Reading, MA: Addison-Wesley, 1995.
Kaner, Cem, Jack Falk, Hung Q. Nguyen
Testing Computer Software, 2d ed. New York,
NY: John Wiley & Sons, 1999.
Larman, Craig.
Applying UML and Patterns: An Introduction to Object-Oriented Analysis
and Design and the Unified Process, 2d ed. Englewood Cliffs, NJ: Prentice Hall, 2001.
McConnell, Steve.
Rapid Development. Redmond, WA: Microsoft Press, 1996.
Wiegers, Karl.
Software Requirements, 2d ed. Redmond, WA: Microsoft Press, 2003.
Manager’s Handbook for Software Development, NASA Goddard
Space Flight Center. Получить информацию можно по адре- су
sel.gsfc.nasa.gov/website/documents/online-doc.htm.
Курс профессиональной подготовки
Изучив следующую литературу, разработчик ПО добьется полного профессиональ- ного соответствия в Construx («уровень лидера»). К каждому разработчику предъяв- ляются отдельные дополнительные требования, здесь перечислены лишь общие для всех требования.
Bass, Len, Paul Clements, and Rick Kazman.
Software Architecture in Practice, 2d ed. Boston,
MA: Addison-Wesley, 2003.
Fowler, Martin.
Refactoring: Improving the Design of Existing Code. Reading, MA: Add- ison-Wesley, 1999.
Gamma, Erich, et al.
Design Patterns. Reading, MA: Addison-Wesley, 1995.
Gilb, Tom.
Principles of Software Engineering Management. Wokingham, England: Add- ison-Wesley, 1988.
Maguire, Steve.
Writing Solid Code. Redmond, WA: Microsoft Press, 1993.
Meyer, Bertrand.
Object-Oriented Software Construction, 2d ed. New York, NY: Prentice
Hall PTR, 1997.
Software Measurement Guidebook, NASA Goddard Space Flight
Center. Информация доступна по адресу:
sel.gsfc.nasa.gov/
website/documents/online-doc.htm.
http://cc2e.com/3514
http://cc2e.com/3521

ГЛАВА 35 Где искать дополнительную информацию
841
Наш сайт
www.construx.com/professionaldev/ подробно зна- комит с программой повышения профессионального уровня и содержит обновленный список литературы.
35.5. Профессиональные ассоциации
Общение с другими программистами, работающими в той же области, что и вы, — один из лучших способов узнать о программировании больше. Региональные группы пользо- вателей конкретных аппаратных средств и языков программирования — один из видов сообществ. К другим относятся национальные и международные организа- ции. Компьютерная ассоциация IEEE — наиболее профессионально-ориентиро- ванная организация, выпускающая журналы «IEEE Computer» и «IEEE Software». Ин- формацию о членстве в IEEE смотрите на сайте
www.computer.org.
ACM была первой профессиональной организацией. Она издает журнал «Communications of the ACM», многие другие специализированные журналы и в сравнении с IEEE боль- ше внимания уделяет теории. Информацию о членстве в ACM см. на сайте
www.acm.org.
http://cc2e.com/3528
http://cc2e.com/3535
http://cc2e.com/3542

842
Библиография
Библиография
«A C Coding Standard.» 1991.
Unix Review 9, no. 9 (September): 42–43.
Abdel-Hamid, Tarek K. 1989. «The Dynamics of Software Project Staffing: A System Dynamics
Based Simulation Approach.»
IEEE Transactions on Software Engineering SE-15, no. 2 (February):
109–19.
Abran, Alain, et al. 2001. Swebok: Guide to the Software Engineering Body of Knowledge: Trial
Version 1.00-May 2001. Los Alamitos, CA: IEEE Computer Society Press.
Abrash, Michael. 1992. «Flooring It: The Optimization Challenge.»
PC Techniques 2, no. 6 (February/
March): 82–88.
Ackerman, A. Frank, Lynne S. Buchwald, and Frank H. Lewski. 1989. «Software Inspections: An
Effective Verification Process.»
IEEE Software, May/June 1989, 31–36.
Adams, James L. 2001.
Conceptual Blockbusting: A Guide to Better Ideas, 4th ed. Cambridge, MA:
Perseus Publishing.
Aho, Alfred V., Brian W. Kernighan, and Peter J. Weinberg. 1977.
The AWK Programming Language.
Reading, MA: Addison-Wesley.
Aho, Alfred V., John E. Hopcroft, and Jeffrey D. Ullman. 1983.
Data Structures and Algorithms.
Reading, MA: Addison-Wesley.
Albrecht, Allan J. 1979. «Measuring Application Development Productivity.» Proceedings of the
Joint SHARE/GUIDE/IBM Application Development Symposium, October 1979: 83–92.
Ambler, Scott. 2003.
Agile Database Techniques. New York, NY: John Wiley & Sons.
Anand, N. 1988. «Clarify Function!»
ACM Sigplan Notices 23, no. 6 (June): 69–79.
Aristotle.
The Ethics of Aristotle: The Nicomachean Ethics. Trans. by J.A.K. Thomson. Rev. by Hugh
Tredennick. Harmondsworth, Middlesex, England: Penguin, 1976.
Armenise, Pasquale. 1989. «A Structured Approach to Program Optimization.»
IEEE Transactions
on Software Engineering SE-15, no. 2 (February): 101–8.
Arnold, Ken, James Gosling, and David Holmes. 2000.
The Java Programming Language, 3d ed.
Boston, MA: Addison-Wesley.
Arthur, Lowell J. 1988.
Software Evolution: The Software Maintenance Challenge. New York, NY:
John Wiley & Sons.
Augustine, N. R. 1979. «Augustine’s Laws and Major System Development Programs.»
Defense Systems
Management Review: 50–76.
Babich, W. 1986.
Software Configuration Management. Reading, MA: Addison-Wesley.
Bachman, Charles W. 1973. «The Programmer as Navigator.» Turing Award Lecture.
Communications
of the ACM 16, no. 11 (November): 653.
Baecker, Ronald M., and Aaron Marcus. 1990.
Human Factors and Typography for More Readable
Programs. Reading, MA: Addison-Wesley.
Bairdain, E. F. 1964. «Research Studies of Programmers and Programming.» Unpublished studies reported in Boehm 1981.

Библиография
843
Baker, F. Terry, and Harlan D. Mills. 1973. «Chief Programmer Teams.»
Datamation 19, no. 12
(December): 58–61.
Barbour, Ian G. 1966.
Issues in Science and Religion. New York, NY: Harper & Row.
Barbour, Ian G. 1974. Myths, Models, and Paradigms: A Comparative Study in Science and Religion.
New York, NY: Harper & Row.
Barwell, Fred, et al. 2002.
Professional VB.NET, 2d ed. Birmingham, UK: Wrox.
Basili, V. R., and B. T. Perricone. 1984. «Software Errors and Complexity: An Empirical Investigation.»
Communications of the ACM 27, no. 1 (January): 42–52.
Basili, Victor R., and Albert J. Turner. 1975. «Iterative Enhancement: A Practical Technique for Software
Development.»
IEEE Transactions on Software Engineering SE-1, no. 4 (December): 390–96.
Basili, Victor R., and David M. Weiss. 1984. «A Methodology for Collecting Valid Software Engi- neering Data.»
IEEE Transactions on Software Engineering SE-10, no. 6 (November): 728–38.
Basili, Victor R., and Richard W. Selby. 1987. «Comparing the Effectiveness of Software Testing
Strategies.»
IEEE Transactions on Software Engineering SE-13, no. 12 (December): 1278–96.
Basili, Victor R., et al. 2002. «Lessons learned from 25 years of process improvement: The Rise and Fall of the NASA Software Engineering Laboratory,»
Proceedings of the 24th International
Conference on Software Engineering, Orlando, FL.
Basili, Victor R., Richard W. Selby, and David H. Hutchens. 1986. «Experimentation in Software
Engineering.»
IEEE Transactions on Software Engineering SE-12, no. 7 (July): 733–43.
Basili, Victor, L. Briand, and W.L. Melo. 1996. «A Validation of Object-Oriented Design Metrics as
Quality Indicators,»
IEEE Transactions on Software Engineering, October 1996, 751–761.
Bass, Len, Paul Clements, and Rick Kazman. 2003.
Software Architecture in Practice, 2d ed. Boston,
MA: Addison-Wesley.
Bastani, Farokh, and Sitharama Iyengar. 1987. «The Effect of Data Structures on the Logical
Complexity of Programs.»
Communications of the ACM 30, no. 3 (March): 250–59.
Bays, Michael. 1999.
Software Release Methodology. Englewood Cliffs, NJ: Prentice Hall.
Beck, Kent. 2000.
Extreme Programming Explained: Embrace Change. Reading, MA: Addison-Wesley.
Beck, Kent. 2003.
Test-Driven Development: By Example. Boston, MA: Addison-Wesley.
Beck, Kent. 1991. «Think Like An Object.»
Unix Review 9, no. 10 (October): 39–43.
Beck, Leland L., and Thomas E. Perkins. 1983. «A Survey of Software Engineering Practice: Tools, Methods,
and Results.»
IEEE Transactions on Software Engineering SE-9, no. 5 (September): 541–61.
Beizer, Boris. 1990.
Software Testing Techniques, 2d ed. New York, NY: Van Nostrand Reinhold.
Bentley, Jon, and Donald Knuth. 1986. «Literate Programming.»
Communications of the ACM 29,
no. 5 (May): 364–69.
Bentley, Jon, Donald Knuth, and Doug McIlroy. 1986. «A Literate Program.»
Communications of
the ACM 29, no. 5 (May): 471–83.
Bentley, Jon. 1982.
Writing Efficient Programs. Englewood Cliffs, NJ: Prentice Hall.
Bentley, Jon. 1988.
More Programming Pearls: Confessions of a Coder. Reading, MA: Addison-Wesley.
Bentley, Jon. 1991. «Software Exploratorium: Writing Efficient C Programs.»
Unix Review 9, no. 8
(August): 62–73.
Bentley, Jon. 2000.
Programming Pearls, 2d ed. Reading, MA: Addison-Wesley.
Berczuk, Stephen P. and Brad Appleton. 2003. Software Configuration Management Patterns:
Effective Teamwork, Practical Integration. Boston, MA: Addison-Wesley.
Berry, R. E., and B. A. E. Meekings. 1985. «A Style Analysis of C Programs.»
Communications of the
ACM 28, no. 1 (January): 80–88.

844

Библиография
845
Booth, Rick. 1997. Inner Loops : A Sourcebook for Fast 32-bit Software Development. Boston,
MA: Addison-Wesley.
Boundy, David. 1991. «A Taxonomy of Programmers.»
ACM SIGSOFT Software Engineering Notes
16, no. 4 (October): 23–30.
Brand, Stewart. 1995. How Buildings Learn: What Happens After They’re Built. Penguin USA.
Branstad, Martha A., John C. Cherniavsky, and W. Richards Adrion. 1980. «Validation, Verification,
and Testing for the Individual Programmer.»
Computer, December, 24–30.
Brockmann, R. John. 1990. Writing Better Computer User Documentation: From Paper to Hyper- text: Version 2.0. New York, NY: John Wiley & Sons.
Brooks, Frederick P., Jr. 1987. «No Silver Bullets—Essence and Accidents of Software Engineering.»
Computer, April, 10–19.
Brooks, Frederick P., Jr. 1995. The Mythical Man-Month: Essays on Software Engineering, Anniversary
Edition (2d ed.). Reading, MA: Addison-Wesley.
Brooks, Ruven. 1977. «Towards a Theory of the Cognitive Processes in Computer Programming.»
International Journal of Man-Machine Studies 9: 737–51.
Brooks, W. Douglas. 1981. «Software Technology Payoff—Some Statistical Evidence.»
The Journal
of Systems and Software 2: 3–9.
Brown, A. R., and W. A. Sampson. 1973.
Program Debugging. New York, NY: American Elsevier.
Buschman, Frank, et al. 1996. Pattern-Oriented Software Architecture, Volume 1: A System of
Patterns. New York, NY: John Wiley & Sons.
Bush, Marilyn, and John Kelly. 1989. «The Jet Propulsion Laboratory’s Experience with Formal
Inspections.»
Proceedings of the Fourteenth Annual Software Engineering Workshop, November 29,
1989. Greenbelt, MD: Goddard Space Flight Center. Document SEL-89-007.
Caine, S. H., and E. K. Gordon. 1975. «PDL—A Tool for Software Design.»
AFIPS Proceedings of the
1975 National Computer Conference 44. Montvale, NJ: AFIPS Press, 271–76.
Card, David N. 1987. «A Software Technology Evaluation Program.»
Information and Software
Technology 29, no. 6 (July/August): 291–300.
Card, David N., Frank E. McGarry, and Gerald T. Page. 1987. «Evaluating Software Engineering
Technologies.»
IEEE Transactions on Software Engineering SE-13, no. 7 (July): 845–51.
Card, David N., Victor E. Church, and William W. Agresti. 1986. «An Empirical Study of Software
Design Practices.»
IEEE Transactions on Software Engineering SE-12, no. 2 (February): 264–71.
Card, David N., with Robert L. Glass. 1990.
Measuring Software Design Quality. Englewood Cliffs,
NJ: Prentice Hall.
Card, David, Gerald Page, and Frank McGarry. 1985. «Criteria for Software Modularization.»
Proceedings of the 8th International Conference on Software Engineering. Washington, DC: IEEE
Computer Society Press, 372–77.
Carnegie, Dale. 1981.
How to Win Friends and Influence People, Revised Edition. New York, NY:
Pocket Books.
Chase, William G., and Herbert A. Simon. 1973. «Perception in Chess.»
Cognitive Psychology 4: 55–81.
Clark, R. Lawrence. 1973. «A Linguistic Contribution of GOTO-less Programming,»
Datamation,
December 1973.
Clements, Paul, ed. 2003.
Documenting Software Architectures: Views and Beyond. Boston, MA:
Addison-Wesley.
Clements, Paul, Rick Kazman, and Mark Klein. 2002.
Evaluating Software Architectures: Methods
and Case Studies. Boston, MA: Addison-Wesley.
Coad, Peter, and Edward Yourdon. 1991.
Object-Oriented Design. Englewood Cliffs, NJ: Yourdon Press.

846
Библиография
Cobb, Richard H., and Harlan D. Mills. 1990. «Engineering Software Under Statistical Quality
Control.»
IEEE Software 7, no. 6 (November): 45–54.
Cockburn, Alistair. 2000.
Writing Effective Use Cases. Boston, MA: Addison-Wesley.
Cockburn, Alistair. 2002.
Agile Software Development. Boston, MA: Addison-Wesley.
Collofello, Jim, and Scott Woodfield. 1989. «Evaluating the Effectiveness of Reliability Assurance
Techniques.»
Journal of Systems and Software 9, no. 3 (March).
Comer, Douglas. 1981. «Principles of Program Design Induced from Experience with Small Public
Programs.»
IEEE Transactions on Software Engineering SE-7, no. 2 (March): 169–74.
Constantine, Larry L. 1990a. «Comments on ‘On Criteria for Module Interfaces.’»
IEEE Transactions
on Software Engineering SE-16, no. 12 (December): 1440.
Constantine, Larry L. 1990b. «Objects, Functions, and Program Extensibility.»
Computer Language,
January, 34–56.
Conte, S. D., H. E. Dunsmore, and V. Y. Shen. 1986.
Software Engineering Metrics and Models. Menlo
Park, CA: Benjamin/ Cummings.
Cooper, Doug, and Michael Clancy. 1982.
Oh! Pascal! 2d ed. New York, NY: Norton.
Cooper, Kenneth G. and Thomas W. Mullen. 1993. «Swords and Plowshares: The Rework Cycles of Defense and Commercial Software Development Projects,»
American Programmer, May 1993,
41–51.
Corbatу, Fernando J. 1991. «On Building Systems That Will Fail.» 1991 Turing Award Lecture.
Communications of the ACM 34, no. 9 (September): 72–81.
Cornell, Gary and Jonathan Morrison. 2002.
Programming VB .NET: A Guide for Experienced
Programmers, Berkeley, CA: Apress.
Corwin, Al. 1991. Private communication.
CSTB 1990. «Scaling Up: A Research Agenda for Software Engineering.» Excerpts from a report by the Computer Science and Technology Board.
Communications of the ACM 33, no. 3 (March):
281–93.
Curtis, Bill, ed. 1985.
Tutorial: Human Factors in Software Development. Los Angeles, CA: IEEE
Computer Society Press.
Curtis, Bill, et al. 1986. «Software Psychology: The Need for an Interdisciplinary Program.»
Proceedings of the IEEE 74, no. 8: 1092–1106.
Curtis, Bill, et al. 1989. «Experimentation of Software Documentation Formats.»
Journal of Systems
and Software 9, no. 2 (February): 167–207.
Curtis, Bill, H. Krasner, and N. Iscoe. 1988. «A Field Study of the Software Design Process for Large
Systems.»
Communications of the ACM 31, no. 11 (November): 1268–87.
Curtis, Bill. 1981. «Substantiating Programmer Variability.»
Proceedings of the IEEE 69, no. 7: 846.
Cusumano, Michael and Richard W. Selby. 1995.
Microsoft Secrets. New York, NY: The Free Press.
Cusumano, Michael, et al. 2003. «Software Development Worldwide: The State of the Practice,»
IEEE Software, November/December 2003, 28–34.
Dahl, O. J., E. W. Dijkstra, and C. A. R. Hoare. 1972.
Structured Programming. New York, NY: Academic
Press.
Date, Chris. 1977.
An Introduction to Database Systems. Reading, MA: Addison-Wesley.
Davidson, Jack W., and Anne M. Holler. 1992. «Subprogram Inlining: A Study of Its Effects on
Program Execution Time.»
IEEE Transactions on Software Engineering SE-18, no. 2 (February):
89–102.
Davis, P. J. 1972. «Fidelity in Mathematical Discourse: Is One and One Really Two?»
American
Mathematical Monthly, March, 252–63.

Библиография
847
DeGrace, Peter, and Leslie Stahl. 1990. Wicked Problems, Righteous Solutions: A Catalogue of
Modern Software Engineering Paradigms. Englewood Cliffs, NJ: Yourdon Press.
DeMarco, Tom and Timothy Lister. 1999.
Peopleware: Productive Projects and Teams, 2d ed. New
York, NY: Dorset House.
DeMarco, Tom, and Timothy Lister. 1985. «Programmer Performance and the Effects of the
Workplace.»
Proceedings of the 8th International Conference on Software Engineering. Washington,
DC: IEEE Computer Society Press, 268–72.
DeMarco, Tom. 1979. Structured Analysis and Systems Specification: Tools and Techniques.
Englewood Cliffs, NJ: Prentice Hall.
DeMarco, Tom. 1982.
Controlling Software Projects. New York, NY: Yourdon Press.
DeMillo, Richard A., Richard J. Lipton, and Alan J. Perlis. 1979. «Social Processes and Proofs of
Theorems and Programs.»
Communications of the ACM 22, no. 5 (May): 271–80.
Dijkstra, Edsger. 1965. «Programming Considered as a Human Activity.»
Proceedings of the 1965
IFIP Congress. Amsterdam: North-Holland, 213–17. Reprinted in Yourdon 1982.
Dijkstra, Edsger. 1968. «Go To Statement Considered Harmful.»
Communications of the ACM 11,
no. 3 (March): 147–48.
Dijkstra, Edsger. 1969. «Structured Programming.» Reprinted in Yourdon 1979.
Dijkstra, Edsger. 1972. «The Humble Programmer.»
Communications of the ACM 15, no. 10 (October):
859–66.
Dijkstra, Edsger. 1985. «Fruits of Misunderstanding.»
Datamation, February 15, 86– 87.
Dijkstra, Edsger. 1989. «On the Cruelty of Really Teaching Computer Science.»
Communications
of the ACM 32, no. 12 (December): 1397–1414.
Dunn, Robert H. 1984.
Software Defect Removal. New York, NY: McGraw-Hill.
Ellis, Margaret A., and Bjarne Stroustrup. 1990.
The Annotated C++ Reference Manual. Boston, MA:
Addison-Wesley.
Elmasri, Ramez, and Shamkant B. Navathe. 1989.
Fundamentals of Database Systems. Redwood
City, CA: Benjamin/Cummings.
Elshoff, James L. 1976. «An Analysis of Some Commercial PL/I Programs.»
IEEE Transactions on
Software Engineering SE-2, no. 2 (June): 113–20.
Elshoff, James L. 1977. «The Influence of Structured Programming on PL/I Program Profiles.»
IEEE
Transactions on Software Engineering SE-3, no. 5 (September): 364–68.
Elshoff, James L., and Michael Marcotty. 1982. «Improving Computer Program Readability to Aid
Modification.»
Communications of the ACM 25, no. 8 (August): 512–21.
Endres, Albert. 1975. «An Analysis of Errors and Their Causes in System Programs.»
IEEE Transactions
on Software Engineering SE-1, no. 2 (June): 140–49.
Evangelist, Michael. 1984. «Program Complexity and Programming Style.»
Proceedings of the First
International Conference on Data Engineering. New York, NY: IEEE Computer Society Press, 534–41.
Fagan, Michael E. 1976. «Design and Code Inspections to Reduce Errors in Program Development.»
IBM Systems Journal 15, no. 3: 182–211.
Fagan, Michael E. 1986. «Advances in Software Inspections.»
IEEE Transactions on Software
Engineering SE-12, no. 7 (July): 744–51.
Federal Software Management Support Center. 1986.
Programmers Work-bench Handbook. Falls
Church, VA: Office of Software Development and Information Technology.
Feiman, J., and M. Driver. 2002. «Leading Programming Languages for IT Portfolio Planning,»
Gartner Research report SPA-17-6636, September 27, 2002.