Preface
- Who should read this book? And why?
- Methods: The good, the bad, and the why
- General method adoption principle: Be pragmatic!
- The templates
- Book content
- The GitHub repository companion to this book
- Current status of book and repository
- About the authors
Introduction
- Content organization and terminology
- Overview and dependencies (steps)
- Quick links (getting started)
- Other method/practice collections
Activities Reference
- Architectural Decision Capturing
- Architecture Modeling
- SMART Non-Functional Requirement (NFR) Elicitation
- Story Splitting
- Strategic Domain-Driven Design (DDD)
- Tactic(al) Domain-Driven Design (DDD)
- User Interface Mocking
- Stepwise Service Design
Artifacts Reference
- Architectural Decision Record (Y-Statement)
- Components, Responsibilities, Collaborations (CRC) Card
- Component Diagram
- Context Diagram
- Deployment Diagram
- Domain Model
- Overview Diagram
- Quality Attribute Scenario (QAS)
- DDD Context Map
- Use Case (Model)
- User Stories
- API Description
- Candidate Endpoint List (CEL)
- Refined Endpoint List (REL)
- Service Level Agreement (SLA)
Roles Reference
- Application and Integration Architect
- API Product Owner
Examples of Design Practices in Action
- Story 1: Architectural decision capturing matters
- Story 2: User stories vs. use cases vs. both
- Story 3: “Patterns for API Design” and its Lakeside Mutual case study
- More examples
Critical Review and Discussion
- When and when not to go “deeper”
- Where to start exploring?
- Really mighty and enabling?