AM Method
The AM Method is simple; with only 7 elements. It supports other methods. It can be used to create Requirements, Stakeholders, Objectives, Integrations and more.. It is formal and can be easily implemented. It supports a business knowledge base. It includes business concepts that other methods address tangentially.
It has been designed from the ground up to be automated in software!
7 Elements
These 7 modeling elements ( Assertion, Authority, Frame, Connection, Perspective, Environment and Implementation) define a simple modeling method with compelling consequences.
Together they address:-
- Who : Authority
- What: Assertion and Frame
- When: Assertion expressed
- Where: Environment
- How: Assertion specification and Connection
- Why: to support other Assertions
- — and Perspectives help you separate concerns and make plans
Supports Other Methods
BIZBOK – A Capability is included as an assessment of the capability
BPMN – Assertions align with processes but stress the decision and information produced.
Requirements – An assertion provides a user story.
Stakeholders – Are Authorities that use or supply information.
Objectives – are assertions of intent by an authority.
AM does NOT have any relationship to Model Assertions or Programming Assertions !
Multi Use
The method supports the generation of an array of artifacts.
Stakeholder Lists – and their responsibilities.
Logic Diagrams – showing how assessment assertions contribute to an objective.
Integration Design – Connections between Environments are generated.
Quality Assurance – assertions without input or output indicate missing knowledge.
Easily Implemented
Choose the assertions to be implemented in a Perspective.
Each assertion is a user story.
The Connections show where the information must be passed.
The Frames show the structure of the information to be managed.
The Environments show where an authority must have access.
All these support fully informed solution design.
Supports Knowledgebase
When you have to manage all the business information you gather you do it on one place.
The elements form the structure of your architecture repository.
Modelers have a single paradigm to work within. So they can concentrate on the business.
Notations and mapping between them disappear.
And because it is simple the maintenance of your architecture repository shrinks too.
Look at the example repository Recruitment Model to see how various modeling concepts are embraced.
Innovative
For example AM identifies the time and frequency of an assertion. Use this to set backlog priorities or decide on what to implement first.
Every important business decision can be represented in AM. Operational , Management, Governance, Strategy. And fully automated, augmented, of purely manual.
Automatically simulate the screens you need while in elucidation. Catch extra needs before the coding begins.
Generate your JIRA requirements automatically.
Capture your business as the network that it is. View it as lists, sequences and feedback loops.
Identify financial events where accounting decisions are initiated.
Methods define the vocabulary and meaning of the terms created and assembled to provide a useful picture of an endeavor. There are 7 main modeling elements in Assertion Modeling. The are powerful, simple, and focused.
With Assertion Modeling you describe the business with the decisions it makes (Assertions), and the resulting information it passes (Frames).
You state who makes the decision (Authorities), how the information is passed (Connections), and to whom( another Authority).
The result is a network that better describes what the business does, manually, verbally, and automatically. You can then browse your model, isolating sections (Perspectives) that address your current concerns(like vague explanations or business issues).
The business environment (Environment) where the decision is made, and where the Authority has access, is part of the business design process. Proposed solutions can be shown as a collection of Authorities implemented in a particular Environment (Implementation).
These 7 modeling elements ( Assertion, Authority, Frame, Connection, Perspective, Environment and Implementation) define a simple modeling method with compelling consequences.
Together they address:-
- Who : Authority
- What: Assertion and Frame
- When: Assertion expressed
- Where: Environment
- How: Assertion specification and Connection
- Why: to support other Assertions
- — and Perspectives help you separate concerns and make plans
Specific Perspectives can encompass many of the concepts currently used for business descriptions. Events, Tasks, Roles, Goals. And custom perspectives support a divide and conquer approach, while maintaining the coherence of the assertions overall. And Perspectives support the population of the wide range of business templates. And align and integrate decisions made using those templates. Create a Perspective for your Template and then how how information flows into the decisionsit supports.
The method is strong because;
- there is a simple software tool (Assertionizer) that helps you build and manage your model and the perspectives you are emphasizing.
- you can simulate each of the Assertions with example data, discussing with the Authority the details of the decision and the meaning of the information produced.
- you can model the management and governance Assertions that justify and monitor the operational Assertions.
- you can create complete stakeholder lists (Authorities) and the role they play.
- you can generate a list of requirements for an implementation (that could be fed to JIRA)
- you can make a change from one perspective and have it immediately reflected in the others.
The Assertion Modeling Method Introduces the elements and how they are defined and related.
AM Relationship to Other Business Methods – talks about other methods used for business description and how AM aligns, enhances or replaces them.
Who What and Why – Who might use it, how and why.
A technical schema is not currently configured, but the definitions and structures of the AM Method are detailed enough to underpin the working software.
“There are more concepts than there are things.
Choose carefully.“