OOSD Report Edited

MOBILE PHONE SERVICE CENTER
MINI PROJECT REPORT

Submitted By
PAVITHRA P- 111721203039
in partial fulfilment for the award of the degree

of
BACHELOR OF TECHNOLOGY
IN
INFORMATION TECHNOLOGY
R.M.K ENGINEERING COLLEGE

(An Autonomous Institution)
R.S.M Nagar, Kavaraipettai - 601
NOVEMBER 2023
ACKNOWLEDGEMENT
We earnestly portray our sincere gratitude and regards to our beloved Founder
Chairman, Thiru. R. S. MUNIRATHINAM for giving us the infrastructure for
conducting the project work and our Chairperson Tmt. MANJULA
MUNIRATHINAM for her blessings. We also thank our Vice Chairman, Thiru. R. M.
KISHORE and our Director, Thiru. R. JOTHI NAIDU for their constant support and
affection shown towards us throughout the course.
We are extremely thankful to our Principal, Dr. K. A. MOHAMED JUNAID,

for being the source of inspiration in this college.
We reveal our sincere thanks to our Professor and Head of the Department,
Information Technology, Dr. M. SHEERIN BANU, for her commendable support and
encouragement for the completion of our project.
We would like to express our sincere gratitude to our Course coordinators

Dr.R.Rajitha Jasmine, and Dr.S.Selvakanmani for their valuable suggestions towards
the successful completion for this project.
We take this opportunity to extend our thanks to all the faculty members of
Department of Information Technology, parents and friends for their care and support
towards the completion of our project
ABSTRACT
Mobile phones have become integral to daily life, emphasizing the need for efficient
service centers. This project introduces a holistic Mobile Phone Service Center
Management System to address existing challenges. The system comprises seven
modules, including Mobile Phone Parts Management, optimizing inventory, and reducing
downtime. Mobile Phone Models consolidate information for quick reference, aiding
service personnel in diverse device troubleshooting. Service Request Registration
streamlines the initiation process, ensuring a seamless experience for users.
Service Request Status Check empowers customers to monitor their requests in real-time,
fostering transparency. Service Request Engineer Allocation optimizes resource
utilization, intelligently assigning tasks to available engineers for swift issue resolution.
The Payment module simplifies billing, providing secure and convenient payment
options. Finally, Customer Management consolidates data to nurture lasting customer
relationships through personalized services.
This innovative system redefines mobile phone service centers by integrating efficient
parts management, model reference, user-friendly request handling, transparent status
tracking, intelligent engineer allocation, secure payments, and robust customer
relationship management. It aspires to elevate service center standards, catering to the
evolving needs.
Chapter Table of Contents Page

Number
Mobile Phone Service Center

Abstract
1 Introduction
1.1 Aim
1.2 Problem Statement
2 System Implementation
2.1 System Specification
2.2 Hardware Requirements
3 System Analysis
3.1 Block Diagram
3.2 Use Case Diagram
3.3 Activity Diagram
3.4 Class Diagram
3.5 Sequence Diagram
3.6 Collaboration Diagram
3.7 Logical Architecture
3.8 State chart Diagram
3.9 Component Diagram
3.10 Deployment Diagram
4 Technology Stack
5 Implementation and Results
5.1 Implementation
5.2. Results (Actual Output / Prototype Model)
Code Snippets
Conclusion and Future Enhancement
References
CHAPTER I
INTRODUCTION
1. 1 AIM
The Mobile Phone Service Center system aims to enhance the efficiency of mobile phone
repair and maintenance operations by incorporating the following key features. Firstly, it
will manage mobile phone parts through real-time inventory tracking, ensuring optimal
stock levels and automated reordering. Secondly, the system will maintain an up-to-date
database of various mobile phone models, providing detailed specifications and
compatibility information. It will also facilitate user-friendly service request registration,
allowing customers to log requests and generating unique service request IDs. The online
portal will enable customers to check the real-time status of their service requests,
providing transparency in the repair process. Automated engineer allocation will optimize
resource utilization based on expertise, workload, and location. The system will integrate
secure payment gateways for seamless transactions and provide flexible payment options
for customers. Lastly, it will maintain a comprehensive customer database, including
contact information, service history, and feedback, for efficient customer management.
1.2 PROBLEM STATEMENT
The current state of mobile phone service centers faces challenges in terms of operational
efficiency, customer experience, and resource management. The absence of a centralized
system leads to manual and time-consuming processes in managing mobile phone parts
inventory, cataloging diverse phone models, and allocating service requests to engineers.
This results in delays, increased turnaround times, and a lack of transparency for
customers regarding the status of their service requests. Additionally, the absence of an
integrated payment system and comprehensive customer management leads to
inefficiencies in financial transactions and customer interactions. The Mobile Phone
Service Center system aims to address these challenges by providing a holistic solution to
streamline operations, improve customer satisfaction, and optimize resource allocation.
CHAPTER II –SYSTEM REQUIREMENTS SPECIFICATION
2.1 HARDWARE SPECIFICATIONS

Processor : Intel Pentium III or later
Main Memory (RAM) : 256 MB
Cache Memory : 512 KB
Monitor : 17-inch Color Monitor
Keyboard : 108 Keys
Mouse : Optical Mouse
Hard Disk : 160 GB
2.2 SOFTWARE SPECIFICATIONS

Front
: Java Server Pages/HTML
End/Language
Back End/Database : MySQL
Additional Tools : Visual Studio 6.0
Windows XP Service Pack 2/Windows Vista/Windows
Operating System :
7/Windows 8
CHAPTER III
SYSTEM DESCRIPTION
3.1 EXISTING SYSTEM
In the current Mobile Phone Service Center system, existing manual processes are
complemented by a Mobile Phone Service Center app, though its functionality presents
limitations. The mobile phone parts management lacks real-time tracking and automation,
similar to the manual procedures, potentially causing inefficiencies in inventory control.
Cataloging mobile phone models within the app is available but may not be regularly
updated, leading to potential discrepancies. Service request registration through the app is
present, but the overall process may still be subject to delays and inaccuracies. The status
check feature for service requests might exist, but it may not offer real-time updates or
comprehensive notifications. Engineer allocation, payment processing, and customer
management features within the app may not be fully optimized, resulting in a
fragmented user experience. Consequently, despite the inclusion of a mobile app, the
existing system struggles to provide a cohesive and efficient operation, impacting both
the functionality of the service center and overall customer satisfaction.
3.2 PROPOSED SYSTEM

The proposed Mobile Phone Service Center Management System aims to revolutionize
the efficiency and customer experience in mobile phone service centers, addressing the
challenges outlined in the provided abstract. Comprising seven integral modules, the
system introduces advanced solutions for Mobile Phone Parts Management, optimizing
inventory and reducing downtime. The Mobile Phone Models module consolidates
information for quick reference, aiding service personnel in diverse device
troubleshooting. Service Request Registration streamlines the initiation process, ensuring
a seamless experience for users. The Service Request Status Check empowers customers
to monitor their requests in real-time, fostering transparency and communication. Service
Request Engineer Allocation optimizes resource utilization by intelligently assigning
tasks to available engineers for swift issue resolution. The Payment module simplifies
billing, providing secure and convenient payment options. Finally, Customer
Management consolidates data to nurture lasting customer relationships through
personalized services.
CHAPTER IV – SYSTEM ARCHITECTURE

4.1 SYSTEM ARCHITECTURE DIAGRAM
Fig 4.1.1 Diagram for system architecture
A system architecture or systems architecture is the conceptual model that defines the
structure and behavior and views of a system. An architecture description is a formal
description and representation of a system, organized in a way that supports reasoning
about the structures and behaviors of the system.
A system architecture can comprise system components, the externally visible properties
of those components, the relationships (e.g. the behavior) between them. It can provide a
plan from which products can be procured, and systems developed, that will work
together to implement the overall system. There have been efforts to formalize languages
to describe system architecture, collectively these are called architecture description
languages. Systems architecture depends heavily on practices and techniques that were
developed over thousands of years in many other fields, perhaps the most important being
civil architecture.
CHAPTER V – TECHNOLOGY DESCRIPTION
5.1 TECHNOLOGY DESCRIPTION
HTML stands for Hyper Text Markup Language, which is the most widely used language on Web to
develop web pages.HTML was created by Berners-Lee in late 1991 but "HTML 2.0" was the first
standard HTML specification which was published in 1995. HTML 4.01 was a major version of HTML
and it was published in late 1999. Though HTML 4.01 version is widely used but currently we are
having HTML-5 version which is an extension to HTML 4.01, and this version was published in
2012.Hypertext refers to the way in which Web pages (HTML documents) are linked together. Thus
the link available on a webpage are called Hypertext. As its name suggests, HTML is a Markup
Language which means you use HTML to simply "mark up" a text document with tags that tell a Web
browser how to structure it to display.
Originally, HTML was developed with the intent of defining the structure of documents like headings,
paragraphs, lists, and so forth to facilitate the sharing of scientific information between researchers.
Now, HTML is being widely used to format web pages with the help of different tags available in
HTML language.
HTML Tags
As told earlier, HTML is a markup language and makes use of various tags to format the content. These
tags are enclosed within angle braces <Tag Name>. Except few tags, most of the tags have their
corresponding closing tags. For example <html> has its closing tag</html> and <body> tag has its
closing tag </body> tag etc.
Above example of HTML document uses folloiwng tags:
Tag Description
<!DOCTYPE...> This tag defines the document type and HTML version.
<html> This tag encloses the complete HTML document and mainly comprises
of document header which is represented by <head>...</head> and
document body which is represented by <body>...</body> tags.
<head> This tag represents the document's header which can keep other HTML
tags like <title>, <link> etc.
<title> The <title> tag is used inside the <head> tag to mention the document
title.
<body> This tag represents the document's body which keeps other HTML tags
like <h1>, <div>, <p> etc.
<h1> This tag represents the heading.
<p> This tag represents a paragraph.
Table 5.1.1 for showing the HTML Tags
To learn HTML, you will need to study various tags and understand how do they behave while
formatting a textual document. Learning HTML is simple as users have to learn the usage of different
tags in order to format the text or images to make a beautiful webpage.
World Wide Web Consortium (W3C) recommends to use lowercase tags starting from HTML 4.
Heading Tags
Any document starts with a heading. You can use different sizes for your headings. HTML also has six
levels of headings, which use the elements <h1>, <h2>, <h3>, <h4>, <h5>, and <h6>. While
displaying any heading, browser adds one line before and one line after that heading.
The <!DOCTYPE> Declaration

The <!DOCTYPE> declaration tag is used by the web browser to understand the version of the HTML
used in the document. Current version of HTML is 5 and it makes use of the following declaration:
There are many other declaration types which can be used in HTML document depending on what
version of HTML is being used. We will see more details on this while discussing <!DOCTYPE...> tag
along with other HTML tags.
Paragraph Tag
The <p> tag offers a way to structure your text into different paragraphs. Each paragraph of text should
go in between an opening <p> and a closing </p> .
Line Break Tag
Whenever you use the <br /> element, anything following it starts from the next line. This tag is an
example of an empty element, where you do not need opening and closing tags, as there is nothing to
go in between them.
The <br /> tag has a space between the characters br and the forward slash. If you omit this space,
older browsers will have trouble rendering the line break, while if you miss the forward slash character
and just use <br> it is not valid in XHTML
Horizontal Lines
Horizontal lines are used to visually break up sections of a document. The <hr> tag creates a line from
the current position in the document to the right margin and breaks the line accordingly.
JSP
JavaServer Pages (JSP) is a server-side programming technology that enables the creation of dynamic,
platform-independent method for building Web-based applications. JSP have access to the entire family
of Java APIs, including the JDBC API to access enterprise databases. JavaServer Pages (JSP) is a
technology for developing web pages that support dynamic content which helps developers insert java
code in HTML pages by making use of special JSP tags, most of which start with <% and end with %>.
A JavaServer Pages component is a type of Java servlet that is designed to fulfill the role of a user
interface for a Java web application. Web developers write JSPs as text files that combine HTML or
XHTML code, XML elements, and embedded JSP actions and commands.
Using JSP, you can collect input from users through web page forms, present records from a database or
another source, and create web pages dynamically.
JSP tags can be used for a variety of purposes, such as retrieving information from a database or
registering user preferences, accessing JavaBeans components, passing control between pages and
sharing information between requests, pages etc. JavaServer Pages often serve the same purpose as
programs implemented using the Common Gateway Interface (CGI). But JSP offer several advantages
in comparison with the CGI.
 Performance is significantly better because JSP allows embedding Dynamic Elements in HTML Pages
itself instead of having a separate CGI files.
 JSP are always compiled before it's processed by the server unlike CGI/Perl which requires the server to
load an interpreter and the target script each time the page is requested.
 JavaServer Pages are built on top of the Java Servlets API, so like Servlets, JSP also has access to all the
powerful Enterprise Java APIs, including JDBC, JNDI, EJB, JAXP etc.
 JSP pages can be used in combination with servlets that handle the business logic, the model supported
by Java servlet template engines.
Finally, JSP is an integral part of Java EE, a complete platform for enterprise class applications. This
means that JSP can play a part in the simplest applications to the most complex and demanding.
Setting up Web Server: Tomcat
A number of Web Servers that support JavaServer Pages and Servlets development are available in the
market. Some web servers are freely downloadable and Tomcat is one of them.
Apache Tomcat is an open source software implementation of the JavaServer Pages and Servlet
technologies and can act as a standalone server for testing JSP and Servlets and can be integrated with
the Apache Web Server. Here are the steps to setup Tomcat on your machine:
 Download latest version of Tomcat from http://tomcat.apache.org/.

 Once you downloaded the installation, unpack the binary distribution into a convenient location. For
example in C:\apache-tomcat-5.5.29 on windows, or /usr/local/apache-tomcat-5.5.29 on Linux/Unix and
create CATALINA_HOME environment variable pointing to these locations.
CHAPTER VI – DESIGN
6.1 USE CASE DIAGRAM
This diagram outlines interactions between system users (actors) like Customers, Service
Center Staff, and Technicians. Use cases include actions such as requesting repairs,
checking repair status, and updating customer information. It provides a high-level view
of the system's functionality and user interactions.
DOCUMENTATION OF USE CASE DIAGRAM
 Use case diagrams depict the interactions between users (actors) and the system.
 Actors: Customer, Service Center Staff, Technician.
 Use Cases: Request Repair, Check Repair Status, Update Customer Information,
Schedule Appointments, etc.
Fig 6.1.1 diagram for Usecase
6.2 CLASS DIAGRAM
DOCUMENTATION OF CLASS DIAGRAM

Class diagrams illustrate the static structure of the system by showing classes, attributes,
methods, and relationships. A static structural diagram that represents the system's classes
(e.g., Customer, Device, Technician) and their relationships. It details attributes and
methods within classes, offering a blueprint for the system's object-oriented design.
Classes: Customer, Device, RepairTicket, Technician, Appointment, ServiceCenter, etc.

Associations: Relationships between classes, such as a Customer having multiple
Devices, a Technician working on multiple Repair Tickets, etc.
Fig 6.2.1 Diagram of Class Diagram
6.3 INTERACTION DIAGRAM
6.3.1 SEQUENCE DIAGRAM

 This dynamic diagram illustrates the chronological flow of messages and
interactions between objects during a specific process or scenario. For a mobile
service center, it could show the sequence of events when a customer requests a
repair, the service center staff creates a repair ticket, and a technician updates the
repair status.
 Sequence diagrams show the interactions between objects over time, illustrating
the flow of messages. Sequences: Customer requests repair, Service Center Staff
creates a Repair Ticket, Technician updates status, etc.
Fig 6.3.1.2 Diagram of sequence diagram
6.3.2 COMMUNICATION DIAGRAM
Depicting how objects interact to achieve specific tasks, this diagram includes objects
like Customer, Repair Ticket, Technician, and Service Center Staff. Arrows and lines
show the communication and collaboration between these objects, offering insights into
the system's dynamic behavior during specific processes.
Collaboration diagrams illustrate how objects collaborate to achieve a specific task.
Objects: Customer, Repair Ticket, Technician, Service Center Staff, etc.
Interactions: Arrows and lines showing communication between objects.
Fig 6.3.2.1 Diagram for Communication diagram
6.4 ACTIVITY DIAGRAM

Activity diagrams are graphical representations of workflows of stepwise activities
and actions with support for choice, iteration and concurrency. In the Unified
Modeling Language, activity diagrams can be used to describe the business and
operational step-by-step workflows of components in a system. An activity
diagram shows the overall flow of control. An activity is shown as a rounded box
containing the name of the operation.
DOCUMENTATION OF ACTIVITY DIAGRAM

Activity diagrams illustrate the workflow of a system or a specific use case.
Activities: Steps involved in handling a repair request, scheduling appointments, etc.
Decision nodes: Conditions for branching in the workflow.
Fig 6.4.2 Diagram for activity diagram

6.5 STATECHART DIAGRAM
State machine diagrams model the states and transitions of an object.

States: Repair Ticket status (e.g., Open, In Progress, Completed, Closed).
Transitions: How a Repair Ticket moves from one status to another (e.g., Open to In
Progress when assigned to a Technician).
Fig 6.5.1 Diagram for state diagram

CHAPTER VII – IMPLEMENTATION
7.1 SCREENSHOTS
LOGIN PAGE
ON CLICKING LOGIN WE WILL GET THE HOME PAGE
ON CLICKING REGISTER THE REGISTRATION FORM OPENS
ONCE REGISTRATION IS SUCCESSFUL YOU WILL GET THIS

NOW ON CLICKING SEARCH THIS WILL APPEAR
ON CLICKING SUBMIT
ENTERING DETAILS AND SUBMITTING GIVES US A NOTIFICATION THROUGH THE
NOTIFY.HTML
7.2 SOURCE CODE
LOGIN.jsp
<html><style type="text/css">
a:link {text-decoration: none;}a:visited {text-decoration: none;
}a:hover {text-decoration: none;}a:active {text-decoration: none;}body {
background-color: #0FC;}</style><body><form action = "welcome.jsp" method="post" name="f1">
<h2> <center>Conference Management System </center> </h2><table align="center"><tr>
<td align="left">UserName</td><td> <input type=text name="user_name"></td></tr>
<tr><td align="left">Password</td><td> <input type=password name="pass_word">
</td></tr><tr></tr><br><tr>
<td> <button type="button"><a href="conference.html">login</a></button> </td><td><button
type="button"><a href="register (1).jsp">register</a></button> </td>
</tr></table></form></body></html>
REGISTER.JSP
<html><style type="text/css">
a:link {text-decoration: none;
}a:visited {text-decoration: none;
}a:hover {text-decoration: none;
}a:active {text-decoration: none;
}body {background-color: #0F9;}</style>
<body><h2> <center>Conference registration Form </center> </h2><table><tr>
<td align="right">Name</td><td> <input type=text name="name"></td>
</tr><tr><td align="right">Age</td><td> <input type=text name="age"> </td></tr><tr>
<td align="right">Educational Qualification</td><td> <input type=text name=edu_qua">
</td></tr><tr>
<td align="right">Email Id:</td><td> <input type=text name="email"> </td></tr>
<tr><td align="right">Phone/Mobile No:</td><td> <input type=text name="phone"> </td>
</tr><tr><td></td></tr><tr><td align="right">Would you like to review?</td>
<td><input type="radio" name="g1" value="yes">yes
<br><input type="radio" name="g1" value="no">no</td></tr>
<tr><td align="right">Area of Interest</td><td> <select name="area"><option >Robotics</option>
<option selected="selected">Imageprocessing</option><option>Cloud computing</option>
<option>Big data analysis</option><option>Android</option></select>
</td></tr><tr><td></td><td><a href="welcome.html">submit</a></td>
</tr></table></form></body></html>
CONFERENCE.jsp
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Untitled Document</title><style type="text/css"></style></head><body link="#336699"
vlink="#990000" alink="#CC0033" leftmargin="20" topmargin="20"><div class="container">
<div class="header"><a href="#" class="header"><img src="river-scenery-wallpaper-01050.jpg"
alt="Insert Logo Here" name="Insert_logo" width="880" height="70" id="Insert_logo"
style="background: #8090AB; display:block;" /> <strong>Conference management system
</strong></a>
</div> <div class="sidebar1"> <ul class="nav">
<li><a href="conference.html">HOME</a></li> <li><a href="search.html">SEARCH</a></li>
<li><a href="submit.html">SUBMIT</a></li> <li><a
href="conference.html">EXIT</a></li></ul>
<p> The Conference system helps you to post and see yours papers for any conference that was being
held in the years so far </p><p> </p>
<p> </p> <p> </p> <p class="sidebar1"> </p> </div>
<div class="content"> <h1>conferences upcoming</h1>
<p>1. IEEE international conference</p> <p>2. RMK engineering electrical and electronic
department symposiums</p> <p>3. Jeppiar college information technology symposium</p>
<p> </p><p> </p><p> </p><h2> </h2>
<p> </p> <p> </p> </div><div class="sidebar2">
<h4>upcoming events</h4> <p>regiter soon if u have not registered to get the best conference
details.</p>
<p>LOGIN if u had done.</p> <p> </p> <p> </p><p> </p> <p> </p>
<p> </p> <p> </p> <p> </p>
</div> <div class="footer"></div></div></body></html>
SEARCH.jsp
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html
xmlns="http://www.w3.org/1999/xhtml">
<head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Untitled Document</title><style type="text/css"></style></head><body><div class="container">
<div class="header"><a href="#"><img src="river-scenery-wallpaper-01050.jpg" alt="Insert Logo
Here" name="Insert_logo" width="880" height="70" id="Insert_logo" style="background: #8090AB;
display:block;" /></a>
</div> <div class="sidebar1"><ul class="nav">
<li><a href="conference.html">HOME</a></li><li><a href="search.html">SEARCH</a></li>
<li><a href="submit.html">SUBMIT</a></li>
<li><a href="conference.html">EXIT</a></li> <li></li>
<p>The Conference system helps you to post and see yours papers for any conference that was being
held</p>
<p></p> </ul> <p> </p> </div> <div class="content"> <h1>search
your paper here</h1> <p><strong>1. robotics mapping by prof.sundharam ,RMK</strong></p>
<p><strong>2. augmented reality by prof.John</strong></p>
<p><strong>3.Ethical hacking by Ms.charulatha</strong></p>
<p> </p> <h2> </h2>
</div> <div class="sidebar2">
<h4> </h4> <h4>upcoming events</h4><p>regiter soon if u have not registered to get the best
conference details.</p>
<p>LOGIN if u had done.</p> <p></p> <p> </p>
</div> <div class="footer"> <p> </p>
</div></div></body></html>
SUBMIT.jsp
<html xmlns="http://www.w3.org/1999/xhtml">
<title>Untitled Document</title><style type="text/css"></style></head><body><div
class="container"> <div class="header"><a href="#"><img src="river-scenery-wallpaper-
01050.jpg" alt="Insert Logo Here" name="Insert_logo" width="880" height="70"
id="Insert_logo" style="background: #8090AB; display:block;" /></a> </div>
<div class="sidebar1"> <ul class="nav"><li><a href="conference.html">HOME</a></li>
<li><a href="search.html">SEARCH</a></li><li><a href="submit.html">SUBMIT</a></li>
<li><a href="conference.html">EXIT</a></li> </ul> <p> </p>
<p>The Conference system helps you to post and see yours papers for any conference that was being
held</p>
<p> </p> <p> </p> <p> </p> <p></p> </div><div
class="content">
<h1> SUBMIT </h1> <p><table><tr><td align="right">Name</td><td> <input type=text
name="name"></td>
</tr><tr><td align="right">Age</td><td> <input type=text name="age"> </td>
</tr><tr><td align="right">Educational Qualification</td><td> <input type=text name=edu_qua">
</td>
</tr><tr><td align="right">Email Id:</td><td> <input type=text name="email"> </td>
</tr><tr><td align="right">Phone/Mobile No:</td><td> <input type=text name="phone"> </td>
</tr><tr><td></td></tr><tr><td align="right">Would you like to review?</td>
<td><input type="radio" name="g1" value="yes">yes
<br><input type="radio" name="g1" value="no">no</td></tr><tr>
<td align="right">title</td><td> </td>
</tr><tr><td></td><td><a href="notify.html">submit</a></td>
</tr></table> </p><p> </p> </div> <div class="sidebar2">
<h4>conferences makes you to showcase your talents in the platform which is perfect.</h4>
<p>enjoy your participation by using our site</p>
<p> </p> <p> </p> <p> </p> <p> </p>
<p> </p><p></p><p> </p>
</div> <div class="footer">
<p> </p> </div> </div>S</body></html>
WELCOME.HTML
<title>Untitled Document</title><style type="text/css">body {background-color:
#0CF;}</style></head><body>
welcome to this conference management system you may now login
to login <a href="login.jsp">click here</a></body></html>
NOTIFY.HTML
<head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><title>Untitled
Document</title>
<style type="text/css">body,td,th {
font-family: Georgia, "Times New Roman", Times, serif;}body {
margin-left: 50px;margin-top: 50px;margin-right: 50px;margin-bottom: 50px;background-color:
#CC0;
}</style></head><body>submitted successfully go to home....<a href="conference.html">click
here....</a></body></html>
CHAPTER VIII – CONCLUSION
8.1 CONCLUSION AND FUTURE ENHANCEMENTS

Thus the project have been implemented, future enhancements like giving ratings for the papers,
journals details are to be developed in future. Present system involves uploading the papers and
reviewing the papers.
FUTURE ENHANCEMENTS IN THE SYSTEM
1. Offering free notifications via email to the users.

2. Conferences search by the departments.
3. Publishing papers in journals.
4. Periodical membership for users.
CHAPTER IX- REFERENCES
9.1 REFERENCES
http://www.tutorialspoint.com/jsp/jsp_client_request.htm
http://www.tutorialspoint.com/jsp/jsp_server_response.htm
http://en.wikipedia.org/wiki/JavaServer_Pages
https://tomcat.apache.org/download-60.cgi
http://www.w3schools.com/html/
http://www.tutorialspoint.com/jsp/jsp_form_processing.htm
http://www.w3schools.com/html/html_responsive.asp
https://www.mysql.com/
http://www.tutorialspoint.com/jsp/jsp_directives.htm
http://www.w3schools.com/html/html_images.asp
http://www.mysql.com/products/enterprise/database/
http://www.vogella.com/tutorials/ApacheTomcat/article.html
http://www.cs.armstrong.edu/liang/intro9e/supplement/Supplement9eTomcat5.5.9.pdf
http://www.codeproject.com/Articles/27292/Database-Programming-With-MySQL

OOSD Report Edited

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OOSD Report Edited

Uploaded by

Copyright:

Available Formats

MOBILE PHONE SERVICE CENTER

MINI PROJECT REPORT

in partial fulfilment for the award of the degree

R.M.K ENGINEERING COLLEGE

We are extremely thankful to our Principal, Dr. K. A. MOHAMED JUNAID,

We would like to express our sincere gratitude to our Course coordinators

Chapter Table of Contents Page

Mobile Phone Service Center

CHAPTER II –SYSTEM REQUIREMENTS SPECIFICATION

2.1 HARDWARE SPECIFICATIONS

2.2 SOFTWARE SPECIFICATIONS

3.2 PROPOSED SYSTEM

CHAPTER IV – SYSTEM ARCHITECTURE

Fig 4.1.1 Diagram for system architecture

Above example of HTML document uses folloiwng tags:

<h1> This tag represents the heading.

<p> This tag represents a paragraph.

Table 5.1.1 for showing the HTML Tags

The <!DOCTYPE> Declaration

Setting up Web Server: Tomcat

 Download latest version of Tomcat from http://tomcat.apache.org/.

6.1 USE CASE DIAGRAM

DOCUMENTATION OF USE CASE DIAGRAM

6.2 CLASS DIAGRAM

DOCUMENTATION OF CLASS DIAGRAM

Classes: Customer, Device, RepairTicket, Technician, Appointment, ServiceCenter, etc.

6.3 INTERACTION DIAGRAM

6.3.1 SEQUENCE DIAGRAM

Fig 6.3.1.2 Diagram of sequence diagram

6.3.2 COMMUNICATION DIAGRAM

Fig 6.3.2.1 Diagram for Communication diagram

6.4 ACTIVITY DIAGRAM

DOCUMENTATION OF ACTIVITY DIAGRAM

Fig 6.4.2 Diagram for activity diagram

State machine diagrams model the states and transitions of an object.

Fig 6.5.1 Diagram for state diagram

ONCE REGISTRATION IS SUCCESSFUL YOU WILL GET THIS

8.1 CONCLUSION AND FUTURE ENHANCEMENTS

FUTURE ENHANCEMENTS IN THE SYSTEM

1. Offering free notifications via email to the users.

You might also like