Towards management of software as assets: A literature review with additional sources

Information and Software Technology

Volumn 50, Issue 4, 2008, Pages 241-258

  Ben Menachem, Mordechai ^a  

^a NONE   (Israel)

Author keywords

Goals Management; Project Management; Software Asset Management; Software Engineering; Software Quality Management

Indexed keywords

INFORMATION RETRIEVAL; PROJECT MANAGEMENT; QUALITY MANAGEMENT;

GOALS MANAGEMENT; SOFTWARE ASSET MANAGEMENT; SOFTWARE QUALITY MANAGEMENT;

SOFTWARE ENGINEERING;

EID: 38049095083     PISSN: 09505849     EISSN: None     Source Type: Journal    
DOI: 10.1016/j.infsof.2007.08.001     Document Type: Article

References (252)

1. Abdel-Hamid T.K., and Madnick S.E. Lessons learned from modeling the dynamics of software development. Communications of the ACM 32 12 (1989) 1426-1438
2. Agarwal R., and Sambamurthy V. Principles and models for organizing the IT function. MIS Quarterly Executive 1 1 (2002) 1-16
3. Aho A.V., Kernighan B.W., and Weinberger P.J. The AWK Programming Language (1988), Addison-Wesley
4. Anderson M.C., Banker R.D., and Ravindran S. The new productivity paradox. Communications of the ACM 46 3 (2003) 91-94
5. Anthony R.N. Planning and Control Systems: A Framework for Analysis (1965), Harvard University Press, Cambridhe, MA
6. ANSI/IEEE Std 730-1984, ANSI/IEEE Standard for Software Quality Assurance Plans, IEEE, 1984.
7. ANSI/MIL-STD-1815A-1983, Reference Manual for the ADA Programming Language, US Department of Defense, 1983, 17 February.
8. Anthes G.H. Trade groups roll out year 2000 seal of approval. Computerworld (1996)
9. Assistant Secretary of Defense for Command, Control, Communications, and Intelligence (ASD C3I), Repairing Latent Year 2000 Defects Caused by Date Windowing, Investment and Acquisition Directorate, US Department of Defense, Version 1.0, 1 April 2002.
10. Avatar, Phase I - Impact Assessment, CFS017 Systems, Project V10301: Technical Assessment Summary, 1996, 11 October.
11. Avatar, Phase I - Impact Assessment, Applications JCH016: Technical Assessment Summary, Mobil Oil Corporation, Avatar Solutions Inc., 1996, 23 December.
12. Avatar, Phase I - Impact Assessment, JCH016 System: Resource Assessment Report, Mobil Oil Corporation, Avatar Solutions Inc., 1996, 14 December.
13. Avatar, Service Level Agreement (SLA), Mobil Oil Corporation, Avatar Solutions Inc., 1996, 14 December.
14. C. Babcock, The redcoats -er- the year 2000 is coming, Computerworld, , 1996, 7 October.
15. Backer S. Exterminating the Millennium Bug: on the scene with a medical insurer's SWAT team. Business Week (1998) 108-110
16. Backer S. Getting ready for the Euro bug: programming computers for the new currency may cost $175 billion. Business Week (1998) 18-19
17. Bakos Y., Brynjolfsson E., and Lichtman D. Shared information goods. Journal of Law and Economics (1999)
18. Barra R. Putting Quality Circles to Work: A Practical Strategy for Boosting Productivity and Profits (1983), McGraw-Hill
19. Barry E.J., Mukhopadhyaya T., and Slaughter S.A. Software Project Duration and Effort: An Empirical Study (2002), Information Technology and Management 3, pp. 113-136
20. V.R. Basilli, Applying the Goal/Question/Metric Paradigm in the Experience Factory, in: 10th Annual CSR Workshop, 1993, October.
21. V.R. Basilli, Software Modeling and Measurement: The Goal/Question/Metric Paradigm, NASA/GSFC, contract number NSG-5123 and AFOSR 90-0031.
22. Baxter P. Focusing measurement on managers' information needs. Cross Talk 15 7 (2002) 22-25
23. Becker S.A., and Bostelman M.L. Aligning strategic and project measurement systems. IEEE Software (1999) 46-51
24. Beizer B. Software System Testing and Quality Assurance (1984), Van Nostrand Reinhold
25. Beizer B. Software Testing Techniques (1983), Van Nostrand Reinhold Company
26. Ben-Menachem M., and Gelbard R. Integrated IT management tool-kit application. Communication of the ACM 45 4 (2002) 96-102
27. Ben-Menachem M., and Marliss G. Inventorying information technology systems: supporting the "Paradigm of Change. IEEE Software (2004) 34-43
28. M. Ben-Menachem, G. Marliss, A review of Requirements Analysis Technologies, in: 15th IPA Conference, Jerusalem, 1980, November.
29. M. Ben-Menachem, G. Marliss, D. Braunschvig, Rapid Prototyping of EDP Systems, in: 16th IPA Conference, Jerusalem, 1981, November.
30. Ben-Menachem M. The PATRIARCH SQA Handbook (1988), MIV∼Meda Ltd.
31. M. Ben-Menachem, A Procedure for Risk Management with reference to software, IEEE Computer Society, Fifth Israel conference on Computer Systems and Software Engineering, 1991, pp. 68-71, May.
32. M. Ben-Menachem, Risk Analysis Forms for Project OMETZ, QA-94110101, Quality Awareness Ltd., 1994 (in Hebrew).
33. Ben-Menachem M. Software Configuration Management Guidebook (1994), McGraw-Hill
34. M. Ben-Menachem, Code Warehousing™ through "Legacy Systems Workbench™", Quality Awareness Ltd., revision 1.8c, 1996, 15 July.
35. Ben-Menachem M. Power Tools™: User's Guide (1997), Software Engineering (SE) R&D (Israel) Ltd.
36. Ben-Menachem M. Getting Started with Power Tools™ (1997), Software Engineering (SE) R&D (Israel) Ltd. September
37. Ben-Menachem M. Power Tools™: Documentation Specialist™ Course Guide (1997), Software Engineering (SE) R&D (Israel) Ltd.
38. Ben-Menachem M., and Garry M. Software Quality, Producing Practical, Consistent Software (1997), International Thompson Computer Press, Boston, USA
39. Ben-Menachem M. Technology Trends: Prognostications and likely results (1998), Software Engineering (SE) R&D (Israel) Ltd.
40. M. Ben-Menachem, Financial Accounting Doesn't Know the Score, Letter-to-the-editor; Business Week, 2000, pp. 5-6, 16 October.
41. M. Ben-Menachem, Relevance: IT/IS Management and Research Directions, invited paper; CAIS, vol. 6, article 5, 2001, March.
42. Bersoff E.H., Henderson V.D., and Siegal S.G. Software Configuration Management: An Investment in Product Integrity (1980), Prentice-Hall
43. Bierman H., Morris W.T., Taylor G.A., Cuninghame R.A., and Couts D.A. Management Decision-Making (1969), Pan Books
44. Blanchard B.S., and Fabrycky W.J. Systems Engineering and Analysis. fourth ed. (2006), Prentice Hall
45. Boehm B. Improving Software Productivity. Computer 20 9 (1987) 43-57
46. Boehm B. Get ready for Agile Methods, with care. Computer 35 1 (2002) 64-69
47. C.A. Bowsher, Executive Guide: Improving Mission Performance Through Strategic Information Management and Technology: Learning from leading organizations, US General Accounting Office, GAO/AIMD-94-115, 1994, May.
48. BPM Forum, Software Drain or Business Gain: Assessing Application Value, Relevance and Cost to Your Company, , 2004, December.
49. T. Braithwaite, Year 2000 Date conversion Management Security Considerations (new), Computer Security Handbook, third ed., 1997 supplement, chapter 26, John Wiley, Inc., pp. 1-12.
50. Bresnahan T., Brynjolfsson E., and Hitt L. Information technology, work organization and the demand for skilled labor: firm-level evidence. Quarterly Journal of Economics (2000) November
51. J.L. Brock Jr., Defense Computers: LSSC Needs to Confront Significant Year 2000 Issues, US Government Accounting Office, GAO/AIMD-97-149, 1997, September.
52. J.L. Brock Jr., Year 2000 Computing Crisis: Actions Needed to Address Credit Union System's Year 2000 Problem, United States General Accounting Office; GAO/T-AIMD-98-48, 1998, January.
53. J.L. Brock Jr., Defense Computers: Air Force Needs to Strengthen Year 2000 Oversight, US Government Accounting Office; GAO/AIMD-98-35, 1998, January.
54. J.L. Brock Jr., Year 2000 Computing Crisis: Federal Deposit Insurance Corporation's Efforts to Ensure Bank Systems Are Year 2000 Compliant, United States General Accounting Office; GAO/T-AIMD-98-73, 1998, 10 February.
55. J.L. Brock Jr., Year 2000 Computing Crisis: Readiness of the Telecommunications Industry, United States General Accounting Office; GAO/T-AIMD-99-293, 1999, September.
56. Broekman B., and Notenboom E. Testing Embedded Software (2003), Addison Wesley
57. Brooks F.P. The Mythical Man-Month. 20th anniversary ed. (1995), Addison Wesley
58. Byrne J. The search for the Young and Gifted: why talent counts. Business Week (1999)
59. E. Brynjolfsson, S. Yang, The intangible costs and benefits of computer investments: evidence from the financial markets, in: Proceedings of the International Conference on Information Systems; Atlanta, Georgia, December, 1997, Revised April 1999.
60. Brynjolfsson E. The Productivity Paradox of information technology. Communications of the ACM 36 12 (1993) 67-77
61. E. Brynjolfsson, L. Hitt, S. Yang, Intangible Assets: How the Interaction of Information Technology and Organizational Structure Affects Stock Market Valuations, MIT Working paper, 2000, July.
62. Brynjolfsson E., and Hitt L.M. Beyond computation: information technology, organizational transformation and business performance. Journal of Economic Perspectives, Fall (2000)
63. E. Brynjolfsson, Hidden Assets, CIO Insight, <, 2001, 6 November.
64. C. Brys-Yee, Business Markets Division, Service Delivery Systems Directorate Metrics Handbook, version 2.0; Enterprise Metrics Initiative, Metrics Model; ATT; Draft, 1996, 3 September.
65. CA-IDEAL, Command and Reference Manual, Reference Manual, release 2.1, Computer Associates, 1990.
66. B. Caldwell, Millennium Mess, Information Week, 1998, pp. 18-19, , 13 April.
67. J. Canton, The Extreme Future, Dutton, Penguin, 2006.
68. Caputo K. CMM Implementation Guide: Choreographing Software Process Improvement (1998), Addison Wesley
69. Cave W.C., and Maymon G.W. Software Lifecycle Management: The Incremental Method (1984), Macmillan
70. S.Y. Chiang, R.G. Sherlund, Y. Ma, EAI: Building the Virtual Enterprise Keiretsu, Goldman Sachs Technology Enterprise Software, 1999, 26 March.
71. ®: Guideline for Process Integration and Product Improvement (2003), Addison Wesley
72. T. Clancy, CHAOS, Standish Group, 1998.
73. C. Von Clausewitz, Clausewitz on War, Penguin Books, 1968 (first published as "Vom Kriege" 1832).
74. Cockburn A. Writing Effective Use Cases (2001), Addison-Wesley
75. A. Cockburn, Characterizing People as Non-Linear, First-Order Components in Software Development, Humans and Technology Technical Report, TR 99.05, 1999, October.
76. Computerweekly, Millennium problem hits overseas calls, Computerweekly, .
77. Computerworld, How many programmers does it take to do the job, Computerworld, 10 March 1997.
78. Computerworld, Year 2000 scoreboard, Computerworld; 1188 days to 2000 (actual date on the article), 76, 1996, 29 September.
79. S.H. Cramm, IT Project Planning: Adult Supervision Required, CIO Magazine (on line) (2001) 4 pages, 15 February.
80. Crosby P.B. Quality is Free: The Art of Making Quality Certain (1979), McGraw-Hill
81. Davenport T.H. Process Innovation: Re-Engineering Work through Information Technology (1993), Harvard Business School Press, Boston, MA
82. P. de Jager, Take a Reporter to Lunch, Datamation, special supplement, 1996, 1 January.
83. DeMillo R., McCracken W.M., Martin R.J., and Passafiume J.F. Software Testing and Evaluation (1987), Benjamine Cummings Publishing Company
84. Deutsch M.S. Software Verification and Validation: Realistic Project Approach (1982), Prentice-Hall
85. L. DiDio, Y2K snag hides in PC hardware, Computerworld 1998, 13 April.
86. E. Dijkstra, The Humble Programmer, ACM Turing Award Lecture; CACM; August 1972, reprinted in: ACM Turing Award Lectures: The First Twenty Years 1966-1985, ACM press, Addison-Wesley, 1987.
87. DoD-STD-2167A, Military Standard: Defence System Software Development, US Department of Defense, 1988, 29 February.
88. Downes V.A., and Goldsack S.J. Programming Embedded Systems with ADA (1982), Prentice-Hall
89. Drucker P. The Practice of Management (1955), Pan Books
90. Dunn R. Software Defect Removal (1984), McGraw Hill
91. Duncan D.E. The Calendar: The 5000-Year Struggle to Align the Clock and the Heavens - and What Happened to the Missing Ten Days (1998), Fourth Estate
92. W.R. Duncan, director of standards, PMBOK Guide: A guide to the Project Management Body of Knowledge, Project Management Institute, standards committee, 1996.
93. Dunne J.W. An Experiment with Time (1927), Faber and Faber Limited
94. Dustin E., Rashka J., and Paul J. Automated Software Testing: Introduction, Management, and Performance (1999), Addison Wesley
95. Ettlie J. Managing Technology Projects (2000), Wiley
96. J. Fitz-enz, The 8 Practices of Exceptional Companies, AMACOM, 1997.
97. W.S. Franklin, Year 2000 Computing Crisis: Audit Program Guide: Exposure Draft, Government Accounting Office; GAO/AIMD-10.1.17, 1997, June.
98. W.S. Franklin, Year 2000 Computing Crisis: An Assessment Guide, Government Accounting Office; GAO/AIMD-10.1.14, 1997, September.
99. GGD/AIMD-99-215, Managing for Results: Opportunities for Continued Improvements in Agencies Performance Plans, Government Accounting Office, 20 July 1999.
100. GGD-96-118, Executive Guide: Effectively Implementing the Government Performance and Results Act, Government Accounting Office, 1996, 1 June.
101. J. Giera, M. Cecere, IT Managers - the Key to Successful Mergers, Special advertising section, Business Week 21 2000, February.
102. H. Gleckman, ZAP! How the Year 2000 Bug will hurt the economy: special report, Business Week, 1998, 8.
103. L. Gomes, Even Some New Software Won't Work In 2000, The Wall Street Journal, 1996, B1-2, 18 September.
104. Gomes L. Companies estimate 'Year 2000' computer costs. The Wall Street Journal (1998) B8
105. Gottschalk P., and Solli-Saether H. Differences in stage of integration between business planning and information systems planning according to value configurations. Informing Science 4 1 (2001) 1-10
106. W. Grosshans, Assessing the Reliability of Computer-Processed Data, US General Accounting Office, GAO/OP-8.1.3, 1991, April.
107. R.M. Graham, Chairman, in: Proceedings of the ACM-SIGPLAN Symposium on the ADA Programming Language, 9-11 December 1980; ACM SIGPLAN Notices, V15 N11, 1980, November.
108. Hancock L., and Krieger M. The C Primer (1982), McGraw-Hill
109. Hayer F.A. The Road to Serfdom (1986), Routledge & Kegan Paul first published 1944
110. R.J. Hillman, SEC Year 2000 Report: Future Reports could Provide More Detailed Information, General Accounting Office, GAO/GGD/AIMD-98-51, 1998, 6 March.
111. R.C. Hite, Information Technology: Inconsistent Software Acquisition Processes at the Defense Logistics Agency Increase Project Risks, Government Accounting Office; GAO-02-9, 2002, January.
112. T. Hoffman, Year 2000 problem comes bundled with legacy of potential litigation, Computerworld, 1996, 14 October.
113. T. Hoffman, R.L. Scheier, Sr. editor, Visa leads charge for compliance, Computerworld, 1997, p. 1, 13 January.
114. T. Hoffman, A double whammy awaits, Computerworld, 1998, p. 12, 9 March.
115. Hopcroft J.E., and Ullman J.D. Formal Languages and their Relation to Automata (1969), Addison-Wesley
116. Hughes B., and Cotterell M. Software Project Management. second ed. (1999), McGraw-Hill
117. Humphrey W.S. Managing the Software Process, SEI Series in Software Engineering (1989), Addison-Wesley
118. J.D. Ichbiah, J.C. Heliard, O. Roubine, J.G.P. Barnes, B. Kreig-Brueckner, B.A. Wichmann, Rationale for the Design of the ADA Programming Language, ACM SIGPLAN Notices, 14(6), 1979, June.
119. ISO 9000-3, Quality management and quality assurance standards - Part 3: Guidelines for the application of ISO 9001:1994 to the development, supply, installation and maintenance of computer software, International Standards Organization, second ed., 1997, 15 December.
120. ISO/IEC 12207, Information technology - Software life cycle processes, International Standards Organization; first edition; 1 August 1995 and IEEE P1448, US implementation of ISO/IEC 12207, Standard for Information Technology - Software life cycle processes, 1996, 1 November.
121. Jemison D.B., and Sitkin S.B. Acquisitions: The Process Can be a Problem (1986), Harvard Business Review pp. 107-116, March-April
122. Joint Task Force on Computing Curricula, IEEE Computer Society and Association for Computing Machinery, Computing Curriculum -Software Engineering, May 2004; National Science Foundation Grant No. 0003263.
123. Jones C. Applied Software Measurement: Assuring Productivity and Quality (1991), McGraw-Hill
124. Juran J.M. Juran on Design for Quality: The New Steps for Planning Quality into Goods and Services (1992), The Free Press
125. Kaman Sciences Corporation, DACS Data Compendium, contract number F30602-92-C-0158; Data & Analysis Center for Software; Rome Laboratory; Rome Air Force Base, 1997, 13 November.
126. Kan S.H. Metrics and Models in Software Quality and Engineering. second ed. (2003), Addison Wesley
127. Karin I., and Preiss K. Strategic marketing models for a dynamic competitive environment. Journal of General Management (2002)
128. Katz B., and Lerman N. Building a three dimensional work breakdown structure. Data Base (1985) 14-17
129. T. Keidar, The PRIMA Model: Software Risk Management using Markov Chains, Ben-Gurion University, Department of Industrial Engineering and Management, M.Sc. Thesis, 2000, August.
130. Keil M. Pulling the plug: Software Project Management and the problem of project escalation. MIS Quarterly (1995) 421-447
131. E. Keller, Technology Paradise Lost: Why companies will spend less to get more from Information Technologies, Wapiti, 2004.
132. Kemerer C.F. Software Project Management: Readings and Cases (1997), Irwin McGraw-Hill
133. Kappelman L.A. Killer Apps & Dead Bodies. InformationWeek (2000) 264
134. Kappelman L.A. Some strategic Y2K blessings. IEEE Software (2000) 42-46
135. Kernighan B.W., and Plauger P.J. The Elements of Programming Style (1974), McGraw-Hill
136. Kerridge A.E. Measure project progress and performance effectively. Hydrocarbon Processing May (1988) 97-102
137. N. Kingsbury, Managing for Results: Opportunities for Continued Improvements in Agencies' Performance Plans, US General Accounting Office; GAO/GGD/AIMD-99-215, 1995, July.
138. Klosch R.R., Glaser P.W., and Truschnegg R.J. A testing approach for large system portfolios in industrial environments. Journal of Systems and Software 62 1 (2002) 1-20
139. Krieg A.F., Miller D.H., and Bressler G.L. Computer Programming in Standard Mumps. second ed. (1984), The MUMPS User's Group
140. Kulpa M.K., and Johnson K.A. Interpreting the CMMI (2003), Auerbach Publications
141. Laudon K.C., and Laudon P. Management Information Systems. eighth ed. (2004), Prentice-Hall
142. LCD-80-69, The Department of Defense's Standardization Program for Military Computers-A More Unified Effort is Needed, Report to the Congress by the Comptroller General of the United States, 1980, 18 June.
143. Lefkon D. Seven Work Plans for Year-2000 Upgrade Projects. Communications of the ACM 40 5 (1997)
144. M.M. Lehman, Uncertainty in Computer Application, Communications of the ACM, Technical Correspondence 33(5) (1990) 584-586.
145. M.M. Lehman, Feedback in the Software Evolution Process, Keynote Address, CSR Eleventh Annual Workshop on Software Evolution: Models and Metrics, Dublin, 7-9 September 1994, Workshop Proc., also in Information and Software Technology, sp. is. on Software Maintenance 38(11) (1996), Elsevier, 1996, pp. 681-686.
146. Lehman M.M., and Ramil J.F. Rules and tools for software evolution planning and management. Annals of Software Engineering 11 (2001)
147. T.R. Leishman, Dr. David a. Cook, Requirements Risks can Drown Software Projects, CrossTalk The Journal of Defense Software Engineering (2002) 4-8.
148. J. Levin, Lectures on Burroughs Implementation of Structures Programming Techniques, Burroughs.
149. E. Lindholm, executive editor, 1,460 Days and Counting, Start Fixing Year 2000 Problems NOW!, Union Pacific Stays on Track for 2000, Call in the Cavalry before 2000, Tool up for 2000, Keep the Millennium Virus off your Net, Datamation, special supplement, 1996, 1 January.
150. Lucas P., and Walk K. On the formal description of PL/I. IBM (1967) 105-182
151. Lynch J.J. Making Manpower Effective: Part 1 (1968), Pan Books
152. Machiavelli N. The Art of War (1979), Penguin Books
153. F. Manzer, Earned Value (EV) and Automated Information Systems, Software Tech News, DACS - Data and Analysis Center for Software, 1997.
154. Martin J., and McClure C. Software Maintenance: The problem and its solutions (1983), Prentice-Hall
155. Mashiko Y., and Basilli V.R. Using the GQM Paradigm to Investigate Influential Factors for Software Process Improvement. Journal of Systems Software 36 (1997) 17-32
156. D.L. McClure, Executive Guide: Maximizing the Success of Chief Information Officers: Learning from Leading Organizations, Government Accounting Office, GAO-01-376G, 2001, February.
157. A. McLoughlin, D. Pughe, Why your bank will let you down in the Y2K, London and Capital PLC, Oxford Y2K conference, Oxford University, 1998, August.
158. McLuhan M., and Fiore Q. War and Peace in the Global Village (1968), Bantam Books
159. M. McNamee, P. Dwyer, C.H. Schmitt, Accounting Wars, Business Week, 2000, 25 September.
160. M. McNamee, How Levitt Won the Accounting Wars, Commentary; Business Week, 2000, 27 November, pp. 38.
161. MIL-STD-105D, Military Standard: Sampling Procedures and Tables for Inspection by Attributes, US Department of Defense, 29 April 1963.
162. J.C. Mihm, Management Reform: Using the Results Act and Quality Management to Improve Federal Performance, Government Accounting Office; T-GGD-99-151; Oversight of Government Management, Restructuring and the District of Columbia Subcommittee, Senate Committee on Governmental Affairs, 1999, 29 July.
163. J.C. Mihm, Management Reform: Elements of Successful Improvement Initiatives, US GAO, testimony before Subcommittee on Oversight of Government Management, Restructuring and the District of Columbia; Committee on Governmental Affairs, U.S. Senate, 1999, 15 October.
164. J.C. Mihm, Managing For Results: Challenges Agencies Face in Producing Credible Performance Information, US General Accounting Office; GAO/GGD-00-52, 2000, February.
165. J.C. Mihm, Managing For Results: Next Steps to Improve the Federal Government's Management and Performance, US General Accounting Office; GAO/GGD-02-439T, 2002, 15 February.
166. Moitra D. Software Engineering in the Small. Computer 32 10 (1999) October
167. Morisio M., and Torchiano M. Developing Services for the Wireless Internet (2006), Springer
168. Munson J.C. Software Engineering Measurement (2003), Auerbach Publications
169. Murray J.T., and Murray M.J. The Year 2000 Computing Crisis (2000), McGraw-Hill
170. Myers G.J. The Art of Software Testing (1979), A Wiley-Interscience Publication
171. Myers G.J. Reliable Software Through Composite Design (1975), Petrocelli/Charter
172. Naisbitt J. Megatrends: ten new directions transforming our lives (1982), Warner Books
173. G. Napolitana, CFA, The Year 2000: A Computer "Bug" Odyssey, Goldman Sachs, 1997, 18 March.
174. Narayan S. Cashing in on Year-2000 Problems (1997), Institutional Investor November, p. 156
175. Norcross H. Dynamic Business Management (1962), Pan Books
176. G. North, Blind Man's Bluff in the Year 2000, , 1998, 1 July.
177. OCG-99-1, Major Management Challenges and Program Risks: A Government wide Perspective, 1999, 1 January.
178. OMB, Getting Federal Computers Ready for 2000, US Office of Management and Budget, 1997, 6 February.
179. O'Rourke P.J. Eat the Rich: A Treatise on Economics (1998), Atlantic Monthly Press
180. Pandian C.R. Software Metrics: A Guide to Planning Analysis and Application (2004), Auerbach Publications
181. M. Parent, Morgan Stanley Year 2000 Issue Paper, Morgan Stanley, 1997, 17 January.
182. L. feffer, A. Olshansky, Computer Networks and Micro-Computers: The Catalysts for a Social, Ideologican and Economic Renaissance in Israel, State of Israel, Ministry of Finance, Bureau of the Budget, 1979, May.
183. Porter M. Competitive Strategy (1980), Free Press
184. Porter M. Competitive Advantage (1985), Free Press
185. Preiss K., Goldman S.L., and Nagel R.N. Cooperate to Compete (1996), Van Nostrand Reinhold, International Thomson Publishing
186. Preiss K. Modelling of knowledge flows and their impact. Journal of Knowledge Management 3 1 (1999) 36-46
187. Preiss K. A Systems Perspective of Lean and Agile Manufacturing. Agility & Global Competition 1 1 (1997) 59-75 Winter
188. K. Preiss, M. Ray, Time-Based Costing: Part 1 - Costing for a Dynamic Business Environment, The Journal of Corporate Accounting & Finance, John Wiley, Inc., 2000, pp. 65-74, July/August.
189. K. Preiss, M. Ray, Time-Based Costing: Part 2 - Scope and Application, The Journal of Corporate Accounting & Finance, John Wiley, Inc., September/October 2000, pp. 47-56.
190. R.S. Pressman, adapted by Darrel Ince, Software Engineering: A Practitioner's Approach, European Adaptation, fifth ed., McGraw-Hill, 2000.
191. Putnam L.H., and Myers W. Five Core Metrics: The Intelligence Behind Successful Software Management (2003), Dorset House Publishing
192. Rada R., and Craparo J. Standardizing Software Projects. Communications of the ACM 43 12 (2000) 21-25
193. Ragland B. The Year 2000 Problem Solver: A Five-Step Disaster Prevention Plan (2000), McGraw-Hill
194. Raheja D.G. Assurance Technologies: Principles and Practices (1991), McGraw-Hill
195. Reel J.S. Critical Success Factors in Software Projects. IEEE Software (1999) 18-23
196. J. Reingold, The Power of Cosmic Thinking, book review of Management Challenges for the 21st Century, Business Week, 1999, p. 7.
197. Reynolds A. The Year 2000 Bug. Money Magazine (1998) 49-52
198. Royce W. Software Project Management: A Unified Framework (1998), Addision-Wesley
199. Rubinstein M.F., and Pfeiffer K. Concepts in Problem Solving (1980), Prentice-Hall
200. Y. Sagi, D. Tartarski, A Website implementation of the ISO/IEC 12207 International Standard, Ben-Gurion University, Department of Industrial Engineering and Management, final project, 2001, 1 August.
201. Schach S. Classical and Object-Oriented Software Engineering, with UML and Java (1999), McGraw-Hill
202. R.L. Scheier, Sr. Editor, Testing Can't Wait: Year 2000, Computerworld 20 (October) (1997) 82-84.
203. Serich S. Prototype stopping rules in software development projects. IEEE Transactions on Engineering Management 52 4 (2005) 478-485
204. J. Sherriton, J.L. Stern, Corporate Culture Team Culture: removing the hidden barriers to team success, AMACOM, 1997.
205. Silverman B.G. Software Cost and Productivity Improvements: An Analogical View. Computer (1985) 86-96
206. Slayton S.T. Equity Derivative Strategy: Y2K - Time Bomb Ticking (1997), Morgan Stanley
207. Smith D.J., and Wood K.B. Engineering Quality Software (1987), Elsevier Applied Science
208. D. Sparks, Will your bank live to see the millennium? Business Week online, 1998, 21 January.
209. Spencer R.H. Computer Usability Testing & Evaluation (1985), Prentice-Hall
210. L. Nathaus Spiro, Panic in the year zero zero, Business Week (1996) pp. 72-73, 10 August.
211. E.B. Staats, FGMSD-80-38, Wider Use of Better Computer Software Technology can Improve Management Control and Reduce Costs, Report to the Congress by the Comptroller General of the United States, 1980, 29 April.
212. E.B. Staats, FGMSD-80-4, Contracting for Computer Software Development - Serious Problems Require Management Attention to Avoid Wasting Additional Millions, Report to the Congress by the Comptroller General of the United States, 1979, 9 November.
213. Staff reporter, SEC Orders Disclosures of Year 2000 Exposure, The Wall Street Journal, 1997, p. A2, 23 October.
214. M. Stepanek, Y2K is worse than anyone thought: The final reckoning for the bug could hit $1 trillion, Business Week, 1998, 14 December.
215. S. Steinberg, L. Landis, M. Sykes, Y. Jing, D. Smith, Guide to Software Engineering Laboratory Data Collection and Reporting, Software Engineering Laboratory; SEL Series SEL-97-001, 1997, September.
216. P. Strassmann, (Paul Strassmann was formerly the Chief Information Officer of the US DoD and is today considered one of the world's foremost Information Systems consultants, particularly for major systems), The Value of computers, Information and Knowledge, , 1996, 30 January.
217. P. Strassmann, The Economics and Politics of Information Management: an account of an executive seminar, , 1996, 27 June.
218. P. Strassmann, Numbers Add Up To A Bigger Year 2000 Disaster, Computerworld, 1997, 9 June.
219. P. Strassmann, The Value of Knowledge Capital, American Programmer 111(3), , 1998, March.
220. P. Strassmann, Introduction to ROM Analysis: Linking Management Productivity and Information Technology, , 2002, 3 February.
221. Sun-Tzu, The Art of Warfare, translated by Roger Ames, Ballantine Books, 1993.
222. SWEBOK: Guide to the Software Engineering Body of Knowledge, IEEE Computer Society; version 0.95.
223. Taylor A. IT Projects Sink or Swim. British Computer Society Review (2001)
224. Tayntor C.B. Six Sigma Software Development (2003), Auerbach Publications
225. Thacker R.A., and Yost C.A. Training students to become effective workplace team leaders. Team Performance Management 8 3/4 (2002) 89-94
226. The Correspondent, Morgan Stanley Committed to Technology 6(1) (1997) (January-February).
227. Tillquist J., and Rodgers W. Using Asset Specificity and Asset Scope to Measure the values of IT. Communications of the ACM 48 1 (2005) 75-80
228. Tockey S. Return on Software (2005), Addison Wesley
229. Truex D.P., Baskerville R., and Klein H. Growing systems in Emergent Organizations. CACM 42 8 (1999)
230. Verhoef C. Quantitative IT portfolio management. Science of Computer Programming 45 1 (2002) 1-96
231. B. Violino, Getting Down to the Wire, Information Week Online, 1997, February.
232. D.M. Walker, Year 2000 Computing Challenge: Estimated Costs, Planned Uses of Emergency Funding, and Future Implications, United States General Accounting Office; GAO/T-AIMD-99-214, 1999, 22 June.
233. D.M. Walker, Major Management Challenges and Program Risks, General Accounting Office, GAO-01-241, 2001, January.
234. D.M. Walker, Managing for Results: Federal Managers' Views on Key Management Issues Vary Widely Across Agencies, General Accounting Office, GAO-01-592, 2001, May.
235. Webster J., and Watson R.T. Analysing the past to prepare for the future: writing a literature review. MIS Quarterly 26 2 (2002) XIII-XXIII
236. Weiner E., and Brown A. Stakeholder analysis for effective issues management. May Planning Review (1986) 27-32
237. D.M. Weiss, The MUDD Report: A Case Study of Navy software Development Practices, NRL Report 7909, National Technical Information Services; Naval Research Laboratory, 21 May 1975.
238. Wetherill G.B. Sampling Inspection and Quality Control. second ed. (1977), Science Paperbacks, Chapman and Hall
239. S.H. Wildstrom, What about your millennium bug? Business Week, 1998, p. 8, 2 March.
240. J.C. Willemssen, GAO/T-AIMD-99-268, Year 2000 Computing Challenge: Readiness Improving Yet Essential Actions Remain to Ensure Delivery of Critical Services, United States General Accounting Office, 1999, 17 August.
241. Wilson A. War Gaming (1968), Pelican Book
242. T. Wilson, Year 2K: Ready or Not? Internet Week, 1997, p. 79, 6 October.
243. T. Wilson, Corporations still behind in race against millennium bug, Internet Week, 1998, p. 8, 17 August.
244. Wirth N. Systematic Programming: An Introduction (1973), Prentice-Hall
245. J. Wood-Smith, research director, Change is already happening: Impact of Y2K, Greig Middleton & Co., Oxford Y2K conference, Oxford University, 1998, August.
246. D.B. Wortman (Ed.), in: Proceedings of an ACM Conference on Language Design for Reliable Software, ACM SIGPLAN Notices, 12 N3 (also Software Engineering Notes V2 N2), 1977, March.
247. E. Yahalomi, ISPM: Integrated Software Project Management, Ben-Gurion University, Department of Industrial Engineering and Management, M.Sc. Thesis, 2003, January.
248. Y. Shinkyu, E. Brynjolfsson, Intangible Assets and Growth Accounting: Evidence from Computer Investments, preliminary and incomplete report from the web site.
249. E. Yardeni, The Y2K Reporter: #16, Deutsche Morgan Grenfell, 1998, 16 March.
250. Yourdon E. Techniques of Program Structure and Design (1975), Yourdon Prentice-Hall
251. Yourdon E. Managing the System Life Cycle (1982), Yourdon Press
252. Ziff P. Semantic Analysis (1960), Cornell Paperbacks