• The DomainDrivenArchitecture
  • DomainDrivenArchitecture
  • 1. Book Change History
  • 2. Book Scope
  • 3. Application Backup
    • 3.1. Backup Change History
    • 3.2. Conceptual framework
    • 3.3. Analysis
      • 3.3.1. Entities and Questions
      • 3.3.2. Backup decision form
    • 3.4. Requirements
    • 3.5. Architecture
      • 3.5.1. Backup Process
      • 3.5.2. Restore Process
    • 3.6. Realization
  • 4. Linked Data Resource Publishing
    • 4.1. Change History
    • 4.2. Scope
    • 4.3. Analysis
      • 4.3.1. ScopeComparison
    • 4.4. Requirements
    • 4.5. Architecture
      • 4.5.1. Principles and Conventions
        • 4.5.1.1. Modelling Principles
        • 4.5.1.2. Modelling Conventions
        • 4.5.1.3. URI Conventions
      • 4.5.2. Publishing
        • 4.5.2.1. Publishing One Data Source
        • 4.5.2.2. Publishing Multiple Data Sources
        • 4.5.2.3. Publishing Requirements as Linked Data
      • 4.5.3. Interlinking
    • 4.6. Realization
      • 4.6.1. User and Groups for Liferay
      • 4.6.2. Articles, Tags and Urls for Liferay
      • 4.6.3. Requirements2Turtle - Transformation with Talend
    • 4.7. Glossary
  • 5. Requirements
    • 5.1. Requirements Change History
    • 5.2. Concepts Scope
    • 5.3. Analysis
      • 5.3.1. The benefit of written requirements
      • 5.3.2. Traps and cost driver
    • 5.4. Requirements
    • 5.5. Architecture
      • 5.5.1. Structure and referencing of requirements
      • 5.5.2. System scope (1.)
      • 5.5.3. Project-Scope (1.)
    • 5.6. Realization
      • 5.6.1. With FitNesse
    • 5.7. Appendix: Further tools and more links
  • 6. Config Management
    • 6.1. Concepts Change History
    • 6.2. Concepts Scope
    • 6.3. Analysis
      • 6.3.1. Scope
      • 6.3.2. Business Value
      • 6.3.3. Modularization
      • 6.3.4. Development
      • 6.3.5. Runtime
      • 6.3.6. Credentials Security
      • 6.3.7. Process Support
    • 6.4. Requirements
    • 6.5. Architecture
      • 6.5.1. Modularization
        • 6.5.1.1. Core Modules
      • 6.5.2. Phases
      • 6.5.3. Config Distribution
      • 6.5.4. State Mgm
      • 6.5.5. Credentials Security
    • 6.6. Realization
      • 6.6.1. Development
        • 6.6.1.1. Coding Conventions
        • 6.6.1.2. Typed Parameters for Interfaces
      • 6.6.2. Quality
      • 6.6.3. TestFirst
      • 6.6.4. Module WebServer
  • 7. Books License
Powered by GitBook

The DomainDrivenArchitecture

DDA Config Management Concept

Table of Content

  • Concepts Change History
  • Concepts Scope
  • Analysis
    • Scope
    • Business Value
    • Modularization
    • Development
    • Runtime
    • Credentials Security
    • Process Support
  • Requirements
  • Architecture
    • Modularization
      • Core Modules
    • Phases
    • Config Distribution
    • State Mgm
    • Credentials Security
  • Realization
    • Development
      • Coding Conventions
      • Typed Parameters for Interfaces
    • Quality
    • TestFirst
    • Module WebServer