Software engineering has strong associations with other areas of science and technology, especially those related to computing. Although software engineering is clearly identified by an emphasis on design, a distinctive feature of engineering programs, discerning the precise boundaries that separate the computing disciplines is not always easy.
The Computing Curricula series includes a volume entitled “Computing Curricula 2005: The Overview Report” that “provides undergraduate curriculum guidelines for five defined sub-disciplines of computing: Computer Science, Computer Engineering, Information Systems, Information Technology, and Software Engineering.” [CC 2005] Readers are encouraged to consult that volume for a good overview of the similarities and differences between computing disciplines.
References
[ABET 2014a] ABET, Accreditation Policy and Procedure Manual, Nov. 2014; http://www.abet.org/appm-2015-2016/.
[ABET 2014b] ABET, Criteria for Accrediting Engineering Programs, Nov. 2014; http://www.abet.org/eac-criteria-2015-2016/.
[ACM 1998] ACM/IEEE-CS Joint Task Force on Software Engineering Ethics and Professional Practices, Software Engineering Code of Ethics and Professional Practice, version 5.2, Sept. 1998; http://www.acm.org/serving/se/code.htm.
[BCS 2001] British Computer Society, Guidelines On Course Exemption & Accreditation For Information For Universities And Colleges, Aug. 2001; http://www1.bcs.org.uk/link.asp?sectionID=1114.
[Beck 2004] K. Beck, Extreme Programming Explained: Embrace Change, 2nd ed., Pearson Addison-Wesley, 2004.
[Beecham et al. 2008] S. Beecham et al., “Motivation in Software Engineering: A Systematic Literature Review,” Information & Software Technology, vol. 50, 2008, pp. 860–878.
[Bloom 1956] B.S. Bloom, ed., Taxonomy of Educational Objectives: The Classification of Educational Goals: Handbook I, Cognitive Domain, Longmans, 1956.
[Boehm 1988] B.W. Boehm, “A Spiral Model of Software Development and Enhancement,” Computer, vol. 21, no. 5, 1988, pp. 61–72.
[Boehm & Turner 2003] B.W. Boehm and R. Turner, Balancing Agility and Discipline: A Guide for the Perplexed, Pearson Addison-Wesley, 2003.
[Brooks 1987] F.P. Brooks, Jr. “No Silver Bullet: Essence and Accidents of Software Engineering,” Computer, vol. 20, no. 4, 1987, pp. 10–19.
[CEAB 2002] Canadian Eng. Accreditation Board, Accreditation Criteria and Procedures, Canadian Council of Professional Engineers, 2002; http://www.ccpe.ca/e/files/report_ceab.pdf.
[CS2013] ACM/IEEE CS Joint Task Force on Computing Curricula. “Computer Science Curricula 2013,” ACM Press and IEEE CS Press, 2013,; DOI: http://dx.doi.org/10.1145/2534860
[da Silva 2012] F.Q.B. da Silva et al., “An Evidence-Based Model of Distributed Software Development Project Management: Results from a Systematic Mapping Study,” Software: Evolution & Process, vol. 24, no. 6, pp. 625–642.
[Denning 1992] P.J. Denning, “Educating a New Engineer,” Comm. ACM, Dec. 1992.
[ECSA 2000] Eng. Council Of South Africa, Policy on Accreditation of University Bachelors Degrees, Aug. 2000; http://www.ecsa.co.za/
[Floyd 1984] C. Floyd, “A Systematic Look at Prototyping,” Approaches to Prototyping Budde R., Kuhlenkamp K., Mathiassen L., and Zullighoven H., eds., Springer Verlag, 1984, pp. 1–18.
[Gladden 1982] G.R. Gladden, “Stop the Life-Cycle, I Want to Get Off,” ACM Software Eng. Notes, vol. 7, no. 2, 1982, pp. 35–39.
[Glass 2003] R.L. Glass, “A Big Problem in Academic Software Engineering and a Potential Outside-the-Box Solution,” IEEE Software, vol. 20, no. 4, 2003, pp. 96, 95.
[Glass et al. 2004] R.L. Glass, V. Ramesh, and I. Vessey, “A Analysis of Research in Computing Disciplines,” Comm. ACM, vol. 47, no. 6, 2004, pp. 89–94.
[Holcombe 2008] M. Holcombe, Running an Agile Software Development Project, Wiley, 2008.
[Hughes 2000] R. Hughes, Practical Software Measurement, McGraw Hill, 2000.
[IEEE 2001b] ACM/IEEE-Curriculum 2001 Task Force, Computing Curricula 2001, Computer Science , Dec. 2001; http://www.computer.org/education/cc2001/final/index.htm.
[IEEE 2004] ACM/IEEE Joint Task Force on Computing Curricula, Software Engineering 2004 Curriculum Guidelines for Undergraduate Degree Programs in Software Engineering, Aug. 2004; http://www.computer.org/portal/c/document_library/get_file?p_l_id=2814020&folderId=3111026&name=DLFE-57602.pdf.
[IEEE 2005] ACM/IEEE Joint Task Force on Computing Curricula, Computing Curricula 2005 The Overview Report, Sept. 2005; http://www.computer.org/portal/c/document_library/get_file?p_l_id=2814020&folderId=3111026&name=DLFE-57601.pdf.
[IEEE 2010] ISO/IEC/IEEE 24765:2010 Systems and Software Engineering—Vocabulary.
[IEI 2000] The Institution of Engineers of Ireland, Accreditation of Engineering Degrees, May 2000; http://www.iei.ie/Accred/accofeng.pdf.
[ISA 1999] Institution of Engineers, Australia, Manual For The Accreditation Of Professional Engineering Programs, Oct. 1999; http://www.ieaust.org.au/membership/res/downloads/AccredManual.pdf.
[JABEE 2003] Japan Accreditation Board for Engineering, Criteria for Accrediting Japanese Engineering Education Programs 2002-2003; http://www.jabee.org/english/OpenHomePage/e_criteria&procedures.htm.
[King 1997] W.K. King and G. Engel, Report on the International Workshop on Computer Science and Engineering Accreditation, , IEEE CS, 1997.
[Leffingwell 2011] D. Leffingwell, Agile Software Requirements, Pearson Addison-Wesley, 2011.
[McCracken & Jackson 1982] D.D. McCracken and M.A. Jackson, “Life-Cycle Concept Considered Harmful,” ACM Software Eng. Notes, vol. 7, no. 2, 1982, pp. 29–32.
[NACE 2013] Nat’l Assoc. of Colleges and Employers. Job Outlook 2013; http://www.naceweb.org/.
[Naur 1969] P. Naur and B. Randell, eds., Software Engineering: Report on a Conference Sponsored by the NATO Science Committee, (7–11 October 1968), Scientific Affairs Division, NATO, 1969.
[OECD 2010] OECD Information Technology Outlook, www.oecd.org.
[Peters & Tripp 1976] L.J. Peters and L.L. Tripp, “Is Software Design ‘Wicked’,’” Datamation, vol. 22, no. 5, 1976, p. 127.
[Pfleeger 2005] S.L. Pfleeger, “Soup or Art? The Role of Evidential Force in Empirical Software Engineering,” IEEE Software, vol. 22, no. 1, 2005, pp. 66–73.
[Rittel & Webber 1984] H.J. Rittel and M.M. Webber, “Planning Problems Are Wicked Problems,” “Developments in Design Methodology”, N. Cross, ed., 1984, Wiley, pp. 135–144.
[Rogers et al. 2011] Y. Rogers, H. Sharp H., and J. Preece, Interaction Design: Beyond Human-Computer Interaction, 3rd ed., Wiley, 2011.
[Schwaber 2004] K. Schwaber, Agile Project Management with Scrum, Microsoft Press, 2004.
[Smite et al. 2010] D. Smite et al., “Empirical Evidence in Global Software Engineering: A Systematic Review, Empirical Software Eng., vol. 15, 2011, pp. 91–118.
[SWEBOK 2014] P. Bourque and R.E. Fairley, eds., Guide to the Software Engineering Body of Knowledge, Version 3.0, IEEE Computer Society, 2014; www.swebok.org.
[Tucker et al. 2011] A. Tucker, R. Morelli, and C. de Silva, Software Development: An Open Source Approach, Chapman & Hall, 2011.
[Weinberg 1971] G.M. Weinberg, The Psychology of Computer Programming, Van Nostrand Reinhold, 1971.
Share with your friends: |