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:

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 is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.

Resource Leveling

Resource leveling is a resource optimization technique in which adjustments are made to the project schedule to keep resource usage at or below a defined limit, often resulting in a longer project duration.

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.

Stakeholder Mapping

Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.

Relative Estimation

Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.

Cost Performance Index (CPI)

Cost Performance Index (CPI) is an EVM efficiency metric that measures cost performance as the ratio of earned value to actual cost: CPI = EV / AC.

Schedule Performance Index (SPI)

Schedule Performance Index (SPI) is an EVM efficiency metric that measures schedule performance as the ratio of earned value to planned value: SPI = EV / PV.

Earned Value Management (EVM)

Earned Value Management (EVM) is a methodology that integrates scope, schedule, and cost data to assess project performance and progress objectively.

Part of

Tools & Techniques

Study full domain →

Test your knowledge

Practice scenario-based questions on this topic with detailed explanations.