References and Sources
This section provides a comprehensive list of all sources and references cited throughout the book, compiled in alphabetical order for ease of reference. Each entry includes information about which chapters reference the source.
Numbered source index
- Source [4]: GitHub Docs. About protected branches. GitHub Documentation, 2024. Referenced in: Chapter 03: Version Control and Code Structure, Chapter 11: Governance as Code, Chapter 14: Practical Implementation, Chapter 23: Software as Code Interplay.
- Source [7]: Cloud Native Computing Foundation. State of Cloud Native Development 2024. Cloud Native Computing Foundation, 2024. Referenced in: Chapter 7: Containerisation and Orchestration as Code.
- Source [8]: Google Cloud. The Site Reliability Workbook: Practical Ways to Implement SRE. O'Reilly Media, 2018. Referenced in: Chapter 05: Automation, DevOps and CI/CD.
- Source [9]: AWS. AWS Cloud Development Kit (CDK) Developer Guide. Amazon Web Services, 2024. Referenced in: Chapter 03: Version Control and Code Structure, Chapter 05: Automation, DevOps and CI/CD, Chapter 14: Practical Implementation.
- Source [12]: Microsoft Learn. Design multi-stage release pipelines with approvals. Microsoft Learn Documentation, 2024. Referenced in: Chapter 05: Automation, DevOps and CI/CD.
- Source [15]: Pulumi. Testing Infrastructure as Code Programs. Pulumi Blog, 2024. Referenced in: Chapter 13: Testing Strategies for Infrastructure as Code.
- Source [16]: HashiCorp. Securing Terraform State. HashiCorp Developer Documentation, 2024. Referenced in: Chapter 9: Security Fundamentals for Architecture as Code, Chapter 9b: Advanced Security Patterns and Implementation.
- Source [17]: HashiCorp. Backend Type: s3. HashiCorp Developer Documentation, 2024. Referenced in: Chapter 9: Security Fundamentals for Architecture as Code, Chapter 9b: Advanced Security Patterns and Implementation.
- Source [18]: Microsoft Learn. Store Terraform state in Azure Storage. Microsoft Learn Documentation, 2024. Referenced in: Chapter 9: Security Fundamentals for Architecture as Code, Chapter 9b: Advanced Security Patterns and Implementation.
- Source [19]: Google Cloud. Store Terraform state in Cloud Storage. Google Cloud Documentation, 2024. Referenced in: Chapter 9: Security Fundamentals for Architecture as Code, Chapter 9b: Advanced Security Patterns and Implementation.
- Source [20]: HashiCorp. Terraform Security Best Practices. HashiCorp Learning Resources, 2023. Referenced in: Chapter 9: Security Fundamentals for Architecture as Code, Chapter 9b: Advanced Security Patterns and Implementation.
Academic and Industry Publications
AaC Open Source Project. "Architecture-as-Code Repository." https://github.com/aacplatform/aac Referenced in: Chapter 6: Structurizr and Diagram Automation, Appendix B: Technical Architecture for Book Production
Architecture Decision Records Community. "ADR Guidelines and Templates." https://adr.github.io
Referenced in: Chapter 4: Architecture Decision Records
Atlassian. "Documentation as Code: Treating Docs as a First-Class Citizen." Atlassian Developer, 2023. Referenced in: Chapter 2: Fundamental Principles
Atlassian. "Git Workflows for Architecture as Code." Atlassian Git Documentation. Referenced in: Chapter 3: Version Control
Brown, S. "C4 Model Overview." https://c4model.com/
Referenced in: Chapter 6: Structurizr and Diagram Automation, Chapter 24: Best Practices
Brown, S. "Documenting Software Architecture with Structurizr." Structurizr Blog, 2022.
Referenced in: Chapter 6: Structurizr and Diagram Automation, Chapter 24: Best Practices
Brown, S. "Software Architecture for Developers." Leanpub, 2024.
Referenced in: Chapter 6: Structurizr and Diagram Automation
Chung, L., et al. "Non-Functional Requirements in Software Engineering." Springer, 2000.
Referenced in: Chapter 2: Fundamental Principles
Cloud Native Computing Foundation. "State of Cloud Native Development 2024." Cloud Native Computing Foundation, 2024. (Source [7]) Referenced in: Chapter 1: Introduction, Chapter 7: Containerisation
FINOS. "CALM: Common Architecture Language Model." FINOS Architecture as Code Community, 2024. https://calm.finos.org/
Referenced in: Chapter 22: Documentation as Code vs Architecture as Code
Ford, Neal et al. "Building Evolutionary Architectures." O'Reilly Media, 2017.
Referenced in: Chapter 22: Documentation as Code vs Architecture as Code
Forsberg, K., Mooz, H. "The Relationship of System Engineering to the Project Cycle." Engineering Management Journal, 1991. Referenced in: Chapter 2: Fundamental Principles
GitLab. "Documentation as Code: Best Practices and Implementation." GitLab Documentation, 2024.
Referenced in: Chapter 2: Fundamental Principles
GitLab. "Building a Single Source of Truth with APIs and CLI." GitLab Topics, 2024.
Referenced in: Chapter 2: Fundamental Principles, Chapter 11: Governance as Code
GitHub Docs. "About protected branches." https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/about-protected-branches Referenced in: Chapter 03: Version Control and Code Structure, Chapter 11: Governance as Code, Chapter 14: Practical Implementation, Chapter 23: Software as Code Interplay
GitHub Open Source Community. "Collaborative Software Development." Platform Documentation, 2024. Referenced in: About the Author
IEEE. "IEEE Standard for Software Verification and Validation." IEEE Std 1012-2016, 2017. Referenced in: Chapter 2: Fundamental Principles
HashiCorp. "Policy as Code Overview." https://developer.hashicorp.com/terraform/enterprise/policy-as-code
Referenced in: Chapter 23: Software as Code Interplay
Kvadrat AB. "Gunnar Nordqvist - Chief Architect Profile." Konsultprofil, 2024. Available at: https://www.kvadrat.se/anlita-kvadrat/hitta-konsult/gunnar-nordqvist/
Referenced in: About the Author
Kvadrat AB. "Technology Consulting Excellence." Company Profile, 2024. Available at: https://www.kvadrat.se/
Referenced in: About the Author
MarketsandMarkets. "Infrastructure as Code Market Report." MarketsandMarkets, 2023.
Referenced in: Chapter 15: Cost Optimisation, Chapter 25: Future Trends Development
Martin, R. "Clean Architecture: A Craftsman's Guide to Software Structure." Prentice Hall, 2017.
Referenced in: Chapter 1: Introduction, Chapter 2: Fundamental Principles
Mermaid. "Mermaid: Diagramming and Charting Tool." Mermaid Documentation, 2024. https://mermaid.js.org/
Referenced in: Chapter 22: Documentation as Code vs Architecture as Code
NIST. "Requirements Engineering for Secure Systems." NIST Special Publication 800-160, 2023.
Referenced in: Chapter 2: Fundamental Principles
Nygard, M. "Documenting Architecture Decisions." 2011.
Referenced in: Chapter 4: Architecture Decision Records
Open Policy Agent. "Policy as Code: Expressing Requirements as Code." CNCF OPA Project, 2024.
Referenced in: Chapter 2: Fundamental Principles
Open Policy Agent. "Policy as Code Overview." https://www.openpolicyagent.org/docs/latest/
Referenced in: Chapter 11: Governance as Code, Chapter 23: Software as Code Interplay
OMG. "Model Driven Architecture (MDA)." Object Management Group White Paper, 2001.
Referenced in: Chapter 2: Fundamental Principles
PlantUML. "PlantUML: Open-source Tool for Creating UML Diagrams." PlantUML Documentation, 2024. https://plantuml.com/
Referenced in: Chapter 22: Documentation as Code vs Architecture as Code
Red Hat. "Architecture as Code Principles and Best Practices." Red Hat Developer.
Referenced in: Chapter 2: Fundamental Principles
Richardson, C. "Microservices Patterns: With Examples in Java." Manning Publications, 2018.
Referenced in: Chapter 22: Documentation as Code vs Architecture as Code
Schmidt, D. C. "Model-Driven Engineering." IEEE Computer, 2006.
Referenced in: Chapter 2: Fundamental Principles
Selic, B. "The Pragmatics of Model-Driven Development." IEEE Software, 2003.
Referenced in: Chapter 2: Fundamental Principles, Chapter 6: Structurizr and Diagram Automation, Chapter 23: Software as Code Interplay
Structurizr. "Structurizr DSL Language Reference." Structurizr Documentation, 2024. https://github.com/structurizr/dsl
Referenced in: Chapter 6: Structurizr and Diagram Automation, Chapter 22: Documentation as Code vs Architecture as Code
Structurizr. "Structurizr Lite." Structurizr Documentation, 2024. https://structurizr.com/help/lite
Referenced in: Chapter 6: Structurizr and Diagram Automation
ThoughtWorks Technology Radar. "Diagrams as Code." https://www.thoughtworks.com/radar/techniques/diagrams-as-code
Referenced in: Chapter 6: Structurizr and Diagram Automation
ThoughtWorks. "Architecture as Code: The Next Evolution." Technology Radar, 2024. Referenced in: Chapter 1: Introduction, Chapter 2: Fundamental Principles, About the Author
ThoughtWorks. "Architecture Decision Records." Technology Radar, 2023.
Referenced in: Chapter 4: Architecture Decision Records
Thoughtworks Technology Radar. "Governance as Code." https://www.thoughtworks.com/radar/techniques/governance-as-code
Referenced in: Chapter 11: Governance as Code
Industry Research and Reports
AWS. "AWS Cloud Development Kit (CDK) Developer Guide." https://docs.aws.amazon.com/cdk/latest/guide/home.html Referenced in: Chapter 03: Version Control and Code Structure, Chapter 5: Automation, DevOps, and CI/CD, Chapter 14: Practical Implementation
Best practice documentation from leading organisations.
Referenced in: Chapter 27: Conclusion
Expert interviews and case studies.
Referenced in: Chapter 27: Conclusion
Gartner. "Forecast Analysis: Public Cloud Services Worldwide." Gartner Research, 2024.
Referenced in: Chapter 15: Cost Optimisation, Chapter 17: Organisational Change
Industry reports on Architecture as Code adoption trends.
Referenced in: Chapter 27: Conclusion
IDC. "Worldwide DevOps Software Tools Forecast, 2023–2027." IDC Research, 2023.
Referenced in: Chapter 5: Automation, DevOps, and CI/CD, Chapter 21: Digitalisation
Research on emerging technologies.
Referenced in: Chapter 27: Conclusion
Google Cloud. "Store Terraform state in Cloud Storage." Google Cloud Documentation, 2024. https://cloud.google.com/docs/terraform/resource-management/store-terraform-state (Source [19]) Referenced in: Chapter 9: Security Fundamentals for Architecture as Code, Chapter 9b: Security Patterns and Implementation
HashiCorp. "Backend Type: s3." HashiCorp Developer Documentation, 2024. https://developer.hashicorp.com/terraform/language/settings/backends/s3 (Source [17]) Referenced in: Chapter 9: Security Fundamentals for Architecture as Code, Chapter 9b: Security Patterns and Implementation
HashiCorp. "Securing Terraform State." HashiCorp Developer Documentation, 2024. https://developer.hashicorp.com/terraform/cloud-docs/state/securing (Source [16]) Referenced in: Chapter 9: Security Fundamentals for Architecture as Code, Chapter 9b: Security Patterns and Implementation
HashiCorp. "State of Cloud Strategy Survey 2024." HashiCorp, 2024.
Referenced in: Chapter 17: Organisational Change, Chapter 27: Conclusion
HashiCorp. "Terraform Security Best Practices." HashiCorp Learning Resources, 2023. https://developer.hashicorp.com/terraform/cloud-docs/recommended-practices/security (Source [20]) Referenced in: Chapter 9: Security Fundamentals for Architecture as Code, Chapter 9b: Security Patterns and Implementation
Microsoft Learn. "Store Terraform state in Azure Storage." Microsoft Learn Documentation, 2024. https://learn.microsoft.com/en-gb/azure/developer/terraform/store-state-in-azure-storage (Source [18]) Referenced in: Chapter 9: Security Fundamentals for Architecture as Code, Chapter 9b: Security Patterns and Implementation
Pulumi. "Testing Infrastructure as Code Programs." Pulumi Blog, 2024. (Source [15]) Referenced in: Chapter 13: Testing Strategies, Chapter 14: Practical Implementation
Using This References Section
This comprehensive list ensures traceability between the book's content and its sources. When reading a chapter:
- Check the chapter's "Sources" section for immediate context
- Refer to this comprehensive list for full bibliographic details
- Use the cross-references to find related discussions across chapters
All citations in the manuscript are included in this compiled list, ensuring complete transparency and academic rigour throughout the work.