Design Practice Reference: Guides and Templates to Craft Quality Software in Style

This document was uploaded by one of our users. The uploader already confirmed that they had the permission to publish it. If you are author/publisher or own the copyright of this documents, please report to us by using this DMCA report form.

Simply click on the Download Book button.

Yes, Book downloads on Ebookily are 100% Free.

Sometimes the book is free on Amazon As well, so go ahead and hit "Search on Amazon"

A collection of proven software engineering and architecture design method elements to accelerate project work and reduce technical risk. Suited for API design and microservice architectures. Activity descriptions and artifact templates for non-functional requirements, domain models, architectural decision records, API contracts (sample content). DPR (pronounced "deeper") collects artifact templates and practices from engineering methods (old and new) that are applicable to service-oriented analysis and design (and beyond)

Author(s): Olaf Zimmermann; Mirko Stocker
Publisher: Leanpub
Year: 2021

Language: English

Table of Contents
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 to DPR
Content Organization and Terminology
Overview and Dependencies (Steps)
Quick Links (Getting Started)
Other Method/Practice Collections
Activities Reference
Architectural Decision Capturing
Architecture Modeling
SMART 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
Domain Model
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 DPR 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?
Done with DPR: What's Next?
Bibliography
Cheat Sheet
Backlog of Missing Method Elements
Copyright, Trademarks, Disclaimers