Skip to content

Software Engineering

← Back to Domain-Specific Abstractions by Domain

10 domain-specific abstractions whose origin domain is Software Engineering.

  • Behavior-Driven Development — Develop software through collaborative discovery of concrete behavior examples that become shared, automatable specifications linking business intent to observable system outcomes.
  • Forward-Deployed Engineer — A customer-embedded software engineer who owns the path from an organization’s open-ended operational problem through production implementation and adoption, while returning reusable field learning to the core product.
  • Magic number (programming) — A literal value embedded in program code whose purpose or provenance is not apparent from its local context, making behavior harder to understand and safely change.
  • Modular programming — A programming paradigm that decomposes software into cohesive units with explicit interfaces and limited dependence on one another.
  • Programming tool — Software whose primary functional role is to help create, inspect, transform, test, package or maintain other software.
  • Proxy Pattern — An object-design pattern in which an interface-compatible surrogate receives a client request, governs or mediates access, and delegates the admissible operation to a real subject.
  • Resource leak — Fail to release an acquired finite computing resource after its logical lifetime, causing retained ownership, exhaustion, or degraded availability across repeated execution.
  • Software quality assurance — Planned process-level activities that establish, monitor and audit standards, methods and evidence so software work products and engineering practices meet defined quality requirements.
  • Structured analysis — A systems-analysis method modeling required data transformations and control responses through hierarchical data-flow and related structured diagrams.
  • The Power of Ten: Rules for Developing Safety-Critical Code — Restrict safety-critical C to ten memorable, mechanically enforceable rules that bound control and resource behavior, localize review, expose contracts and errors, reduce indirection, and keep warning-based analysis continuously clean.