An architecturally-evident coding style: making your design visible in your code

Authors:
George H. Fairbanks
Affiliations:
Rhino Research
Venue:
Proceedings of the ACM international conference companion on Object oriented programming systems languages and applications companion
Year:
2010

Citing 3
Cited 0

Smalltalk: best practice patterns

Smalltalk: best practice patterns
Architecture, design, implementation

Proceedings of the 25th International Conference on Software Engineering
Domain-Driven Design: Tacking Complexity In the Heart of Software

Domain-Driven Design: Tacking Complexity In the Heart of Software

Quantified Score

Hi-index	0.00

Visualization

Abstract

Because of Eric Evans' Domain Driven Design, software developers are already familiar with embedding their domain models in their code. But the architecture and design is usually hard to see from the code. How can you improve that? This tutorial describes an architecturally-evident coding style that lets you drop hints to code readers so that they can correctly infer the design. You will learn why some design intent (the intensional part) is always lost between your design/architecture and your code. It builds upon ideas like Kent Beck's Intention Revealing Method Name pattern and provides a set of lightweight coding patterns and idioms that let you express your design intent in the code.