Throughout this book, we have introduced new, and sometimes radical, ideas for how to approach software design. Many of these ideas are about thinking differently, using different language, and reconsidering the very job of software designers as what we used to call “architects.”
Accompanying these ideas we have introduced many templates as well. These serve to bring this new approach of deconstructive software design into a pragmatic, practical realm so that you can apply it today in your own work. Deconstructive design is more a mindset and a “way of life” than a silver bullet; I don’t advertise it as a silver bullet. It’s hard work. You’ll likely spend some time swimming upstream of your corporate culture to change how you approach software design in this new way.
These are the key components, templates, checklists, scorecards, and practical frameworks, that together form the semantic designer’s toolbox. You can download the toolbox at https://aletheastudio.com.
For these, see Chapter 5.
Mural
Vision box
Mind map
Use cases
Principles
Position paper
Approach document
RAID
Design Definition Document
These tools help capture the ideas in Chapter 6:
Business glossary
Business capabilities model
Process map
System inventory
These are in Chapter 7:
Guidelines list
These are the toolbox components in Chapters 10 and 11:
Role of architect
Lateral thinking guide
Operational scorecard
Service-oriented organization template
Scalable business machine template
Program management framework
Change management framework
Governance framework
Service design checklist
In Chapter 12, the manifesto, the following is offered:
Deconstruction design practice list
Together, these templates, frameworks, scorecards, and lists together form a complete and practical semantic designer’s toolbox.