What every engineer should know about software engineering

What Every Engineer Should Know about Software Engineering

Volumn , Issue , 2007, Pages 1-312

  Laplante, Phillip A ^a  

^a NONE

Author keywords

[No Author keywords available]

Indexed keywords

APPLICATION PROGRAMS; ENGINEERS;

DEVELOPMENT APPROACH; MULTIPLE APPLICATIONS; QUALITY SOFTWARE; REPETITIVE TASK;

PROFESSIONAL ASPECTS;

EID: 40349103125     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.1201/9781420006742     Document Type: Book

References (137)

1. Certified Software Development Professional Program (CDSP), IEEE Computer Society, http://www.computer.org/portal/site/ieeecs/menuitem. c5efb9b8ade90 96b8a9ca0108bcd45f3/index.jsp?&pName=ieeecs_ level1&path= ieeecs/educa-tion/certification&file=index.xml&xsl=generic.xsl&, accessed September 14, 2006.
2. Institute of Industrial Engineers (IIE), State board pays Novell in “engineer” title suit. IIE Solutions, 32(1), 10, 2000.
3. Demming, P., Great principles of computing, Commun. ACM, 46(11), 15–20, 2003.
4. Laplante, P.A. (Editor-in-Chief), Comprehensive Dictionary of Computer Science, Engineering and Technology, CRC Press, Boca Raton, FL, 2001.
5. Laplante, P.A., Professional licensing and the social transformation of software engineers, Technol. Soc. Mag., IEEE, 24(2), 40-45, 2005.
6. Marciniak, J. (Ed.), Encyclopedia of Software Engineering, Vol. 2, John Wiley & Sons, New York, 1994, 528–532.
7. Statute, Texas Board of Professional Engineers, http://www.tbpe.state.tx.us/, accessed August 11, 2006.
8. Bourque, P., Dupuis, R., Abran, A., Moore, J.W., and Tripp, L.L., The Guide to the Software Engineering Body of Knowledge,” IEEE Software, 16, 35–44, 1999.
9. Thayer, R.H., Software system engineering: a tutorial, Computer, 35(4), 68–73, 2002.
10. Tripp, L.L., Benefits of certification, Computer, 35(6), 31–33, 2002.
11. Ambler, S., “Are you Agile or Fragile?” presentation, http://www.whysmalltalk.com/Smalltalk_Solutions/ss2003/pdf/ambler.pdf last accessedApril 10, 2006.
12. Beck, K., Embracing change with extreme programming, Computer, 32(10), 70–77, 1999.
13. Boehm, B.W., A spiral model of software development and enhancement, Computer, 21(5), 61–72, 1988.
14. Boehm, B.W. and Turner, R., Balancing Agility and Discipline: A Guide to the Perplexed, Addison-Wesley, Boston, MA, 2004.
15. Brooks, F.P., The Mythical Man-Month, 20th Anniversary Edition, Addison-Wesley, Boston, MA, 1995.
16. Institute of Electrical and Electronic Engineers (IEEE), IEEE 1473-1999, IEEE Standard for Communications Protocol Aboard Trains, 1999.
17. Laplante, P.A., Software Engineering for Image Processing Systems, CRC Press, Boca Raton, FL, 2004.
18. Martin, R.C., Agile Software Development: Principles, Patterns, and Practices, Prentice-Hall, Englewood Cliffs, NJ, 2002.
19. Neill, C.J. and Laplante, P.A., Requirements engineering: the state of the practice, Software, 20(6), 40–46, 2003.
20. Nerur, S., Mahapatra, R., and Mangalaraj, G., Challenges of migrating to agile methodologies, Commun. ACM, 48(5), 73–78, 2005.
21. Nord, R.L. and Tomayko, J.E., Software architecture-centric methods and agile development, Software, 23(2), 47–53, 2006.
22. Parnas, D.L. and Clements, P. C., A rational design process: how and why to fake it, IEEE Trans. Software Eng., 12(2), 251–257, 1986.
23. Reifer, D., How good are agile methods, Software, 19(4), 16–18, 2002.
24. Royce, W., Software Project Management: A Unified Framework, Addison-Wesley, Boston, MA, 1998.
25. Theuerkorn, F., Lightweight Enterprise Architectures, Auerbach Publications, Boca Raton, FL, 2005.
26. Tucker, A.B., Jr. (Editor-in-Chief), The Computer Science and Engineering Handbook, CRC Press, Boca Raton, FL, 1996.
27. Wang, Y.W., and King, G., Software Engineering Processes: Principles and Applications, CRC Press, Boca Raton, FL, 2000.
28. “The Rules and Practices of Extreme Programming,” www.extremeprogramming. org/rules.html, accessed September 14, 2006.
29. Akao, Y. (Ed.). Quality Function Deployment, Productivity Press, Cambridge, MA, 1990.
30. Beyer, H. and Holtzblatt, K., Apprenticing with the customer: a collaborative approach to requirements definition, Commun. ACM, 38(5), 45–52, 1995.
31. Coad, P. and E. Yourdon, Object-Oriented Analysis, 2nd ed., Yourdon Press, Upper Saddle River, NJ, 1990.
32. Davis, A., Software Requirements: Objects, Functions and States, 2nd ed., Prentice-Hall, Upper Saddle River, NJ, 1993.
33. Davis, A.M., The art of requirements triage, IEEE Computer, 36(3), 42–49, 2003.
34. Haag, S., Raja, M.K., and Schkade, L.L., Quality function deployment usage in software development, Commun. ACM, 39(1), 41–49, 1996.
35. Karlsson, J., Managing software requirements using quality function deployment, Software Q. J., 6(4), 311–326, 1997.
36. Laplante, P. A., Software Engineering for Image Processing Systems, CRC Press, Boca Raton, FL, 2004.
37. NASA Goddard Spaceflight Center, Automated Requirement Measurement (ARM) Tool, satc.gsfc.nasa.gov/tools/arm/, accessed September 29, 2006.
38. Nuseibeh, B. and Easterbrook, S., Requirements engineering: a roadmap, Proc. Intl. Conf. Software Eng., Limerick, Ireland, June 2000, 35–46.
39. Wilson, W.M., “Writing Effective Requirements Specifications,” presented at the Software Technology Conference, Salt Lake City, Utah, April 1997.
40. Zave, P., Classification of research efforts in requirements engineering, ACM Comp. Surveys, 29(4), 315–321, 1997.
41. Alexander, C., Ishikawa, S., and Silverstein, M, A Pattern Language, Oxford University Press, New York, 1977.
42. Beck, K., Extreme Programming: Embracing Change, Addison-Wesley, Boston, MA, 1999.
43. Buschmann, F., Meunier, R., Rohnert, H., Sommerlad, P., and Stal, M., Pattern-Oriented Software Architecture, Volume 1: A System of Patterns, John Wiley & Sons, New York, 1996.
44. Fowler, M., Analysis Patterns: Reusable Object Models, Addison-Wesley, Boston, MA, 1996.
45. France, R.B., Ghosh, S., Dinh-Trong, T., and Solberg, A., Model-driven development using UML 2.0: promises and pitfalls, Computer, 39(2), 59–66, 2006.
46. Kruchten, P., Obbink, H., and Stafford, J., The past, present, and future of software architecture, IEEE Software, 23(2), 22–30, 2006.
47. Laplante, P.A., Software Engineering for Image Processing Systems, CRC Press, Boca Raton, FL, 2004.
48. Larman, C., Applying UML and Patterns, Prentice-Hall, Englewood Cliffs, NJ, 2002.
49. Levine, D. and Schmidt, D., Introduction to Patterns and Frameworks, Washington University, St Louis, 2000.
50. Liskov, B. and Wing, J., A behavioral notion of subtyping, ACM Trans. Program. Lang. Syst., 16(6), 1811–1841, 1994.
51. Martin, R.C., Agile Software Development: Principles, Patterns, and Practices, Prentice-Hall, Englewood Cliffs, NJ, 2002.
52. Meyer, B., Object-Oriented Software Construction, 2nd ed., Prentice Hall, Englewood Cliffs, NJ, 2000.
53. Parnas, D. L. On the criteria to be used in decomposing systems into modules, Commun. ACM, 15(12), 1053–1058, 1972.
54. Pressman, R.S. Software Engineering: A Practitioner's Approach, 6th ed., McGraw-Hill, New York, 2005.
55. Sommerville, I., Software Engineering, 7th ed., Addison-Wesley, Boston, MA, 2005.
56. Cardelli, L. Bad engineering properties of object-oriented languages, ACM Comp. Surveys, 28A(4), 150–158, 1996.
57. Chen, Y., Dios, R., Mili, A., Wu, L., and Wang, K., An empirical study of programming language trends, IEEE Software, 22(3), 72–78, 2006.
58. Fowler, M., Refactoring, Addison-Wesley, Boston, MA, 2000.
59. Gamma, E., Helm, R., Johnson, R., and Vlissides, J., Design Patterns: Elements of Reusable Object-Oriented Software, Addison-Wesley, Boston, MA, 1995.
60. Kernighan, B.W. and Ritchie, D.M., The C Programming Language, 2nd ed., Prentice Hall, Englewood Cliffs, NJ, 1988.
61. Laplante, P.A., Software Engineering for Image Processing Systems, CRC Press, Boca Raton, FL, 2004a.
62. Laplante, P.A., Real-Time Systems Design and Analysis: An Engineer’s Handbook, 3rd ed., IEEE Press/John Wiley & Sons, New York, 2004.
63. Louden, K.C., Programming Languages: Principles and Practice, 2nd ed., Thomson Course Technology, Boston, MA, 2002.
64. McConnell, S., Code Complete, 2nd ed., Microsoft Press, Redmond, WA, 2004.
65. Meyer, B., Object-Oriented Software Construction, 2nd ed., Prentice Hall, Englewood Cliffs, NJ, 2000.
66. Sebesta, R.W., Concepts of Programming Languages, 7th ed., Addison-Wesley, Boston, MA, 2006.
67. Stewart, D.B. Twenty-five most common mistakes with real-time software development, Class #270, Proc. 1999 Embedded Syst. Conf., San Jose, CA, 1999.
68. Basili, V.R., Caldiera, G., and Rombach, H.D., The goal question metric approach, in Boehm, B., Software risk management: principles and practice, IEEE Software, 8(1), 32–41, 1991.
69. Boehm, B. and Basili, V., Software defect reduction top-10 list, in Foundations of Empirical Software Engineering, Boehm, B., Rombach, H.D., and Zelkowitz, M., Eds., Springer, Secaucus, NJ, 2005, 427–431.
70. Brooks, F.W., The Mythical Man Month, 20th Anniversary Edition, Addison-Wesley, Boston, MA, 1995.
71. Chidamber, S.R. and Kemerer, C.F., A metrics suite for object oriented design, IEEE Trans. Software Eng., 20(6), 476–493, 1994.
72. Darcy, D. and Kemerer, C., OO metrics in practice, IEEE Software, 22(6), 17–19, 2005.
73. Dvorak, J., Conceptual entropy and its effect on class hierarchies, Computer, 27(6), 59–63, 1994.
74. Eickelmann, N., Measuring maturity goes beyond process, IEEE Software, 12–13, 2004.
75. Godfrey, M. and Tu, Q. Growth, evolution and structural change in open source software, Proc. 2001 Intl. Workshop on Principles of Software Evolution (IWPSE-01), Vienna, September 2001.
76. Grady, R., Practical Software Metrics for Project Management & Process Improvement, Prentice Hall, Englewood Cliffs, NJ, 1992.
77. Hardgrave, W. and Armstrong, N.Y, Software process improvement: it’s a journey not a destination, Commun. ACM, 49(11), 93–96, 2005.
78. Jones, C., Estimating Software Costs, McGraw-Hill, New York, 1998.
79. Jorgensen, P.C., Software Testing: A Craftsman’s Approach, 2nd ed., CRC Press, Boca Raton, FL, 2002.
80. Kandt, K., Software Engineering Quality Practices, Auerbach Publications, Boca Raton, FL, 2005.
81. Koch, S., Evolution of open source software systems — A large-scale investigation, in Proc. 1st Intl. Conf. OSS, Scotto, M. and Succi, G., Eds., July 11–15, 2005, Genova, 148–153.
82. Lakos, J., Large-Scale C++ Ssoftware Design, Addison-Wesley, Boston, MA, 1996.
83. Lange, C.F.J., Chaudron, M.R.V., and Muskens, J., UML software architecture and design description, IEEE Software, 23(2) 40–46, 2006.
84. Laplante, P.A., Software Engineering for Image Processing Systems, CRC Press, Boca Raton, FL, 2004.
85. Machiavelli, N., The Prince, 1513.
86. McCabe, T., A software complexity measure, IEEE Trans. Software Eng., SE-2, 308–320, 1976.
87. Martin, R.C., Agile Software Development: Principles, Patterns, and Practices, Prentice-Hall, Englewood Cliffs, NJ, 2002.
88. Munson, J., Software Engineering Measurement, Auerbach Publications, Boca Raton, FL, 2003.
89. Nakakoji, K., Yamamoto, Y., Nishinaka, Y., Kishida, K., and Ye, Y., Evolution patterns of open-source software systems and communities, Proc. Intl. Workshop on Principles of Software Evolution, ACM Press, Orlando, FL, May 2002.
90. NIST, Planning Report 02-3, The Economic Impact of Inadequate Infrastructure for Software Testing, www.nist.gov/director/prog-ofc/report02-3.pdf.
91. Paulk, M.C. et al., The Capability Maturity Model, Guidelines for Improving the Software Process, Addison-Wesley, Boston, MA, 1995.
92. Pfleeger, S. L. Measuring software reliability, IEEE Spectrum, 55–60, 1992.
93. Pressman, R.S., Software Engineering: A Practitioner's Approach, 6th ed., McGraw-Hill, New York, 2005.
94. Raymond, E.S. The cathedral and the bazaar. musings on linux and open source by an accidental revolutionary, 2001, O’Reilly Media, Cambridge, MA.
95. Scacchi, W., Understanding open source software evolution, in Software Evolution, Madhavji, N.H., Lehman, M.M., Ramil, J.F., and Perry, D., Eds., John Wiley & Sons, New York, 2004.
96. Sharp, J. et al., Tensions around the adoption and evolution of software quality management systems: a discourse analytic approach, J. Human-Computer Studies, 61, 219–236, 2005.
97. Sommerville, I., Software Engineering, 6th ed., Addison-Wesley, Boston, MA, 2000.
98. Stelzer, D. and Mellis, W., Success factors of organizational change in software process improvement, Software Process — Improvement and Practice, 4, 227–250, 1998.
99. Voas, J.M. and McGraw, G., Software Fault Injection: Inoculating Programs Against Errors, John Wiley & Sons, New York, 1998.
100. Voas, J. and Agresti, W.W., Software quality from a behavioral perspective, IT Pro, 6(4), 46–50, 2004.
101. West, M., Real Process Improvement Using CMMI, Auerbach Publications, Boca Raton, FL, 2004.
102. Zubrow, D., Current trends in the adoption of the CMMI® product suite, compsac, 27th Annu. Intl. Comp. Software Appl. Conf., 2003, 126–129.
103. Beck, K. et al., The Agile Manifesto, http://agilemanifesto.org/principles.html, accessed October 1, 2006.
104. Boehm, B., Software Engineering Economics, Prentice-Hall, Englewood Cliffs, NJ, 1981.
105. Boehm, B.W., Software Risk Management, IEEE Computer Society Press, Los Alamitos, CA, 1989.
106. Boehm, B. and Turner, R., Balancing Agility and Discipline: A Guide to the Perplexed, Addison-Wesley, Boston, MA, 2003.
107. Bramson, R., Coping with Difficult People, Dell Paperbacks, New York, 1988.
108. Brooks, F.P., The Mythical Man Month, 20th Anniversary Edition, Addison-Wesley, Boston, MA, 1995.
109. Cohen, C., Birkin, S., Garfield, M., and Webb, H., Managing conflict in software testing, Commun. ACM, 47(1), 76–81, 2004.
110. Covey, S.R., Principle-Centered Leadership, Simon & Schuster, New York, 1991.
111. Gilb, T., Principles of risk management, http://www.gilb.com/Download/Risk.pdf, accessed August 30, 2006.
112. IEEE 1490-1998 IEEE Guide — Adoption of PMI Standard — A Guide to the Project Management Body of Knowledge IEEE Standards, Piscataway, NJ, 1998.
113. Jones, C., Patterns of Software Systems Failure and Success, International Thomson Computer Press, Boston MA, 1996.
114. Laplante, P.A., Software Engineering for Image Processing Systems, CRC Press, Boca Raton, FL, 2003.
115. Laplante, P.A. and Neill, C.J., Antipatterns: Identification, Refactoring, and Management, Auerbach Publications, Boca Raton, FL, 2006.
116. Morgan, J.N., A roadmap of financial measures for IT project ROI, IT Prof., Jan./Feb., 52–57, 2005.
117. Raffo, D., Settle, J., and Harrison, W., Investigating Financial Measures for Planning of Software IV&V, Portland State University Research Report #TR-99-05, Portland, OR, 1999.
118. Reifer, D.J., Web development: estimating quick-to-market software, IEEE Software, Nov./Dec., 57–64, 2000.
119. Reifer, D.J., Estimating Web development costs: there are differences, June 2002, available at www.stsc.hill.af.mil/crosstalk/2002/06/reifer.html, accessed 1/3/07.
120. Reifer, D., How good are agile methods?, Software, July/Aug., 16–18, 2002b.
121. Stelzer, D. and Mellis, W., Success factors of organizational change in software process improvement, Software Process — Improvement and Practice, 4, 227–250, 1998.
122. Thayer, R.H., Software system engineering: a tutorial, Computer, 35(4)68–73, 2002.
123. Belady, L.A. and Lehman, M.M., A model of large program development, IBM Syst. J., 15(1), 225–252, 1976.
124. Damian, D. and Moitra, D., Global software development: How far have we come? IEEE Software, 23(5), 17–19, 2006.
125. German, D., Using software trails to reconstruct the evolution of software, J. Software Mainten. Evol.: Res. Practice, 16(6), 367–384, 2004.
126. Godfrey, M. and Tu, Q., Evolution in open source software: A case study, Proc. 2000 Intl. Conf. Software
127. Johnson, R.E. Reverse engineering and software archaeology, The DoD SoftwareTech News, 8(3), 4–8, October 2005.
128. Koru, A. and Tian, J., Comparing high-change modules and modules with the highest measurement values in two large-scale open-source products, IEEE Trans. Software Eng., 31(8), 625–642, 2005.
129. Laplante, P.A., Singh, P., Bindiganavile, S., Costello, T., and Landon, M., The who, what, where, why, and when of IT outsourcing, IT Prof., 6(1) 37–41, 2004.
130. Lehman, M.M., Perry, D.E., Ramil, J.F., Turski, W.M., and Wernick, P.D., Metrics and laws of software evolution — the nineties view, Proc. Metrics ’97, IEEE–CS, Albuquerque, NM, November 5–7, 1997, pp. 20–32.
131. Nakakoji, K., Yamamoto, Y., Nishinaka, Y., Kishida, K., and Ye, Y., Evolution patterns of open-source software systems and communities, Proc. Intl. Workshop on Principles of Software Evolution, ACM Press, Los Alamitos, CA, May 2002.
132. Paulson, J.W., Succi, G., and Eberlein, A., An empirical study of open-source and closed source software products, IEEE Trans. Software Eng., 30(4), 246–256, 2004.
133. Raymond, E. S., The Cathedral and the Bazaar, O’Reilly, Cambridge, MA, 1999.
134. Sangwan, R., Neill, C., Laplante, P., Paulish, D., and Kuhn, W., A framework for agile development in outsourced environments, WSEAS Trans. Comput., 3(5), 1530–1537, 2004.
135. Sangwan, R., Bass, M., Mullick, N., and Paulish, D., Managing Global Software Development, Auerbach Publications, Boca Raton, FL, 2006.
136. Scacchi, W., Free and open source development practices in the game community, IEEE Software, 21(1), 59–66, 2004.
137. Schneider, A. and Windle, P., Software archaeology, The DoD SoftwareTech News, 8(3), 9–13, October 2005.