Person with Disability (PWD) Information System ER Diagram

Person with Disability (PWD) Information System ER Diagram

The capstone project entitled Person with Disability (PWD) Information System is an online platform specifically intended to record the information of PWD in an electronic or digital version. It is a city wide project wherein every barangay of the city or municipality can encode their PWD in the system. The records will be consolidated in the city hall where the administrator of the system can access the records of every barangay. This project was developed to easily disseminate information and activities related to PWD or person with disability.

You may visit and read the articles posted in relation to Person with Disability (PWD) Information System

  1. Person with Disability (PWD) Information System Database Design
  2. Person with Disability Information System Free Template in PHP and Bootstrap
  3. Abstract of Person with Disability (PWD) Information System

This article will discuss the step by step process on how to prepare the entity relationship diagram or ERD of the project entitled Person with Disability (PWD) Information System .

The first step in the development of the Person with Disability (PWD) Information System  is to prepare the ER diagram that will serve as the basis later on in the creation of the actual database.

We will create and explain the process of making the entity relationship diagram of Person with Disability (PWD) Information System .

Let’s start from the symbols used in the ER Diagram.

Entity is represented by the rectangle shape. The entity will be our database table of Person with Disability (PWD) Information System  later on.

Attribute is represented by the oval shape. This will be the columns or fields of each table in the Person with Disability (PWD) Information System .

Relationship is represented by diamond shape. This will determine the relationships among entities. This is usually in a form of primary key to foreign key connection.

We will follow the 3 basic rules in creating the ER Diagram.

  1. Identify all the entities.
  2. Identify the relationship between entities and
  3. Add meaningful attributes to our entities.

Step 1. In the Person with Disability (PWD) Information System  we have the following entities

  • User
  • User Group
  • Barangay
  • Blood Type
  • Disability Type
  • Services
  • PWD Information
  • Notification

Our design of Person with Disability (PWD) Information System consists of 8 entities; the specified entities will be our database tables in the design and implementation of PWD Information System database schema.

We will now draw the entities of the Person with Disability (PWD) Information System  specified above and it will be represented by a rectangle shape. The image below is the entities identified in the scope of the Person with Disability (PWD) Information System .

Person with Disability (PWD) Information System ER Diagram - Step 1 Identify Entities
Person with Disability (PWD) Information System ER Diagram – Step 1 Identify Entities

Step 2. After we have specified our entities, it is time now to connect or establish a relationship among the entities.

Person with Disability (PWD) Information System ER Diagram - Step 2 Table Relationship
Person with Disability (PWD) Information System ER Diagram – Step 2 Table Relationship
  • User of the system belongs to a specific user type or group that corresponds with their role and permissions. The user group includes the functions the user can access (1 to 1 relationship).
  • The user encodes, updates, and manages the notification information (1 to many relationship).
  • The user encodes, updates, and manages the disability type information (1 to many relationship). The administrator type of user can only access this information
  • The user encodes, updates, and manages the blood type information (1 to many relationship). The administrator type of user can only access this information
  • The user encodes, updates, and manages the barangay information (1 to many relationship). The administrator type of user can only access this information
  • The user encodes, updates, and manages the services information (1 to many relationship).
  • The user encodes, updates, and manages the PWD information (1 to many relationship). The user per barangay is the one who will encode their respective PWD information.

Step 3. The last part of the ERD process is to add attributes to our entities.

Person with Disability (PWD) Information System ER Diagram - Step 3 Complete ERD
Person with Disability (PWD) Information System ER Diagram – Step 3 Complete ERD

User Entity has the following attributes:

  • User ID – primary key represented with underline
  • Username
  • Password
  • Fullname
  • Avatar
  • Email
  • Contact
  • User Category – foreign key
  • Status

User Group Entity has the following attributes:

  • User Group ID – primary key represented with underline
  • Name
  • Description
  • Allow Add
  • Allow Edit
  • Allow Print
  • Allow Export
  • Allow Import
  • Allow Delete

Barangay Entity has the following attributes:

  • Brgy ID – primary key represented with underline
  • Barangay Name
  • Brgy Information
  • User ID – foreign key

Blood Type Entity has the following attributes:

  • Blood Type ID – primary key represented with underline
  • Blood Type
  • Blood Type Info

Disability Type Entity has the following attributes:

  • Disability Type ID – primary key represented with underline
  • Disability Type Name
  • Description

Services Entity has the following attributes:

  • Services ID – primary key represented with underline
  • Service Name
  • Date Recorded
  • Remarks
  • PWD ID – foreign key
  • User ID – foreign key

PWD Information Entity has the following attributes:

  • PWD ID – primary key represented with underline
  • Brgy ID – foreign key
  • PWD City Code No
  • Profile Picture
  • First name
  • Middle name
  • Last name
  • Contact Number
  • Complete Address
  • Birthdate
  • Birthplace
  • Blood Type ID – foreign key
  • Disability Type ID – foreign key
  • Philhealth
  • Employment Type
  • Gender
  • Occupation
  • Emergency Contact Person
  • Emergency Contact Address
  • Relationship to Contact Person
  • User ID – foreign key

Notification Entity has the following attributes:

  • Notification ID – primary key represented with underline
  • Notification Name
  • Notification Message
  • Notification Date
  • Message Intended To
  • User ID – foreign key

Note: all attributes with underline represents the primary key of the entity or table.

The next step is to convert the plan designed on ER Diagram into the actual database, please search for the Person with Disability (PWD) Information System article which was already posted.

Contact us on our facebook page for the softcopy of the Person with Disability (PWD) Information System .

You may visit our facebook page for more information, inquiries and comments.

Hire our team to do the project.

, ,

Post navigation