UNIVERSITY OF SOUTH AFRICA (UNISA)
College of Science, Engineering and Technology
⋄
INF3703 – DATABASE II
ASSIGNMENT 02 – 2026
Database Design for Huurkor Property Group
⋄
Module Code: INF3703
Module Name: Database II
Assignment No.: Assignment 02
Due Date: 26 June 2026
Semester: Semester 1, 2026
Submitted in partial fulfilment of the requirements for INF3703 – Database II
at the University of South Africa.
,UNISA | INF3703 Huurkor Property Group – Database Design
Question 1: Organisation and Problem Identification
1.1 Background of the Organisation
Huurkor Property Group is a South African property management company founded in 1968 by
the late Mr R.J. Venter. Headquartered at 187 Robert Sobukwe Street, Sunnyside, Pretoria, in
the Gauteng province, the company has grown over more than five decades into one of the most
widely recognised Sectional Title Administrators in the region. The group operates through two
main entities: Huurkor (Pty) Ltd, which is responsible for the letting and sale of commercial
buildings, factories, blocks of flats, single units and houses; and HuurkorAdmin (Pty) Ltd, which
handles the administrative management of community schemes such as bodies corporate and
home owners associations. Both entities are registered with the Property Practitioners Regulatory
Authority (PPRA) and hold compulsory fidelity cover as required by law.
The company’s service portfolio covers levy collection, budget preparation, insurance claim
management, utility metering, council account payments and maintenance coordination across
residential, industrial and commercial schemes (HuurkorAdmin, 2025). With properties spread
across Gauteng and a large volume of tenants, owners, properties and financial transactions to
track, the organisation handles a considerable amount of data on a daily basis.
1.2 Identified Database Problems
Despite its long operational history, Huurkor Property Group currently faces several database-
related challenges that reduce operational efficiency and increase the risk of data errors.
Problem 1: Fragmented and inconsistent record-keeping. Tenant records, lease agreements,
payment histories, maintenance requests and owner information are stored across separate
spreadsheets and filing systems. There is no single integrated repository where all property-
related data is linked. This fragmentation means that when a tenant changes a unit or a property
is sold, data must be updated in multiple places manually, raising the risk of inconsistency.
Problem 2: Absence of a centralised transaction and levy management system. Levy
payments, council account disbursements, insurance premiums and other financial transactions
are processed without a single unified database tracking them. This makes it difficult to generate
accurate financial reports or identify overdue accounts quickly.
Problem 3: No structured maintenance request tracking. When tenants log maintenance
requests, these are recorded informally. There is no database entity linking a tenant, the specific
unit, the type of fault and the contractor assigned to resolve it. This leads to requests falling
through the cracks and no audit trail for completed repairs.
Problem 4: Utility metering data is not integrated with tenant billing. Huurkor Admin’s
metering services read electricity and water meters per unit, but the data from these readings is
not automatically linked to tenant invoices in a consolidated database, requiring staff to transfer
figures by hand each month.
The proposed solution is to design a new relational database that consolidates all property,
tenant, owner, lease, financial and maintenance data into a structured, integrated system. This
will address data redundancy, improve reporting accuracy, and support the growing volume of
Page 1 of 15
, UNISA | INF3703 Huurkor Property Group – Database Design
transactions the company processes.
Key Distinction
Scope of This Database Design: This assignment proposes a new database. Since
Huurkor Property Group does not currently operate an integrated relational database
system, there is no existing conceptual or logical model to present before the proposed
one. The design that follows is entirely new.
Page 2 of 15
College of Science, Engineering and Technology
⋄
INF3703 – DATABASE II
ASSIGNMENT 02 – 2026
Database Design for Huurkor Property Group
⋄
Module Code: INF3703
Module Name: Database II
Assignment No.: Assignment 02
Due Date: 26 June 2026
Semester: Semester 1, 2026
Submitted in partial fulfilment of the requirements for INF3703 – Database II
at the University of South Africa.
,UNISA | INF3703 Huurkor Property Group – Database Design
Question 1: Organisation and Problem Identification
1.1 Background of the Organisation
Huurkor Property Group is a South African property management company founded in 1968 by
the late Mr R.J. Venter. Headquartered at 187 Robert Sobukwe Street, Sunnyside, Pretoria, in
the Gauteng province, the company has grown over more than five decades into one of the most
widely recognised Sectional Title Administrators in the region. The group operates through two
main entities: Huurkor (Pty) Ltd, which is responsible for the letting and sale of commercial
buildings, factories, blocks of flats, single units and houses; and HuurkorAdmin (Pty) Ltd, which
handles the administrative management of community schemes such as bodies corporate and
home owners associations. Both entities are registered with the Property Practitioners Regulatory
Authority (PPRA) and hold compulsory fidelity cover as required by law.
The company’s service portfolio covers levy collection, budget preparation, insurance claim
management, utility metering, council account payments and maintenance coordination across
residential, industrial and commercial schemes (HuurkorAdmin, 2025). With properties spread
across Gauteng and a large volume of tenants, owners, properties and financial transactions to
track, the organisation handles a considerable amount of data on a daily basis.
1.2 Identified Database Problems
Despite its long operational history, Huurkor Property Group currently faces several database-
related challenges that reduce operational efficiency and increase the risk of data errors.
Problem 1: Fragmented and inconsistent record-keeping. Tenant records, lease agreements,
payment histories, maintenance requests and owner information are stored across separate
spreadsheets and filing systems. There is no single integrated repository where all property-
related data is linked. This fragmentation means that when a tenant changes a unit or a property
is sold, data must be updated in multiple places manually, raising the risk of inconsistency.
Problem 2: Absence of a centralised transaction and levy management system. Levy
payments, council account disbursements, insurance premiums and other financial transactions
are processed without a single unified database tracking them. This makes it difficult to generate
accurate financial reports or identify overdue accounts quickly.
Problem 3: No structured maintenance request tracking. When tenants log maintenance
requests, these are recorded informally. There is no database entity linking a tenant, the specific
unit, the type of fault and the contractor assigned to resolve it. This leads to requests falling
through the cracks and no audit trail for completed repairs.
Problem 4: Utility metering data is not integrated with tenant billing. Huurkor Admin’s
metering services read electricity and water meters per unit, but the data from these readings is
not automatically linked to tenant invoices in a consolidated database, requiring staff to transfer
figures by hand each month.
The proposed solution is to design a new relational database that consolidates all property,
tenant, owner, lease, financial and maintenance data into a structured, integrated system. This
will address data redundancy, improve reporting accuracy, and support the growing volume of
Page 1 of 15
, UNISA | INF3703 Huurkor Property Group – Database Design
transactions the company processes.
Key Distinction
Scope of This Database Design: This assignment proposes a new database. Since
Huurkor Property Group does not currently operate an integrated relational database
system, there is no existing conceptual or logical model to present before the proposed
one. The design that follows is entirely new.
Page 2 of 15
