Software Engineering

Warning: mkdir() [function.mkdir]: Permission denied in /home/webs/affiliatelib2/CacheManager.php on line 12

Warning: mkdir() [function.mkdir]: No such file or directory in /home/webs/affiliatelib2/CacheManager.php on line 12

Warning: fopen(/home/templatecore2cache//*cluesnet.com/7e/7ef6bf772f56fd9fba9774d43c913d1705c016e9.tc2cache) [function.fopen]: failed to open stream: No such file or directory in /home/webs/affiliatelib2/CacheManager.php on line 130

Warning: fwrite(): supplied argument is not a valid stream resource in /home/webs/affiliatelib2/CacheManager.php on line 131

Warning: fclose(): supplied argument is not a valid stream resource in /home/webs/affiliatelib2/CacheManager.php on line 132

Software engineering is the application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software.“IEEE Standard Glossary of Software Engineering Terminology,” IEEE std 610.12-1990, 1990. The term software engineering was popularized during the List of publications in computer science#Software engineering: Report of a conference sponsored by the NATO Science Committee (held in Garmisch, Germany) by its chairman F.L. Bauer, and has been in widespread use since. The discipline of software engineering encompasses knowledge, tools, and methods for defining software requirements, and performing software design, computer programming, software testing, and software maintenance tasks. Software engineering also draws on knowledge from fields such as computer engineering, computer science, management, mathematics, project management, quality management, software ergonomics, and systems engineering.

As of 2004, the Bureau of Labor Statistics counts 760,840 software engineers holding jobs in the United States; for comparison, in the U.S. there are some 1.4 million practitioners employed in all other engineering disciplines combined.Bureau of Labor Statistics, U.S. Department of Labor, USDL 05-2145: Occupational Employment and Wages, November 2004, Table 1. The term software engineer is used very liberally in the corporate world. Very few of the practicing software engineers actually hold engineering degrees from accredited universities. There are estimated to be about 1.5 million practitioners in the European Union, Asia, and elsewhere. List of software engineering topics#Pioneers include Barry Boehm, Fred Brooks, C. A. R. Hoare, and David Parnas.

Nature David Parnas has said that software engineering is, in fact, a form of engineering., p. 39: "In my opinion, theanswer to that question is clear: Professional software development should be engineering. Is it? No. But should it be? Unquestionably, yes. " Donald Knuth has said that programming is an art and a science. Transcript of the 1974 Turing Award lecture.

The Bureau of Labor Statistics classifies computer software engineers as a subcategory of "computer specialists", along with occupations such as computer scientist, programmer, and network administrator.U.S Department of Labor and Statistics The 2000 Standard Occupational Classification (SOC) System: 15-0000 Computer and Mathematical Occupations The BLS classifies all other engineering disciplines, including computer hardware engineers, as "engineers".U.S Department of Labor and Statistics The 2000 Standard Occupational Classification (SOC) System: 17-0000 Architecture and Engineering Occupations

The U.K. has seen the alignment of the Information Technology Professional and the Engineering Professionals. 'British Computer Society' - "BCS is licensed by the Engineering Council to award Chartered Engineer status (CEng) and Incorporated Engineer status (IEng);" Software engineering in Canada has seen some contests in the courts over the use of the title "Software Engineer" 'Professional Engineers of Ontario' - "Quebec Engineers win court battle against Microsoft"

Definition Typical formal definitions of software engineering are

"the application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software".“IEEE Standard Glossary of Software Engineering Terminology,” IEEE std 610.12-1990, 1990.
"an engineering discipline that is concerned with all aspects of software production"{{cite book|last= Sommerville|first=Ian|authorlink=Ian Sommerville

| title = Software Engineering|origyear = 1982 | url = http://www.pearsoned.co.uk/HigherEducation/Booksby/Sommerville/ | edition = 8th ed. | year = 2007 | publisher = Pearson Education | location = Harlow, England | isbn = 0-321-31379-8 | pages = P. 7 | chapter = 1.1.2 What is software engineering? | quote = Software engineeering is an engineering discipline that is concerned with all aspects of software production from the early stages of system specification to maintaining the system after it has gone into use. In this definition, there are two key phrases:
1. Engineeering discipline Engineers make things work. They apply theories, methods and tools where these are appropriate . . Engineers also recognise that they must work to organisational and financial constraints. . .
2. All aspects of software production Software engineering is not just concerned with the technical processes of software development but also with activities such as software project management and with the development of tools, methods and theories to support software production. -->

"the establishment and use of sound engineering principles in order to economically obtain software that is reliable and works efficiently on real machines"Ubiquitously cited as a quote from F.L. Bauer at the original NATO Conference on Software Engineering, the usual citation being:

{{cite conference | year = 1969 | month = January| title = NATO Software Engineering Conference 1968 | booktitle = Software Engineering: Report of a conference sponsored by the NATO Science Committee, Garmisch, Germany, 7-11 Oct. 1968 | editor = edited by P. Naur and B. Randell; published January 1969| publisher = Scientific Affairs Division, NATO | location = Brussels| url = http://homepages.cs.ncl.ac.uk/brian.randell/NATO/nato1968.PDF| format = pdf-->

Other meanings As Edsger W. Dijkstra pointed out, the terms software engineering and software engineer have, at times, also been misused in a much wider sense, particularly in America. {{cite web| url = http://www.cs.utexas.edu/users/EWD/transcriptions/EWD11xx/EWD1165.html| title = There is still a war going on (manuscript Austin, 3 December 1993)| accessdate = 2007-02-17 | last = Dijkstra | first = Edsger W| authorlink = Edsger Dijkstra| coauthors = transcribed by Mario Béland|date = 1993-12-03; transcription last revised 2004-11-23| work = E. W. Dijkstra Archive| publisher = The University of Texas at Austin, Department of Computer Sciences| quote = When the term was coined in 1968 by F.L. Bauer of the Technological University of Munich, I welcomed it. . . I interpreted the introduction of the term “software engineering” as an apt reflection of the fact that the design of software systems was an activity par excellence for the mathematical engineer. . .. As soon the term arrived in the USA, it was relieved of all its technical content. It had to be so for in its original meaning it was totally unacceptable . . In the mean time, software engineering has become an almost empty term, as was nicely demonstrated by Data General who overnight promoted all its programmers to the exalted rank of “software engineer”! --> The term has been used less formally:

as the informal contemporary term for the broad range of activities that was formerly called programming and systems analysis;: "For some, software engineering is just a glorified name for programming. If you are a programmer, you might put 'software engineer' on your business card—never 'programmer' though."
as the broad term for all aspects of the practice of computer programming, as opposed to the theory of computer programming, which is called computer science;Mills, Harlan D., J. R. Newman, and C. B. Engle, Jr., "An Undergraduate Curriculum in Software Engineering," in , p. 26: "As a practical matter, we regard software engineering as the necessary preparation for the practicing, software development and maintenance professional. The Computer Scientist is preparing for further theoretical studies..."
as the term embodying the advocacy of a specific approach to computer programming, one that urges that it be treated as an engineering discipline rather than an art or a craft, and advocates the codification of recommended practices in the form of Methodology (software engineering).: "We believe that software engineering can only advance as an engineering discipline by moving away from its current dependence upon advocacy and analysis...."

Purpose Software is often found in products and situations where very high reliability is expected, even under demanding conditions, such as monitoring and controlling nuclear power plants, or keeping a modern airliner aloft{{cite book | last = Pecht | first = Michael | coauthors = | year = 1995| title = Product Reliability, Maintainability, and Supportability Handbook | publisher = CRC Press| location = | id = ISBN 0-8493-9457-0--> . Such applications contain millions of Source lines of code, making them comparable in complexity to the most complex modern machines. For example, a modern airliner has several million physical parts Boeing 747, By the Numbers "Six million: the number of parts, half of which are fasteners." (and the space shuttle about ten million parts{{cite book | last = Grübler | first = Arnulf | authorlink = | coauthors = | year = 2003| title = Technology and Global Change | publisher = Cambridge University Press | location = | id = ISBN 0-521-54332-0--> p. 33: "A Boeing 747 roughly 3.5 million ... the apogee (and nightmare) of mechanical complexity is the space shuttle, with 10 million parts."), while the software for such an airliner can run to 4 million lines of code., "The 2.5 million lines of newly developed software were approximately six times more than any previous Boeing commercial airplane development program. Including commercial-off-the-shelf (COTS) and optional software, the total size is more than 4 million lines of code."

Technologies and practices Software engineers advocate many different technologies and practices, with much disagreement, which has originated a debate that has gone on for over 60 years. Software engineers use a wide variety of technologies: compilers, code repositories, text editors. They also use a wide variety of practices to carry out and coordinate their efforts: pair programming, code reviews and daily stand up meetings.

In spite of the enormous economic growth and productivity gains enabled by software, persistent complaints about the quality of software remain.

The software engineering profession Debate over the term 'engineering' Some people believe that software development is a more appropriate term than software engineering for the process of creating software. Pete McBreen, (author of "Software Craftsmanship: The New Imperative" (ISBN 0-201-73386-2)), argues that the term Software Engineering implies levels of rigor and proven processes that are not appropriate for all types of software development. He argues strongly for 'craftsmanship' as a more appropriate metaphor because that term brings into sharper focus the skills of the developer as the key to success instead of the "manufacturing" process. Using a more traditional comparison, just as not everyone who works in construction is a civil engineer, not everyone who can write code is a software engineer.

Some people dispute the notion that the field is mature enough to warrant the title "engineering". In each of the last few decades, at least one radical new approach has entered the mainstream of software development (e.g. Structured programming, Object-oriented programming, ... ), implying that the field is still changing too rapidly to be considered an engineering discipline. Other people would argue that the supposedly radical new approaches are actually evolutionary rather than revolutionary, the mere introduction of new tools rather than fundamental changes.

Education People from many different educational backgrounds make important contributions to SE. Today, software engineers earn software engineering, computer engineering or computer science degrees. However, there are a great number of people in the industry without engineering degrees earned from accredited universities, so the use of the term "software engineer" is somewhat ambiguous.

Software degrees in the U.S. and Canada: About half of all practitioners today have computer science academic degrees. A small, but growing, number of practitioners have software engineering academic degrees. In 1996, Rochester Institute of Technology established the first BSSE degree program in the United States but did not obtain ABET until 2003, the same time as Clarkson University, Milwaukee School of Engineering and Mississippi State University . Since then, software engineering undergraduate degrees have been established at many universities. A standard international curriculum for undergraduate software engineering degrees was recently defined by the CCSE. As of 2004, in the U.S., about 50 universities offer software engineering degrees, which teach both computer science and engineering principles and practices. The first graduate software engineering degree (MSSE) was established at Seattle University in 1979. Since then graduate software engineering degrees have been made available from many more universities. Likewise in Canada, the Canadian Engineering Accreditation Board (CEAB) of the Canadian Council of Professional Engineers has recognized software engineering programs in engineering faculties such as McMaster University, the University of Waterloo, the University of Ottawa and the University of Western Ontario since 2001.In 1998, the prestigious US Naval Postgraduate School (NPS) established the first doctoral program in Software Engineering in the world. As of the beginning of 2006, thirteen students had graduated from the program and assumed senior-level leadership roles in the Department of Defense research and development community.

Domain degrees: Some practitioners have degrees in application domains, bringing important domain knowledge and experience to projects. In Management Information Systems, some practitioners have business degrees. In embedded systems, some practitioners have electrical engineering or computer engineering degrees, because embedded software often requires a detailed understanding of hardware. In medical software, some practitioners have medical informatics, general medical, or biology degrees.

Other degrees: Some practitioners have mathematics, science, engineering, or other technical degrees. Some have philosophy (logic in particular) or other non-technical degrees. And, some have no degrees. For instance, Barry Boehm earned degrees in mathematics.

Professional recognition difficulties in Canada: The Canadian Council of Professional Engineers (C.C.P.E. or "Engineers Canada") will not grant a "Professional Engineer" status/license to anyone who has not completed a recognized academic engineering program. Many software, and other, engineers, qualified outside Canada, are unable to obtain a "Professional Engineer" "license" in Canada. (See Council for Access to the Profession of Engineering )

Employment See also: software engineering demographics

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 required 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 (Requirements analysis, Software architecture, Software developer, Software testing, technical support, Project management) and in academia (educators, researchers).

There is considerable debate over the future employment prospects for Software Engineers and other Information Technology Professionals. For example, an online futures market called the Future of IT Jobs in America attempts to answer whether there will be more IT jobs, including software engineers, in 2012 than there were in 2002.

Certification Certification (software engineering) is a contentious issue. Some see it as a tool to improve Professional engineer.

Most successful certification programs in the software industry are oriented toward specific technologies, and are managed by the vendors of these technologies. These certification programs are tailored to the institutions that would employ people who use these technologies.

The Association for Computing Machinery had a professional certification program in the early 1980s, which was discontinued due to lack of interest. As of 2006, the IEEE had certified over 575 software professionals. In Canada the Canadian Information Processing Society has developed a legally recognized professional certification called Information Systems Professional (ISP).

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 Worker Visa . Although government statistics do not currently show a threat to software engineering itself; a related career, computer programming does appear to have been affected . 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 . It is the quasi-management aspects of software engineering that appear to be what has kept it from being impacted by globalization.

Comparing related fields Many fields are closely related to software engineering; here are some key similarities and distinctions. Comparing SE with other fields helps explain what SE is and helps define what SE might or should become. There is considerable debate over which fields SE most resembles (or should most resemble). These complex and inexact comparisons explain why some see software engineering as its own field.

History Software engineering has a long evolving history. Both the tools that are used and the applications that are written have evolved over time. It seems likely that software engineering will continue evolving for many decades to come.

60 year time line

1940s: First computer users wrote machine code by hand.
1950s: Early tools, such as macro assemblers and interpreters were created and widely used to improve productivity and quality. First-generation optimizing compilers.
1960s: Second generation tools like optimizing compilers and inspections were being used to improve productivity and quality. The concept of software engineering was widely discussed. First really big (1000 programmer) projects. Commercial mainframes and custom software for big business. The influential List of publications in computer science#Software engineering: Report of a conference sponsored by the NATO Science Committee was held.
1970s: Collaborative software tools, such as Unix, code repositories, make, and so on. Minicomputers and the rise of small business software.
1980s: Personal computers and personal workstations became common. Commensurate rise of consumer software.
1990s: Object-oriented programming and Agile software development like Extreme programming gained mainstream acceptance. Computer memory capacity sky-rocketed and prices dropped drastically. These new technologies allowed software to grow more complex. The WWW and hand-held computers made software even more widely available.
2000s: Managed code and interpreted platforms such as Java (programming language), .NET Framework, Ruby (programming language), Python (programming language) and PHP made writing software easier than ever before. Offshore outsourcing changed the nature and focus of software engineering careers.

Current trends in software engineering Software engineering is a young discipline, and is still developing. The directions in which software engineering is developing include:

Aspects: Aspect-oriented programming help software engineers deal with -ilities by providing tools to add or remove Boilerplate (text) code from many areas in the source code. Aspects describe how all objects or functions should behave in particular circumstances. For example, aspect (computer science)s can add debugging, Data logging, or Lock (software engineering) control into all objects of particular types. Researchers are currently working to understand how to use aspects to design general-purpose code. Related concepts include generative programming and Template (programming).

Agile: Agile software development guides software development projects that evolve rapidly with changing expectations and competitive markets. Proponents of this method believe that heavy, document-driven processes (like TickIT, CMM and ISO 9000) are fading in importance. Some people believe that companies and agencies export many of the jobs that can be guided by heavy-weight processes. Related concepts include Extreme Programming and Lean software development.

Experimental: Experimental software engineering is a branch of software engineering interested in devising experiments on software, in collecting data from the experiments, and in devising laws and theories from this data. Proponents of this method advocate that the nature of software is such that we can advance the knowledge on software through experiments only.

Model-driven: Model-driven development uses (both textual and graphical) models as primary development artifacts. By means of model transformation and code generation a part or complete applications are generated.

Software Product Lines: Product Family Engineering is a systematic way to produce families of software systems, instead of creating a succession of completely individual products. This method emphasizes extensive, systematic, formal code reuse, to try to industrialize the software development process.

The Future of Software Engineering conference (FOSE), held at ICSE 2000, documented the state of the art of SE in 2000 and listed many problems to be solved over the next decade. The FOSE tracks at the ICSE 2000 and the ICSE 2007 conferences also help identify the state of the art in software engineering.The Feyerabend project attempts to discover the future of software engineering by seeking and publishing innovative ideas.

Software engineering today In 2006, Money Magazine and Salary.com rated software engineering as the best job in America in terms of growth, pay, stress levels, flexibility in hours and working environment, creativity, and how easy it is to enter and advance in the field.{{cite web| last = Kalwarski | first = Tara | coauthors = Daphne Mosher, Janet Paskin and Donna Rosato | year = 2006 | url = http://money.cnn.com/magazines/moneymag/bestjobs/2006/ | title = Best Jobs in America | work = MONEY Magazine | publisher = CNN | accessdate = 2006-04-20 -->, "MONEY Magazine and Salary.com researched hundreds of jobs, considering their growth, pay, stress-levels and other factors. These careers ranked highest. 1. Software Engineer..."

See also software engineering economics.

Conferences, organizations and publications Conferences Several academic conferences devoted to software engineering are held every year. There are also many other academic conferences every year devoted to special topics within SE, such as programming languages, requirements, testing, and so on.

; ICSE: The biggest and oldest conference devoted to software engineering is the International Conference on Software Engineering. This conference meets every year to discuss improvements in research, education, and practice.

; COMPSAC: The Annual International Computer Software and Applications Conference was first held in Chicago in 1977 and is designated as the IEEE Computer Society signature conference on software technology and applications.

; ESEC: The European Software Engineering Conference.

; FSE: The Foundations of Software Engineering conference is held every year, alternating between Europe and North America. It emphasizes theoretical and foundational issues.

; CUSEC: Conferences dedicated to inform undergraduate students like the annual Canadian University Software Engineering Conference are also very promising for the future generation. It is completely organized by undergraduate students and lets different Canadian universities interested in Software Engineering host the conference each year. Past guests include Kent Beck, Joel Spolsky, Philippe Kruchten, Hal Helms, Craig Larman, David Parnas as well as university professors and students.

; SEPG: The annual Software Engineering Process Group conference, sponsored by the Carnegie Mellon Software Engineering Institute (SEI), is a conference and exhibit showcase for systems and software engineering professionals. The four-day event emphasizes systematic improvement of people, Process improvement, and technology.

; INFORMATICS-INFORMATIQUE: The annual Canadian information technology, data processing and software engineering symposium, sponsored by the Canadian Information Processing Society. First held in 1958.

; ICALEPS: International Conference on Accelerator and Large Experimental Physics Control Systems Conference . Biennial conference covering software engineering for large scale scientific control systems. First held in 1987.

; APSEC: Asia Pacific Software Engineering Conference .

; UYMS: National Software Engineering Symposium (in Turkish: Ulusal Yazilim Muhendisligi Sempozyumu) (not available in English). Biennial symposium first held in İzmir, Turkey in 2003.

Organizations

Association for Computing Machinery (ACM)
Australian Computer Society (ACS)
British Computer Society (BCS)
Canadian Information Processing Society (CIPS) - Information Systems Professional certification.
IEEE Computer Society
Lero, the Irish Software Engineering Research Centre
RUSSOFT
Software Association of Oregon (SAO)
Software Engineering Institute (SEI)
Software Industry Professionals
The Safety and Reliability Society

Publications

List of important publications in computer science#Software engineering
CrossTalk: The Journal of Defense Software Engineering

See also Main lists: List of basic software engineering topics and List of software engineering topics

Association for Computing Machinery
Computer Science
Custom software development
Informatics
Search Based Software Engineering
Software development
Software Quality Assurance
System testing
Software Assurance
Software System Safety
Structured analysis
Systems Analyst
User experience

References

Further reading

{{cite book|last= Sommerville|first=Ian|authorlink=Ian Sommerville

{{cite book|last= Pressman|first=Roger S|authorlink=

Carlo Ghezzi, Mehdi Jazayeri, Dino Mandrioli: Fundamentals of Software Engineering, 2nd (International) ed.: 2003 (1st ed.: 1991), Pearson Education @ Prentice-Hall

External links

Guide to the Software Engineering Body of Knowledge
Computer Software Engineers - Definition and statistics from the U.S. Bureau of Labor Statistics
Big Ball of Mud A "yes but why not" point of view by Brian Foote and Joseph Yoder, Department of Computer Science, University of Illinois at Urbana-Champaign
Software Engineering Radio A podcast on software engineering

Software Engineering at Oxford | Welcome to the Software Engineering ...
Part time postgraduate study Courses in software systems security, object technology, software architecture, precise modelling, development processes Delivered by experts ... The ...

Sommerville - Software Engineering
These textbook presents the general overview of software engineering where I concentrate on practical approaches that are used for developing ...

Ian Sommerville
I am a full professor of software engineering at St Andrews University in Scotland and the author of a widely used textbook on software engineering, now in its 8th edition.

Ian Sommerville - Software Engineering
The latest update edition of my software engineering book is now available. Follow the link below to access the 8th edition website.

Sommerville - Software Engineering
These textbook presents the general overview of software engineering where I concentrate on practical approaches that are used for developing ...

software engineering from FOLDOC
software engineering < programming > (SE) A systematic approach to the analysis, design, implementation and maintenance of software. It often involves the use of CASE tools.

Software Engineering - BSc(Hons) - Course Information - Undergraduate ...
BSc(Hons) - Software Engineering - Kingston's Software Engineering BSc(Hons) examines the tools, techniques and methodologies that represent best practice in industry. Topics ...

Software Engineering :SES :King's College London
The Software Engineering Section in Computer Science at King's College London ... King's Software Engineering Section specialises in developing innovative ways to optimise software ...

NATO Software Engineering Conferences
P. Naur and B. Randell, (Eds.). Software Engineering: Report of a conference sponsored by the NATO Science Committee, Garmisch, Germany, 7-11 Oct. 1968, Brussels, Scientific ...

Undergraduate Courses - Software Engineering
Detailed information about studying Software Engineering at the University of Stirling. ... Software Engineering focuses on the art of designing and building complex software ...