Manish Kuthe Project Report
Manish Kuthe Project Report
A PROJECT REPORT
ON
“Local Service Search Engine Management systeam”
partial fulfilment for the award of Bachelor of Science in Computer Science during
Date of Submission :
User:
ER Diagram:
The Entity-Relationship (ER) model was originally proposed by Peter in 1976 [Chen76] as a way to unify
the network and
relational database views. Simply stated the ER model is a conceptual data model that views the real
world as entities and
relationships. A basic component of the model is the Entity-Relationship diagram which is used to visually
represent data
objects. Since Chen wrote his paper the model has been extended and today it is commonly used for
database design for the
database designer, the utility of the ER model is:
It maps well to the relational model. The constructs used in the ER model can easily be transformed into
relational tables.
It is simple and easy to understand with a minimum of training. Therefore, the model can be used by the
database designer
to communicate the design to the end user.
In addition, the model can be used as a design plan by the database developer to implement a data
model in specific
database management software.
3.7.
ER Notation
There is no standard for representing data objects in ER diagrams. Each modeling methodology uses its
own notation. The
original notation used by Chen is widely used in academics texts and journals but rarely seen in either
CASE tools or
publications by non-academics. Today, there are a number of notations used; among the more common
are Bachman, crow's
foot, and IDEFIX.
All notational styles represent entities as rectangular boxes and relationships as lines connecting boxes.
Each style uses a
special set of symbols to represent the cardinality of a connection. The notation used in this document is
from Martin. The
symbols used for the basic ER constructs are:
Entities are represented by labeled rectangles. The label is the name of the entity. Entity names should
be singular nouns.
Relationships are represented by a solid line connecting two entities. The name of the relationship is
written above the
line. Relationship names should be verbs
Attributes, when included, are listed inside the entity rectangle. Attributes which are identifiers are
underlined. Attribute
names should be singular nouns.
Cardinality of many is represented by a line ending in a crow's foot. If the crow's foot is omitted, the
cardinality is one.
Existence is represented by placing a circle or a perpendicular bar on the line. Mandatory existence is
shown by the bar (looks
like a 1) next to the entity for an instance is required. Optional existence is shown by placing a circle next
to the entity that is
The goal of the system testing process was to determine all faults in our project .The program was
subjected to a set of test
inputs and many explanations were made and based on these explanations it will be decided whether the
program behaves as
expected or not. Our Project went through two levels of testing
1. Unit testing
2. Integration testing
4.1.1. UNIT TESTING
Unit testing is commenced when a unit has been created and effectively reviewed .In order to test a single
module we need to
provide a complete environment i.e. besides the section we would require
1. The procedures belonging to other units that the unit under test calls
2. Non local data structures that module accesses
3. A procedure to call the functions of the unit under test with appropriate parameters
1. Test for the admin module
Testing admin login form-This form is used for log in of administrator of the system. In this form we
enter the username
and password if both are correct administration page will open otherwise if any of data is wrong it will
get redirected back
to the login page and again ask the details.
Report Generation: admin can generate report from the main database.
4.1.2. INTEGRATION TESTING
In the Integration testing we test various combination of the project module by providing the input.
The primary objective is to test the module interfaces in order to confirm that no errors are occurring
when one module
invokes the other module.
EVALUATION
Project URL: http://localhost/lssems
Home Page
Categories
About Us
Admin Login
Dashboard
Add Category
Manage Category
Update Category
Add Person
Manage Person
Update Person
About Person
Admin Profile
Change Password
Forgot Password
Contact us
CONCLUSION
This Application provides an online version of Local Service
System which will benefit the system administrator who
wants to maintain records of serviceman and also help to
users who search serviceman according to his/her
requirement in their own locality.
It makes entire process online and can generate reports.
The Application was designed in such a way that future
changes can be done easily. The following conclusions can be
deduced from the development of the project.
Automation of the entire system improves the
productivity.
It provides a friendly graphical user interface which
proves to be better when compared to the existing
system.
It gives appropriate access to the authorized users
depending on their permissions.
It effectively overcomes the delay in communications.
Updating of information becomes so easier.
System security, data security and reliability are the
striking features.
The System has adequate scope for modification in
future if it is necessary.
References
For PHP
[1] https://www.w3schools.com/php/default.asp
[2] https://www.sitepoint.com/php/
[3] https://www.php.net/
For MySQL
[1] https://www.mysql.com/
[2] http://www.mysqltutorial.org
For XAMPP
[1] https://www.apachefriends.org/download.html
[2] Wangkhem, K., & Joshi, K. IOT FOR HEALTHCARE AND
ITS CHALLENGES. International Educational Journal
of Science and Engineering (IEJSE) –Volume, 1.
[3] Kaur, J., S., Ganjoo, P., Vaqur, M., & Joshi, K. A Review:
Image Fusion using DCT and DWT. International
Journal of Scientific & Engineering Research (IJSER)-
Volume, 10, 702-707.
[4] Joshi, K., Kashyap, D., Bisht, B., & Bagwari, A. GPS
based Location Tracker: A Review. International
Journal of Advanced Research in Computer and
Communication Engineering (IJARCCE)- Volume, 8.
[5] Joshi, K., Joshi, K, N., Diwakar, M. Image Fusion using
Cross Bilateral Filter and Wavelet Transform Domain.
International Journal of Engineering and Advanced
Technology (IJEAT)- Volume, 8, 110-115.
[6] Kumar, R., Singh, G., Joshi, K. Emotion Recognition
System using Local Binary Pattern. International
Journal of Inventive Engineering and Sciences (IJIES)-
Volume, 5.