The Bellew-Norrie Method
A proposed software-design method for small teams that combines traceability, domain language, cohesion, low coupling, contracts, and invariant protection.
Summary
This document proposes the Bellew-Norrie Method as a software-design approach for small teams and companies developing new products. It combines Object-Oriented Software Engineering, Domain-Driven Design, Yourdon–Constantine structured design, and Design by Contract around six qualities: traceability, readability, cohesion, low coupling, explicit contracts, and invariant protection.
Using a grocery store’s online ordering system as a recurring example, the document explains how use cases, shared business terminology, focused components, controlled interfaces, and enforced domain rules can support future changes. It advocates concentrating design effort on core components while keeping temporary supporting utilities lightweight without duplicating or bypassing core rules.
The document presents a conceptual method supported by cited literature and illustrative examples. It does not report an empirical evaluation of the method.
Document context
The title page identifies:
- Author: Nathan Bellew
- Displayed date: October 25, 2026
“Norrie” appears in the method’s title, but the document does not list a second author. No institution, course, publication venue, peer-review status, thesis status, dissertation status, or numbered version is stated.
Topics covered
- requirements traceability through use cases;
- readable models based on shared domain terminology;
- cohesive component responsibilities;
- low coupling through defined interfaces and domain boundaries;
- explicit preconditions and postconditions;
- invariant protection through controlled domain updates.
The original PDF is embedded below without converting or rewriting its full text.
Original document
Read the supplied PDF in the embedded viewer or open it directly.