concept-design

Concept design structures software functionality into discrete, reusable concepts using Daniel Jackson's methodology. It creates rigorous specifications with formal state notation and atomic action definitions to ensure logical soundness.

To create a concept specification, you define the feature using a canonical format covering purpose, state, actions, and operational principle. This structures software functionality into discrete, reusable concepts before writing any code.

You should use domain modeling and formal state notation when building new features to define concept boundaries, state, and atomic actions before writing code, or when auditing existing systems for overloaded concepts and missing abstractions.

Yes, you can use this methodology to analyze existing systems during design auditing. It helps identify overloaded concepts, missing abstractions, and improper coupling within your software architecture.

The best way to define concept boundaries and atomic actions is by applying Daniel Jackson's methodology to create rigorous specifications, ensuring clear operational principles and formal state notation before development begins.