A
PROJECT REPORT
ON
Car insurance system
Towards partial fulfillment of the requirement in
<Semester><Program><Year>
Submitted By:-
<190510101115> <Karan .K. Patel>
<190510101114> <Parth.A.Patel>
<Enrollment Number> <Student Name>
Submitted To:-
Parul Institute of Computer Application,
Parul University.
Under The Guidance of
<Khyati Bane>
<Abhishek Mehta - Assistant Professor> OR < Arpan Raval - Assistant Professor >
OR <Bhavika Vaghela - Assistant Professor> OR <Jinal Shah - Assistant Professor
> OR <Khyati Vyas - Assistant Professor>OR < Vijya Tulsani - Assistant Professor>
<System Name> 2019-20
__________________________________________________________________________________________________________________________________________
INDEX
Content Page No.
1. Introduction to Project System
2. System Requirement Specification
2.1 Introduction to SRS
2.2 Literature Review
2.3 Hardware Requirement
2.4 Software Requirement
2.5 System Users
2.6 Description of User Role
2.7 System Modules
2.8 Description of Modules
2.9 Timeline Chart
3. System Flow Diagram
4. Data Dictionary
5. Screenshots of Development Phase -1
6. Screenshots of Development Phase -2
7. Screenshots of Development Phase -3
8. Conclusion
9. Future Enhancement
10. References
BCA 2 PICA 2|P a g e
<System Name> 2019-20
__________________________________________________________________________________________________________________________________________
ABSTRACT
BCA 2 PICA 3|P a g e
<System Name> 2019-20
__________________________________________________________________________________________________________________________________________
Chapter 1
Introduction to Project System
BCA 2 PICA 4|P a g e
<System Name> 2019-20
__________________________________________________________________________________________________________________________________________
Chapter 2
System Requirement Specification
2.1 Introduction to SRS
2.1.1 What is SRS?
A software requirements specification (SRS) is a description of a software system to
be developed. It lays out functional and non-functional requirements, and may include
a set of use cases that describe user interactions that the software must provide.
2.1.1 Need of SRS
In order to fully understand one’s project, it is very important that they come up with
a SRS listing out their requirements, how are they going to meet it and how will they
complete the project. It helps the team to save upon their time as they are able to
comprehend how are going to go about the project. Doing this also enables the team
to find out about the limitations and risks early on.
2.2 Literature Review
(Note: Refer at least 5 paper/ Documentation/ Website related to your System/
Project)
Sr. Name of Title Year Functionality Future Referen
No. the (If Applicable) Work ce Link
Journal/
Website/
Company/
Document
ation
Table 2.2. Literature Review of <System Name>
2.3 Hardware Requirement
BCA 2 PICA 5|P a g e
<System Name> 2019-20
__________________________________________________________________________________________________________________________________________
Hardware Components Specification
Processor Intel core I3,/I5
RAM 4GB/8GB
Hard disk 512GB/1TB
2.4 Software Requirement
(For C)
Name of component Specification
Operating System WindowsXP,windows10
Software Development Kit Turboc++/CodeBlock for
Windows 7 or above
Programming language C programming(coding)
Or
Software Requirement
(For Python)
Name of component Specification
Operating System WindowsXP,windows10
Software development kit Python Version 3 or above, Python
IDLE/ Pycharm
Scripting language Python Programming(Script)
2.5 System Users
2.6 Description of User Role
2.7 System Modules
2.7.1 Module 1
2.7.2 Module 2
-
-
-
N
2.8 Description of Modules
2.8.1 Module 1
<Description of Module 1>
2.8.2 Module 2
BCA 2 PICA 6|P a g e
<System Name> 2019-20
__________________________________________________________________________________________________________________________________________
<Description of Module 2>
-
-
-
N
2.9 Timeline Chart
Development 75 Days Duratio
phase n
N
0to10 11to20 21to30 31to40 41to50 51to75 (days)
days days days days days days
Requirement 07
Gathering
Analysis 09
Design 10
Development 13
Phase 1
Development 13
Phase 2
Development 13
Phase 3
Documentation 10
Total time 75
(Days)
2.9 Time line chart of <System Name>
BCA 2 PICA 7|P a g e
<System Name> 2019-20
__________________________________________________________________________________________________________________________________________
Chapter 3
System Flow Diagram
4. System Flow Diagram of <System Name>
BCA 2 PICA 8|P a g e
<System Name> 2019-20
__________________________________________________________________________________________________________________________________________
Chapter 4
Data Dictionary
4.1 <Table Name>
<Write Full Name of Table E.G Table_Registration(correct) instead of
tbl_reg(incrrect)>
Field Data Type Field Size for Description Example
Name Display
Table 4.1 <Table Name>
4.2 <Table Name>
<Write Full Name of Table E.G Table_Registration(correct) instead of
tbl_reg(incrrect)>
Field Data Type Field Size for Description Example
Name Display
Table 4.2 <Table Name>
-
-
-
N number of Table
BCA 2 PICA 9|P a g e
<System Name> 2019-20
__________________________________________________________________________________________________________________________________________
Chapter 5
Screenshot of Development Phase 1
5.1 <Form Name> Design
F
Figure 5.1 <Form Name>Design
5.2Code of <Form Name>
BCA 2 PICA 10|P a g e
<System Name> 2019-20
__________________________________________________________________________________________________________________________________________
Figure 5.2 Code of <Form Name>
Chapter 6
Screenshot of Development Phase 2
6.1 <Form Name> Design
F
Figure 6.1 <Form Name>Design
6.2Code of <Form Name>
BCA 2 PICA 11|P a g e
<System Name> 2019-20
__________________________________________________________________________________________________________________________________________
Figure 6.2 Code of <Form Name>
Chapter 7
Screenshot of Development Phase 3
7.1 <Form Name> Design
F
Figure 7.1 <Form Name>Design
7.2Code of <Form Name>
BCA 2 PICA 12|P a g e
<System Name> 2019-20
__________________________________________________________________________________________________________________________________________
Figure 7.2 Code of <Form Name>
Chapter 8
Conclusion
BCA 2 PICA 13|P a g e
<System Name> 2019-20
__________________________________________________________________________________________________________________________________________
Chapter 9
Future Enhancement
BCA 2 PICA 14|P a g e
<System Name> 2019-20
__________________________________________________________________________________________________________________________________________
Chapter 10
References
1.
BCA 2 PICA 15|P a g e
