لطفا منتظر باشید ...
References
Abdel-Hamid, T. K., andMadnick, S. E. "The Elusive Silver Lining: How We Fail to Learn from Software Development Failures." Sloan Management Review 32, no. 1 (1990): 39–48.Anthes, G. H. "IRS Project Failures Cost Taxpayers $50B Annually." Computerworld, October 14, 1996a, pp.1.Anthes, G. H. "IRS: Tough to Get Any Respect." Computerworld, October 14, 1996b, pp. 28.Applegate, L. M. BAE Automated Systems: (A) and (B), Teaching Note. Case study no. 5–399–099. Boston: Harvard Business School Press, 1999.Barki, H.,Rivard, S., andTalbot, J. "Towards an Assessment of Software Development Risk." Journal of Management Information Systems 10, no. 2 (1993): 203–225.Barki, H.,Rivard, S., andTalbot, J. "An Integrative Contingency Model of Software Project Risk Management." Journal of Management Information Systems 17, no. 4 (2001): 37–69.Barwise, J. "Mathematical Proofs of Computer System Correctness." Notices of the American Mathematical Society 36, no. 9 (1989): 844–851.Berghel, H. "The Y2K E-Commerce Tumble." Communications of the ACM 44, no. 8 (2001): 15–17.Blum, B. I. "Improving Software Maintenance by Learning from the Past: A Case Study." Proceedings of the IEEE 77, no. 4 (1987): 596–606.Blum, B. I. "A Taxonomy of Software Development Methods." Communications of the ACM 37, no. 11 (1994): 82–94.Boddie, J. "The Project Post-Mortem." Computerworld, December 7, 1987, pp. 77–82.Boehm, B. W. Software Engineering Economics. Englewood Cliffs, NJ: Prentice Hall., 1981.Boehm, B. W. "Seven Basic Principles of Software Engineering." Journal of Systems and Software 3 (1983): 3–24.Boehm, B. W. "Software Risk Management: Principles and Practices." IEEE Software, January 1991, pp. 32–41.Boehm, B. W. "Project Termination Doesn't Equal Project Failure." Computer, September 2000, pp. 94–96.Bronzite, M. System Development: A Strategic Framework. London: Springer-Verlag, 2000.Brooks, F. P., Jr. "No Silver Bullet: Essence and Accidents of Software Engineering." IEEE Computer, April 1987, pp. 10–19.Brooks, F. P., Jr. The Mythical Man-Month: Essays on Software Engineering. Anniversary edition. Reading, Mass.: Addison-Wesley, [1975] 1995.Brooks, F. P., Jr. "The Computer Scientist as Toolsmith II." Communications of the ACM 39, no. 3 (1996): 61–68.Bulkeley, W. M. "When Things Go Wrong." Wall Street Journal, November 18, 1996, p. R25.Capers Jones, "Patterns of Large Software Systems: Failure and Success." IEEE Computer, March 1995, pp. 86–87.Chikofsky, E. J. "Changing Your Endgame Strategy." IEEE Software, November 1990, p. 87.Cohen, M. J.,March, J. G., andOlsen, J. "A Garbage Can Model of Organizational Choice." Administrative Science Quarterly 7 (1972): 1–25.Cole, A. "Runaway Projects—Cause and Effects." Software World (UK) 26, no. 3 (1995): 3–5.Collett, S. "Hershey Earnings Drop as New Warehouse, Order Systems Falter." Computerworld, October 26, 1999.Collier, B.,DeMarco, T., andFearey, P. "A Defined Process for Project Postmortem Review." IEEE Software, July 1996, pp. 65–71.Collins, T., andBicknell, D. Crash: Learning from the World's Worst Computer Disasters. London: Simon and Schuster, 1997.Constantine, L. L. On Peopleware. Englewood Cliffs, NJ: Yourdon Press/ Prentice Hall, 1993.Corti, G. "Risk, Uncertainty and Cost Benefit: Some Notes on Practical Difficulties for Project Appraisals." In J. N. Wolfe, ed., Cost Benefit and Cost Effectiveness, 75–87. London: Allen & Unwin, 1973.Curtis, B.,Krasner, H., andIscoe, N. "A Field Study of the Software Design Process for Large Systems." Communications of the ACM 31, no. 11 (1988): 1268–1287.Dash, J. "Two Big Failures Cite Cap Gemini." Computerworld, December 13, 1999.Davis, G. B., andOlson, M. H. Management Information Systems: Conceptual Foundation, Structure, and Development. New York: McGraw-Hill, 1985.DeGrace, P., andStahl, L. H. Wicked Problems, Righteous Solutions: A Catalogue of Modern Software Engineering Paradigms. Englewood Cliffs, NJ: Yourdon Press/ Prentice Hall, 1990.DeMarco, T., andLister, T. Peopleware: Productive Projects and Teams. New York: Dorset House, 1987.Denning, P., andDargan, P. "Action-Centered Design." In T. Winograd, ed., Bringing Design to Software, 105–119. Reading, MA: Addison-Wesley, 1996.Denzin, N. K. The Research Act. New York: McGraw-Hill, 1978.De Young, L. "Organizational Support for Software Design." In T. Winograd, ed., Bringing Design to Software, 253–267. Reading, MA: Addison-Wesley, 1996.Dijkstra, E. W. "The Structure of ‘THE’-Multiprogramming System," Communications of the ACM 11 (1968): 341–346.Edstrom, A. "User Influence and the Success of MIS Projects: A Contingency Approach." Human Relations 30, no. 7 (1977): 589–607.Eischen, K. "Software Development: An Outsider's View." Computer, May 2002, pp. 36–44."ERP Stumbles." Comptroller's Report. Computerworld, May 2000.Ewusi-Mensah, K. "Evaluating Information Systems Projects: A Perspective on Cost-Benefit Analysis." Information Systems 14, no. 3 (1989): 205–217.Ewusi-Mensah, K. "The Abandonment of Information Systems Development Projects in Organizations." Proposal to the National Science Foundation, Loyola Marymount University, 1991.Ewusi-Mensah, K. "Critical Issues in Abandoned Information Systems Development Projects." Communications of the ACM 40, no. 9 (1997): 74–80.Ewusi-Mensah, K. Interview Notes of IS Group: The CODIS Project, 1992, p. 8. Available from the author.Ewusi-Mensah, K. "Why IS Development Projects Are Abandoned: A Diagnosis from User Perspectives." Working paper, College of Business Administration, Loyola Marymount University, 1998.Ewusi-Mensah, K., andPrzasnyski, Z. H. "On Information Systems Project Abandonment: An Exploratory Study of Organizational Practices." MIS Quarterly 15 (March 1991): 67–85.Ewusi-Mensah, K., andPrzasnyski, Z. H. "Factors Contributing to the Abandonment of Information Systems Development Projects." Journal of Information Technology 9 (1994): 185–201.Ewusi-Mensah, K., andPrzasnyski, Z. H. "Learning from Abandoned Information Systems Development Projects." Journal of Information Technology 10 (1995): 3–14.Fetzer, J. H. "Program Verification: The Very Idea." Communications of the ACM 31, no. 9 (1988): 1048–1063.Fetzer, J. H. "Author's Response [to various letters about 1988 paper]." Communications of the ACM 32, no. 3 (1989): 377–381.Fisher, G. H. Cost Considerations in Systems Analysis. New York: Elsevier, 1971.Flowers, S. Software Failures: Management Failure—Amazing Stories and Cautionary Tales. London: Wiley, 1997.GAO. Tax Systems Modernization: Management and Technical Weaknesses Must Be Corrected If Modernization Is to Succeed. Report to the Commissioner of the Internal Revenue Service. GAO/AIMD-95-156, July 1995. Washington, DC: GPO.GAO. Tax Systems Modernization: Actions Underway But IRS Has Not Yet Corrected Management and Technical Weaknesses. Report to Congressional Requesters. GAO/AIMD-96-106, June 1996. Washington, DC: GPO.GAO. Medicare Transaction System: Success Depends upon Correcting Critical Managerial and Technical Weaknesses. Report to Congressional Requesters. GAO/AIMD-97-78, May 1997. Washington, DC: GPO.Gibbs, W. W. "Software's Chronic Crisis." Scientific American, September 1994, pp. 86–95.Gladden, G. R. "Stop the Life-Cycle, I Want to Get Off." Software Engineering Notes 7, no. 2 (April 1982): 35–39.Glaser, G. "Managing Projects in the Computer Industry." Computer, October 1984, pp. 45–53.Glass, R. L. Software Runaways: Lessons Learned from Massive Software Project Failures. Englewood Cliffs, NJ: Prentice Hall, 1998.Glass, R. L. "The Realities of Software Technology Payoffs." Communications of the ACM 42, no. 2 (1999): 74–79.Halper, M. "IS Cover-Up Charged in System Kill." Computerworld, August 10, 1992a, p. 1.Halper, M. "Outsourcer Confirms Demise of Reservation Coalition Plan." Computerworld, August 3, 1992b, p. 1.Halper, M. "Marriott Suit Damns AMR Role in Confirm." Computerworld, October 12, 1992c, p. 8.Halper, M. "Too Many Pilots." Computerworld, October 12, 1992c, p. 8.Harel, D. "Biting the Silver Bullet." Computer, January, 1992, pp. 8–20.Hedberg, B. "How Organizations Learn and Unlearn." In P. C. Nystrom and W. H. Starbuck, eds., Handbook of Organizational Design, 3–27. Oxford: Oxford University Press, 1981.Heinrich, E. "Money to Burn." Infosystems Executive, October 1998, pp. 10–16.Hoare, C. A. R. "Programming: Sorcery or Science?" IEEE Software, April 1984, pp. 5–6.Howard, A. "Software Engineering Project Management." Communications of the ACM 44, no. 5 (2001): 23–24."IRS Admits Its Computers Are a Nightmare." San Francisco Chronicle, January 31, 1997, p. A1."IRS Computer Project Has ‘Very Serious Problems,’ Rubin Says." Los Angeles Times, March 29, 1996, p. D1."IRS Drops Internet Filing Plan." San Francisco Chronicle, November 11, 1996, p. A3."It Doesn't Compute." San Francisco Chronicle, February 2, 1997, editorial page.Ives, B.,Hamilton, S., andDavis, G. "A Framework for Research in Computer Based Management Information Systems." Management Science 26 (1980): 910–934.Ives, B., andOlson, M. "User Involvement and MIS Success: A Review of Research." Management Science 30, no. 5 (1984): 586–603.Jesitus, J. "Broken Promises? FoxMeyer's Project Was a Disaster. Was the Company Too Aggressive or Was It Misled?" Industry Week, November 3, 1997, pp. 31–37.Johnson, J. "Chaos: The Dollar Drain of IT Project Failures." Application Development Trends 2, no. 1 (1995): 41–47.Keider, S. P. "Why Systems Development Projects Fail." Journal of Information Systems Management 1, no. 3 (summer 1984): 33–38.Keil, M.,Cule, P. E., Lyytinen, K., andSchmidt, R. C. "A Framework for Identifying Software Project Risks." Communications of the ACM 41, no. 11 (1998): 76–83.Keil, M., andRobey, D. "Blowing the Whistle on Troubled Software Projects." Communications of the ACM 44, no. 4 (2001): 87–93.Klein, G.,Jiang, J. J., andTesch, D. B. "Wanted: Project Teams with a Blend of IS Professional Orientations." Communications of the ACM 45, no. 6 (2002): 81–87.Krault, R. E., andStreeter, L. A. "Coordination in Software Development." Communications of the ACM 38, no. 3 (1995): 69–81.Kumar, K. "Post Implementation Evaluation of Computer-Based Information Systems: Current Practices." Communications of the ACM 33, no. 2 (1990): 203–212.Lehman, M. M. "Programs, Life Cycles, and Laws of Software Evolution." Proceedings of the IEEE 68, no. 9 (1980): 1060–1076.Lehman, M. M. "Uncertainty in Computer Applications and Its Control through the Engineering of Software." Software Maintenance: Research and Practice 1 (1989): 3–27.Leith, P. "Fundamental Errors in Legal Logic Programming." Computer Journal 29 (1986): 545–552.LJX files. "The Complaint in Brown v. Andersen Consulting." 1988. Available at <http://wwww.LJX.com/LJX/image/library/english/10127_bankruptcy/andersenl>.Lucas Jr., H. C. Why Information Systems Fail. New York: Columbia University Press, 1975.Lyytinen, K. "Different Perspectives on Information Systems: Problems and Solutions." ACM Computing Surveys 19, no. 1 (March 1987): 5–46.Lyytinen, K., andHirschheim, R. "Information Systems Failures—A Survey and Classification of the Empirical Literature." Oxford Surveys in Information Technology 4 (1987): 257—309.MacCormack, A. "Product Development Practices That Work: How Internet Companies Build Software." MIT Sloan Management Review, winter 2001, 75–84.MacCormack, A.,Verganti, R., andIansiti, M. "Developing Products on ‘Internet Time’: The Anatomy of a Flexible Development Process." Management Science 47, no. 1 (2001): 133–150.Maglitta, J. "Learning Lessons from IRS's Biggest Mistakes." Computerworld, October 14, 1996, p. 30.March, J. G., andOlsen, J. P. Ambiguity and Choice in Organizations. Bergen: Universitetsforlaget, 1976.Marciniak, J. J. ed. Encyclopedia of Software Engineering. Vol. 1. New York: Wiley, 1994.Markus, M. L. "Power, Politics and MIS Implementation." Communications of the ACM 26, no. 6 (1983): 430–444.McCarthy, J. Dynamics of Software Development. Redwood, WA: Microsoft Press, 1995.McFarlan, F. W. "Portfolio Approach to Information Systems." Harvard Business Review 65 (March–April 1981): 68–74.McPartlin, J. P. "The Collapse of Confirm." Information Week, October 19, 1992, pp. 12.Mearian, L. "Highmark Sues KPMG over Failed IT Project." Computerworld, November 7, 2001a.Mearian, L. "Insurer Sues, Claims KPMG Mismanaged Billing Project." Computerworld, November 12, 2001b.Modha, J.,Gwinnett A., andBruce, M. "A Review of Information Systems Development Methodology ( ISDM ) Selection Techniques." Omega 18, no. 5 (1990): 473–490.Montealegre, R.,Knoop, C. I., Nelson, H. J., andApplegate, L. M. BAE Automated Systems (A): Denver International Airport Baggage-Handling System". Case study no. 9-396-311. Boston: Harvard Business School Press, 1996.Neumann, P. G. "System Development Woes." Communications of the ACM 40, no. 12 (1997): 160.Newman, M., andNoble, F. "User Involvement as an Interaction Process: A Case Study." Information Systems Research 1, no. 1 (March 1990): 89–113.Nicholson, L. "Executive Says Administrative-Software Failures Are Part of Fine-Tuning." Philadelphia Inquirer, November 6, 1999.OASIG. "Why Do IT Projects So Often Fail?" OR Newsletter, September 1996, pp. 12–16.Olle, T. W.,Hagelstein, J., Macdonald, I. G., Rolland, C., Sol, H. G., Van Assche, F. J. M., andVerrijn-Stuart, A. A. Information Systems Methodologies—A Framework for Understanding. 2d ed. Reading, MA: Addison-Wesley, 1991.Osterland, Andrew. "Blaming ERP." CFO: The Magazine for Senior Financial Executives 16, no. 1 (2000): 89–93.Oz, E. "When Professional Standards Are Lax: The CONFIRM Failure and Its Lessons." Communications of the ACM 37, no. 10 (October 1994): 29–36.Parnas, D. L. "Software Aspects of Strategic Defense Systems." Software Engineering Notes 10, no. 5 (October 1985): 15–23.Patton, M. Q. How to Use Qualitative Methods in Evaluation., Newbury Park, CA: Sage, 1987.Patton, M. Q. Qualitative Research and Evaluation Methods. 3rd ed. Thousand Oaks, CA: Sage, 2002.Petroski, H. "History and Failure." American Scientist 80 (November–December 1992): 524–526."PG&E Dumps CIS Project." PCWEEK 14, no. 17 (April 28, 1997): 1.Powers, R. F., andDickson, G. W. "MIS Project Management: Myths, Opinions, and Reality." California Management Review 15, no. 3 (spring 1973): 147–156.Pressman, R. S. Software Engineering: A Practitioner's Approach. New York: McGraw-Hill, 1992.Ramamoorthy, C. V.,Prakash, A., Wei-Tek, T., andUsuda, Y. "Software Engineering: Problems and Perspectives." Computer, October 1984, pp. 191–209.Reyment, R., andJreskog, K. G. Applied Factor Analysis in the Natural Sciences. Cambridge: Cambridge University Press, 1993.Rifkin, G. "What Really Happened at Denver's Airport?" Forbes, SAP Supplement, August 1994, pp. 111–114.Rittel, H. W., andWebber, M. M. "Dilemmas in a General Theory of Planning." Policy Sciences 4 (1973): 155–169.Robinson, H.,Hall, P., Hovenden, F., andRachel, J. "Postmodern Software Development." Computer Journal 41, no. 6 (1998): 363–375.Ropponen, J., andLyytinen, K. "Components of Software Development Risk: How to Address Them? A Project Manager Survey." IEEE Transactions on Software Engineering 26, no. 2 (2000): 98–111.Saarinen, T. "System Development Methodology and Project Success." Information & Management 19 (1990): 183–193.Sage, A. P., andPalmer, J. D. Software Systems Engineering. New York: Wiley, 1990.Sauer, C. Why Information Systems Fail: A Case Study Approach. Henley-on-Thames, Oxfordshire: Alfred Waller, 1993.Sillince, J. A. A., andMouakket, S. "Varieties of Political Process during Systems Development." Information Systems Research 8, no. 4 (1997): 368–397.Simon, H. A. The Sciences of the Artificial. 2nd ed. Cambridge, MA: MIT Press, 1984.Sommerville, I. "Software Process Models." In A. B. Tucker, Jr., The Computer Science and Engineering Handbook, pp. 2259–2277. Boca Raton, FL: CRC Press, 1997.Songini, M. "Halloween Less Haunting for Hershey This Year." Computerworld, November 2, 2000.Standish Group. "Chaos." Sample research paper, May 1995. Available at <http://www.standishgroup.com>.Standish Group. "Chaos." Sample research paper, May 1998. Available at <http://www.standishgroup.com>.Stedman, C. "Update: Failed ERP Gamble Haunts Hershey." Computerworld, October 29, 1999.Stedman, C. "IT Woes Contribute to Hershey Sales, Profits Decline." Computerworld, February 2, 2000.Stockman, S. G. "The Recovery of Software Projects." In B. A. Kitchenham, ed., Software Engineering for Large Systems, 209–219. London: Elsevier Applied Science, 1990.Szilagyi, J. G. "Bank of America's Masternet System: A Case Study in Risk Assessment." In R. L. Glass, ed., Software Runaways: Lessons Learned from Massive Software Project Failures. Englewood Cliffs, NJ: Prentice Hall, 1998.Tait, P., andVessey, I. "The Effect of User Involvement on System Success: A Contingency Approach." MIS Quarterly 12 (March 1988): 91–108.Tellioglu, H., andWagner, I. "Software Cultures." Communications of the ACM 42, no. 12 (1999): 71–77.Walz, D. B.,Elam, J. J., andCurtis, B. "Inside a Software Design Team: Knowledge Acquisition, Sharing and Integration." Communications of the ACM 36, no. 10 (October 1993): 63–77.Wasserman, A. I. "Information System Design Methodology." Journal of the American Society for Information Science 31, no. 1 (1980): 25–44.Wheatley, M. "ERP Disasters; Bet the Company; and Lose." Financial Director, March 1, 2000, pp. 35–39.Whiting, R. "Development in Disarray." Software Magazine 18, no. 9 (1998): 20.Winograd, T. "Introduction." In T. Winograd, ed., Bringing Design to Software, xiii–xxv Reading, MA: Addison-Wesley, 1996.Wysocki, Jr., B. "Pulling the Plug: Some Firms, Let Down By Costly Computers, Opt to ‘De-Engineer’." The Wall Street Journal, April 30, 1998, pp. 1–2.Yourdon, E. Death March: The Complete Software Developer's Guide to Surviving "Mission Impossible" Projects. Englewood Cliffs, NJ: Prentice Hall, 1997.Zellner, W. "Portrait of a Project as a Total Disaster." Business Week, January 17, 1994, p. 36.
