Outline of software engineering

Print Print
Reading time 12:53

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 defacto standard classification system for the field. The major section "Software and its Engineering" provides an outline and ontology for software engineering.

Technologies and practices

Skilled software engineers use technologies and practices from a variety of fields to improve their productivity in creating software and to improve the quality of the delivered product.

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.

  • Business software
    • Accounting software
  • Analytics
  • Airline reservations
  • Banking
  • Commerce
    • Trade
    • Auctions (e.g. eBay)
    • Reverse auctions (procurement)
    • Bar code scanners
  • Compilers
  • Communication
    • E-mail
    • Instant messengers
    • VOIP
    • Calendars — scheduling and coordinating
    • Contact managers
  • Computer graphics
    • Animation
    • Special effects for video and film
    • Editing
    • Post-processing
  • Cryptography
  • Databases, support almost every field
  • Embedded systems Both software engineers and traditional engineers write software control systems for embedded products.
    • Automotive software
    • Avionics software
    • Heating ventilating and air conditioning (HVAC) software
    • Medical device software
    • Telephony
    • Telemetry
  • Engineering All traditional engineering branches use software extensively. Engineers use spreadsheets, more than they ever used calculators. Engineers use custom software tools to design, analyze, and simulate their own projects, like bridges and power lines. These projects resemble software in many respects, because the work exists as electronic documents and goes through analysis, design, implementation, and testing phases. Software tools for engineers use the tenets of computer science; as well as the tenets of calculus, physics, and chemistry.
  • File
    • FTP
    • File sharing
    • File synchronization
  • Finance
    • Bond market
    • Futures market
    • Stock market
  • Games
  • Information systems, support almost every field
    • LIS Management of laboratory data
    • MIS Management of financial and personnel data
  • Logistics
    • Supply chain management
  • Manufacturing
    • Computer Aided Manufacturing (CAM)
    • Distributed Control Systems (DCS)
  • Music
    • Music sequencers
    • Sound effects
    • Music synthesis
  • Network Management
    • Network management system
    • Element Management System
    • Operations Support System
    • Business Support Systems
  • Networks and Internet
  • Office suites
  • Operating systems
  • Robotics
  • Signal processing, encoding and interpreting signals
    • Image processing, encoding and interpreting visual information
    • Speech processing
    • Text recognition
    • Handwriting recognition
  • Simulation, supports almost every field.
    • Engineering, A software simulation can be cheaper to build and more flexible to change than a physical engineering model.
    • Sciences
  • Sciences
    • Genomics
  • Traffic Control
  • Training
    • Drill
    • Simulation
    • Testing
  • Visualization, supports almost every field
    • Architecture
    • Engineering
    • Sciences
  • Voting
  • World wide web

Software engineering topics

Many technologies and practices are (mostly) confined to software engineering, though many of these are shared with computer science.

Programming languages
COBOL Pascal C C++
C# Clojure Common Lisp D
ColdFusion Delphi Dylan Eiffel
Erlang Fortran F# Groovy
Java Lasso ML OCaml
Perl PHP PL/SQL Prolog
Go Rust Swift JavaScript
Haskell Python Ruby Scala
Scheme Smalltalk Tcl T-SQL
Verilog VHDL Visual Basic Visual Basic .NET
Assembly language • • • Scripting language • • • List of programming languages

Programming paradigm, based on a programming language technology


Graphical user interfaces

  • GTK+ GIMP Toolkit
  • wxWidgets
  • Ultimate++
  • Qt toolkit
  • FLTK

Programming tools


Design languages

Patterns, document many common programming and project management techniques

Processes and methodologies


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

  • Decision tables
  • Feature
  • User stories
  • Use cases

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.

  • Number representation
  • Set (computer science)
  • Bags
  • Graphs
    • Sequences
    • Trees
    • Graph (data structure)
  • Logic
    • Deduction
    • First-order logic
    • Higher-order logic
    • Combinatory logic
  • Induction
  • Combinatorics


  • Domain knowledge
  • Statistics
  • Decision theory
  • Type theory

Life cycle phases


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.

  • Application software — the software
  • Database — schemas and data.
  • Documentation, online and/or print, FAQ, Readme, release notes, Help, for each role
  • Administration and Maintenance policy, what should be backed-up, checked, configured, ...
  • Installers
  • Migration
    • Upgrade from previous installations
    • Upgrade from competitor's installations
  • Training materials, for each role
    • User
    • Administrator
    • Manager
    • Buyer
  • Support info for computer support groups.
  • Marketing and sales materials
    • White papers, explain the technologies used in the applications

Business roles

  • Operations
    • Users
    • Administrators
    • Managers
    • Buyers
  • Development
  • Business
    • Consulting — customization and installation of applications
    • Sales
    • Marketing
    • Legal — contracts, intellectual property rights
    • Privacy and Privacy engineering
    • Support — helping customers use applications
    • Personnel — hiring and training qualified personnel
    • Finance — funding new development
  • Academe
    • Educators
    • Researchers

Management topics

  • Leadership
    • Coaching
    • Communication
    • Listening
    • Motivation
    • Vision, SEs are good at this
    • Example, everyone follows a good example best
  • Human resource management
    • Hiring, getting people into an organization
    • Training
    • Evaluation
  • Project management
    • Goal setting
    • Customer interaction (Rethink)
    • Estimation
    • Risk management
    • Change management
  • Process management

Business topics

  • Quality programs
    • Malcolm Baldrige National Quality Award
    • Six Sigma
    • Total Quality Management (TQM)

Software engineering profession

  • Software engineering demographics
  • Software engineering economics
  • CCSE
  • History of software engineering
  • Software engineering professionalism
    • Ethics
    • Licensing
  • Legal

History of software engineering

History of software engineering


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

See also

  • List of programmers
  • List of computer scientists

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 [1]
  • 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:

Related fields

See also

  • Index of software engineering articles
  • Search-based software engineering
  • SWEBOK Software engineering body of knowledge
  • CCSE Computing curriculum for software engineering
  • Computer terms etymology, the origins of computer terms
  • Complexity or scaling
  • Second system syndrome
  • optimization
  • Source code escrow
  • Feature interaction problem
  • Certification (software engineering)
  • Engineering disasters#Failure due to software
  • Outline of software development


  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.

By: Wikipedia.org
Edited: 2021-06-18 19:18:16
Source: Wikipedia.org