The following outline is provided as an overview of and topical guide to software engineering:

Software engineering application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software; that is the application of engineering to software.[1]

The ACM Computing Classification system is a poly-hierarchical ontology that organizes the topics of the field and can be used in semantic web applications and as a de facto standard classification system for the field. The major section "Software and its Engineering" provides an outline and ontology for software engineering.

Software applications

Software engineers build software (applications, operating systems, system software) that people use.

Applications influence software engineering by pressuring developers to solve problems in new ways. For example, consumer software emphasizes low cost, medical software emphasizes high quality, and Internet commerce software emphasizes rapid development.

Software engineering topics

Programming languages
AdaAPLB
COBOLPascalCC++
C#ClojureCommon LispD
ColdFusionDelphiDylanEiffel
ErlangFortranF#Groovy
JavaLassoMLOCaml
PerlPHPPL/SQLProlog
GoRustSwiftJavaScript
HaskellPythonRubyScala
SchemeSmalltalkTclT-SQL
VerilogVHDLVisual BasicVisual Basic .NET
Assembly language • • • Scripting language • • • List of programming languages

Programming paradigm, based on a programming language technology

Databases

Graphical user interfaces

Programming tools

Libraries

Design languages

Patterns, document many common programming and project management techniques

Processes and methodologies

Platforms

A platform combines computer hardware and an operating system. As platforms grow more powerful and less costly, applications and tools grow more widely available.

Other Practices

Other tools

Computer science topics

Skilled software engineers know a lot of computer science including what is possible and impossible, and what is easy and hard for software.

Mathematics topics

Discrete mathematics is a key foundation of software engineering.

Other

Life cycle phases

Deliverables

Deliverables must be developed for many SE projects. Software engineers rarely make all of these deliverables themselves. They usually cooperate with the writers, trainers, installers, marketers, technical support people, and others who make many of these deliverables.

Business roles

Management topics

Business topics

Software engineering profession

History of software engineering

History of software engineering

Pioneers

Many people made important contributions to SE technologies, practices, or applications.

See also

Notable publications

  • About Face: The Essentials of User Interface Design by Alan Cooper, about user interface design. ISBN 0-7645-2641-3
  • The Capability Maturity Model by Watts Humphrey. Written for the Software Engineering Institute, emphasizing management and process. (See Managing the Software Process ISBN 0-201-18095-2)
  • The Cathedral and the Bazaar by Eric Raymond about open source development.
  • The Decline and Fall of the American Programmer by Ed Yourdon predicts the end of software development in the U.S. ISBN 0-13-191958-X
  • Design Patterns by Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides. ISBN 0-201-63361-2
  • Extreme Programming Explained by Kent Beck ISBN 0-321-27865-8
  • "Go To Statement Considered Harmful" by Edsger Dijkstra.
  • "Internet, Innovation and Open Source:Actors in the Network" — First Monday article by Ilkka Tuomi (2000) source
  • The Mythical Man-Month by Fred Brooks, about project management. ISBN 0-201-83595-9
  • Object-oriented Analysis and Design by Grady Booch. ISBN 0-8053-5340-2
  • Peopleware by Tom DeMarco and Tim Lister. ISBN 0-932633-43-9
  • The pragmatic engineer versus the scientific designer by E. W. Dijkstra
  • Principles of Software Engineering Management by Tom Gilb about evolutionary processes. ISBN 0-201-19246-2
  • The Psychology of Computer Programming by Gerald Weinberg. Written as an independent consultant, partly about his years at IBM. ISBN 0-932633-42-0
  • Refactoring: Improving the Design of Existing Code by Martin Fowler, Kent Beck, John Brant, William Opdyke, and Don Roberts. ISBN 0-201-48567-2
  • The Pragmatic Programmer: from journeyman to master by Andrew Hunt, and David Thomas. ISBN 0-201-61622-X
  • Software Engineering Body of Knowledge (SWEBOK) ISO/IEC TR 19759

See also:

See also

References

  1. Bourque, Pierre; Dupuis, Robert, eds. (2004). Guide to the Software Engineering Body of Knowledge - 2004 Version. IEEE Computer Society. p. 1. ISBN 0-7695-2330-7.
Professional organizations
Professionalism
Education
Standards
Government organizations
Agile
Other organizations
Demographics
Surveys
Other
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.