Kanban

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.

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.

Clean Architecture

A software design philosophy separating concerns into layers with dependencies pointing inward toward business rules.

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.

A design pattern that prevents cascading failures by stopping calls to a failing service temporarily.

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

A software practice where code changes can be released to production at any time through automated pipelines.

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

A technique for controlling the number of requests a client can make to an API within a specified time period.

A deployment strategy using two identical production environments to achieve zero-downtime releases.

A design pattern where dependencies are provided to a component rather than created within it.

Evaluating a system's speed, responsiveness, and stability under various load conditions.