Conceptual Models: What They Are and How to Use Them

UPI Study › Courses › Software Engineering › Free lessons › Lesson 15.7 Free with a free account

Conceptual Models: What They Are and How to Use Them

Software Engineering · Chapter 15: Distributed Systems, Services, and Sociotechnical TopicsSection 15.7 · lesson 101 of 1036 min · free with a free account

← People and Technology Together: Sociotechnical Systems TheoryNext lesson: Managing Procurement in Software Projects →

Earn 3 college credits for Software EngineeringRecommended for credit by NCCRS · Computer Science 301 · self-paced · one payment, lifetime access
Enroll in Software Engineering · $250 →Download the syllabus (PDF)

In this lesson

Agreeing on what matters in a domain - before anything gets formalized.

  • Define a conceptual model, and how it differs from a class diagram
  • Explain why it comes before detailed design
  • Describe what a conceptual model contains
  • Apply the habits that make one useful

Transcript

Everything said in the video, section by section (779 words). Read along, or search it.

Distributed Systems, Services, and Sociotechnical Topics

Conceptual Models: What They Are and How to Use Them

Before anything gets formalized into a class diagram or a database schema, it helps to agree on what the important things in a domain actually are. And on how the people who work in that domain already think they relate. That agreement, captured informally, is a conceptual model.

Shared Understanding First

What a Conceptual Model Is

A conceptual model is a simplified, high-level representation of a problem domain's key concepts, and how they relate. It is shared understanding, not yet a technical design. It is deliberately more informal than a class diagram or a data model. It does not worry about data types, method signatures, or storage structure. It worries about a simpler question first. What are the important things in this domain, and how do the people who actually work in it think about them relating to one another?

Before Detailed Design

Check Assumptions While They're Cheap

Design depends on the structured output of analysis. A conceptual model sits even earlier than that. Its purpose is getting stakeholders aligned on the core concepts and relationships, including domain experts with no technical background at all. And it does that before anyone makes binding technical decisions about how to represent them. Jumping straight to a class diagram or a database schema, risks quietly encoding the team's own assumptions about a domain. Those assumptions may never have been checked against someone who genuinely understands it.

Figure 1

Concepts in Plain Language

Here is a small conceptual model. A customer places an order, and an order contains products. There are no diamonds, no multiplicities, and no attribute compartments. Just the concepts, and how people already describe them relating. Even a domain rule is written the way people say it. A customer can have many orders, but an order belongs to exactly one customer.

What It Contains

3 Kinds of Content

A conceptual model typically contains three kinds of content. The key domain concepts, without yet deciding whether each one will become a class, a database table, or something else entirely. The relationships between them, described in plain language, rather than formal notation. And important domain rules, stated informally, rather than as a technical multiplicity. It is meant to be readable and checkable by domain experts, who may not know any formal notation at all. That is the entire point.

Table 1

Conceptual Model vs. Class Diagram

Here is how a conceptual model compares with a class diagram, or a data model. The conceptual model's audience is domain experts and stakeholders, including non-technical people. A class diagram's audience is developers and designers. A conceptual model uses informal, plain language. A class diagram uses formal, standardized notation. And a conceptual model comes before detailed design, to build and check shared understanding. A class diagram comes during design, to guide the technical implementation.

Worth Noticing

Informality Is the Feature

Here is something worth noticing. A conceptual model that a domain expert cannot read without translation has already failed its purpose. The informality is not a shortcut taken to save time. It is the entire feature that makes the technique work.

Using It Well

4 Habits

A conceptual model earns its keep through a few habits. Keep it genuinely simple, and free of technical jargon. If a domain expert needs a translation to follow it, it is not doing its job. Validate it directly with domain experts, before treating it as settled. The value is catching misunderstandings early and cheaply, in plain language. Expect it to change early on, rather than over-polishing it prematurely. And recognize when to move on. Once the core concepts are validated and reasonably stable, that is the signal to move into formal, detailed design.

Apply It

2 Ways to Fail

So there are two ways a conceptual model can fail. It can be too formal. If it is full of multiplicities and data types, the domain expert cannot check it, and the misunderstandings survive. Or it can never be replaced. A conceptual model that is kept as the final word has also failed. It was only ever meant to lead into more detailed design work.

Key Terms

The Vocabulary of This Section

Let's lock in the key terms. A conceptual model is a simplified, high-level, informal representation of a domain's key concepts and how they relate, used to build shared understanding before detailed design. A domain concept is a key idea or entity in the domain, represented without yet deciding its technical form. And domain expert validation is checking the model directly with people who genuinely understand the domain, before treating it as settled.

Key Takeaways

What to Carry Forward

To pull this together. A conceptual model captures shared understanding of a domain, not a technical design. It comes before detailed design, so the team's assumptions get checked while they are still cheap to fix. It holds concepts, relationships, and domain rules, all in plain language. It is validated with domain experts, and expected to change. And once it is stable, the team moves on to formal design. It was never meant to be the final word.

About Software Engineering at UPI Study

Software Engineering (Computer Science 301) is a self-paced online course of 103 video lessons in 15 chapters, from process models and agile to requirements, design, user interfaces, reliability, security and project management. It carries a NCCRS credit recommendation for 3 semester credits.

Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Enroll now → Course details Download the syllabus All Computer Science courses Every course with PRO →

Compare: Software Engineering vs Systems Analysis

Why take it here

Why students take Software Engineering with UPI Study

How professional software gets builtSoftware Engineering covers how teams turn requirements into working, maintainable software: process models, agile, requirements, design, testing, reliability and project management. It is a core course in computer science and software degrees.
Credit at a fraction of the priceThe same 3 credits can cost $750 or more at a US college. Here it is one payment, self-paced, with lifetime access.
Finish your degree soonerTransfer credits reduce the courses you still owe, so you can graduate earlier or lighten a heavy semester.
Strengthen an applicationA completed college-level course on an official transcript shows admissions and scholarship committees you can do the work.
Study on your own scheduleNo start dates, no deadlines. Watch the lessons, practice, and take the final when you are ready.
130,000+students helped with college creditsACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Where the credit goes

Universities that work with NCCRS

Software Engineering carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Thomas Edison State UniversityThomas Edison State UniversitySigned partnerUniversity of the PeopleUniversity of the PeopleSigned partnerCharter Oak State CollegeCharter Oak State CollegeSigned partnerStrayer UniversityStrayer UniversitySigned partnerColumbia Southern UniversityColumbia Southern UniversitySigned partnerIndiana TechIndiana TechSigned partnerPenn StatePenn StateWorks with NCCRSSouthern New Hampshire UniversitySouthern New Hampshire UniversityWorks with NCCRSSUNYSUNYWorks with NCCRS +many more cooperating universitiesFind my college →

Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.

FAQ

Questions students ask us

About Conceptual Models: What They Are and How to Use Them

What is a conceptual model in software engineering?
A conceptual model is a simplified, high-level, informal representation of a problem domain's key concepts and how they relate, used to build shared understanding before detailed design. For example, it might say that a customer places an order and an order contains products. It ignores data types, method signatures, and storage, focusing only on how people in the domain think about it.
What is the difference between a conceptual model and a class diagram?
A conceptual model is written in plain language for domain experts and stakeholders, including non-technical people, and comes before detailed design. A class diagram uses formal, standardized notation for developers and designers and comes during design to guide implementation. A conceptual model states a rule as "a customer can have many orders" rather than as a formal multiplicity.
Why create a conceptual model before detailed design?
A conceptual model lets the team check its assumptions about a domain while they are still cheap to fix. Jumping straight to a class diagram or database schema risks encoding the team's own unchecked assumptions. Validating a plain-language model with domain experts first catches misunderstandings early, before anyone makes binding technical decisions about how to represent the concepts.
What are common mistakes when building a conceptual model?
The two common failures are making the model too formal and never replacing it. A model full of multiplicities and data types cannot be checked by domain experts, so misunderstandings survive. A model kept as the final word also fails, because it was meant to lead into formal design. Keep it simple, validate it with experts, and move on once it is stable.

About the Software Engineering course

How many college credits is Software Engineering?
Software Engineering (Computer Science 301) carries a NCCRS credit recommendation for 3 semester credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
How much does Software Engineering cost and what is included?
$250, paid once, with lifetime access: all 103 video lessons, a practice quiz after each, the graded work and final exam, and an official transcript when you finish. Students who want several courses choose UPI Study PRO instead.
Which universities accept UPI Study credits?
UPI Study has signed partner agreements with universities such as Thomas Edison State University, University of the People and Charter Oak State College, and works with universities such as Penn State, SNHU and SUNY. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities. Use "Find my college" on this page to check yours.
How long does Software Engineering take?
It is self-paced with no deadlines. The 103 lessons total about 11 hours of video; most students add reading and practice time and finish in a few weeks to a few months, on their own schedule.
How are the exams done?
Quizzes and assignments are online in the course. The final exam is taken online with proctoring; a person on the UPI Study team checks assignments, usually within two days.
How do my credits reach my college?
When the course shows 100% complete, request the official transcript from your dashboard. It is sent to the college you name, and you can send it to more than one. Check your college first with "Find my college" on this page, or ask Athena.

Ready for the full course? Earn 3 credits in Software Engineering.

103 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.

Enroll in Software Engineering →Download the syllabusEvery course with PRO →
Software Engineering
3 credits · NCCRSEnroll →