DBST 660 is a three-credit graduate course at the University of Maryland Global Campus, with DBST 651 as the prerequisite.
UMGC describes it as an introduction to the concepts and techniques for designing databases for structured and unstructured data, including database quality techniques and best practices for choosing modeling methods and tools.
The central skill is choosing the right model for the job. The course names relational, dimensional, wide column, document and graph/RDF models, and assignments require a remote access laboratory. Students often find it hard because the best answer depends on how the data will be used.
Course at a Glance
| Item | Details |
|---|---|
| University | University of Maryland Global Campus (UMGC) |
| Code and title | DBST 660 Advanced Data Modeling |
| Credits | 3 |
| Prerequisite | DBST 651 |
| Lab | Assignments require use of a remote access laboratory |
| Subject area | Database design and modeling |
What DBST 660 Covers
| Model type (from UMGC) | Best suited to |
|---|---|
| Relational | Transactional data with clear structure and integrity rules |
| Dimensional | Analytical reporting using facts and dimensions |
| Wide column | Large-scale data accessed by known row keys and column families |
| Document | Flexible, nested records such as JSON |
| Graph/RDF | Data where relationships are the main subject |
The course also covers database quality techniques and the selection of modeling tools.
Key Concepts Explained
Fitting the Model to the Use Case
Start with the questions the system must answer. Frequent joins across many entities suggest relational or graph; summaries by time and category suggest dimensional; varied nested records suggest document.
Illustrative example: A retailer reports sales by product, store and month. A star schema with a sales fact table and product, store and date dimensions makes those summaries simple. Modeling the same data as fully normalized transactional tables works, but reports need many joins.
Denormalisation on Purpose
Document and dimensional models often repeat data deliberately to speed reads. The key is to say what is duplicated and how consistency is maintained.
Model Quality
Quality checks include completeness, consistent naming, correct keys and cardinality, and traceability to requirements. Showing that you checked these is part of a strong answer.
Typical Assignments and How to Approach Them
| Assignment type | What it tests | How to approach it |
|---|---|---|
| Model design from a case | Selecting and applying a model | List the questions the data must answer before drawing |
| Model comparison | Understanding strengths and limits | Use a table of criteria for each model type |
| Modeling tool lab | Producing diagrams in a tool | Learn the notation first, then the tool |
| Quality review | Checking a model against requirements | Build a checklist and apply it line by line |
Where Students Get Stuck
- Choosing by habit. Justify the model with the use case, not familiarity.
- Notation errors. Cardinality symbols and arrow directions differ between notations.
- Unstructured data. Decide what structure is needed at read time and what can stay flexible.
- Missing rationale. Explain why alternatives were rejected.
Planning Your Work
| Stage | Do this | Output |
|---|---|---|
| Read the case | List entities, relationships and key queries | Requirements list |
| Choose model | Score options against criteria | Comparison table |
| Draw | Build the diagram in the required tool | Model file |
| Review | Apply a quality checklist | Corrections and notes |
A comparison table is the fastest route to strong marks. Rows can be criteria such as flexibility, query speed, integrity, and ease of change, columns the candidate models, and a final line the choice with a one-sentence reason.
A Worked Comparison: Document Versus Relational
Illustrative example: A product catalog where each product has different attributes (a laptop has RAM and screen size, a shirt has size and color). In a relational model this needs many nullable columns or an attribute table. In a document model each product is one record with only its own attributes, which suits flexible catalogs. The cost is weaker enforcement of consistent fields and harder cross-product reports.
The reasoning pattern is: what varies, what must stay consistent, and what questions will be asked. Apply it to any case study and state the answer for each model in the comparison.
When you present a model, label the notation and the assumptions. A short assumptions list, such as "each order has one customer" or "prices are stored at the time of sale", prevents markers from misreading your diagram and shows you thought about the business rules.
Finally, remember that a hybrid is sometimes the best answer. Many organizations keep transactions in a relational store and send summaries to a dimensional or document store. If you recommend this, explain how the data moves and how often.
Study Tips for DBST 660
- Learn one notation well and use it consistently.
- Practice converting one small data set into three models.
- For each model, write what it is bad at; this is as important as what it is good at.
- Keep a requirements-to-model trace so you can show where each entity came from.
How We Help with DBST 660
Send the case, rubric, diagrams and feedback. We can explain concepts, prepare custom worked solutions, or review your own models and rationale for gaps. We do not log in to lab environments for you.
GradeEssays is independent of UMGC. Our work is a study and reference aid; you complete and submit your own work under UMGC's academic integrity policy. Orders are written from scratch, include free revisions within the scope of your original request, and are refunded in full if late.
Make Sense of Your DBST 660 Models
Share the case study and your attempt. A database writer prepares a worked model to study and compare with.
Start My DBST 660 HelpFree revisions · Full refund if late · Written from scratch for your order
Frequently Asked Questions
DBST 651.
Relational, dimensional, wide column, document and graph/RDF, according to UMGC.
Yes, assignments require use of a remote access laboratory.
Three credits.
Yes, UMGC says it introduces designing databases for structured and unstructured data.
DBST 665 focuses on data warehouses; dimensional modeling here is a useful foundation.