Software engineering
academic discipline that studies systematic approaches to developing software
Software engineering is a branch of both computer science and engineering focused on designing, developing, testing, and maintaining software applications. It involves applying engineering principles and computer programming expertise to develop software systems that meet user needs.
A software engineer applies a software development process to define, implement, test, manage, and maintain software systems.
History
Beginning in the 1960s, software engineering was recognized as a separate field of engineering.
The development of software engineering was seen as a struggle. Problems included software that was over budget, exceeded deadlines, required extensive debugging and maintenance, and failed to meet users' needs or was never even completed.
In 1968, NATO organized the first conference on software engineering, which addressed emerging challenges in software development
and played a key role in formalizing guidelines and best practices for creating reliable and maintainable software.
The origins of the term software engineering have been attributed to various sources. The term appeared in a list of services offered by companies in the June 1965 issue of "Computers and Automation" and was used more formally in the August 1966 issue of Communications of the ACM (Volume 9, number 8) in "President's Letter to the ACM Membership" by Anthony A. Oettinger. It is also associated with the title of a NATO conference in 1968 by Professor Friedrich L. Bauer.
The public source identifies “Software engineering” as academic discipline that studies systematic approaches to developing software. This brief keeps that definition visible, then builds a research path around Software, engineering and academic.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Software engineering”, the useful work is to connect “academic discipline that studies systematic approaches to developing software” to the records capable of establishing context and consequence.
The date and method of observation matter as much as the stated conclusion, especially where classification or consensus has changed. The source revision retrieved here is dated Sep 4, 2026. The linked authority identifier is Q80993. The Library of Congress control number is sh87007398. None of the 1 selected statements returned an explicit reference. The first chronological checks are 1968, 1965 and 1966.
Current terminology should not be projected backward without checking the classification used when the underlying evidence was created. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Check terminology, classification and the date of the cited evidence. Scientific names and technical consensus can change while older records retain historical value.
- Current terminology
- Classification context
- Finding cited technical literature
Primary datasets, specimen catalogues, standards bodies and the most recent peer-reviewed literature.
Three-step research path
- Establish the record: confirm the title “Software engineering”, its source revision and the description used here.
- Expand the search: follow Software engineering primary sources, Software engineering archive and Software research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Software engineering”?
- Is the terminology current, historical or disputed?
- Has classification or technical consensus changed since the cited source?
Search terms from this dossier
This entry incorporates text from “Software engineering” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.