CivilCode Playbook
  • The CivilCode Playbook
  • Method
    • Engagement
      • Qualification
      • Introductory Meeting
    • Onboarding
      • Roles and responsibilities
      • Product Owner Role
    • Discovery
    • Iteration Zero
      • Kickoff
    • Development
      • Develop an Object Model
      • Build a Feature List
  • Guides
    • Operations
      • Setup the VPN
      • Developer Setup Guide
      • Maintain Virtual Machine
    • Practices
      • Pair Programming Practice
      • Friday Practice
      • Project Retrospective
      • Daily Practices
  • Education
    • Trails
      • Elixir
      • Domain-Driven Design and CQRS/ES
      • Event Storming
      • Feature-Driven Development
      • Functional Programming
      • GraphQL
      • Object Design
      • Object Modeling
      • Specification by Example
      • Story Mapping
      • Testing
      • Type Classes
Powered by GitBook
On this page
  • How we work
  • 1. How we model the domain
  • 2. How we develop features
  • 3. How we automate acceptance tests
  1. Method

Development

PreviousKickoffNextDevelop an Object Model

Last updated 4 years ago

How we work

Before contributing to development there are a number of concepts you need to understand:

  1. How we model the domain

  2. How we develop features

  3. How we automate acceptance tests

1. How we model the domain

See the Trail.

2. How we develop features

We develop the application feature by feature using the process. This means:

  1. We start with

  2. We (module, feature-set, feature) based on the Object Model

  3. We Plan Feature Development based on the Roadmap

  4. We Design by Feature

  5. We Build by Feature

3. How we automate acceptance tests

To be developed.

For building features please review the in the example application that provide checklists for modules, abilities, tasks.

Object Modeling
Feature-Driven Development
Developing an Overall Object Model
Build a Feature Roadmap
Github Issues Template folder