Software Engineering

Software Engineering addresses process, methods, and tools for building reliable software systems. It sits within Programming and Languages and inherits that area’s core questions about correctness, scale, and tractability. This page surveys the conceptual axes of the topic and points to the references that frame ongoing research and teaching. The intent is to be useful both as an entry point for newcomers and as an index for practitioners cross-checking their mental model against the field’s primary sources.

Work on software engineering can be organised around a few interlocking concerns: the formal objects under study, the algorithms or systems that compute over them, the resource trade-offs (time, memory, communication, statistical efficiency), and the empirical or theoretical guarantees that practitioners rely on. The sources cited below approach the topic from a mix of these angles.

Foundational references

Sommerville, Software Engineering (2015) is a standard reference for this material and is used both as a curriculum anchor and as a long-form survey of techniques.

Supporting and complementary work

Winters, Software Engineering at Google (2020) provides supporting material that complements the primary references — readers comparing approaches will find useful framings, alternative notations, or extensions there. Martin, Clean Code (2008) provides supporting material that complements the primary references — readers comparing approaches will find useful framings, alternative notations, or extensions there.

Open methodological questions in software engineering cluster around how to compose the techniques above under realistic constraints — scale, adversarial inputs, partial observability, and shifting workloads. The cited references give the precise statements, proofs, and empirical evaluations that this overview only sketches; downstream topic pages drill into specific subfields.