Order Entry Example
The industry uses Order Entry as an oversimplified example for a wide range of methodologies. This example shows just how complex Order Entry can be, and helps tame the complexity of real business description. This example was undertaken to explore the capabilities of AM to create rich and formal specifications for a business to be automated. The specifications recognize the structure of an implemented set of software components. They map between the two realms.
Fully Hyperlinked Report for Order Entry >
The framework and structure of Domain Driven Design (DDD) was used as the target, and so the resulting application is delivered with Domains, Bounded Contexts, Domain Services, Aggregates, Entities, and Value Object.
See the DDD Specifications generated from the Order Entry Model >
This example was taken to the next level!
A real application was built from the specifications. This research explored the decisions tha must be made to implement a business, and it recognized that code is the last and most detailed description of the business.
Order Entry uses Implementation Design
This model shows where the intent of the implementation can be captured in each assertion. It brings implementation decisions into the capabilities of Assertionizer software. Discover the interactions of the software components before any coding starts.