The business object model is described in Appendix A.
From that diagram we can create the Corticon Vocabulary
Initially there will be a Corticon entity corresponding to each business object in the diagram:
Next we need to model the relationships between the entities:
For example, the diagram shows that a property may be associated with many documents:
This now shows in the vocabulary as
After modeling the other relationships we’ll end up with a vocabulary like this:
Next we can enter all of the attributes of each business object
This vocabulary can be used by all the use cases.
UML Diagram (generated by Corticon from the Vocab)
Notice the addition of 1:N associations between Document and Rule and between Document and Event.
If premiumAmount is 10% lower or higher compared to the premiumAmount on the current policy then raise event “Verify premium: Amount too high/low compared to existing policy”
Assuming that “existing policy” really means “current policy”
So the rule sheet only executes if there are no events already attached to the property.
The attribute “isCurrentPolicy” is used to select the current policy.
This attribute needs to be set in another rule sheet.
Two steps are required:
Determine if a document matches an existing policy
Classify the remaining documents
This compares all documents and all policies to find if an existing policy matches
This classifies the remaining documents with reference to the current policy (determined using the rule sheet described earlier)
Add new insurance policy with data from document
Send a letter to the Property Address
Step 4 Classify Document