Database Management System BCS403
Introduction to FIR File Management System Project
The FIR File Management System is a software solution designed to streamline and digitize
the process of filing, storing, retrieving, and managing First Information Reports (FIRs)
within police departments and law enforcement agencies. Traditionally, FIRs are maintained
in physical registers, which makes data handling, tracking, and communication inefficient
and time-consuming. This system aims to modernize the process through a secure and user-
friendly digital platform.
The project provides a centralized platform where citizens can register complaints, and
police officers can manage FIRs more efficiently. It supports role-based access—allowing
citizens to file and track complaints, while administrators and police officials can view,
update, and generate reports. Features such as automated report generation, real-time status
updates, and data backup contribute to better transparency, accessibility, and accountability
in the complaint registration process.
By leveraging technology, the FIR File Management System reduces paperwork, minimizes
human error, and speeds up investigative workflows, thereby enhancing the overall
effectiveness of the justice delivery system.
Objectives of FIR File Management System
1. Digitization of FIR Records: To eliminate manual paperwork and store all FIR-
related data in a secure digital format for easy access and management.
2. Simplify FIR Filing Process: To provide an easy-to-use interface for citizens to file
complaints online without the need to visit the police station in person.
3. Improve Data Accessibility and Retrieval: To allow quick and efficient search, view,
and retrieval of FIRs by authorized personnel.
4. Enhance Transparency and Accountability: To ensure that citizens can track the
status of their complaints in real-time, promoting trust in the system.
5. Role-Based Access Control: To maintain data security by providing different access
levels for citizens, police officers, and administrators.
6. Automated Report Generation: To facilitate the generation of reports and
summaries for internal analysis and administrative use.
7. Time and Resource Efficiency: To reduce delays in FIR processing and optimize the
workload of police staff.
8. Maintain Data Integrity and Backup: To ensure that FIR records are protected from
unauthorized modifications and regularly backed up for disaster recovery.
9. Scalability and Integration: To design the system in a way that it can be scaled and
integrated with other government or law enforcement databases in the future.
1|Page
Database Management System BCS403
Introduction to MongoDB
MongoDB is a high-performance, document-oriented NoSQL database that is well-suited for
managing complex and evolving data structures, such as those used in a First Information
Report (FIR) File Management System. Unlike traditional relational databases, MongoDB
stores data in flexible, JSON-like documents, which allows for dynamic fields and nested
data—ideal for capturing varying details in police reports and case files.
In an FIR management context—where each report may contain diverse information such as
complainant details, incident descriptions, suspects, evidence, case progress, and officer
notes—MongoDB provides key advantages:
Schema Flexibility: Easily handles the variable structure of FIRs, which may differ
from case to case.
Horizontal Scalability: Supports growing data volumes and user access across
multiple police departments or jurisdictions.
Real-time Performance: Enables fast retrieval and updates of case files, critical for
timely law enforcement actions.
Seamless Integration: Works effectively with web and mobile applications for on-
the-go data entry and case tracking.
By using MongoDB, an FIR File Management System can efficiently manage unstructured
or semi-structured data, reduce database maintenance overhead, and provide a responsive
interface for police officers, investigators, and administrative personnel.
Step 1: Define Entities (Tables)
We need tables for:
1. Officers
2. Victims
3. FIR
4. Evidence
5. Case_Updates
2|Page
Database Management System BCS403
Step 2: Create Tables with SQL Code
OFFICERS TABLE
CREATE TABLE Officers (
Officer_ID INT NOT NULL PRIMARY KEY,
Officer_Name VARCHAR(50),
Officer_Post VARCHAR(50),
Contact_Num VARCHAR(15)
);
VICTIMS TABLE
CREATE TABLE Victims (
Victim_ID INT NOT NULL PRIMARY KEY,
Victim_Name VARCHAR(50),
Victim_Address VARCHAR(100),
Phone_No VARCHAR(15)
);
FIR TABLE
CREATE TABLE FIR (
FIR_ID INT NOT NULL AUTO_INCREMENT PRIMARY KEY,
FIR_DATE DATE,
Crime_type VARCHAR(50),
Case_Status VARCHAR(50),
Location VARCHAR(50),
Officer_ID INT,
Victim_ID INT,
FOREIGN KEY (Officer_ID) REFERENCES Officers(Officer_ID),
FOREIGN KEY (Victim_ID) REFERENCES Victims(Victim_ID)
);
3|Page
Database Management System BCS403
EVIDENCE TABLE
CREATE TABLE Evidence (
Evidence_ID INT NOT NULL PRIMARY KEY,
FIR_ID INT,
Evidence_Description TEXT,
Evidence_type VARCHAR(50),
Storage_location VARCHAR(100),
FOREIGN KEY (FIR_ID) REFERENCES FIR(FIR_ID)
);
CASE_UPDATES TABLE
CREATE TABLE Case_Updates (
Update_ID INT NOT NULL PRIMARY KEY,
FIR_ID INT,
Update_Time TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
Officer_ID INT,
Status_Update VARCHAR(50),
Remarks TEXT,
FOREIGN KEY (FIR_ID) REFERENCES FIR(FIR_ID),
FOREIGN KEY (Officer_ID) REFERENCES Officers(Officer_ID)
);
Step-by-Step Workflow
Add Officer Details
INSERT INTO Officers (Officer_ID,Officer_Name,Officer_Post, Contact_Num)
VALUES
(1,'Rajeev Kumar', 'Sub-Inspector', '9876543210'),
(2,'Priya Singh', 'Constable', '9876543211'),
(3,'Anil Verma', 'Inspector', '9876543212'),
(4,'Neha Deshmukh', 'Assistant Sub-Inspector', '9894011122'),
(5,'Sandeep Patil', 'Constable', '9765432100'),
(6,'Aman Gupta', 'Inspector', '9810023344');
Output:
SELECT * FROM Officers;
4|Page
Database Management System BCS403
Officer_ID Officer_Name Officer_Post Contact_Num
1 Rajeev Kumar Sub-Inspector 9876543210
2 Priya Singh Constable
3 Anil Verma Inspector 9876543211
4 Neha Deshmukh Assistant Sub-Inspector
9876543212
5 Sandeep Patil Constable
6 Aman Gupta Inspector 9894011122
9765432100
9810023344
Add Victim Details
INSERT INTO Victims (Victim_ID, Victim_Name, Victim_Address, Phone_No)
VALUES
(1,'Sunita Sharma', '23 MG Road, Indore, Madhya Pradesh', '9826012345'),
(2,'Mohammed Faiz', '10 Park Street, Lucknow, Uttar Pradesh', '9834098765'),
(3,'Kavita Iyer', 'Flat 7B, Raghuram Apartments, Chennai, Tamil Nadu', '9894898756'),
(4,'Ravi Mehta', '202 Vasant Kunj, Delhi', '9812233445'),
(5,'Lalita Joshi', '3rd Cross Road, Koramangala, Bengaluru', '9845098756'),
(6,'Jitendra Kumar', 'Near City Chowk, Patna, Bihar', '9700556600');
Output:
SELECT * FROM Victims;
Victim_ID Victim_Name Victim_Address Phone_No
1 Sunita Sharma 23 MG Road, Indore, Madhya 9826012345
Pradesh
2 Mohammed Faiz 10 Park Street, Lucknow, Uttar 9834098765
Pradesh
3 Kavita Iyer Flat 7B, Raghuram Apartments, 9894898756
Chennai, Tamil Nadu
4 Ravi Mehta 202 Vasant Kunj, Delhi 9812233445
5 Lalita Joshi 3rd Cross Road, 9845098756
Koramangala,
Bengaluru
6 Jitendra Kumar Near City Chowk, Patna, 9700556600
5|Page
Database Management System BCS403
Bihar
Add FIR Details
INSERT INTO FIR (FIR_ID,FIR_Date, Crime_type, Case_Status, Location, Officer_ID,
Victim_ID)
VALUES
(1,'2025-04-28', 'Chain Snatching', 'Open', 'Sector 17, Chandigarh', 1, 1),
(2,'2025-05-01', 'Burglary', 'Under Investigation', 'Charminar Area, Hyderabad', 2, 2),
(3,'2025-05-03', 'Assault', 'Closed', 'Marine Drive, Mumbai', 3, 3),
(4,'2025-05-04', 'Cyber Fraud', 'Under Investigation', 'Salt Lake Sector V, Kolkata', 4, 4),
(5,'2025-05-06', 'Domestic Violence', 'Open', 'BTM Layout, Bengaluru', 5, 5),
(6,'2025-05-07', 'Hit and Run', 'Open', 'Ashok Rajpath, Patna', 6, 6);
Output:
SELECT * FROM FIR;
FIR_ID FIR_Date Crime_type Case_Status Location Officer_ID Victim_ID
1 2025-04-28 Chain Open Sector 17, 1 1
Snatching Chandigarh
2 2025-05-01 Burglary Under Charminar 2 2
Investigation Area,
Hyderabad
3 2025-05-03 Assault Closed Marine 3 3
Drive,
Mumbai
4 2025-05-04 Cyber Fraud Under Salt Lake 4 4
Investigation Sector V,
Kolkata
5 2025-05-06 Domestic Open BTM 5 5
Violence Layout,
Bengaluru
6 2025-05-07 Hit and Run Open Ashok 6 6
Rajpath,
Patna
6|Page
Database Management System BCS403
Add Evidence Details
INSERT INTO Evidence (Evidence_ID, FIR_ID, Evidence_Description, Evidence_Type,
Storage_Location)
VALUES
(1, 1, 'Gold chain recovered from crime scene', 'Physical Object', 'Indore Police Station
Evidence Room'),
(2, 2, 'Smashed window and tool found', 'Photograph', 'Hyderabad Central Station
Archive'),
(3, 3, 'Medical report of injuries', 'Document', 'Mumbai Crime Record Office'),
(4, 4, 'Email phishing screenshot and bank statement', 'Digital', 'Cyber Cell, Kolkata
Police HQ'),
(5, 5, 'Doctor\'s medical examination report', 'Document', 'Women Safety Unit,
Bengaluru'),
(6, 6, 'Car bumper found near accident spot', 'Physical Object', 'Forensics Lab, Patna
HQ');
Output:
SELECT * FROM Evidence;
Evidence_ID FIR_ID Evidence_Description Evidence_Type Storage_Location
1 1 Gold chain recovered Physical Object Indore Police
from crime scene Station Evidence
Room
2 2 Smashed window and Photograph Hyderabad
tool found Central Station
Archive
3 3 Medical report of Document Mumbai Crime
injuries Record Office
4 4 Email phishing Digital Cyber Cell,
screenshot and bank Kolkata Police
statement HQ
5 5 Doctor's medical Document Women Safety
examination report Unit, Bengaluru
6 6 Car bumper found near Physical Object Forensics Lab,
accident spot Patna HQ
7|Page
Database Management System BCS403
Add Case_Upsates
INSERT INTO Case_Updates (Update_ID, FIR_ID, Officer_ID, Status_Update,
Remarks)
VALUES
(1, 1, 1, 'FIR Registered', 'Investigation team formed and CCTV footage collected.'),
(2, 2, 2, 'Suspect Identified', 'Fingerprint match found; warrant issued.'),
(3, 3, 3, 'Case Closed', 'Suspect convicted in district court.'),
(4, 4, 4, 'Complaint Logged', 'Bank transaction logs collected for investigation.'),
(5, 5, 5, 'Medical Examination Done', 'Victim\'s medical report submitted.'),
(6, 6, 6, 'Vehicle Traced', 'CCTV footage led to vehicle identification.');
Output:
SELECT * FROM Case_Updates;
Update_ID FIR_ID Officer_ID Status_Update Remarks
1 1 1 FIR Registered Investigation team
formed and CCTV
footage collected.
2 2 2 Suspect Identified Fingerprint match
found; warrant issued.
3 3 3 Case Closed Suspect convicted in
district court.
4 4 4 Complaint Logged Bank transaction logs
collected for
investigation.
5 5 5 Medical Examination Victim's medical report
Done submitted.
6 6 6 Vehicle Traced CCTV footage led to
vehicle identification.
8|Page
Database Management System BCS403
FIR Management System
System Overview
The FIR (First Information Report) Management System is a web-based database
application designed to simplify and digitize the process of filing, tracking, and managing
police complaints. The system provides a structured way for both citizens and police
departments to handle FIRs efficiently, ensuring transparency, accountability, and ease of
access.
Objective
The main goal of this system is to automate the traditional manual process of lodging
FIRs, thus reducing paperwork, minimizing delays, and improving case management by
maintaining a centralized digital record.
Users of the System
1. Admin/Police Officer
• Register/view FIRs
• Update investigation status
• Assign officers to cases
• Generate reports
2. Citizen/Complainant
• Register/login
• File new FIR
• Track status of submitted FIRs
Functionalities
• User authentication and role-based access
• Online FIR registration with incident details
• Automatic FIR number generation
• FIR status updates by officers
• FIR assignment to investigating officers
9|Page
Database Management System BCS403
• View FIR history and details
• Search FIRs by various filters (date, location, status, etc.)
• Generate printable FIR reports
System Architecture
1. Frontend (User Interface):
• Web interface for both citizens and police
• Forms for FIR submission and status tracking
2. Backend (Application Logic):
• Business logic to handle FIR lifecycle
• Authentication and access control
• FIR assignment and status update workflows
3. Database (Storage Layer):
• Stores user details, FIR records, officer assignments, case statuses
• Ensures data integrity and fast retrieval
10 | P a g e
Database Management System BCS403
Implementation of FIR Management System
The implementation of the FIR Management System involves the development of a web-
based application using a three-tier architecture: Presentation Layer (Frontend), Application
Layer (Backend), and Data Layer (Database). The project is designed for easy use by both
citizens and police departments, ensuring proper management of complaints and case
investigations.
1. Frontend (Presentation Layer)
The frontend is responsible for user interaction. It includes interfaces for citizen and admin
(police) roles.
Technologies Used:
• HTML5, CSS3
• JavaScript
• Bootstrap (for responsive design)
Key Pages:
• Home Page: Introduction and navigation
• Login / Registration Page: For both citizens and police
• FIR Submission Page: Form to file a new FIR
• FIR Status Page: View and track FIR status
• Admin Dashboard: View/manage all FIRs, assign officers
2. Backend (Application Layer)
The backend processes user requests, performs business logic, and communicates with the
database.
Technologies Used:
• PHP / Python (Flask or Django) / Node.js (choose based on your project setup)
• RESTful APIs (optional for scalability)
• Session management for secure logins
•
11 | P a g e
Database Management System BCS403
Functionalities:
• User authentication (login, registration)
• FIR creation with auto-generated FIR number
• FIR status updates by police officers
• Assignment of FIRs to officers
• Role-based access control (admin vs. citizen)
3. Database (Data Layer)
The database stores all information related to users, FIRs, and assignments.
Technologies Used:
MySQL / SQLite / PostgreSQL (based on availability)
Main Tables:
Officers (Officer_ID,Officer_Name,Officer_Post, Contact_Num)
Victims (Victim_ID, Victim_Name, Victim_Address, Phone_No)
FIR (FIR_ID,FIR_Date, Crime_type, Case_Status, Location, Officer_ID, Victim_ID)
Case_Updates (Update_ID, FIR_ID, Officer_ID, Status_Update, Remarks)
Evidence (Evidence_ID, FIR_ID, Evidence_Description, Evidence_Type, Storage_Location)
4. System Flow
1. Citizen registers/logs in.
2. Citizen fills and submits the FIR form.
3. FIR gets stored in the database with status “Open”.
4. Admin (Police) logs in and views submitted FIRs.
5. Admin assigns FIR to a police officer.
6. Officer updates status as the case progresses (e.g., Under Investigation, Closed).
12 | P a g e
Database Management System BCS403
7.
7. Citizen can view the status at any time from their dashboard.
5. Sample Screenshots / UI Mockups
(You can insert screenshots or sample UI designs of login page, FIR form, status page, admin
dashboard, etc.)
6. Security Measures
• Password hashing using bcrypt or similar
• Input validation to prevent SQL injection
• Role-based access control to restrict unauthorized actions
Final Output
Fully functional FIR portal
Citizens can file and track complaints online
Admin can manage, assign, and update FIRs
All data is securely stored and easily retrievable
SCHEMA DIAGRAM:
13 | P a g e
Database Management System BCS403
CONCLUSION
The FIR Management System is a robust and user-friendly platform developed to digitize
and streamline the process of filing and managing First Information Reports. By replacing
the traditional paper-based system with a centralized, database-driven application, the system
enhances transparency, accountability, and efficiency in police complaint handling.
This project successfully achieves its objectives by:
Allowing citizens to file FIRs online and track their status.
Providing police officers and administrators with tools to manage and update FIR records.
Ensuring secure storage of sensitive data through role-based access and authentication
mechanisms.
The system reduces manual workload, speeds up the registration and investigation processes,
and ensures better coordination between citizens and law enforcement authorities. With
future enhancements like SMS/email alerts, advanced analytics, and mobile app integration,
this system can be scaled further to become a comprehensive law enforcement management
solution.
14 | P a g e
