Clean Architecture

Software Engineering

The systematic application of engineering principles to the design, development, testing, and maintenance of software.

Agile Methodology

An iterative approach to software development emphasising flexibility, collaboration, and rapid delivery of working software.

Scrum

An agile framework using fixed-length iterations called sprints for incremental product delivery with defined roles and ceremonies.

Kanban

A visual workflow management method that limits work in progress and optimises the flow of tasks through a system.

Waterfall Model

A sequential software development methodology where each phase must be completed before the next begins.

Technical Architecture

The design and structure of a software system's technical components and their relationships.

Design Pattern

A reusable solution to a commonly occurring problem within a given context in software design.

SOLID Principles

Five principles of object-oriented design promoting maintainable, flexible, and understandable code.

Domain-Driven Design

A software design approach focusing on modelling the business domain and aligning code with business logic.

Stress Testing

Testing a system beyond normal operational capacity to determine its breaking point and failure behaviour.

Technical Documentation

Written materials describing the architecture, design, APIs, and usage of software systems.

Database Design

The process of defining the structure, storage, and retrieval of data in a database system.

Storing frequently accessed data in a fast-access storage layer to reduce latency and improve performance.

A development approach where application behaviour is described in a natural language format before implementation.

An extension of continuous integration where code changes are automatically deployed to production after passing tests.

A systematic examination of source code by developers other than the author to identify bugs and improve quality.

A system that records changes to files over time so that specific versions can be recalled later.

A development practice where code changes are automatically built and tested when merged to a shared repository.

Testing individual components or functions in isolation to verify they produce the expected output.

A deployment strategy where changes are gradually rolled out to a small subset of users before full deployment.