Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
PROJECT REPORT ON
“SERVICE MAINTENANCE AND TRACKING SYSTEM”
SUBMITTED TO
SAVITRIBAI PHULE PUNE UNIVERSITY
IN A PARTIAL,FULLFILLMENT OF
M.Sc.(COMPUTER SCIENCE)(SEMESTER-IV)
SUBMITTED BY
LAYGUDE PRAJAKTA MAHENDRA
KHANDAGALE PRAJAKTA BALAJI
1 Introduction
2 Scope of System
4 Proposed System
6 Feasibility Study
7 System Requirements
8 ER-Diagram
9 Class Diagram
11 Activity Diagram
12 Sequence Diagram
13 Component Diagram
14 Deployment Diagram
15 Data Dictionary
18 Conclusion
13.Manage MCQ’s
• Interviews
• Questionnaire
• Record View
• Observation
• Interview:-
Analysts uses interview to collect information from individual or
from groups . The respondents are generally the current user of
existing systems or new user of the proposed system. The
respondent may be customer or client who provide data for the
proposed system or will be affected by it.
Interviews is the best method for providing qualitative
information like opinions, policies and subjective description of
activities and problems. Interviews are taken by system analyst.
Interview can be structured or unstructured.
1. How existing system works?
2. What are the problems in the existing system?
3. Is there any alternative to solve the problem existing in current?
• Questionnaire:-
Questionnaire allows analyst to collect information about various
aspects of the system form large number of persons. The customer
of the standardized question format can produce more reliable data
than fact finding techniques.
However this method doesn’t allow analyst to observe the
expression or reactions of the respondent. In addition to this the
answers may be limited, since completing questionnaire may not
have higher priority among the respondents.
Analyst uses open ended questionnaire to learn about
feelings, opinions and general experience or to explore a process or
a problem.
• Record View:-
Many kinds of records and reports provide valuable information
about the organization and the operations perform in the organization.
Records include writer policy manual, regulations and standard
operation procedure used by most organization as
Guide for managers and employees. Records don’t show what activity
are actually occurring, who takes the decision, how the take is
performed, etc. however they can help analyst in understanding the
system with actual operation which must be supported in the new
system.
• Observation:-
Observation analyst to get information which they can’t obtain by any
other fact finding techniques, through the observation analyst can obtain
the hand information about how activities are carried out. This method is
most useful when the analyst need to be actually observe how
documents are handled, how processors are carried out, and whether
specified step are actually followed or not.
As there are no specific users of this system, we have to use the
observation technique for fact finding. We observe some of the websites
available for online compilation and figured out what things we have to
implement in our systems.
2. Feasibility Study
I assumed whether the project is feasible or not in terms of
technical aspects, resources and time duration .
• Technical Feasibility
• Economical Feasibility:
• Operational Feasibility:
Operational feasibility considers the acceptability of the
system. The project may be rejected due to operational non-
feasibility. It checks whether system will be used if it is developed
and implemented, are the users of the system able to handle the
system, whether the proposed system cause any trouble etc.
System requirements
Software specification:-
Hardware Specification:-
ER Diagram
Admin
register
take
1 M M
M M 1 1 1
Walk_In view Service Provider register Service
1 1 1 M 1
1
record
view Done
for
register
M M
M 1 1
1 1 1 M
Feedback give User does Payment
M M
Manage Report generate
Is a
1
M
Follow_Up
Class Diagram
1 M 1
Admin Service Provider User
+AId:int +SPId:int M +UId:int
+AName: varchar +SPName: varchar +UName: varchar
+AUname: varchar +SPAddress: varchar +UAddress: varchar
+APassword: varchar +SPPhoneNo:int +UPhoneNo:int
Manage Admin() +SPUname: varchar +UEmail: varchar
1
+SPPassword: varchar View Services() 1
+SPEmail: varchar Use Services()
Manage Service()
Manage Payment() 1
1 1 Manage Feedback()
Walk In Manage Walk In()
+WId:int Manage reports() M
+WName: varchar Manage User()
Manage Follow Up()
+WPhoneNo:int Services
+WAddress:
varchar +Sid:int
+SName: varchar
+SType: varchar
M
1 M
1
Follow Up Payment
+WId:int +PId:int 1
+PId:int +PName: varchar
+PMode: varchar
+PType: varchar Feedback
+Fid:int 1
+FName varchar
+FAddress: varchar
+FMsg:varchar
Use Case Diagram
Login
logL
Add Admin
Registration
Add Services
Use Services
Super Admin
Manage Payment
Generate Report
Give Feedback
Manage Walk In
Manage Follow Up
Logout
Activity Diagram
SSStart
Registration
re
Login
No
End username & password
lihhjj
Manage Services Manage Registration Registration
Gives Feedback
SSStop
Sequence Diagram:
:User :Service Provider :Admin :System
Login
LValidation
Registration
L Login
Validation
L
AddL services
L View Services
L
Registration
L Login
L Validation
Use
L Services
Does payment
Report Generated
Logout
Gives Feedback
View Feedbacks
Manage Walk In
Logout
Logout
Component Diagram
DataBase
System
System
ALogin.Jsp SPLogin.jsp
Registration.
SMTS.war
SMTS.war
Jsp
Browser
Web Server
HTTP
chrome Apache
User
TCP/IP
Database Server
Mysql
Data Dictionary
Services:
Registration:
Feedback:
Each and every system has some limitation that can restrict them
on a particular environment through our system is providing
high amount of accuracy but there is still some limitation that
laid us to in greater deficiency to work on that system. Some of
the limitation that is observed during all the process is mention
below.