Software Engineering & Development Methodologies
Software Engineering & Development Methodologies
Software engineering is an engineering approach to developing, operating, and maintaining software through systematic and disciplined methods.
This section covers 14 topics.
Introduction to this section and its core frameworks.
- Agile: An umbrella term for iterative software development methodologies that value people and communication and responsiveness to change over rigid plans and…
A methodology developed by David J. Anderson that applies Toyota’s kanban system to knowledge work — a flow-based work management system that detects bottlenecks and…
A development philosophy created by Mary and Tom Poppendieck by applying the Lean philosophy of the Toyota Production System (TPS) to software development — based on…
An Agile-based software development methodology proposed by Jeff De Luca that systematically manages large-scale projects through a five-phase process — developing an…
- TDD (Test-Driven Development): A development methodology in which a failing unit test is written first, before the implementation code, followed by writing the…
A development methodology that extends TDD to the business perspective. It specifies the behavior a system must exhibit as Given-When-Then natural-language scenarios…
An organizational culture and methodology that emphasizes communication, collaboration, and integration between software Development and Operations, enabling faster,…
A staged set of guidelines and integrated process maturity model for evaluating and improving an organization’s software development and service process capability.
A methodology for solving complex business problems by placing the model and logic of the business domain — rather than the technical implementation — at the center…
Five core principles of object-oriented design established by Robert C. Martin — Single Responsibility (SRP), Open/Closed (OCP), Liskov Substitution (LSP), Interface…
A body of design knowledge consisting of 23 software design patterns cataloged by Erich Gamma and three co-authors (the ‘Gang of Four’), classifying proven solutions…
An architecture proposed by Robert C. Martin whose core principle is the Dependency Rule — ‘source code dependencies must point only inward, toward policy’ — a…
A software architecture style that decomposes a single large application into small, independently deployable service units that interact with one another through APIs.