Examples
Examples give you the opportunity to see and understand AM from a concrete perspective. Not possibilites — real examples!
The examples are rich because they are intended to show the full capabilities of AM. They appear complex, because real business is complex. But always the decisions and connections can be observed from perspectives. And always the implications of business improvement ideas can be confirmed from all the perspectives.
Recruitment Management includes more manual assertions where decisions by the authority are not automatically calculated, but considered by a person.
Order Entry emphasizes automated assertions, where code will implement the decisions.
Both examples include rationale (built into the model) for why the assertions have been designed as they have. You will identify places where your view of the business differs. That is because AM is so explicit. You can even ask for your own copy of these examples to model in Assertionizer. When you model you think business not how to use the methodology.
Recruitment Management Model
Recruitment Management (RecMod) is an excellent example to show the richness of an Assertion Model.
Maintained in Assertionizer ( the AM Software) RecMod is shown here as the generated, hyperlinked, report. The hyperlinked report contains all of the information in RecMod and is easy to browse using the hyperlinks.
RecMod appears large and complex because it contains the full model and it shows all the perspectives.
Full Hyperlinked Report for Recruitment >
– A complete, linked report generated from the Recruitment Management Model software for browsing.
A Tour of the Recruitment Model
Walk through all the parts of a mature Assertion Model for Recruitment. Keep the full hyperlinked report open while you step through various parts of the report and understand the role they play in providing a comprehensive model.
– A walkthrough of Recruitment explaining key AM concepts and referring to the HTML report.
Check out the video of Assertionizer Software in use!
Order Entry Model
The industry uses Order Entry as an oversimplified example for a wide range of methodologies. This example shows how complex Order Entry canb be and helps tame the complexity of real business description. This example was undertaken to explore the capabilites 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 >
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.
The framework and structure of Domain Driven Design (DDD) was used as the target, and so the resulting application is deivered with Domains, Bounded Contexts, Domain Services, Aggregates, Entities, and Value Object.
This model shows where the intent of the implementation can be captured in each assertion. It brings implementation decisions into the capabilites of Assertionizer software. Discovery of the interactions of the software components begins before any coding starts.
More coming on Order Entry Example in DDD