We are working on several products as the IT department and we try to provide solutions for different departments within the same company. The core of our business is insurance and the main goal is to have automated processes for brokers, back-office people, and finance department (there are some other groups, but it is worst to mention only 3 for now). When we started working on our products, we identified 2 bounded contexts (that cover only the business we are working on at this moment).
In our bounded contexts we have the following core concepts:
- Insurance Policy Proposal - what our clients provide (propose) to our brokers to get an insurance policy
- Insurance Policy - it is a document that provides proof of having insurance coverage for a person (or group of people)
When a proposal is submitted by brokers, it is passed to back-office people who must review and verify what was provided in the proposal. If everything is ok and there are no mistakes, the proposal will become an insurance policy. As you can see we have two different departments:
- Brokers create/manage and submit proposals
- Back office people review proposals and manage policies after moving proposals to policies
If you want me to share something about the content of proposal and policy, they are almost identical in the beginning and the first version of the policy will have the same attributes as the initial proposal has.
And we have some kind of feeling that proposals (and everything around) belong to one sub-domain and policies are the part of another sub-domain. At least we have the following signs of that:
- Both terms/definitions are used by business
- The first concept is managed by one department, another one is managed by another
Could you please help me to understand how we can make sure that our hypothesis is wrong or right?