Trustworthy Systems Through Quantitative Software Engineering

Trustworthy Systems Through Quantitative Software Engineering

Volumn , Issue , 2005, Pages 1-437

  Bernstein, Lawrence ^a   Yuhas, C M ^b  

^a STEVENS INSTITUTE OF TECHNOLOGY   (United States)

^b NONE

Author keywords

[No Author keywords available]

Indexed keywords

EID: 84889471854     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.1002/0471750336     Document Type: Book

References (208)

1. Bernstein, Larry. "Software in the Large," AT&T Technical Journal, Vol. 75, No. 1, Jan./Feb. 1996, pp. 5-14.
2. Binder, Robert V. Testing Object-Oriented Systems-Models, Patterns, Tools, Addison-Wesley, Reading, MA, March 2003.
3. Boehm, Barry W., et al. Software Cost Estimation with COCOMO II, Prentice Hall, Englewood Cliffs, NJ, 2000.
4. Crowley, Thomas. "Safeguard Data-Processing Subsystem," The Bell System Technical Journal, Special Supplement, 1975.
5. Carnegie Mellon University Software Engineering Institute. The Capability Maturity Model: Guidelines for Improving the Software Process, Addison-Wesley, Reading, MA, 1995.
6. Fowler, Martin. Refactoring Improving the Design of Existing Code, Addison-Wesley, Reading, MA, 2000.
7. Hatton, Les. Safer C-Developing Software for High-Integrity and Safety-Critical Systems, McGraw-Hill, New York, 1997.
8. Hoffman, Daniel M. and Weiss, David M. Software Fundamentals Collected Papers by David L. Parnas, Addison-Wesley, Reading, MA, 2002.
9. Jones, T. Capers. Estimating Software Costs, McGraw-Hill, New York, 1998.
10. Leavitt, Harold J. and Bahrami, Homa. Managerial Psychology: Managing Behavior in Organizations, 5th ed. University of Chicago Press, Chicago, IL, 1988.
11. Martin, Robert C. Agile Software Development, Prentice Hall, Englewood Cliffs, NJ, 2003.
12. Maxwell, Katrina D. Applied Statistics for Software Mangers, Prentice Hall, Englewood Cliffs, NJ, 2002.
13. McConnell, Steve. Software Project-Survival Guide, Microsoft Press, Redmond, WA, 1998.
14. Peters, James F. and Pedrycz, Witold. Software Engineering-An Engineering Approach, John Wiley and Sons, New York, 2000.
15. Pressman, Roger S. Software Engineering: A Practioner's Approach, McGraw-Hill, New York, 2002.
16. Van Vliet, Hans. Software Engineering-Principles and Practices, 2nd ed. John Wiley and Sons, New York, 2000.
17. Voas, Jeffrey and McGraw, Gary. Software Fault Injection: Inoculating Programs Against Errors, John Wiley and Sons, New York, 1998.
18. Wallnau, Kurt, et al., Building Systems from Commercial Components, Addison-Wesley, Reading, MA, 2001.
19. Barton, John J. and Nackman, Lee. Scientific and Engineering C++, Addison-Wesley, Reading, MA, 1995.
20. Bernstein, Lawrence and Yuhas, C. M. "And the Walls Come Tumblin' Down," IEEE Communications Magazine, Dec. 1992.
21. Boehm, Barry. Software Engineering Economics, Prentice Hall, Englewood Cliffs, NJ, 1981, Sections 26.3 and 33.6.
22. Booch, Grady. Object Oriented Analysis and Design with Applications, Benjamin Cummings, Redwood City, CA, 1994.
23. Coplien, James O. Advanced C++ Programming Styles and Idioms, Addison-Wesley, Reading, MA, 1992.
24. DeMarco, Tom and Lister, Timothy. Peopleware: Productive Projects and Teams, 2nd ed. Dorset House Publishing Co., New York, 1999.
25. Frey, Anthony. "Into ORBit, Object Request Brokers: Servers of the 21st Century," Network Computing, Vol. 8, No. 4, March 1, 1997, pp. 51-60.
26. Gamma, Erich, Helm, Richard, Johnson, Ralph, and Vlissides, John. Design Patterns: Elements of Reusable Object Oriented Software, Addison-Wesley, Reading, MA,1995.
27. Gaudin, Sharon. "Object Stamp of Approval," ComputerWorld, Vol. 31, No. 11, March 17, 1997, p. 1.
28. Goldberg, Adele and Rubin, Kenneth S. Succeeding with Objects: Decision Frameworks for Project Management, Addison-Wesley, Reading, MA, 1995.
29. Graham, Ian. "Making Progress in Metrics, Task-Point Analysis Can Be Performed at the Requirements Stage," Object Magazine, Vol. 6, No. 8, October 1996, pp. 68-73.
30. Highsmith, James A. III. Adaptive Software Development, Dorset House Publishing, New York, NY, 2000.
31. Korson, Tim and McGregor, John D. "Understanding Object Oriented: a Unifying Paradigm," Communications of the ACM, Sept. 1990, pp. 41-60.
32. Landauer, Thomas, K. The Trouble with Computers: Usefulness, Usability, and Productivity, MIT Press, Cambridge, MA, 1996, pp. 13-35.
33. Levy, Leon. Taming the Tiger-Software Engineering and Software Economics, Springer-Verlag, New York, 1987, ch. 4.
34. Mancl, Dennis and Havanas, William."A Study of the Impact of C++ on Software Maintenance," Proceedings IEEE Conference on Software Maintenance, Nov. 1990, pp. 63-69.
35. McGregor, John D. and Sykes, David A. Object Oriented Software Development: Engineering Software for Reuse, Van Nostrand Reinhold, New York, 1992.
36. Meyers, Scott. Effective C++: 50 Specific Ways to Improve Your Programs and Designs, Addison-Wesley, Reading, MA, 1992.
37. Murray, Robert B. C++ Strategies and Tactics, Addison-Wesley, Reading MA, 1993.
38. O'Donnell, Debra. "Hello MOM and OOP Shops," Software Magazine, April 1997, p. 25.
39. Shneiderman, Ben. Software Psychology-Human Factors in Computer and Information Systems, Winthrop Publications, London, U.K., 1980, Sections 1.3.5 and 3.5.
40. Software Engineering Institute, Carnegie Mellon University. The Capability Maturity Model: Guidelines for Improving the Software Process, Addison-Wesley SEI Series in Software Engineering, Reading, MA, 1995. See www.sei.cmu.edu/cmmi/general for updates on CMMI.
41. Taylor, David. Object Oriented Technology: a Manager's Guide, Addison-Wesley, Reading, MA, 1990.
42. Van Vliet, Hans. Software Engineering-Principles and Practices, 2nd ed., John Wiley and Sons, 2000.
43. Vaughan-Nichols, S. "Corporate Success Stories: Integrating Objects With Rules," Object Magazine, Vol. 7, No. 1, March 1997, p. 66.
44. Weinberg, Gerald. The Psychology of Computer Programming, Van Nostrand Reinhold Company, New York, 1971, pp. 135-136.
45. Wilkinson, Nancy M. Using CRC Cards, SIGS Books, New York, 1995.
46. Wirfs-Brock, Rebecca J., Wilkerson, Brian, and Wiener, Lauren. Designing Object Oriented Software, Prentice-Hall, Englewood Cliffs, NJ, 1990.
47. "Best Current Practices: Software Architecture Validation," AT&T, Murray Hill, N.J., 1993.
48. "Function Points as Asset Reporting to Management," IFPUG Conference Proceedings, 1990.
49. "Process Engineering with the Evolutionary Spiral Process Model: Version 01.00.06,"
50. Tech. Report SPC-93098-CMC, Software Productivity Consortium, Herndon, VA, 1994.
51. Bachman/Function Point Analyst, Product Announcement, Bachman, Inc., 1994.
52. Bernstein, Lawrence. "Where to Invest Your Software Bucks," IEEE, Piscataway, NJ Feb. 1995.
53. Boehm, B. and Bose, P. "A Collaborative Spiral Software Process Model Based on Theory W," Proceedings of the International Conference of Software Process, IEEE CS Press, Los Alamitos, CA, 1994, pp. 59-68.
54. Boehm, Barry et al. "Software Requirements as Negotiated Win Conditions," Proceedings of the International Conference on Requirements Engineering, IEEE CS Press, Los Alamitos, CA, 1994, pp. 74-83.
55. Boehm, Barry, et al. "Prototyping Versus Specifying: A Multiproject Experiment," IEEE Transactions on Software Engineering, May 1984.
56. Boehm, Barry."Software Risk Management, Principles, and Practices," IEEE Software, Jan. 1991.
57. Boehm, Barry. "A Spiral Model of Software Development and Enhancement," Computer, May1988, pp. 61-72.
58. Boehm, Barry. Software Engineering, IEEE CS Press, Los Alamitos, CA, 1990.
59. Boehm, Barry. "Anchoring the Software Process," IEEE Software, July 1996, pp. 73-82.
60. Carleton, Anita D., Park, Robert E., and Goethert, Wolfhart B. "The SEI Core Measures: Background Information and Recommendations for Use and Implementation," CrossTalk, May 1994.
61. Fisher, R. and Ury W. Getting to Yes, Penguin Books, New York, 1981.
62. Flowers, Stephen. "Software Failure: Management Failure," Report of the Inquiry into the London Ambulance Service, Feb. 1993.
63. Frazier, T. and Bailey, J. "The Costs and Benefits of Domain-Oriented Software Reuse: Evidence from the STARS Demonstration Projects," IDA Paper P-3191, Institute for Defense Analyses, Alexandria, VA, 1996.
64. Jones, T. Capers. Applied Software Measurement, McGraw-Hill, New York, 1991.
65. Lusher, Paul W. "Function Point Analysis for Real-Time Weapons Control," IFPUG Conference Proceedings, Sept. 1992.
66. Neumann, Peter G. Computer-Related Risks, ACM Press, New York, 1995.
67. Neumann, Peter G. "Inside Risks," ACM SIGSOFT Software Engineering Notes, Vol. 16.3, 1991, pp. 19-20.
68. Neumann, Peter G. "Inside Risks," ACM SIGSOFT Software Engineering Notes, Vol. 16.4, 1991, pp. 17-18.
69. Neumann, Peter G. "Inside Risks," ACM SIGSOFT Software Engineering Notes, Vol. 17.2, 1992, pp. 4-5.
70. Neumann, Peter G. "Inside Risks," ACM SIGSOFT Software Engineering Notes, Vol. 18.1, 1993, p. 25.
71. Royce, W. E. "TRW's Ada Process Model for Incremental Development of Large Software Systems," Proceedings of the 12th International Conference of Software, 1990, pp. 2-11.
72. Samadani, Hamid, et al."Army Reuse Center Tackles CASE-Based Reuse," CrossTalk, May 1994, Vol. 5, p. 10.
73. Shneiderman, Ben and Plaisant, Catherine. Designing the User Interface, 4th ed. Pearson Addison Wesley, Reading, MA, 2005.
74. Simpson, Moira. "999!: My computer's stopped breathing!", The Computer Law and Security Report, March-April 1994, pp. 76-81. The National Software Council Charter, April 1995.
75. Andrews, D.C."JAD:A crucial dimension for rapid applications development," Journal of Systems Management, March 1991, pp. 23-31.
76. Appel, J. J. and Bernstein, L. "Requirements or Prototyping? Yes!," Proceedings of the Sixth International Conference on Software Engineering for Telecommunications Switching Systems, Eindhoven, The Netherlands, April 14-18, 1986, pp. 170-175.
77. Bernstein, L. and Yuhas, C.M."Software Engineering in Telecommunications Systems,"Encyclopedia of Software Engineering Volume 2, 2nd ed., John Marciniak, Editorin-Chief, Wiley-InterScience, New York, 2002, pp. 1497-1507.
78. Bernstein, L."Foreword: Importance of Software Prototyping," Journal of Systems Integration, Vol. 6, No. 1/2, March 1996, pp. 9-14.
79. Boehm, B.W. "Spiral Model of Software Development and Enhancement," Computer, Vol. 2, No. 5, May 1988, pp. 61-72.
80. Boehm, B.W. Software Risk Management, IEEE CS Press, Los Alamitos, CA, 1989.
81. Boehm, Barry W. and Sullivan, Kevin J. "Software Economics," University of Southern California and University of Virginia, Dec. 1999, boehm@cs.usc.edu.
82. Boehm, Barry. Software Engineering Economics, Prentice-Hall, Englewood Cliffs, NJ, 1981.
83. Connell, John L. and Shafer, Linda Brice. Structured Rapid Prototyping, Yourdon Press, Prentice-Hall, Englewood Cliffs, NJ, 1989.
84. Drusinsky, D. and Shing, M. "Verification of Timing Properties in Rapid System Prototyping," Proceedings of Rapid System Prototyping Conference, 2003.
85. Drusinsky, D., Michael, J. B., and Shing, M. "Behavioral Modeling and Run-Time Verification of System-of-Systems Architectural Requirements," International Conference on Computing, Communications and Control Technologies, 2004.
86. Luqi and M. Shing. "Real-Time Scheduling for Software Prototyping," Journal of Systems Integration, Special Issue on Computer Aided Prototyping, 1996, pp. 44-72.
87. Luqi, Berzins, V., Shing, M., and Nada, N. "Evolutionary Computer-Aided Prototyping System (CAPS)," Proceedings of the TOOLS USA 2000 Conference, Santa Barbara, CA, July 30-Aug. 3, 2000.
88. Luqi, Yeh, R. "Rapid Prototyping in Software Evolution," Encyclopedia of Software Engineering, John Wiley and Sons, New York, 1994, pp. 1-21.
89. Luqi. "Computer-Aided Software Prototyping," IEEE Computer, Sept. 1991, pp. 111-112.
90. Rapid Application Development, Center for Software Engineering at the University of Southern California, workshop report.
91. "Krutchen 4+1 Systems," Proceedings of the TRI-Ada '94 Conference ACM, Baltimore, MD, November 6-11, 1994.
92. "Software Architecture Documentation in Practice:Documenting Architectural Layers," The Software Engineering Institute (SEI) Carnegie Mellon University, 2004, http://www.sei.cmu.edu/publications/documents/00.reports/sr004/00sr004chap02.html.
93. Aho, Alfred V., Kernighan, Brian W., and Weinberger, Peter J. "Awk-A Pattern Scanning and Processing Language," Software-Practice and Experience, Vol. IX, No. 4, April 1979, pp. 267-279.
94. Arnold, B. R. T., van Deursen, A., and Res, M. "An Algebraic Specification of a Language for Describing Financial Products," M.Wirsing (Ed.), Proceedings of the ICSE-17 Workshop on Formal Methods Applications, Software Engineering Practice, Seattle, WA, April 1995, pp. 6-13.
95. Astley, Mark, Sturman, Daniel C., and Agha, Gul A. "Customizable Middleware for Modular Distributed Software," Communications of the ACM, Vol. 44, No. 5, May 2001, pp. 99-107.
96. Bass, Len, Clements, Paul, and Kazman, Rick. Software Architecture in Practice, Addison-Wesley, Reading, MA, 1998.
97. Bernstein, Lawrence. "Software Fault Tolerance Forestalls Crashes: To Err is Human; To Forgive Is Fault Tolerant," Advances in Computers, Elsevier Science, New York, 2003, pp. 239-285.
98. Buschmann, Frank, et al. A System of Patterns, John Wiley and Sons, New York, 1996.
99. Cameron, John. JSP & JSD: The Jackson Approach To Software Development, 2nd ed. IEEE Computer Society, New York, 1989, Section 5.
100. Donahoo, Michael and Calvert, Kenneth. The Pocket Guide to TCP/IP Sockets C Version, Morgan Kaufman, New York, 2001.
101. Gacek, Christina, Abd-allah, Ahmed, Clark, Bradford, and Boehm, Barry. "On the Definition of Software System Architecture," ICSE 17 Software Architecture Workshop, April 1995, Center for Software Engineering, University of Southern California, Los Angeles, CA.
102. Garlan, D. and Shaw, M."An Introduction to Software Architecture," Advances in Software Engineering and Knowledge Engineering, Vol. 1, World Scientific Publishing, Singapore, 1993.
103. Hall, Jane (Ed). Management of Telecommunication Systems and Services, Springer, New York, 1991.
104. Hatton, Les. Safer C: Developing Software for High-integrity and Safety-critical Systems, McGraw-Hill International, London, 1997.
105. IEEE Software, Vol. 12, No. 6, Nov. 1995. Entire issue devoted to architectural questions and developments.
106. IEEE Software, Vol. 22, No. 4, July/August 2005. Entire issue devoted to COTS Integration.
107. Jackson, M. A. Principles of Program Design, Academic Press, New York, 1975.
108. Kruchten, Philippe B. "The 4+1 View Model of Architecture," IEEE Software, Vol. 12, No. 6, Nov. 1995, pp. 42-50.
109. Landauer, Thomas K. The Trouble with Computers, MIT Press, Cambridge, MA, 1996, p. 70.
110. Leavens, Gary T. and Sitaraman Murali. Foundations of Component-Based Systems, Cambridge University Press, Cambridge, U.K., 2000.
111. Lenzi, Marie. "Conduit and Content," Object Magazine, Oct. 1996, pp. 4-6.
112. Linger, R. C., Mills, H. D. and Witt, B. I. Structured Programming: Theory and Practice, Addison-Wesley, Reading, MA, 1979, ch. 4.
113. Morris, Charles R. and Ferguson, Charles H. "How Architecture Wins Technology Wars," Harvard Business Review, March-April 1993, pp. 86-94.
114. Parnas, David."Concurrency and Scheduling," Software Fundamentals Collected Papers by David L Parnas, edited by Daniel M. Hoffman and David M.Weiss, Addison-Wesley, London, 2001.
115. Schmidt, D. C. and Cleeland, C. "Applying Patterns to Develop Extensible ORB Middleware," IEEE Communications Magazine, IEEE CS Press, Los Alamitos, CA, Vol. 37, No. 4, 1999, pp. 54-63.
116. Sha, Lui. "Using Simplicity to Control Complexity," IEEE Software, Volume 18, No. 4, July/Aug. 2001, p. 27.
117. Shaw, Mary and Garlan, David. Software Architecture: Perspectives on an Emerging Discipline, Simon & Schuster, New York, 1996.
118. Siewiorek, D. P., Chillarege, R., and Plank J. K. "Reflections on Industry Trends and Experimental Research in Dependability," IEEE Transaction on Dependable and Secure Computing, IEEE Computer Society, Vol. 1, No. 2, April-June 2004, p. 120. software@computer.org.
119. Wallnau, Kurt, et al. Building Systems from Commercial Components, Addison-Wesley, Reading, MA, 2002.
120. Witt, B. I., Baker, F.T., and Merritt, E.W. Software Architecture and Design-Principles, Models, and Methods, Van Nostrand Reinhold, New York, 1994.
121. Albrecht, Allan J. "Software Function, Source Lines of Code, and Development Effort Prediction: A Software Science Validation," IEEE Transactions on Software Engineering, Vol. SE-9, No. 6, Nov. 1983, pp. 639-647.
122. Arthur, Lowell Jay. Programmer Productivity: Myths, Methods, and Murphology A Guide for Managers, Analysts, and Programmers, John Wiley and Sons, 1983, pp. 25-27.
123. Bachman/Function Point Analyst, Product Announcement, Bachman, Inc., 1994.
124. Bernstein, Lawrence and Lubashevsky, Alex. "Living with Function Points" AT&T.
125. Bernstein, Lawrence and Yuhas, C. M. "Software Investment Strategy," Engineering Management Journal, Vol. 7 No. 4, Dec. 1995, pp. 15-21.
126. Boehm, Barry et al. "Prototyping Versus Specifying: A Multiproject Experiment," IEEE Transactions on Software Engineering, May 1984.
127. Boehm, Barry W., Gray, T. E., and Seewaldt, T. "Prototyping Versus Specifying: A Multiproject Experiment," IEEE Transactions on Software Engineering, Vol. SE-10, No. 3, May 1984.
128. Boehm, Barry."Software Risk Management, Principles, and Practices," IEEE Software, Jan. 1991.
129. Carleton, Anita D., Park Robert E., and Goethert, Wolfhart B. "The SEI Core Measures: Background Information and Recommendations for Use and Implementation," CrossTalk, May 1994.
130. Desmond, John. "IBM's Workgroup Hides Repository," Application Development Trends, April 1994, p. 25.
131. Dijkstra, E. "The Humble Programmer," 1972 ACM Turing Award Lecture in Classics in Software Engineering, 1979.
132. Fairley, Richard. "Risk Management for Software Projects," IEEE Software, May 1994, pp. 57-67.
133. "Function Points as Asset Reporting to Management," IFPUG, 1990.
134. Garmus, Dave. "Function Point Counting," Software Development, Sept. 1993, pp. 67-69.
135. Humphrey, Watts. A Discipline for Software Engineering, Addison-Wesley, Reading, MA, 1995.
136. Humphrey, Watts. Managing the Software Process, Addison-Wesley, Reading, MA,1989. International Function Point Users Group.
137. Jones, T. Capers. "What are Function Points?" Software Productivity Research.
138. Jones, T. Capers. Applied Software Measurement, McGraw-Hill, New York, 1991.
139. Jones, T. Capers. Programming Productivity, McGraw-Hill Book, New York, 1986, pp. 83-210.
140. Kemerer, Chris F. "Reliability of Function Points Measurement," Communications of the ACM, Feb. 1993, pp. 85-97.
141. Lusher, Paul W. "Function Point Analysis for Real-Time Weapons Control," IFPUG Conference Proceedings, Sept. 1992.
142. Mills, Harlan. Software Productivity, Dorset House Publishing, New York, 1988, pp. 13-18.
143. Poulin, J. S., Caruso, J. M., and Hancock, D. R."The Business Case for Software Reuse," IBM Systems Journal, Vol. 32, No. 4, 1993, pp. 567-594.
144. Pressman, Roger. "Hackers in a Decade of Limits," American Programmer, Jan. 1994, pp. 7-8.
145. Samadani, Hamid, et al."Army Reuse Center Tackles CASE-Based Reuse," Cross Talk, May 1994.
146. Selby, R. "Empirically Analyzing Software Reuse in a Production Environment," in Software Reuse: Emerging Technology, W. Tracz (Ed.), IEEE Computer Society Press, New York, 1988, pp. 176-189.
147. Addison, Tom and Vallabh, Seema. "Controlling Software Project Risks-an Empirical Study of Methods used by Experienced Project Managers," Proceedings of SAICSIT, 2002.
148. Department of the Air Force, Software Technology Support Center. "Guidelines for Successful Acquisition and Management of Software Intensive Systems: Weapon Systems, Command and Control Systems," Management Information Systems, Vol. 1, Version 1.1, Department of the Air Force, Software Technology Support Center, Salt Lake City, UT, 1995.
149. Asaravala, Amit. "Managing at Microsoft," SD PEOPLE & PROJECTS, Jan. 2005.
150. Bernstein, L. "Software Project Management Audits," Journal of Systems and Software, Vol. 2, 1981, pp. 281-287.
151. Boehm, Barry. Software Engineering Economics, Prentice-Hall, Englewood Cliffs, NJ, 1981, Chs. 19 and 20.
152. Boehm, Barry. "A Spiral Model of Software Development and Enhancement," IEEE Computer, May 1988, pp. 61-72.
153. Boehm, Barry. Software Risk Management, IEEE Computer Society Press, New York, 1989.
154. Boehm, B. and Ross, R. "Theory-W Software Project Management Principles and Examples," IEEE Transactions on Software Engineering, Vol. 15, 1989, pp. 902-916.
155. Boehm, Barry W. "Software Risk Management: Principles and Practices." IEEE Software, Vol. 8, Jan. 1991, pp. 32-41.
156. Boehm, Barry, et al. Software Cost Estimation with COCOMO II, Prentice-Hall, Englewood Cliffs, NJ, 2000, p. 403.
157. Buckle, J. K. Managing Software Projects, American Elsevier, New York, 1977.
158. Endres, Albert and Rombach, Dieter. A Handbook of Software and Systems Engineering-Empirical Observations, Laws and Theorems, Pearson Addison Wesley, Reading, MA, 2003, p. 201.
159. Keil, M., et al. "A Framework for Identifying Software Project Risks, Communications of the ACM, Vol. 41, 1998, pp. 77-83.
160. McDonald, James. "Software project management audits-update and experience report," The Journal of Systems and Software, Vol. 64, 2002, pp. 247-255.
161. Putnam, Lawrence H. and Myers, Ware. Industrial Strength Software: Effective Management Using Measurement, IEEE Computer Society Press, New York, 1997, Ch. 18 for discussion of SLIM and Rayleigh curve.
162. Yourdon, Edward Nash. Death March: The Complete Software Developer's Guide to Surviving 'Mission Impossible' Projects, Prentice-Hall, Englewood, Cliffs, NJ, 1997.
163. Arthur, Lowell Jay. Programmer Productivity: Myths, Methods, and Murphology A Guide for Managers, Analysts, and Programmers, John Wiley and Sons, New York, 1983, pp. 25-27.
164. Bailey, Robert. Human Performance Engineering A Guide for System Designers, Prentice-Hall, Englewood Cliffs, NJ 1982.
165. Bernstein, L. "Software Project Management Audits," The Journal of Systems and Software, Vol. 2, No. 4, Dec. 1981, pp. 281-287.
166. Bernstein, L. and Yuhas, C. M. Basic Understanding of Telecommunications Networks: Copper to Sand to Glass to Air, Kluwer Academic Publishing, New York, 2000.
167. Bernstein, Lawrence and Yuhas, C. M. "Software Investment Strategy," Engineering Management Journal, Vol. 7, No. 4, Dec. 1995, pp. 15-21.
168. Boehm, Barry W. "Software Engineering," Classics in Software Engineering, Yourdin Press, New York, 1979, p. 325.
169. Boehm, Barry W., Gray, T. E., and Seewaldt, T. "Prototyping Versus Specifying: A Multiproject Experiment," IEEE Transactions on Software Engineering, Vol. SE-10, No. 3, May 1984.
170. Basili, Victor R. and Salwa, K. Abd-El-Hafiz. A Knowledge-Based Approach to Program Understanding, Kluwer Academic Publishers, New York, July 1995.
171. Bentley, Jon. Programming Pearls, 2nd ed. Addison-Wesley, Reading, MA, 1999.
172. Bernstein, L. "Get the Design Right!" IEEE Software, Sept. 1993, pp. 61-63.
173. Bernstein, L. "Software Fault Tolerance Forestalls Crashes:To Err is Human;To Forgive Is Fault Tolerant," Advances in Computers, Elsevier Science, 2003, pp. 239-285.
174. Blaha, Michael and Rumbaugh, James. Object-Oriented Modeling and Design with UMLTM, 2nd ed. Pearson Prentice-Hall, Englewood Cliffs, NJ, 2005.
175. Boehm, Barry. Software Engineering Economics, Prentice-Hall, Englewood Cliffs, NJ, 1981.
176. Brooks, Frederick. "No Silver Bullet-Essence and Accidents of Software Engineering," IEEE Computer, Vol. 20, No. 4, pp. 10-19, 1989.
177. CrossTalk Open Source Software-Sharing From a Well of Ideas, 4, Vol. 18, No. 1, Jan. 2005.
178. Hatton, Les. Safer C: Developing Software for High-Integrity and Safety-Critical Systems, The McGraw-Hill International Series in Software Engineering, New York, 1997.
179. IEEE Software Developing with Open Source Software, www.computer.org/software, Jan./Feb. 2004, pp. 34-40.
180. Kernighan Brian W. and Plauger P. J. The Elements of Programming Style, McGraw-Hill, New York, 1974.
181. Koenig, Andrew. C Traps and Pitfalls, Addison-Wesley, Reading, MA, 1989.
182. Kruchten, Philippe. The Rational Unifies Process-An Introduction, 2nd ed. Addison-Wesley, Reading, MA, 2000.
183. Leveson, Nancy G. Safeware System Safety and Computers, Addison-Wesley, Reading, MA, 1995.
184. Lewis, Ted G. and Oman, Paul W. Milestones in Software Evolution, IEEE Computer Society Press, Los Alamitos, CA, 1990.
185. Linger, R. C., Mills, H.D., and Witt, B. I. Structured Programming: Theory and Practice, Addison-Wesley, Reading, MA, 1979.
186. Martin, Robert C. Agile Software Development Principles, Patterns, and Practices, Prentice-Hall, Englewood Cliffs, NJ, 2003.
187. Sha, Lui. "Using Simplicity to Control complexity," IEEE Software, Vol. 18, No. 4, July/Aug. 2001.
188. "Open Source Software: Sharing From a Well of Ideas," CrossTalk, 2005 Vol. 18, No. 1. Entire issue is devoted to aspects of Open Source.
189. Bernstein, Lawrence and Yuhas, C. M. "Software Manufacturing" UNIX Review, Vol. 7, No. 7, July 1989, pp. 38-45.
190. Binder, Robert V. Testing Object-Oriented Systems: Models, Patterns, and Tools, Addison-Wesly, Reading, MA, 2000.
191. Culbertson, Robert, et al. Rapid Testing, Software Quality Institute Series, Prentice-Hall, Englewood Cliffs, NJ, 2002.
192. Currit, P. A., Dyer, M., and Mills, "Certifying the reliability of software," IEEE Transactions on Software Engineering, Vol. SE-12, No. 1, Jan. 1986, pp. 3-11.
193. Gacek, Cristina and Arief, Budi. "The Many Meanings of Open Source," IEEE Software, Jan./Feb. 2004, pp. 34-48.
194. Humphrey, W. S., Snyder, T. R., and Willis, R. R. "Software Process Improvement at Hughes Aircraft," IEEE Software, July 1991, pp. 11-23.
195. Kulak, Daryl and Guiney, Eamonn. Use Cases-Requirements in Context, 2nd ed. Addison-Wesley, Reading, MA, 2004.
196. Kusumoto, S., Matsumoto, K., Kikuno, T., and Torii, K."Approaches to Improving Effectiveness of Review Activities in Technical Review Process," International Software Quality Exchange'92 Conference Proceedings, Juran Institute Inc., 1992, pp. 7B1-7B16.
197. Lam, John."Painless SCM," Software Development, Vol. 12, No. 12, Dec. 2004, pp. 23-26.
198. Leon-Garcia, Alberto and Widjaja, Indra. Communications Networks-Fundamental Concepts and Key Architectures, 2nd ed., McGraw Hill, New York, 2004, Sections 5.2 and 5.4.
199. Levendel, Y. "Improving Quality With a Manufacturing Process," IEEE Software, March 1991, pp. 13-25.
200. McFarlane, M. L. and Sutton, A. Structured, Automatic Testing: A Hard Slog, Cadence Design Systems, Santa Clara, CA, Dec. 22, 1989.
201. Perry, William. Effective Methods for Software Testing, 2nd ed. John Wiley and Sons, New York, 2000.
202. Phadke, M. S. Quality Engineering Using Robust Design, Prentice-Hall, Englewood Cliffs, NJ, 1989, pp. 5-6.
203. Phadke, Madhav S. "Planning Efficient Software Tests," CrossTalk, Oct. 1997.
204. Proceedings of the 2nd International Workshop on Software Configuration Management, ACM SIGSOFT, Vol. 17, No. 7, Nov. 1989, ACM Order NO. 594891, IEEE Order No. 2014.
205. Sherer, S. A. "A Cost Effective Approach to Testing," IEEE Software, March 1991, pp. 34-40.
206. Staknis, M. E. "Software Quality Assurance Through Prototyping and Automated Testing," Information and Software Technology, Vol. 32, No. 1, Jan./Feb. 1990, pp. 26-33.
207. Whittaker, James A. How to Break Software: A Practical Guide to Testing, Addison-Wesley, Reading, MA, 2003.
208. Yoshida, T. "Attaining Higher Quality in Software Development-Evaluation in Practice," Fujitsu Science Technical Journal, Vol. 21, July 1985, pp. 305-316.