Software Engineering

Software engineering is a profession and field of study dedicated to designing, implementing, and modifying software so that it is of higher quality, more affordable, maintainable, and faster to build. The term software engineering first appeared in the 1968 NATO Software Engineering Conference, and was meant to provoke thought regarding the perceived "software crisis" at the time.[1][2] Since the field is still relatively young compared to its sister fields of engineering, there is still much debate around what software engineering actually is, and if it conforms to the classical definition of engineering. Some people argue that development of computer software is more art than science [3], and that attempting to impose engineering disciplines over a type of art is an exercise in futility because what represents good practice in the creation of software is not even defined.[4] Others, such as Steve McConnell, argue that engineering's blend of art and science to achieve practical ends provides a useful model for software development.[5] The IEEE Computer Society's Software Engineering Body of Knowledge defines "software engineering" as the application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software, and the study of these approaches; that is, the application of engineering to software.[6]
Software development, a much used and more generic term, does not necessarily subsume the engineering paradigm. Although it is questionable what impact it has had on actual software development over the last more than 40 years,[7][8] the field's future looks bright according to Money Magazine and Salary.com, who rated "software engineering" as the best job in the United States in 2006.[9]

History

Main article: History of software engineering
When the first modern digital computers appeared in the early 1940s,[10] the instructions to make them operate were wired into the machine. Practitioners quickly realized that this design was not flexible and came up with the "stored program architecture" or von Neumann architecture. Thus the first division between "hardware" and "software" began with abstraction being used to deal with the complexity of computing.
Programming languages started to appear in the 1950s and this was also another major step in abstraction. Major languages such as Fortran, ALGOL, and Cobol were released in the late 1950s to deal with scientific, algorithmic, and business problems respectively. E.W. Dijkstra wrote his seminal paper, "Go To Statement Considered Harmful",[11] in 1968 and David Parnas introduced the key concept of modularity and information hiding in 1972[12] to help programmers deal with the ever increasing complexity of software systems. A software system for managing the hardware called an operating system was also introduced, most notably by Unix in 1969. In 1967, the Simula language introduced the object-oriented programming paradigm.
These advances in software were met with more advances in computer hardware. In the mid 1970s, the microcomputer was introduced, making it economical for hobbyists to obtain a computer and write software for it. This in turn led to the now famous Personal Computer (PC) and Microsoft Windows. The Software Development Life Cycle or SDLC was also starting to appear as a consensus for centralized construction of software in the mid 1980s. The late 1970s and early 1980s saw the introduction of several new Simula-inspired object-oriented programming languages, including C++, Smalltalk, and Objective C.
Open-source software started to appear in the early 90s in the form of Linux and other software introducing the "bazaar" or decentralized style of constructing software.[13] Then the Internet and World Wide Web hit in the mid 90s, changing the engineering of software once again. Distributed systems gained sway as a way to design systems, and the Java programming language was introduced with its own virtual machine as another step in abstraction. Programmers collaborated and wrote the Agile Manifesto, which favored more lightweight processes to create cheaper and more timely software.
The current definition of software engineering is still being debated by practitioners today as they struggle to come up with ways to produce software that is "cheaper, bigger, quicker".

Profession

Main article: Software engineer
Legal requirements for the licensing or certification of professional software engineers vary around the world. In the UK, the British Computer Society licenses software engineers and members of the society can also become Chartered Engineers (CEng), while in some areas of Canada, such as Alberta, Ontario,[14] and Quebec, software engineers can hold the Professional Engineer (P.Eng)designation and/or the Information Systems Professional (I.S.P.) designation; however, there is no legal requirement to have these qualifications.
The IEEE Computer Society and the ACM, the two main professional organizations of software engineering, publish guides to the profession of software engineering. The IEEE's Guide to the Software Engineering Body of Knowledge - 2004 Version, or SWEBOK, defines the field and describes the knowledge the IEEE expects a practicing software engineer to have. The IEEE also promulgates a "Software Engineering Code of Ethics".[15]

Employment

In 2004, the U. S. Bureau of Labor Statistics counted 760,840 software engineers holding jobs in the U.S.; in the same time period there were some 1.4 million practitioners employed in the U.S. in all other engineering disciplines combined.[16] Due to its relative newness as a field of study, formal education in software engineering is often taught as part of a computer science curriculum, and as a result most software engineers hold computer science degrees.[17]
Most software engineers work as employees or contractors. Software engineers work with businesses, government agencies (civilian or military), and non-profit organizations. Some software engineers work for themselves as freelancers. Some organizations have specialists to perform each of the tasks in the software development process. Other organizations require software engineers to do many or all of them. In large projects, people may specialize in only one role. In small projects, people may fill several or all roles at the same time. Specializations include: in industry (analysts, architects, developers, testers, technical support, managers) and in academia (educators, researchers).
There is considerable debate over the future employment prospects for software engineers and other IT professionals. For example, an online futures market called the "ITJOBS Future of IT Jobs in America"[18] attempts to answer whether there will be more IT jobs, including software engineers, in 2012 than there were in 2002. 

Certification

Professional certification of software engineers is a contentious issue, with some professional organizations supporting it,[19] and others claiming that it is inappropriate given the current level of maturity in the profession.[20] Some see it as a tool to improve professional practice; "The only purpose of licensing software engineers is to protect the public".[21]
The ACM had a professional certification program in the early 1980s,[citation needed] which was discontinued due to lack of interest. The ACM examined the possibility of professional certification of software engineers in the late 1990s, but eventually decided that such certification was inappropriate for the professional industrial practice of software engineering.[20] As of 2006, the IEEE had certified over 575 software professionals as a Certified Software Development Professional (CSDP).[19] In 2008 they added an entry-level certification known as the Certified Software Development Associate (CSDA).[22] In the U.K. the British Computer Society has developed a legally recognized professional certification called Chartered IT Professional (CITP), available to fully qualified Members (MBCS). In Canada the Canadian Information Processing Society has developed a legally recognized professional certification called Information Systems Professional (ISP)[23]. The Software Engineering Institute offers certification on specific topic such as Security, Process improvement and Software architecture[24].
Most certification programs in the IT industry are oriented toward specific technologies, and are managed by the vendors of these technologies.[25] These certification programs are tailored to the institutions that would employ people who use these technologies.
In some countries, the United States included, the software engineer is an actual engineering degree (Bachelor of Science or Bachelor of Engineering), as an example in Education in Israel software engineer has the right to be written in the engineering registry, and it would be a felony If a person describe himself as an engineer ( The engineering law defines that a person stating himself as an engineer without the proper license / registration could be sentenced to up to 6 months in jail). 

Impact of globalization

Many students in the developed world have avoided degrees related to software engineering because of the fear of offshore outsourcing (importing software products or services from other countries) and of being displaced by foreign visa workers.[26] Although statistics do not currently show a threat to software engineering itself; a related career, computer programming does appear to have been affected.[27][28] Often one is expected to start out as a computer programmer before being promoted to software engineer. Thus, the career path to software engineering may be rough, especially during recessions.
Some career counselors suggest a student also focus on "people skills" and business skills rather than purely technical skills because such "soft skills" are allegedly more difficult to offshore.[29] It is the quasi-management aspects of software engineering that appear to be what has kept it from being impacted by globalization.[30]

Education


A knowledge of programming is the main pre-requisite to becoming a software engineer, but it is not sufficient. Many software engineers have degrees in Computer Science due to the lack of software engineering programs in higher education. However, this has started to change with the introduction of new software engineering degrees, especially in post-graduate education. A standard international curriculum for undergraduate software engineering degrees was defined by the CCSE.
Steve McConnell opines that because most universities teach computer science rather than software engineering, there is a shortage of true software engineers.[31] In 2004 the IEEE Computer Society produced the SWEBOK, which has become an ISO standard describing the body of knowledge covered by a software engineer[citation needed].
The European Commission within the Erasmus Mundus Programme offers a European master degree called European Master on Software Engineering for students from Europe and also outside Europe[32]. This is a joint program (double degree) involving four universities in Europe.

Sub-disciplines

Software engineering can be divided into ten subdisciplines. They are:[6]

Related disciplines

Software engineering is related to the disciplines of computer science, project management, and systems engineering.[33][34] 

Computer science 

Software engineering is considered a subfield of computer science by many academics.[citation needed] Many of the foundations of software engineering come from computer science. 

Project management 

The building of a software system is usually considered a project and the management of it borrows many principles from the field of Project management. 

Systems engineering 

Systems engineers have been dealing with the complexity of large systems for many decades and their knowledge is applied to many software engineering problems. 

See also

Main article: Outline of software engineering

References

  1. ^ 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. http://homepages.cs.ncl.ac.uk/brian.randell/NATO/nato1968.PDF. Retrieved 2008-12-26. 
  2. ^ Randell, Brian (10 Aug 2001). "The 1968/69 NATO Software Engineering Reports". Brian Randell's University Homepage. The School of the Computer Sciences, Newcastle University. http://homepages.cs.ncl.ac.uk/brian.randell/NATO/NATOReports/index.html. 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." 
  3. ^ Hey, Programmers, We Got No Theory! Dr. Dobbs Journal, March 22, 2010 (Retrieved March 26, 2010)
  4. ^ Why We Need a Theory for Software Engineering, Ivar Jacobson and Ian Spence, Dr. Dobbs Journal, October 02, 2009 (Retrieved March 26, 2010)
  5. ^ McConnell, Steve (January/February 1998). "The Art, Science, and Engineering of Software Development". IEEE Software (1). http://www.stevemcconnell.com/ieeesoftware/bp13.htm. 
  6. ^ a b 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. p. 1–1. ISBN 0-7695-2330-7. http://www.swebok.org. 
  7. ^ The end of software engineering and the start of economic-cooperative gaming
  8. ^ 35 years on: to what extent has software engineering design achieved its goals?
  9. ^ Kalwarski, Tara; Daphne Mosher, Janet Paskin and Donna Rosato (2006). "Best Jobs in America". MONEY Magazine. CNN. http://money.cnn.com/magazines/moneymag/bestjobs/2006/. Retrieved 2006-04-20. 
  10. ^ Leondes (2002). intelligent systems: technology and applications. CRC Press. ISBN 9780849311215. 
  11. ^ Dijkstra, E. W. (March 1968). "Go To Statement Considered Harmful". Communications of the ACM 11 (3): 147–148. doi:10.1145/362929.362947. http://www.cs.utexas.edu/users/EWD/ewd02xx/EWD215.PDF. Retrieved 2009-08-10. 
  12. ^ 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. http://www.acm.org/classics/may96/. Retrieved 2008-12-26. 
  13. ^ Raymond, Eric S. The Cathedral and the Bazaar. ed 3.0. 2000.
  14. ^ Williams, N.S.W. (19-21 Feb 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. 
  15. ^ Software Engineering Code of Ethics
  16. ^ Bureau of Labor Statistics, U.S. Department of Labor, USDL 05-2145: Occupational Employment and Wages, November 2004, Table 1.
  17. ^ "Software Engineering". http://computingcareers.acm.org/?page_id=12. Retrieved 2008-02-01. 
  18. ^ Future of IT Jobs in America
  19. ^ a b IEEE Computer Society. "2006 IEEE computer society report to the IFIP General Assembly" (PDF). http://www.ifip.org/minutes/GA2006/Tab18b-US-IEEE.pdf. Retrieved 2007-04-10. 
  20. ^ a b ACM (July 17, 2000). "A Summary of the ACM Position on Software Engineering as a Licensed Engineering Profession". Association for Computing Machinery (ACM). http://www.cs.wm.edu/~coppit/csci690-spring2004/papers/selep_main.pdf. Retrieved 2009-03-03. "At its meeting in May 2000, the Council further concluded that the framework of a licensed professional engineer, originally developed for civil engineers, does not match the professional industrial practice of software engineering. Such licensing practices would give false assurances of competence even if the body of knowledge were mature; and would preclude many of the most qualified software engineers from becoming licensed." 
  21. ^ Kruchten, Philippe, "Licensing Software Engineers?", IEEE SOFTWARE nov/dec 2008
  22. ^ IEEE. "CSDA". http://www.computer.org/portal/web/certification/csda. Retrieved 2010-04-20. 
  23. ^ Canadian Information Processing Society. "I.S.P. Designation". http://www.cips.ca/standards/isp. Retrieved 2007-03-15. 
  24. ^ SEI certification page
  25. ^ Wyrostek, Warren (March 14, 2008). "The Top 10 Problems with IT Certification in 2008". InformIT. http://www.informit.com/articles/article.aspx?p=1180991. Retrieved 2009-03-03. 
  26. ^ As outsourcing gathers steam, computer science interest wanes
  27. ^ Computer Programmers
  28. ^ Software developer growth slows in North America | InfoWorld | News | 2007-03-13 | By Robert Mullins, IDG News Service
  29. ^ Hot Skills, Cold Skills
  30. ^ Dual Roles: The Changing Face of IT
  31. ^ McConnell, Steve (July 10, 2003. Professional Software Development: Shorter Schedules, Higher Quality Products, More Successful Projects, Enhanced Careers. ISBN 978-0321193674.
  32. ^ http://ec.europa.eu/education/programmes/mundus/index_en.html
  33. ^ Ian Sommerville (2004). Software Engineering. 7th edition. Chapter 1. Bezien 20 Okt 2008.
  34. ^ Table 2 in Chapter 1,"Guide to the Software Engineering Body of Knowledge". February 6, 2004. http://www.swebok.org/swebokcontents-ch1.html#ch1. Retrieved 2008-02-21. 
35.Overview of Software R&D and Globalization Insights from Zinnov

Further reading

External links

 Source : http://en.wikipedia.org/wiki/Software_engineering

    No comments:

    Post a Comment

    Hi All...
    thanks for reading my post.
    I would be glad if you give me a comment about this post

    Subscribe to: Posts (Atom)