EVOPEDIA

← all systems · see it in The System

Software engineering

Software engineering is a branch of both computer science and engineering focused on designing, developing, testing, and maintaining software applications (src:wp:software-engineering); 'programming integrated over time' (Software Engineering at Google, as quoted there). Whether it is engineering at all is contested (C-2260, C-3228).

Properties published scienceour proposal

Sourced fields, and our own readings.

born at1965-1968: the term in print (June 1965 Computers and Automation; August 1966 CACM) and the NATO conference, Garmisch, October 1968
born precisiona few years; contested (C-3227)
boundaryInside: the people, practices, records and processes by which software is specified, designed, built, tested, released and maintained (requirements, design, construction, testing, version control, process and management). Outside: the software product once running (sys:software), the machines (sys:computer), the users and domain it serves, the theory of computing (sys:computer-science).
nested levelA branch of both computer science and engineering (rung 12), carried by developers in organisations; it runs on people and organisations and produces software.
scalesocial

Measures (19) published science

OS/360 release interval90 days
Agile iteration (sprint) length1-4 weeks
Errors corrected in one OS/360 release1074 errors (plus 16 changes)
OS/360 corrections rate between versionsover 11 corrections per day
OS/360 development effortat least 5000 man-years
Maintenance share of project cost40-80 %
Communication paths in a team of n peopleabout n^2/2 paths
Professional software engineers worldwide26.9 million (2022); 21 million (2016) people
US software developers employed (BLS 2018)1,365,500 people
Standish 1994 project outcomes (contested)16 success / 53 challenged / 31 failed %
IT projects in the cost-overrun sample5,392 projects; overruns follow a power law, no calculable mean
Annual US cost of software bugs (NIST 2002)59.5 billion US dollars per year
Therac-25 overdose relative to normalup to 250 times
Change in task time with early-2025 AI tools (experienced open-source developers)+19 (forecast -24, felt afterwards -20) % completion time
Copilot trial: speed-up on an HTTP server task55.8 (95% CI 21-89) % faster
Causes of developer unhappiness identified219 (from 1,318 complete responses of 2,220 developers) factors
Group size range of superlinear open-source productivity5 to a few hundred developers
Scientists writing software who are primarily self-taught90 or more %
Languages with a significant defect association after reproduction4 (of 11 claimed) languages

Open contentions (9) open contention

Where sources or readings disagree. Both stay on the map.

Partners and parts published science

Built from / builds (8)

Sits inside / holds (3)

Trades with (valence) (12)

expressed by (22)

floor filled by (17)

Kinds (4)

Notes published science

Layers

The ways it takes in its world, where they meet, and how it acts back, each from L1 (where it meets the world) up.

building and keeping software over time, as software engineers describe it: from the world the software serves, through requirements, records, design, construction and process, to software released into use and evolved (reader's view)

  1. L1: The world the software serves and runs in: users and their activities, the machines, and the part of the world an E-type program mechanizes
  2. L2: Intake: requirements elicitation, tests run, failures and change requests reported from the field
  3. L3: Records: requirements specifications and backlogs, source code under version control, issue trackers, documentation
  4. L4: Deciding what to build or change: requirements analysis and design (interface, architectural, detailed)
  5. L5: Construction and verification: coding, code review, unit and integration testing, debugging
  6. L6: Process and coordination: the methodology (waterfall, spiral, agile), project management, estimation and the team's communication
  7. L7: Release and evolution: software delivered into use and kept fit through maintenance and continuing change; the discipline's purpose, reliable software obtained economically

the boardroom (shared floors)

  1. L4: Deciding what to build or change: requirements analysis and design at interface, architectural and detailed levels
  2. L5: Construction and verification: coding, review, testing, integration and debugging
  3. L6: Process and coordination: methodology, project management, estimation, the team's communication structure
  4. L7: Release and evolution: software delivered into use and continually adapted; the discipline's purpose, reliable software obtained economically

way in: AI assistants: code suggested by language models

  1. L1: Code suggested by an AI pair programmer
  2. L2: Suggestions accepted, edited or rejected in the editor

way in: Code read: source text seen on screens

  1. L1: Source text shown on a screen
  2. L2: The developer's eyes (Human's sight channel)
  3. L3: Program comprehension in the brain's multiple demand system, not the language system

way in: Emotion: happiness, unhappiness and being stuck

  1. L1: Work events: being stuck, time pressure, bad code, broken code
  2. L2: Unhappiness measured with a validated instrument
  3. L3: Affect perceived to raise or lower productivity

way in: Field: failures and change requests from software in use

  1. L1: Software in use, in an environment that keeps changing
  2. L2: Errors reported by users and installations
  3. L3: Errors and requests queued for the next release

way in: History: the repository's record of past changes

  1. L1: Source files and other hand-made files
  2. L2: The version control system records each revision
  3. L3: The history graph: trunk, branches and merges
  4. L4: Comparing and restoring past versions while changing code

way in: Literature and training: methods, bodies of knowledge, research

  1. L1: Written methods, standards and research
  2. L2: Education: degrees and training
  3. L3: The body of knowledge a graduate engineer is expected to master

way in: Money and schedule: budgets, estimates, deadlines

  1. L1: Funding and contracts
  2. L2: Estimates of cost, time and functionality
  3. L3: Overrun recorded against the estimate
  4. L4: The economic constraints among the requirements
  5. L5: Measuring progress

way in: Needs: what users, customers and the domain require

  1. L1: Users, customers and the part of the world the program mechanizes
  2. L2: Elicitation: interviews and customer collaboration
  3. L3: Requirements specified: functional, non-functional and domain requirements

way in: Review: colleagues' comments on a change

  1. L1: A proposed change and colleagues' written comments
  2. L2: Comments on defects, design and style
  3. L3: Understanding the change and its context
  4. L4: Knowledge transfer and team awareness

way in: Team talk: what everyone else is doing

  1. L1: Speech and messages between team members
  2. L2: Meetings: the daily stand-up's coded questions
  3. L3: Keeping in sync: knowing what everyone else is doing
  4. L4: Communication paths: about half the square of the number of people
  5. L5: The organisation's communication structure, which resembles its administrative structure where protocol restricts it

way in: Tests: the program run against expectations

  1. L1: The program executed on a machine
  2. L2: Test cases and harnesses compare behaviour with expectation
  3. L3: Failures and regressions recorded
  4. L4: Debugging: locating the cause of a failure

way in: Thought: the problem held in mind

  1. L1: The problem and the program held in one mind, within the limited size of one's skull (where ideas come from: contested, C-413)
  2. L4: Abstraction and intellectually manageable programs, within the limited size of one's skull

way out: Documenting and specifying

  1. L1: Documents and specifications
  2. L4: A design to hand on

way out: Publishing methods and bodies of knowledge

  1. L1: Published manifesto, standards and papers
  2. L7: Ways of developing software worked out in practice

way out: Releasing: software delivered into use

  1. L1: Running software among its users
  2. L6: Releases on a cadence (OS/360: every 90 days)
  3. L7: Early and continuous delivery of valuable software

way out: Talking: stand-ups, reviews and design discussion

  1. L1: Speech and messages
  2. L6: Information to share with the team

way out: Writing code: typed changes committed to the repository

  1. L1: Source text in files
  2. L2: Typing at a keyboard (Human's movement outlet)
  3. L3: Incremental changes committed as revisions
  4. L5: A change designed and ready to make

Sources (33) published science

Engineering (Wikipedia, via Wikimedia Enterprise cache, revision of 2026-10-21)
Software engineering (Wikipedia, Wikimedia Enterprise snapshot 2026-11-01 via tools/wme)
Waterfall model (Wikipedia, Wikimedia Enterprise snapshot 2026-11-01 via tools/wme) (behind its links)
Naur & Randell (eds.) 1969, Software Engineering: Report on a conference sponsored by the NATO Science Committee, Garmisch, 7-11 October 1968 (behind its links)
Lehman's laws of software evolution (encyclopedia) (behind its links)
Cunningham 1992, The WyCash Portfolio Management System, OOPSLA '92 experience report (behind its links)
Brooks's law (Wikipedia, Wikimedia Enterprise snapshot 2026-11-01 via tools/wme) (behind its links)
Beck K et al. (2001) Principles behind the Agile Manifesto (behind its links)
Conway ME (1968) How Do Committees Invent? Datamation, April 1968 (author's reprint) (behind its links)
Software crisis (encyclopedia) (behind its links)
Bacchelli A, Bird C (2013) Expectations, Outcomes, and Challenges of Modern Code Review. ICSE 2013 (authors' copy) (behind its links)
Computer science (Wikipedia, via Wikimedia Enterprise snapshot 2026-11-01) (behind its links)
Agile software development (Wikipedia, Wikimedia Enterprise snapshot 2026-11-01 via tools/wme) (behind its links)
Eveleens JL, Verhoef C (2010) The Rise and Fall of the Chaos Report Figures. IEEE Software 27(1):30-36 (authors' copy) (behind its links)
Flyvbjerg B et al. (2022) The Empirical Reality of IT Project Cost Overruns: Discovering a Power-Law Distribution. J Management Information Systems 39(3):607-639, doi:10.1080/07421222.2022.2096544 (arXiv:2210.01573) (behind its links)
Software testing (encyclopedia) (behind its links)
Therac-25 (encyclopedia) (behind its links)
Becker J, Rush N, Barnes B, Rein D (2025) Measuring the Impact of Early-2025 AI on Experienced Open-Source Developer Productivity. arXiv:2507.09089 (behind its links)
Peng S, Kalliamvakou E, Cihon P, Demirer M (2023) The Impact of AI on Developer Productivity: Evidence from GitHub Copilot. arXiv:2302.06590 (behind its links)
Graziotin D, Fagerholm F, Wang X, Abrahamsson P (2017) On the Unhappiness of Software Developers. EASE '17 (arXiv:1703.04993) (behind its links)
Sornette D, Maillart T, Ghezzi G (2014) How much is the whole really more than the sum of its parts? 1+1=2.5: superlinear productivity in collective group actions. PLoS ONE 9(8):e103023, doi:10.1371/journal.pone.0103023 (behind its links)
Wilson G et al. (2014) Best Practices for Scientific Computing. PLoS Biol 12(1):e1001745, doi:10.1371/journal.pbio.1001745 (behind its links)
Berger ED, Hollenbeck C, Maj P, Vitek O, Vitek J 2019. On the impact of programming languages on code quality: a reproduction study. arXiv:1901.10220 (TOPLAS) (behind its links)
Version control (encyclopedia) (behind its links)
Brooks, No Silver Bullet: Essence and Accidents of Software Engineering, UNC technical report TR86-020 (1986) (behind its links)
Ivanova et al. 2020, Comprehension of computer code relies primarily on domain-general executive brain regions, eLife 9:e58906, doi:10.7554/eLife.58906 (behind its links)
Dijkstra EW (1972) The Humble Programmer (EWD340), ACM Turing Award Lecture, Communications of the ACM 15(10) (transcription) (behind its links)
MacCormack A, Rusnak J, Baldwin C (2012) Exploring the Duality between Product and Organizational Architectures: A Test of the 'Mirroring' Hypothesis. Research Policy 41:1309-1324 (HBS Working Paper 08-039) (behind its links)
Raymond ES (1998) The cathedral and the bazaar. First Monday 3(3). doi:10.5210/fm.v3i2.578 (behind its links)
Software development process (Wikipedia, Wikimedia Enterprise snapshot 2026-11-01 via tools/wme) (behind its links)
Royce WW (1970) Managing the development of large software systems. Proceedings, IEEE WESCON, August 1970 (behind its links)
Beck K et al. (2001) Manifesto for Agile Software Development (behind its links)
Maillart T, Sornette D. 2016. Aristotle vs. Ringelmann: on superlinear production in open source software. arXiv:1608.03608 (behind its links)