Data Modeling: Define Your Data Before You Design | بالعربي

TITLE ON SCREEN: "Data Modeling — Know Your Data Before You Build"
Here is one of the most common mistakes beginner developers make: they open
their IDE, create a JFrame, and start dragging components onto the form —
before they have ever thought about what data the form actually needs to handle.
The result: they miss fields, group things incorrectly, use the wrong controls,
and then have to redesign everything from scratch.

The solution is Data Modeling — and it always comes BEFORE the form design.
SECTION 1: What is Data Modeling?
Data Modeling is the process of defining:
• What information does the application need to collect?
• How do we group related information logically?
• What data type does each field use?
• Which fields are required and which are optional?
Once you have a clear data model, you can:
• Design the right Java classes for the data
• Choose the right Swing control for each field
• Create a well-structured, complete form — with no missing fields
SECTION 2: How to Build a Data Model
Step 1 — List ALL data fields the form needs.
Step 2 — Group related fields into logical categories.
Step 3 — Define the data type for each field.
Step 4 — Mark which fields are required vs. optional.
Step 5 — Note any calculated fields (fields derived from other fields).
SECTION 3: Worked Example — Employee Form Data Model
[SHOW ON SCREEN — the following table:]
GROUP 1: MAIN / PERSONAL IDENTITY INFO
Field Data Type Notes
Employee ID int/String Auto-generated, unique identifier
National Number String National ID card number
First Name String Required
Second Name String Middle name / Father's name
Third Name String Grandfather's name
Last Name String Required

GROUP 2: EDUCATION INFO
Field Data Type Notes
Last Degree String Bachelor's, Master's, PhD
Institute Name String University or college
GPA double e.g., 3.75 out of 4.0
Major String Field of study
Degree Country String Country where degree was earned
Graduation Year int Year

GROUP 3: HR INFO
Field Data Type Notes
Job Title String e.g., Software Engineer, Manager
Department String e.g., IT, Finance, HR
Basic Salary double Monthly base salary
Allowances double Housing, transport, etc.
Deductions double Taxes, insurance
Net Salary CALCULATED = Basic + Allowances - Deductions

GROUP 4: PERSONAL INFO
Birth Date (Day, Month, Year) int
Gender String Male / Female
Address: Street, Building, Apt, City, Country — all String
Nationality String
Email String Must contain @

Text input → JTextField
Long text → JTextArea
Date → JSpinner with SpinnerDateModel, or JComboBoxes for day/month/year
Gender / select one → JComboBox or JRadioButton
Country / long list → JComboBox
Yes/No flag → JCheckBox
Multiple choices → multiple JCheckBoxes
Calculated field → JTextField set to setEditable(false)
Salary, GPA → JTextField with numeric validation in try-catch
Once the data model is defined, we design the Java classes.

[SHOW ON SCREEN — the Employee, Address, Education, HRInfo class structure:]

The Address group → becomes a dedicated Address class
The Education group → becomes an Education class
The HR group → becomes an HRInfo class with a getNetSalary() method
Employee → has fields for identity data plus composed objects:
Address address, Education education, HRInfo hrInfo

This is Composition — one of the OOP relationships we covered earlier.
Real data modeling always leads naturally to OOP class design.

Data modeling takes 15–30 minutes on paper.
It saves hours of redesign later.
Always define your data model before you open the IDE.
Next video: we build the Student Admission Form from scratch.

Видео Data Modeling: Define Your Data Before You Design | بالعربي канала Abdulrahman