Computer Science

From bradwiki
Revision as of 01:10, 4 April 2026 by Bradley Monk (talk | contribs) (Created page with "== Conceptual & Structural Systems == (How software is *organized* at a high level) * '''Architecture''' – The fundamental structure of a system: components, responsibilities, and relationships. * '''Design Pattern''' – Reusable solutions to recurring structural or behavioral problems. * '''System Design''' – End-to-end planning of components, data flow, scaling, and failure modes. * '''Platform''' – A base system upon which other software or se...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Conceptual & Structural Systems

(How software is *organized* at a high level)

  • Architecture – The fundamental structure of a system: components, responsibilities, and relationships.
  • Design Pattern – Reusable solutions to recurring structural or behavioral problems.
  • System Design – End-to-end planning of components, data flow, scaling, and failure modes.
  • Platform – A base system upon which other software or services are built.
  • Ecosystem – Interacting tools, libraries, services, and users around a platform.
  • Stack – A layered collection of technologies used together (e.g., LAMP, MERN).
  • Subsystem – A self-contained functional unit within a larger system.
  • Module – A discrete, replaceable unit of functionality.
  • Component – A deployable or reusable unit with a defined interface.


Code Reuse & Capability Systems

(Things you *build with*)

  • Framework – Opinionated structure that controls application flow.
  • Library – Reusable code invoked by the developer.
  • SDK (Software Development Kit) – Tools, libraries, docs, and examples for a platform.
  • API – A formal interface for interacting with a system or service.
  • Middleware – Software that connects or mediates between systems.
  • Runtime – The environment in which code executes.
  • Plugin System – Mechanism for extending a host application.
  • Extension – Add-on module that enhances functionality.
  • Package – A distributable unit of code.
  • Dependency – External code required by a system.


Execution & Environment Systems

(Where software *runs*)


Development & Tooling Systems

(How developers *work*)

  • IDE – (Integrated Development Environment) Unified coding, debugging, and tooling system.
  • Editor – Code authoring environment.
  • Build System – Automates compilation, linking, and packaging.
  • Toolchain – Collection of compilers, linkers, debuggers, etc.
  • Package Manager – Manages dependencies and versions.
  • Task Runner – Automates development workflows.
  • Debugger – Inspection and control of execution.
  • Profiler – Performance measurement system.
  • Linter – Static analysis and style enforcement.
  • Formatter – Code layout normalization system.


Data & State Systems

(How information is *stored and managed*)


Distributed & Service Systems

(How software *communicates*)


Deployment & Operations Systems

(How software *lives in the world*)


Security & Governance Systems

(How systems *protect themselves*)


AI-Specific System Terms (given your recent work)

(Modern “systems” framing)