This appendix lists every tool that the ten earlier volumes of The Transformed Architecture describe, as recorded in data/tool_inventory.jsonl. An entry gives the tool as its book names it, the book and chapters where it appears, the identifier family where there is one, and the chapter of this book that treats it. The list is generated by scripts/generate_outlines.py; edit the inventory, not this file. The repository's own publishing scripts are listed in Appendix B.
The catalogue has 1402 entries.
Primary topics explored
- Artefacts
- Own tools
- Third-party tools and standards
- Methods
About Tools
Tools is a companion to The Transformed Architecture. It collects the tools that Books 1 to 10 describe in one reference, organised by what the practitioner is doing: artefacts (templates, manifests, records), own tools, third-party tools and standards, and methods. Each entry says what a tool is for, when to use it, what it needs and produces, and where the book that defines it explains the reasoning. The book covers choosing, adopting and retiring tools, architecture and delivery, governing AI, securing and testing, operating, agents and autonomy, and people, organisation and society, for European enterprises and public authorities. It comes with a template library, an inventory, three web tools and the Toolbox Maturity Method.
It builds on the conclusions of Architecture as Code, AI Governance, AI Platform and Security, AI Red Team, AI Threat, The Transformed Security Architect, AI Boss, AI Blue, AI Purple and AI Operations.
Architects and security architects, CIOs and CISOs, platform and operations leads, heads of governance, risk, compliance and third-party risk, AI governance and AI platform teams, red, blue and purple team leads, boards and management bodies, procurement and vendor managers, supervisors and auditors, works councils and unions, data protection officers, and public-sector leaders.
Continue with the full chapter
Appendix A: Appendix A: The Catalogue of Tools of the Series in Tools gives the detailed explanations, practical examples and implementation patterns behind this summary.
This whitepaper belongs to “Appendices” and is one of 29 drawn from the manuscript.