Development Of A Web Based Human Right Violation Reporting System For National Human Rights Commission

This approach is adopted due to the following reasons:
i.    The proposed system requirements are well known, and understood.
ii.    The proposed system requirements are not ambiguous.
iii.    The technology and required resources for the development of this system are freely available.
3.6    The Proposed System
3.6.1    System Overview
The system is designed to address the problems facing the existing reporting system at National Human Rights Commission (NHRC) Nigeria. The stake holders of this system are the NHRC Executive Secretary, The Governing Council and the Complainant.
3.6.2    The Stakeholders of the Proposed System
This refers to the various groups of people that can access the system. They are:
i.    The NHRC Executive Secretary and The Governing Council: This is the section where the NHRC Executive Secretary and The Governing Council will be able gain access to the reported cases after register and login to the system. They will have access to view all the submitted cases and update the case status as the cases are being reviewed.
ii.    The Complainant: This section is for any Nigerian citizen that want to lodge a human rights violation complaint to the commission. The complainant will fill the complainant form and provide related evidence of the event. The complainant can also keep track of their submitted cases to know if their cases are being attending to.
3.7    Database Design for the Proposed System
Database design is the process of producing a detailed data model of database. This data model contains all the needed logical and physical design choices and physical storage parameters needed to generate a design in a data definition language, which can then be used to create a database.
3.7.1    Database Schema Design of the Proposed System
The figure 3.2 below is the physical representation of the proposed system’s database. The database section displays the connection of both users in all the three layers i.e. (application layer, client layer and server layer) to submit the necessary information, keep track of the submitted case and view all the submitted cases through the application interface.

An entity relationship (ER) diagram is graphical representation of entities and their relationships to each other, typically used in computing in regard to the organization of data within databases or information systems.
Figure 3.3 below shows the entity relationship model for the proposed system and how they relate with each other.