1. SWEBOK executive editors, Alain Abran, James W. Moore ; editors, Pierre Bourque, Robert Dupuis. (2004). Pierre Bourque and Robert Dupuis. ed. Guide to the Software Engineering Body of Knowledge - 2004 Version. IEEE Computer Society. pp. 1–1. ISBN 0-7695-2330-7.
2. Laplante, Phillip (2007). What Every Engineer Should Know about Software Engineering. Boca Raton: CRC. ISBN 9780849372285. Retri
3. ACM (2006). "Computing Degrees & Careers". ACM. Retrieved 2010-11-23.
eved 2011-01-21.
4. Peter, Naur; Brian Randell (7–11 October 1968). "Software Engineering: Report of a conference sponsored by the NATO Science Committee" (PDF). Garmisch, Germany: Scientific Affairs Division, NATO. Retrieved 2008-12-26.
5. Randell, Brian (10 August 2001). "The 1968/69 NATO Software Engineering Reports". Brian Randell's University Homepage. The School of the Computer Sciences, Newcastle University. Retrieved 2008-10-11. "The idea for the first NATO Software Engineering Conference, and in particular that of adopting the then practically unknown term "software engineering" as its (deliberately provocative) title, I believe came originally from Professor Fritz Bauer."
6. The end of software engineering and the start of economic-cooperative gaming
7. 35 years on: to what extent has software engineering design achieved its goals?
8. Kalwarski, Tara; Daphne Mosher, Janet Paskin and Donna Rosato (2006)."Best Jobs in America". MONEY Magazine. CNN. Retrieved 2006-04-20.
9. Leondes (2002). intelligent systems: technology and applications. CRC Press.ISBN 9780849311215.
10. Dijkstra, E. W. (March 1968). "Go To Statement Considered Harmful".Communications of the ACM 11 (3): 147–148. doi:10.1145/362929.362947. Retrieved 2009-08-10.
11. Parnas, David (December 1972). "On the Criteria To Be Used in Decomposing Systems into Modules". Communications of the ACM 15 (12): 1053–1058.doi:10.1145/361598.361623. Retrieved 2008-12-26.
12. Williams, N.S.W. (19–21 February 2001). "Professional Engineers Ontario's approach to licensing software engineering practitioners". Software Engineering Education and Training, 2001 Proceedings. 14th Conference on. Charlotte, NC:IEEE. pp. 77–78.
13. Software Engineering Code of Ethics
14. 97 Things Every Software Architect Should Know - O'Reilly Media, Inc.(published February 5, 2009) ISBN: 978-0-596-52269-8
15. Bureau of Labor Statistics, U.S. Department of Labor, USDL 05-2145: Occupational Employment and Wages, November 2004, Table 1.
16. "Software Engineering". Retrieved 2008-02-01.
17. "Computer Software Engineers and Computer Programmers". Retrieved 2009-12-17.
18. Wyrostek, Warren (March 14, 2008). "The Top 10 Problems with IT Certification in 2008". InformIT. Retrieved 2009-03-03.
19. IEEE Computer Society. "2006 IEEE computer society report to the IFIP General Assembly" (PDF). Retrieved 2007-04-10.
20. IEEE. "CSDA". Retrieved 2010-04-20.
21. Canadian Information Processing Society. "I.S.P. Designation". Retrieved 2007-03-15.
22. ACM (July 17, 2000). "A Summary of the ACM Position on Software Engineering as a Licensed Engineering Profession". [dead link]
23. As outsourcing gathers steam, computer science interest wanes
24. Computer Programmers
25. Software developer growth slows in North America | InfoWorld | News | 2007-03-13 | By Robert Mullins, IDG News Service
26. Gartner Magic Quadrant
27. Abran, Alain, ed (2005) [2004]. "Chapter 1: Introduction to the Guide". Guide to the Software Engineering Body of Knowledge. Los Alamitos: IEEE Computer Society. ISBN 0769523307. Retrieved 2010-09-13. "The total volume of cited literature is intended to be suitable for mastery through the completion of an undergraduate education plus four years of experience."
28. Young, Michal; Faulk, Stuart (2010). "Sharing What We Know About Software Engineering" (pdf). Proceedings of the FSE/SDP workshop on Future of software engineering research (FoSER '10). ACM. pp. 439–442.doi:10.1145/1882362.1882451. ISBN 978-1-4503-0427-6. Retrieved 2011-02-25.
