How do concept models typically start?

Concept models typically start with a glossary of business vocabulary because understanding the terminology used within a particular domain is fundamental to establishing clear communication. A glossary provides a shared reference point for all stakeholders involved in the project, ensuring that everyone interprets terms in the same way. This foundational step helps in defining concepts accurately, which is crucial for effective requirement gathering and analysis.

By starting with a glossary, the team can clarify the scope of the project, avoid misunderstandings, and set a common language that will be used throughout the development process. This clarity aids in creating a more cohesive and focused concept model that accurately reflects the needs and viewpoints of stakeholders. It fosters an environment where discussions can be more productive because all participants are aligned on the definitions of the terms being used.

In contrast, starting with a list of stakeholders, financial analysis, or a marketing strategy, while valuable in their own right, do not lay the foundational clarity that a glossary of business vocabulary provides for the creation of concept models. These elements, while important for different aspects of the project lifecycle, do not directly contribute to building a structured understanding of the domain's concepts at the outset.