Ларри Константин - Человеческий фактор в программировании

«ОК! — отвечаете вы. — Партнеры®!»

И так далее. Кто-то где-то подает сейчас заявку на регистрацию вашей любимой фразы, вашего любимого цвета или, быть может, даже вашего имени. Можете на это рассчитывать.

Гарантировано. Точка®.

Библиография

[1] Ancona, D. G. andD. F. Caldwell. 1992. «Bridging the Boundary: External Activity and Performance in Organizational Teams», Administrative Science Quarterly 37(4): 634-65.

[2] Anderson, L. E. and W. K. Balzer. 1991. «Effects of Timing of Leaders' Opinions on Problem-Solving Groups», Group amp; Organizational Studies 16(1): 86-101.

[3] Belbin, R. M. 1981. Management Teams: Why They Succeed or Fail. London: Heinemann.

[4] Beyer, H., and K. Holtzblatt. 1997. Contextual Design: Defining Customer-Centered Systems. NY: Morgan Kaufman.

[5] Bollinger, Т. B. and C. McGowan. 1991. «А Critical Look at Software Capability Evaluations», IEE Software 8(4): 25–41.

[6] Case, J. 1990. The Open-Book Managers», Inc. 12(9): 104-13.

[7] Chidamber, S., and C. Kemerer. 1994. «А Metrics Suite for Object-Ori-ented Design», IEEE Trans. Software Eng. 20 (6): 476–493.

[8] Cobb, R. H. and H. D. Mills. 1990. «Engineering Software Under Statistical Quality Control», IEEE Software 7(6): 44–54.

[9] Collins, D. 1995. Designing Object-Oriented User Interfaces. Redwood City, CA: Benjamin/Cummings.

[10] Constantine, L. L. 1986. Family Paradigms. New York: Guilford Press.

[11] Constantine, L. L. 1989. «Teamwork Paradigms and the Structured Open Team», Proceedings: Embedded Systems Conference. San Francisco: Miller Freeman.

[12] Constantine, L. L. 1990. «Organization Paradigms and the Management of Change», Proceedings: Software Development 90. San Francisco: Miller Freeman.

[13] Constantine, L. L. 1991a. «Building Structured Open Teams to Work», Software Development 91 Proceedings. San Francisco: Miller Freeman.

[14] Constantine, L. L. 1991b. «Toward Usable Interfaces: Bringing Users and User Perspectives into Design», American Programmer 4(2): 6-14.

[15] Constantine, L. L. 1991c. «Fitting Intervention to Organization Paradigm», Organization Development Journal 9(2): 41–50.

[16] Constantine, L. L. 1992a. «Managing for Quality User Interfaces», Software Management 1992 Proceedings. San Francisco: Miller Freeman.

[17] Constantine, L. L. 1992b. «Getting the User Interface Right: Basic Principles», Software Development 1992 Proceedings. San Francisco: Miller Freeman.

[18] Constantine, L. L. 1992c. «Quality by Increments: Small Steps with Big Payoffs», American Programmer 5 (2).

[19] Constantine, L. L. 1993a. «Objects in Your Face», Object Magazine, July.

[20] Constantine, L. L. 1993b. «User Interface Design for Embedded Systems», Embedded Systems Programming, August.

[21] Constantine, L. L. 1993c. «Work Organization Paradigms for Project Management and Organizations», Communications of the ACM 36(10). October.

[22] Constantine, L. L. 1994a. «More than Just a Pretty Face: Designing for Usability», Software Development 1994 Proceedings. San Francisco: Miller Freeman.

[23] Constantine, L. L. 1994b. «Collaborative Usability Inspections for Embedded Systems», Embedded Systems Conference Proceedings. San Francisco: Miller Freeman.

[24] onstantine, L. L. 1994c. «Interfaces for Intermediates», IEEE Software 11(4): 96–99.

[25] Constantine, L. L. 1994d. «Graphical Navigation», Windows Tech Journal, August.

[26] Constantine, L. L. 1995. Constantine on Peopleware. Englewood Cliffs, NJ: Prentice Hall.

[27] Constantine, L. L. 1996. «Usage-Centered Software Engineering: New Models, Methods, and Metrics», In Purvis, M. (ed.) Software Engineering: Education amp; Practice. Los Alamitos, CA: IEEE Computer Society Press.

[28] Constantine, L. L. 1997. «Visual Coherence and Usability: A Cohesion Metric for Assessing the Quality of Dialogue and Screen Designs». OzCHI'96 Proceedings. Los Alamitos, CA: IEEE Computer Society Press.

[29] Constantine, L. L. 1998. «Rapid Abstract Prototyping», Software Development, 6 (11), November.

[30] Constantine, L. L., and Lockwood, L. A. D. 1999. Software for Use: A Practical Guide to the Models and Methods of Usage-Centered Design. Reading, MA: Addison-Wesley.

[31] Cooper, A. 1995. About Face: The Essentials of User Interface Design. Foster City, CA: IDG Books.

[32] DeMarco, T. 1982. Controlling Software Projects. New York: Yourdon Press.

[33] DeMarco, T. and T. Lister. 1987. Peopleware: Productive Projects and Teams. New York: Dorset House.1

[34] Dijkstra, E. W. 1968. «Go To Statement Considered Harmful», Communications of the ACM, Vol. 11, No. 3, March, pp. 147–148.

[35] Doyle, M. and M. Strauss. 1982. How to Make Meetings Work. New York: Jove.

[36] Finegan, J. 1990. «The Education of Harry Featherstone,»Inc. 12 (7): 57–66.

[37] Fisher, R. and W. Ury. 1981. Getting to Yes. New York: Houghton Mifflin.

[38] Fisher, R. and Brown. 1988. Getting Together: Building Relationships As We Negotiate. New York: Penguin.

[39] Henderson-Sellers, В., L. L. Constantine, and I. M. Graham 1996. «Coupling and Cohesion: Toward a Valid Metrics Suite for Object-Oriented Analysis and Design», To appear in Object-Oriented Systems.

[40] Holtzblatt, K. and H. Beyer. 1993. «Making Customer-Centered Design Work for Teams», Communications of the ACM 36(10), October.

[41] Humphrey, W. S., T. S. Snyder, and R. R. Willis. 1991. «Software Process Improvement at Hughes Aircraft», IEEE Software 8(4): 11–23.

[42] Hyman, R. B. 1993. «Creative Chaos in High-Performance Teams: An Experience Report», Communications of the ACM 36(1). October.

[43] Jacobson, I., G. Booch, and J. Rumbaugh 2000. The Unified Software Development Process. Reading, MA: Addison-Wesley.

[44] Jacobson, I., M. Christerson, P. Jonsson, and G. Overgaard. Object-Oriented Software Engineering: A Use Case Driven Approach. Reading, Mass.: Addison-Wesley.

[45] Kantor, D. K. and W. Lehr. 1975. Inside the Family: Toward a Theory of Family Process. San Francisco: Jossey-Bass.

[46] Kruchten, P. 2000. The Rational Unified Process. Reading, MA: Addison-Wesley.

[47] Larson, С. E. and F. M. J. LaFasto. 1989. TeamWork. Beverly Hills: Sage.

[48] Lickert, R. 1989. New Patterns in Management. New York: McGraw-Hill.

[49] Lockwood, L. A. D., and L. L. Constantine 1993. «From Events to Objects: The Heresy of Event-Orientation in a World of Objects», OOPSLA 92: Addendum to the Proceedings. New York, ACM Press.

[50] Mackenzie, D. D. 1966. «The Philosophy of Conventions», in Concepts in Program Design, L. L. Constantine, ed. Cambridge, Mass.: Information amp; Systems Press.

[51] Newmann, P. G. 1976. «Peopleware in Systems», in Peopleware in Systems 15–18. Cleveland, Ohio: Association for Systems Management.

[52] Nielsen, J. 1993. Usability Engineering. Boston: Academic Press.

[53] Norman, D. O. 1988. The Psychology of Everyday Things. New York: Basic Books.

[54] Page-Jones, M. 1980. Practical Guide to Structured Systems Design. New York: Yourdon Press.

[55] Page-Jones, M. 1995. What Every Programmer Should Know About Object-Oriented Design. New York: Dorset House.

[56] Page-Jones, M. 2000. Fundamentals of Object-Oriented Design in UML. Reading, MA: Addison-Wesley.

[57] Page-Jones, M., L. L. Constantine, and S. J. Weiss. 1990. «Modeling Object-Oriented Systems: A Uniform Object Notation», Computer Language 7(1), October.

[58] Plauger, P. J. 1993. Programming on Purpose II: Essays on Software People. Englewood Cliffs, N. J.: Prentice Hall.

[59] Priem, R. L. and К. H. Price. 1991. «Process and Outcome Expectations for Dialectical Inquiry, Devil's Advocacy, and Consensus Techniques of Strategic Decision Making», Group amp; Organizational Studies 16(2): 206-25.

[60] Rettig, M. 1990. «The Practical Programmer: Software Teams». Communications of the ACM 33(10), October.

[61] Sutherland, I.E. 1968. «SketchPad: A Man-Machine Graphical Communication System», in Proceedings, AFIPS Spring Joint Computer Conference. 1963. 23. pp. 329–346.

[62] Thomsett, R. 1990. «Effective Project Teams: A Dilemma, A Model, A Solution», American Programmer 3(7/8): 25–35.

[63] van Harmelan, M. (ed.) 2001. Object Modeling and User Interface Design. Harlow, England: Addison-Wesley.

[64] Ward, P. 1992. «The Evolution of Structured Analysis. Part II: Maturity and Its Problems», American Programmer 5(4): 18–29.

[65] Watzlawick, P., J. H. Beavin, and D. D. Jackson. 1967. Pragmatics of Human Communication. New York: Norton.

[66] Weinberg, G. M. and E. L. Schulman. 1974. «Goals and Performance in Computer Programming», Human Factors 16(1): 70–77.

[67] Whitchurch, G. G. and L. L. Constantine. 1992. «Systems Theory», in Sourcebook of Family Theories and Methods: A Contextual Approach, P. B. Boss et al., eds. New York: Plenum.

[68] Wirfs-Brock, R., B. Wilkerson, and L. Weiner. 1990. Designing Object-Oriented Software. Englewood Cliffs, N.J.: Prentice Hall.

[69] Wood, J. and D. Silver. 1989. Joint Application Design. New York: John Wiley amp; Sons.

[70] Yourdon, E., and L. L. Constantine 1974. Structured Design, first printing. New York: Yourdon, Inc.

[71] Zahniser, R. A. 1990. «Building Software in Groups», American Programmer 3(7/8): 50–56.

[72] Zahniser, R. A. 1993. «Design by Walking Around», Communications of the ACM 36(10), October.

Примечания