Laura Lally
- 1.Caron, J. Raymond, Sirkka L. Javenpaa, and Donna B. Stoddard,"Business Reengineering at CIGNA Corporation: Experiences and Lessons Learned from the First Five Years," MIS Quarterly, September, 1994, p. 233-250. Google Scholar
Digital Library
- 2.Champy, James, Reengineering Management: The Mandate for New Leadership, HarperCollins: New York, 1995.Google Scholar
- 3.Collins, W. Robert, Keith W. Miller, Bethany J. Spielman, and Philip Wherry, "How Good is Good Enough?" Communications of the ACM, 37(1), January, 1994. p. 81-91. Google ScholarDigital Library
- 4.Costello, Scott H., "Software Engineering Under Deadline Pressure," ACM SIGSOFT Software Engineering Notes, 9(5), October, ! 984, p. 15. Google ScholarDigital Library
- 5.Davenport, Thomas, H., Nitin Nohria, "Case Management and the Integration of Labor," Sloan Management Review, 35(2) Winter 1994, p. I 1-23.Google Scholar
- 6.DeBoever, Larry, "Reengineering Your I/S Architecture," The Computer Conference Analysis Newsletter, 349. p. I-3.Google Scholar
- 7.Gibbs, W. Wayt, "Software's Chronic Crisis," Scientific American, September, 1994, p. 86-95.Google ScholarCross Ref
- 8.Hammer, Michael, "Reengincedng Work: Don't Automate, Obliterate," Harvard Business Review, 90(4), July- August, 1990, p. 104-112.Google Scholar
- 9.Hammer, Michael, and James Champy, Reengineering the Corporation, HarpcrCollins Publishers, New York, 1993.Google Scholar
- 10.Hammer, Michael, and Steven A. Stanton, The Reengineering Revolution: A Handbook, HarperCollins Publishers, New York, 1995.Google Scholar
- 11.Lewis, Peter, "A Rise in Intcrnet Break-lns Sets off a Security Alarm," New York Times, February, 5, 1994, p. bl, b48.Google Scholar
- 12.Littlewood, Bey, and Lorenzo Strigini, "The Risks of Software," Scientific American, November, 1992, p. 62-75.Google ScholarCross Ref
- 13.Longo, Susan C., "After Reengincering- 'Dcjobbing'" CPA Journal, 65(3), March 1995, p. 69.Google Scholar
- 14.Morris, Joe, "Another Computer Taken Hostage," Software Engineering Notes, 12(3), July 1987, p. 13.Google Scholar
- 15.Neumann, Peter, "Inside Risks: Some Reflections on a Telephone Switching Problem," Communications of the ACM, 33(7), July, 1990, p. 154. Google ScholarDigital Library
- 16.Neumann, Peter, "Inside Risks: Certifying Professionals," Communications of the ACM, 34(2), February, 1991, p. 130. Google ScholarDigital Library
- 17.Neumann, Peter, "Inside Risks: Leap-Year Problems," Communications of the ACM, 35(6), June, 1992b, p. 162. Google ScholarDigital Library
- 18.Neumann, Peter, "Inside Risks: Fraud by Computer," Communications of the ACM, 35(8), August, 1992c, p. 154. Google ScholarDigital Library
- 19.Neumann, Peter, Computer Related Risks, Addison Wesley, New York, 1995. Google ScholarDigital Library
- 20.Nissenbaum, Helen, "Computing andAccountability," Communications of the ACM, 37(1), January, 1994, p. 73-80. Google ScholarDigital Library
- 21.Norman, Donald, "Commentary: Human Error and the Design of Computer Systems," Communications of the ACM, 33(i), p. 4-7. Google ScholarDigital Library
- 22.Pamas, David L., John van Schouwen, and Shu Po Kwan, "Evaluation of Safety-Critical Software," Communications of the ACM, 33(6), June, 1990, p. 636-648. Google ScholarDigital Library
- 23.Perrow, Charles, Normal Accidents: Living with High Risk Technologies, Basic Books: New York, 1984.Google Scholar
- 24.Sagan, Scott, The Limits of Safety, Princeton University Press: Princeton, New Jersey, 1993.Google Scholar
- 25.Schwartau, Winn, Information Warfare, Thunder's Mouth Press: New York, 1995.Google Scholar
- 26.Scott-Morgan, Peter, "Why Change Fails to Motivate the Workers," Computer Weekly, January, 5, 1995, p. 14.Google Scholar
- 27.Sears, Woody, Roy Trotter, "Reengineering Readiness Test: What's Your Infrastructure IQ?" Industrial Engineering, 27(I), January 1995, p. 16-17.Google Scholar
- 28.Wiener, Lauren, Digitial Woes: Why We Should Not Depend on Software, Addison-Wesley: Reading Massachusetts, 1993. Google ScholarDigital Library
Index Terms
- Enumerating the risks of reengineered processes
Recommendations
Insuring computer risks
Individuals and organizations who own or use computers in daily operations face many exposures to the risk of loss of hardware, software, and other computing assets, including liability arising from computing operations. Many loss prevention techniques ...
A holistic approach to manage risks in NPD process
2017 Annual Reliability and Maintainability Symposium (RAMS)New product development (NPD) is expensive as well as risky endeavor for any organization owing to high product failure rates. A holistic risk management (RM) model may play a significant role in identifying, analyzing and mitigating the risks involved in ...
Comments