One of the most useful tools for explicating the terminology of customers is a conceptual model. Conceptual models depict the concepts in the problem domain and their relationships.
At Cauvin, Inc., we compose conceptual models in the form of static structure diagrams. Conceptual models resemble glossaries (in that they define the words in the domain), but they are richer and more concise.
Here is an example of a conceptual model:
Conceptual models in this format contain the following elements:
At Cauvin, Inc., we compose conceptual models in the form of static structure diagrams. Conceptual models resemble glossaries (in that they define the words in the domain), but they are richer and more concise.
Here is an example of a conceptual model:
Conceptual models in this format contain the following elements:
- Concepts. Each rectangular box depicts a concept.
- Links. A line between two concepts shows that an association exists between them.
- Association. The name of an association is shown on or next to a link between two concepts.
- Multiplicities. Multiplicities show how many instances of the concepts participate in the association. An asterisk (*) means that an indefinite (potentially infinite) number of instances participates in the relationship.
- Specialization. A specialization is a kind of association with a hollow triangle connecting the link to a concept. The concept on the triangle link is the general concept. The concept on the other end of the link is its specialization, which means it is a kind of the general concept.
- A product is sold in zero or more markets.
- A market is divided into zero or more market segments.
- A segmentation method is a method of segmenting a market.
- Regional segmentation is a kind of segmentation method.
- Regional segmentation segments a market by zero or more regions.
Comments
The most effective conceptual models that I have seen/used were simplistic in communicating the business model (compelling/viability) at the highest level. If I am trying to communicate with a development team, it might be more intuitive.
While I would probably not use this format, I think it does a great job outlining the relationships between the entities.
To startwith simplified graphic models (diagrams) are helpful but they should be extencible to express higher complexity with precision and rigor. Otherwise, the initial documentation looses correlation with design / implementation details. Currently UML 2.0 Diagrams are OK but extensibility is yet to evolve to reduce the gap between the diagrams and the software that gets developed. I understand that "Executable UML" aims to achieve this.
Putcha V. Narasimham
Once you get the conceptual model encoded, you do terminology managment. In terminology management, you are creating a vocabulary for your conceptualization.
Once you have your terminology done, you are ready to move the conceptual model to UML.
Concepts may look like UML, but there is a leap between them.
That UML is now executable means that it is much closer to be the carrier than the carried. UML is the automating, rather than the automated.
Programmers diverge from requirements. They deal with language constraints, APIs, design patterns, and things that move them away from the use of resulting software.
UML diverges as well. It has to diverge to deal with programmer considerations.
Once the UI is finished. The users take it out for a drive. As they drive they notice the response. They build a user conceptual model of their experiences. Hopefully, the conceptual model emerging from requirements elicitation matches the conceptual model emerging from the user experience.
I did not see your comment earlier.
How long it takes to reduce the gaps is one aspect but I see the very purpose of UML or any such language is to reduce the gap between the concepts and their representations. Text is considered too elaborate but not precise enough. So we find that a lot of math, drawings, diagrams, simulations, come in different combinations. The key is to reduce the gap formally so that it becomes executable.
Cheers,
09FEB14
Those who may be interested may take a look at
http://www.slideshare.net/putchavn/concept-maps-knowledge-encoding
This is on the basics of relation...
http://www.slideshare.net/putchavn/relation-need-for-radical-redefinition-pdf
Best wishes,