Scribd
Upload
5 views

Assignment No 1 Software Case

Uploaded by

mruzair135
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
5 views

Assignment No 1 Software Case

Uploaded by

mruzair135
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Subject:

Software case tools and application

Topic:
Data Modeling, Data Models

Submitted By:
Name: M Uzair Shakeel
Section: Bs SE (6th 3M)
Roll no. : F21BSEEN1M01077
Submitted to:
Miss Ayman Khan

The Islamia University of Bahawalpur


What is data modeling?
Data modeling is the process of creating a simplified
diagram of a software system and the data elements it contains, using text and symbols to
represent the data and how it flows. Data models provide a blueprint for designing a new
database or reengineering a legacy application. Overall, data modeling helps an
organization use its data effectively to meet business needs for information. A data model
can be thought of as a flowchart that illustrates data entities, their attributes and the
relationships between entities.

Types of data models


Like any design process, database and information system design begins at a high level of
abstraction and becomes increasingly more concrete and specific. Data models can
generally be divided into three categories, which vary according to their degree of
abstraction. The process will start with a conceptual model, progress to a logical model and
conclude with a physical model. Each type of data model is discussed in more detail in
subsequent sections:

Conceptual data models:


They are also referred to as domain models and offer a big-
picture view of what the system will contain how it will be organized, and which business
rules are involved. Conceptual models are usually created as part of the process of
gathering initial project requirements. Typically, they include entity classes (defining the
types of things that are important for the business to represent in the data model), their
characteristics and constraints, the relationships between them and relevant security and
data integrity requirements. Any notation is typically simple.

Logical data models:


They are less abstract and provide greater detail about the
concepts and relationships in the domain under consideration. One of several formal data
modeling notation systems is followed. These indicate data attributes, such as data types
and their corresponding lengths, and show the relationships among entities. Logical data
models don’t specify any technical system requirements. This stage is frequently omitted in
agile or DevOps practices. Logical data models can be useful in highly procedural
implementation environments, or for projects that are data-oriented by nature, such as
data warehouse design or reporting system development.

Physical data models:


They provide a schema for how the data will be physically stored
within a database. As such, they’re the least abstract of all. They offer a finalized design
that can be implemented as a relational database, including associative tables that
illustrate the relationships among entities as well as the primary keys and foreign keys
that will be used to maintain those relationships. Physical data models can include
database management system (DBMS)-specific properties, including performance
tuning.
ER Diagram:

Uml Diagram:

You might also like