School of Computer Science Engineering and Technology
Course- BTech Type- Core
Course Code- CSET201 Course Name- Information Management
System
Year- 2025 Semester- Odd
Date- 19/08/2025 Batch- 2024-2028
Type- Lab Assignment No. (Week 4, Assignment No. 3)
CO-Mapping
CO1 CO2 CO3
Q1 √ √
Q2 √ √
Objectives
1. Student will be able to learn the concept of ER Diagram.
2. Student will be able to learn the concept of primary key, foreign key.
3. Student will be able to association, aggregation and composition.
Link for ER diagram tools - [Link]
An Entity-Relationship (ER) diagram illustrates the connections between sets of entities. An entity
set pertains to a collection of akin entities, each possessing attributes. In the context of a Database
Management System (DBMS), an entity corresponds to a table or a table's attribute within a
database. Thus, by delineating the interrelationships amongst tables and their attributes, an ER
diagram depicts the comprehensive logical framework of a database. To grasp this notion better,
let's examine a basic ER diagram.
[Link] is a high-end property portal that caters to a global market with its unique services
and novel online features. Having been launched in the year 2006 by Times Group, Magicbricks has
quickly risen to being the No. 1 Property Portal in India.
Magicbricks' design is based on rigorous research, one-of-a-kind product developments, and an
innovative initiative that has been well received by users. Magicbricks realty portal features are
constantly invented, evaluated, and upgraded in order to better serve users. Magicbricks is a full-
service real estate provider, offering 15+ services such as home loans, rent payment, packers and
movers, legal assistance, property valuation, and expert advice. Magicbricks has an active base of
over 15 lakh property listings and is the largest platform for buyers and sellers of property to
connect in a transparent manner.
School of Computer Science Engineering and Technology
Create a database schema to store data about real estate properties. The following details should be
kept in your database:
Property: Represents a property listing.
Attributes: PropertyID (Primary Key), Title, Description, Price, Location, Type
Description: Stores information about a property listed on Magicbricks, including its details and
characteristics.
PropertyType: Defines property types (e.g., Apartment, House, Villa).
Attributes: TypeID (Primary Key), TypeName
Description: Represents different types of properties that can be listed.
PropertyFeature: Defines property features (e.g., Swimming Pool, Garden).
Attributes: FeatureID (Primary Key), FeatureName
Description: Represents various features that a property can have.
PropertyImage: Stores images associated with properties.
Attributes: ImageID (Primary Key), PropertyID (Foreign Key referencing Property), ImageURL
Description: Contains URLs of images linked to specific properties.
Relationships between Entities:
Property to PropertyType: Each property is assigned to a specific property type (e.g., Apartment,
House), whereas each property type can have multiple properties. This is a many-to-one
relationship.
Property to PropertyFeature: Each property may have multiple features (for example, a swimming
pool or a garden), and each feature may be associated with multiple properties. This results in a
many-to-many relationship.
Property to PropertyImage: Each property can have multiple images, but each image is only
associated with one property. As a result, a one-to-many relationship is formed.
Questions
School of Computer Science Engineering and Technology
Ql. Create an ER diagram of the real estate properties management system using the
constraints listed above.
Q2. Create every possible table for the case study mentioned above using SQL (Take necessary
assumptions wherever required).
