Skip to content
PMPCAPM

Logical Data Model

A logical data model is a data representation technique that visually describes the data entities, attributes, and relationships within an organization or system without regard to physical implementation.

Share:

Know it well enough for the exam? Questions on Logical Data Model are scenario-based, not definitional.

Practice it free

Explanation

A logical data model is a visual representation of an organization's data, showing entities (things about which data is stored), their attributes (characteristics), and the relationships between them. Unlike a physical data model, which describes how data is stored in a database, a logical data model is technology-independent and focuses on what data is needed and how it relates, not how it will be implemented.

In project management, logical data models are used during requirements analysis, particularly for projects involving system development, data migration, or business process reengineering. They help the project team and stakeholders agree on the data requirements before committing to a technical solution. Entity-Relationship Diagrams (ERDs) are the most common format for logical data models.

Logical data models serve as a bridge between business requirements and technical design. They ensure that the project team understands the data landscape and that the technical solution will support the organization's information needs.

Key Points

  • •Describes data entities, attributes, and relationships visually
  • •Technology-independent, focused on business data requirements
  • •Entity-Relationship Diagrams (ERDs) are the most common format
  • •Bridges business requirements and technical database design

Exam Tip

A logical data model is about WHAT data is needed and how it relates, not HOW it is stored. If a question asks about technology-independent data representation, this is the answer.

Frequently Asked Questions

Related Topics

High-yield topics our learners drill most before exam day.

Matrix Diagrams

Matrix diagrams are a data representation technique that uses a grid format to show relationships between two or more groups of factors, commonly used for responsibility assignments and prioritization.

Burndown Chart

A burndown chart plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.

Burn-Up Chart

A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.

Resource Leveling

Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.

Deliverables

A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.

Power Interest Grid (Power/Influence Grid)

The power interest grid is a 2x2 stakeholder mapping tool that plots each stakeholder by power (ability to affect the project) and interest (concern about its outcome) to decide how to engage them: manage closely, keep satisfied, keep informed, or monitor.

Critical Path Method (CPM)

The Critical Path Method (CPM) is a schedule network analysis technique that calculates early and late start and finish dates for every activity to find the longest path through the project, the minimum project duration, and the float on every other path.

Weighted Shortest Job First (WSJF)

Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.

Risk Register

The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.

Part of

Tools & Techniques

Study full domain →

Practice Logical Data Model

Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.