arc42 by Example

(ebook) (audiobook) (audiobook)

Autorzy:: Dr. Gernot Starke, Michael Simons, Stefan Zörner, Ralf D. Müller

arc42 by Example Dr. Gernot Starke, Michael Simons, Stefan Zörner, Ralf D. Müller - okładka książki

arc42 by Example Dr. Gernot Starke, Michael Simons, Stefan Zörner, Ralf D. Müller - okładka audiobooka MP3

arc42 by Example Dr. Gernot Starke, Michael Simons, Stefan Zörner, Ralf D. Müller - okładka audiobooks CD

Wydawnictwo:: Packt Publishing (Z chęcią przeczytam książkę w języku polskim)
Ocena:: Bądź pierwszym, który oceni tę książkę
Stron:: 236
Dostępne formaty::      PDF

     ePub

     Mobi

Ebook

89,90 zł

Dodaj do koszyka lub Kup na prezent Kup 1-kliknięciem

Przenieś na półkę

Do przechowalni

When developers document the architecture of their systems, they often invent their own specific ways of articulating structures, designs, concepts, and decisions. What they need is a template that enables simple and efficient software architecture documentation. arc42 by Example shows how it's done through several real-world examples.

Each example in the book, whether it is a chess engine, a huge CRM system, or a cool web system, starts with a brief description of the problem domain and the quality requirements. Then, you'll discover the system context with all the external interfaces. You'll dive into an overview of the solution strategy to implement the building blocks and runtime scenarios. The later chapters also explain various cross-cutting concerns and how they affect other aspects of a program.

Wybrane bestsellery

Ebooka przeczytasz na:

czytnikach Inkbook, Kindle, Pocketbook, Onyx Boox i innych
systemach Windows, MacOS i innych

systemach Windows, Android, iOS, HarmonyOS
na dowolnych urządzeniach i aplikacjach obsługujących formaty: PDF, EPub, Mobi

Masz pytania? Zajrzyj do zakładki Pomoc »

Audiobooka posłuchasz:

w aplikacji Ebookpoint na Android, iOS, HarmonyOs
na systemach Windows, MacOS i innych

na dowolonych urządzeniach
i aplikacjach obsługujących format MP3
(pliki spakowane w ZIP)

Masz pytania? Zajrzyj do zakładki Pomoc »

Kurs Video zobaczysz:

Oceny i opinie klientów: arc42 by Example Dr. Gernot Starke, Michael Simons, Stefan Zörner, Ralf D. Müller (0) Weryfikacja opinii następuję na podstawie historii zamówień na koncie Użytkownika umieszczającego opinię. Użytkownik mógł otrzymać punkty za opublikowanie opinii uprawniające do uzyskania rabatu w ramach Programu Punktowego.

Szczegóły książki

Tytuł oryginału:: arc42 by Example
ISBN Ebooka:: 978-18-392-1926-9, 9781839219269
Data wydania ebooka:: 2019-10-07 Data wydania ebooka często jest dniem wprowadzenia tytułu do sprzedaży i może nie być równoznaczna z datą wydania książki papierowej. Dodatkowe informacje możesz znaleźć w darmowym fragmencie. Jeśli masz wątpliwości skontaktuj się z nami sklep@helion.pl.
Język publikacji:: angielski
Rozmiar pliku Pdf:: 14.9MB
Rozmiar pliku ePub:: 28.7MB
Rozmiar pliku Mobi:: 60.1MB

Kategorie:
Big Data » Analiza danych

Spis treści książki

Acknowledgements
- Disclaimer
Preface
- About the Book
  - About the Authors
  - Learning Objectives
  - Audience
  - Approach
  - Conventions
Chapter 1
I - Introduction
- I.1 What is arc42?
  - Why arc42?
  - Where to Get Additional Information
- I.2 Why This Book?
- I.3 What This Book is Not
- I.4 An Overview of Examples
  - HTML Sanity Checking
  - Mass Market Customer Relationship Management
  - biking2
  - DokChess a Chess Engine
  - docToolchain
  - MiniMenu
- I.5 A table of arc42 Topics
Chapter 2
II - HTML Sanity Checking
- II.1 Introduction and Goals
  - 1.1 Requirements Overview
  - Basic Usage
  - Basic Requirements
  - Required Checks
  - 1.2 Quality Goals
  - 1.3 Stakeholders
- II.2 Constraints
- II.3 Context
  - 3.1 Business Context
  - 3.2 Deployment Context
- II.4 Solution Strategy
- II.5 Building Block View
  - 5.1 HtmlSanityChecker (Whitebox)
  - Contained Blackboxes
  - 5.2 Building Blocks Level 2
  - Contained Blackboxes
  - 5.3 Building Blocks Level 3
  - Contained Blackboxes
- II.6 Runtime View
  - II.6.1 Executing All Checks
  - II.6.2 Report Checking Results
- II.7 Deployment View
  - Prerequisites
- II.8 Crosscutting Concepts
  - 8.1 Domain Model
  - 8.2 Structure of HTML Links
  - 8.3 Multiple Checking Algorithms
  - 8.4 Reporting
- II.9 Design Decisions
  - 9.1 Checking of External Links Postponed
  - 9.2 HTML Parsing with jsoup
- II.10 Quality Scenarios
  - Quality Scenarios
- II.11 Risks and Technical Debt
  - 11.1 Technical Risks
  - 11.2 Business or Domain Risks
- II.12 Glossary
Chapter 3
III - Mass Market Customer Relationship Management
- III.1 Introduction and Requirements
  - 1.1 Requirements Overview
  - 1.1.1 Campaign Example: Mobile Phone Contract Modification
  - 1.1.2 Campaign Configuration
  - 1.1.3 Activities Subject to Charge
  - 1.1.4 Additional Requirements
  - 1.2 Quality Goals
  - 1.2.2 Quality Goals (Scenarios)
  - 1.3 Stakeholder
  - 1.3.1 Special Case: German e-Health Card
  - 1.3.2 Partner or Mandator-Specific Interface Details
- III.2 Constraints
  - General Constraints
  - Software Infrastructure Constraints
  - Operational Constraints
- III.3 Context
  - 3.1 (Generic) Business Context
  - 3.1.1 Formal Business Context
  - 3.1.2 Specific Business Context: Mobile Phone Contract Modification
  - 3.1.2 Technical/Deployment Context
- III.4 Solution Strategy
- III.5 Building Blocks
- III.6 Runtime View
  - 6.1 Import File
- III.7 Deployment View
  - 7.1 Deployment Overview
  - 7.2 Campaign-Specific Virtual Machine
  - 7.3 Common Metadata Store (CoMeS)
  - 7.4 Campaign Configuration Machine
- III.8 Cross cutting Concepts
  - 8.1 Generated Persistence Based on the Domain Model
  - 8.2 CSV Import/Export
  - 8.3 Configurable File Filters
  - 8.4 Rule Engine for Process and Flow Control
- III.9 Architecture Decisions
- III.10 Quality Scenarios
  - Flexibility Scenarios
  - Runtime Performance Scenarios
  - Security Scenarios
- III.11 Risks
- III.12 Glossary
Chapter 4
IV - biking2
- IV.1 Introduction and Requirements
  - 1.1 Requirements Overview
  - 1.2 Quality Goals
  - 1.3 Stakeholders
- IV.2 Architecture Constraints
  - 2.1 Technical Constraints
  - 2.2 Organizational Constraints
  - 2.3 Conventions
- IV.3 System Scope and Context
  - 3.1 Business Context
  - 3.2 Technical Context
- IV.4 Solution Strategy
- IV.5 Building Blocks-Level 1
  - 5.1 Whitebox biking2::api
  - 5.1.1 bikes (Blackbox)
  - 5.1.2 tracks (Blackbox)
  - 5.1.3 trips (Blackbox)
  - 5.1.4 locations (Blackbox)
  - Files
  - 5.1.5 bikingPictures (Blackbox)
  - 5.2 Building Blocks Level 2
  - 5.2.1 bikes (Whitebox)
  - 5.2.2 tracks (Whitebox)
  - 5.2.3 trips (Whitebox)
  - 5.2.4 locations (Whitebox)
  - 5.2.5 bikingPictures (Whitebox)
  - 5.2.6 galleryPictures (Whitebox)
- IV.6 Runtime View
  - Creating New Tracks
  - Fetching Biking Pictures from Daily Fratze
- IV.7 Deployment View
- IV.8 Technical and Crosscutting Concepts
  - Domain Models
  - Persistency
  - User Interface
  - JavaScript and CSS Optimization
  - Transaction Processing
  - Session Handling
  - Security
  - Safety
  - Communication and Integration
  - Plausibility and Validity Checks
  - Exception/Error Handling
  - Logging and Tracing
  - Configurability
  - Internationalization
  - Migration
  - Testability
  - Build Management
- IV.9 Architecture Decisions
  - Using GPSBabel to Convert TCX into GPX Format
  - Using Local File Storage for Image and Track Data
- IV.10 Quality Scenarios
  - 10.1 Quality Tree
  - 10.2 Evaluation Scenarios
- IV.11 Risks
- IV.12 Glossary
Chapter 5
V - DokChess
- V.1 Introduction and Requirements
  - 1.1 Requirements Overview
  - 1.2 Quality Goals
  - 1.3 Stakeholders
- V.2 Constraints
  - 2.1 Technical Constraints
  - 2.2 Organizational Constraints
  - 2.3 Conventions
- V.3 Context
  - 3.1 Business Context
  - 3.2 Deployment Context
- V.4 Solution Strategy
  - 4.1 Structure of DokChess
  - 4.2 Game Strategy
  - 4.3 The Connection of the Engine
- V.5 Building Block View
  - 5.1 Building Block View-Level 1
  - 5.1.1 Subsystem Text UI (Blackbox)
  - 5.1.2 Subsystem Rules (Blackbox)
  - 5.1.3 Subsystem Engine (Blackbox)
  - 5.1.4 Subsystem Opening (Blackbox)
  - 5.2 Level 2: Engine (Whitebox)
  - 5.2.1 Search (Blackbox)
  - 5.2.2 Evaluation (Blackbox)
- V.6 Runtime View
  - 6.1 Move Determination Walkthrough
- V.7 Deployment View
  - 7.1 Windows Infrastructure
- V.8 Technical and Cross cutting Concepts
  - 8.1 Dependencies between Modules
  - 8.2 Chess Domain Model
  - 8.3 User Interface
  - 8.4 Plausibility Checks and Validation
  - 8.5 Exception and Error Handling
  - 8.6 Logging and Tracing
  - 8.7 Testability
- V.9 Design Decisions
  - 9.1 How Does the Engine Communicate with the Outside World?
  - 9.2 Are Position Objects Changeable or Not?
- V.10 Quality Scenarios
  - 10.1 Utility Tree
  - 10.2 Evaluation Scenarios
- V.11 Risks
  - 11.1 Risk: Connecting to a Frontend
  - 11.2 Risk: Effort of Implementation
  - 11.3 Risk: Reaching the Playing Strength
- V.12 Glossary
Chapter 6
VI - docToolchain
- VI.1 Introduction and Goals
  - 1.1 Problem Statement
  - 1.2 Quality Goals
  - 1.3 Stakeholders
- VI.2 Architecture Constraints
- VI.3 System Scope and Context
  - Business Context
  - Scope
- VI.4 Solution Strategy
  - General Solution Strategy
  - Individual Solution Strategy
  - Export Tasks
  - Version Control of Exported Artifacts
  - Generate Tasks
- VI.5 Building Block View
  - 5.1 Level 1
  - 5.2 Level 2
  - 5.2.1 Export Tasks
  - Utility Tasks
  - 5.2.4 Generate Tasks
- VI.6 Runtime View
- VI.7 Deployment View
  - 7.1 Option 1: Installed the Command-Line Tool
  - 7.2 Option 2: Git Submodule
  - 7.3 Option 3: Docker Container
- VI.8 Cross cutting Concepts
  - Automated Testing
- VI.9 Design Decisions
  - DD1: Wrapped Plugins instead of Ruby Gems
  - DD2: Visual Basic Script for EA Automation
  - DD3: Support for Maven and Gradle
  - DD4: Binary Gradle Plugins
  - DD5: AsciiDoc as Basis
  - DD6: Deployment Options
  - DD6.1: Embedded
  - DD6.2: Gradle Script Plugins
  - DD6.3: Gradle Binary Plugins
- VI.10 Quality Requirements
  - QS1: Confidentiality
  - QS2: Security (besides Confidentiality)
  - QS3: Repeatability
  - QS4: Transformation Stability
  - QS5: Performance
  - QS6: Ease of Use
  - QS7: Maintainability
- VI.11 Risks and Technical Debts
  - TR1: Outdated Technology
  - TR2: Missing Acceptance of the Docs-as-Code Approach
  - TR3: Git Submodules
  - TR4: Automated Tests (Technical Debt)
- VI.12 Glossary
Chapter 7
VII - macOS Menu Bar Application

pokaż cały spis treści