The document outlines the development of a Driving Licence Management System (DLMS) aimed at automating the issuance, renewal, and management of driving licences, addressing the inefficiencies of the current manual process. It details the project's objectives, features, and benefits such as improved user experience, data accuracy, and system transparency, while outlining the technical requirements and user roles involved. The proposed system will enhance efficiency through automation, provide scalability, and ensure compliance with regulatory standards.

1. Tic Tac Toe Game Page - 1 -
1
CHAPTER
INTRODUCTION
The purpose of this chapter is to provide an introduction to the company
profile and also define basic terminology used in our system that is Driving
Licence System. Chapter-1 presents an overview of existing system and need
of system, scope of work and different operating environment.
 Project Profile
 Existing System and Need for System
 Scope of Work
 Operating Environment – Hardware and Software

2. Tic Tac Toe Game Page - 2 -
1.1Project Profile
1. Project Overview:
The Driving Licence Management System (DLMS) is a
comprehensive software solution designed to streamline the
process of issuing, renewing, and managing driving licences. It
serves as a centralized platform for both users and
administrators to handle various tasks related to driving licences
efficiently.
2. Objectives:
 To automate the process of applying for and renewing driving
licences.
 To provide users with a user-friendly interface for accessing and
managing their licence information.
 To enable administrators to efficiently manage licence
applications, approvals, and renewals.
 To enhance the overall efficiency and transparency of the driving
licence management process.
3. Features:
 User Registration/Login: Allows users to create accounts or log
in to access the system.
 Driving Licence Application: Enables users to apply for a new
driving licence by providing necessary personal and vehicle
information.
 Licence Renewal: Facilitates the renewal of driving licences by
guiding users through the renewal process and updating expiry
dates.
 Search and View Licence Details: Allows users to search for
and view their driving licence details, including expiry date,
vehicle class, and endorsements.

3. Tic Tac Toe Game Page - 3 -
 Update Licence Information: Provides users with the ability to
update personal information or vehicle details associated with
their driving licence.
 Admin Panel Functions: Offers administrators access to a
dashboard for managing licence applications, approvals, and
renewals, as well as user accounts and system settings.
1.2 Existing System and need of
system
a. Manual Process:
 Describe the current manual process of issuing and managing
driving licences.
 Highlight the steps involved, such as filling out paper forms,
physical document verification, and manual data entry.
 Discuss the limitations of the manual process, including
inefficiency, errors, and delays in processing.
b. Challenges and Limitations:
 Identify the key challenges and limitations of the existing system,
such as:
 High processing time: Manual processes are time-consuming
and prone to delays.
 Data inaccuracies: Manual data entry increases the risk of errors
and inconsistencies.
 Lack of transparency: Limited visibility into the status of licence
applications and approvals.
 Difficulty in tracking and managing licence renewals: Manual
tracking systems may result in missed renewals and expired
licences.
c. Stakeholder Feedback:

4. Tic Tac Toe Game Page - 4 -
 Gather feedback from stakeholders, including applicants,
administrators, and government officials, on their experiences
and pain points with the existing system.
 Highlight common issues and areas for improvement based on
stakeholder feedback.
2. Need for Driving Licence Management System:
a. Automation and Efficiency:
 Discuss the need to automate the driving licence management
process to improve efficiency and reduce processing time.
 Highlight the benefits of automation, such as:
 Streamlined application process: Online forms and automated
workflows expedite the application process.
 Faster approvals: Automated verification and processing reduce
turnaround time for licence approvals.
 Time savings: Reduced manual intervention frees up resources
for other critical tasks.
b. Data Accuracy and Integrity:
 Emphasize the importance of maintaining accurate and reliable
licence data.
 Explain how a digital system can ensure data accuracy through
centralized storage and automated validation checks.
 Discuss the risks associated with manual data entry errors and
inconsistencies, such as incorrect licence information and delays
in processing.
c. Transparency and Accountability:
 Address the need for transparency and accountability in the
licence management process.
 Explain how a digital system provides visibility into the status of
licence applications and approvals for both applicants and
administrators.
 Discuss how transparent processes foster trust among
stakeholders and promote accountability in decision-making.
d. Enhanced User Experience:

5. Tic Tac Toe Game Page - 5 -
 Highlight the benefits of a user-friendly interface for driving
licence applicants.
 Discuss how online access to licence information and application
status improves the overall user experience.
 Explain how self-service features empower users to manage their
licence information conveniently and efficiently.
e. Compliance and Regulation:
 Discuss the importance of compliance with regulatory
requirements and standards in driving licence management.
 Explain how a digital system can help ensure compliance
through automated validation checks and audit trails.
 Highlight the need for a system that adapts to evolving
regulatory changes and requirements.
f. Scalability and Future-Proofing:
 Address the need for a scalable and adaptable solution that can
accommodate future growth and changes in demand.
 Discuss how a digital system provides scalability to handle
increasing volumes of licence applications and users.
 Highlight the importance of future-proofing the system to
support emerging technologies and regulatory developments.

6. Tic Tac Toe Game Page - 6 -
1.3 Scope of work
1. Project Scope:
a. System Overview:
 Develop a web-based Driving Licence Management System
(DLMS) to streamline the process of issuing, renewing, and
managing driving licences.
 The system will consist of both frontend and backend
components, utilizing technologies such as PHP for backend
logic and HTML, CSS, and JavaScript for the frontend user
interface.
b. User Roles:
 Define user roles and permissions within the system, including:
 Applicant: Individuals applying for new driving licences or
renewals.
 Administrator: Government officials responsible for managing
licence applications, approvals, and system settings.
2. Key Features:
a. User Registration/Login:
 Implement user registration and login functionality for
applicants and administrators.
 Ensure secure authentication and session management to
protect user accounts.
b. Driving Licence Application:
 Design and implement a user-friendly interface for applicants to
fill out driving licence application forms online.
 Include validation checks to ensure completeness and accuracy
of application data.
c. Licence Renewal:

7. Tic Tac Toe Game Page - 7 -
 Enable users to renew their driving licences through the system,
with prompts for renewal reminders.
 Implement automated renewal processes to expedite the
renewal process.
d. Search and View Licence Details:
 Provide users with the ability to search for and view their driving
licence details, including expiry dates, vehicle classes, and
endorsements.
 Implement filters and sorting options for easy navigation of
licence records.
e. Update Licence Information:
 Allow users to update their personal information and vehicle
details associated with their driving licences.
 Ensure data validation to prevent invalid or incorrect information
from being submitted.
f. Admin Panel Functions:
 Develop an administrative dashboard for administrators to
manage licence applications, approvals, and renewals.
 Include features such as application review, approval/rejection,
and reporting capabilities.
3. Technical Requirements:
a. Backend Development:
 Utilize PHP for backend development, including business logic,
data processing, and database interactions.
 Implement RESTful APIs for communication between frontend
and backend components.
b. Frontend Development:
 Use HTML, CSS, and JavaScript to create responsive and user-
friendly interfaces for both applicants and administrators.

8. Tic Tac Toe Game Page - 8 -
 Ensure cross-browser compatibility and accessibility standards
compliance.
c. Database Management:
 Choose a suitable database system (e.g., MySQL, PostgreSQL) for
storing licence data and user information.
 Design and implement an efficient database schema to support
system requirements and scalability.
4. Testing and Quality Assurance:
a. Functional Testing:
 Conduct thorough testing of all system functionalities to ensure
they meet specified requirements.
 Implement automated testing frameworks for regression testing
and continuous integration.
b. User Acceptance Testing (UAT):
 Engage stakeholders and end-users in UAT to gather feedback
and validate system usability and performance.
 Address any issues or concerns raised during UAT to ensure a
smooth deployment process.
5. Deployment and Maintenance:
a. Deployment Strategy:
 Plan and execute the deployment of the DLMS to production
servers or cloud platforms.
 Implement deployment scripts and procedures to streamline the
deployment process.
b. Maintenance and Support:
 Provide ongoing maintenance and support services to address
any issues or enhancements post-deployment.
 Monitor system performance and security, applying patches and
updates as needed.

9. Tic Tac Toe Game Page - 9 -
1.4 Operating environment –
hardware and software
Development based on the customer requirements, technology
capability and the skills available, the following technologies are
implemented with the project.
1.4.1) Software:
Hardware :
System – PC / Laptop / Desktop
System Type – 32/64-bit operating system, x64-based processor, Windows 8 or
higher, Min i3 Processor or similar
RAM – minimum 4 GB is required
Disk Space – 200 MB (Directly depended on the stored data)
Software :
xampp versipn 8.2.0 +
VS Code
Chrome or any other browser
Front-End Used :
HTML
CSS
Javascript
Back-End Used :
PHP
MySQL
Table 1.2

10. Tic Tac Toe Game Page - 10 -
2
CHAPTER
PROPOSED SYSTEM
This chapter gives you an idea about the project which I have
undertaken. It explains the user requirements of the system to
be developed leading to proposing a solution for the same from
our side. User requirements we get from our users so it’s totally
based on their needs.
 Proposed System
 Objectives of System
 User Requirements

11. Tic Tac Toe Game Page - 11 -
2.1 Proposed system
FUNCTIONAL CAPABILITIES:
1. User Registration:
 Allow users to register with the system by providing personal
information such as name, contact details, and identification
documents.
2. License Application Submission:
 Enable applicants to submit driving license applications through
the system, including uploading necessary documentation.
3. Document Verification:
 Verify the authenticity of submitted documents, such as
identification proof and address proof, to ensure compliance
with regulations.
4. Testing and Evaluation:
 Schedule and manage driving tests for applicants to assess their
driving skills and knowledge of traffic rules and regulations.
 Record test results and evaluations within the system for further
processing.
5. License Issuance:
 Issue driving licenses to applicants who have successfully
completed all requirements, including tests and document
verification.
6. License Renewal:
 Notify license holders of upcoming renewals and provide them
with the option to renew their licenses online through the
system.
 Update license expiration dates and issue renewed licenses upon
completion of the renewal process.
7. Profile Management:
 Allow users to update their personal information, contact details,
and license details (e.g., change of address, license class
upgrade) as needed.
8. Application Management (Administrative):

12. Tic Tac Toe Game Page - 12 -
 Provide administrators with tools to review and process driving
license applications, verify submitted documents, and schedule
tests for applicants.
9. Renewal Management (Administrative):
 Enable administrators to monitor and manage license renewals,
including sending renewal notifications to users and updating
license expiration dates.
10. Database Management (Administrative):
 Maintain a secure and centralized database of all license holders
and applicants, ensuring data integrity and compliance with
regulations.
11. Reporting and Analytics (Administrative):
 Generate reports on various aspects of the licensing process,
such as license issuance, renewals, test results, and user
demographics, for analysis and decision-making purposes.
12. Search and Verification (Administrative):
 Allow administrators and authorized personnel to search for and
verify driving licenses online, ensuring easy access to license
information for verification purposes.
13. User Support and Feedback:
 Provide user support through helpdesk services and FAQs to
assist users with any issues they may encounter.
 Gather feedback from users to continuously improve the
system's functionality and user experience.
PERFORMANCE LEVEL:
1. Speed and Responsiveness:
 The system should respond quickly to user interactions such as
submitting applications, processing requests, and loading pages.
 Response time for critical functions like license issuance and
renewal should be within a few seconds to ensure a smooth user
experience.
2. Reliability and Availability:
 The system should be available and accessible to users and
administrators without significant downtime.
 Aim for a high level of reliability, ensuring that the system can
handle heavy loads and unexpected spikes in traffic without
crashing or malfunctioning.
3. Scalability:

13. Tic Tac Toe Game Page - 13 -
 The system should be able to scale horizontally or vertically to
accommodate an increasing number of users and transactions.
 Scalability ensures that the system can handle growth over time
without sacrificing performance or user experience.
4. Resource Utilization:
 Optimize resource utilization, including CPU, memory, and
storage, to ensure efficient use of hardware resources and
minimize operating costs.
 Monitor resource usage regularly and optimize system
configurations as needed to maintain optimal performance
levels.
5. Concurrency and Throughput:
 Support multiple concurrent users and transactions without
significantly degrading performance.
 Ensure high throughput to process a large number of requests
efficiently, especially during peak usage periods.
6. Security and Compliance:
 Maintain a high level of security to protect user data and
sensitive information from unauthorized access or breaches.
 Ensure compliance with data protection regulations and industry
standards to build trust with users and stakeholders.
7. Error Handling and Recovery:
 Implement robust error handling mechanisms to detect and
handle errors gracefully without impacting user experience.
 Provide mechanisms for data recovery and system restoration in
case of failures or disruptions.
8. User Experience:
 Prioritize user experience by designing intuitive interfaces,
providing informative feedback, and minimizing unnecessary
steps in the workflow.
 Aim for a seamless and user-friendly experience that encourages
user adoption and satisfaction.
DATA STRUCTURES
1. User Profile Data Structure:
 This structure stores information about users, including their
personal details such as name, contact information, and
identification documents.

14. Tic Tac Toe Game Page - 14 -
 It may include fields such as user ID, username, password
(hashed for security), email, phone number, address, etc.
2. License Application Data Structure:
 This structure holds data related to driving license applications
submitted by users.
 Fields may include application ID, applicant ID (linked to user
profile), application date, status (pending, approved, rejected),
and references to uploaded documents.
3. Driving Test Data Structure:
 Stores data pertaining to driving tests scheduled for applicants.
 Includes fields such as test ID, applicant ID, test date and time,
test location, examiner ID, test results, etc.
4. License Data Structure:
 Holds information about issued driving licenses.
 Fields may include license ID, holder ID (linked to user profile),
license type (e.g., learner's permit, full license), expiration date,
endorsements, restrictions, etc.
5. Document Verification Data Structure:
 Stores records of document verification processes.
 Includes fields such as verification ID, submitted document ID,
verification status (verified, pending, rejected), verification date,
comments, etc.
6. Renewal Request Data Structure:
 Manages data related to license renewal requests.
 Fields may include renewal request ID, license ID, renewal date,
renewal status, renewal fee, payment information, etc.
7. Administrative User Data Structure:
 Stores information about administrative users who manage the
system.
 Includes fields such as admin ID, username, password (hashed),
role (e.g., super admin, moderator), permissions, etc.
8. Database Management Data Structure:
 Manages metadata related to the system's database.
 Includes fields such as table name, field name, data type,
constraints, indexes, etc.
SAFETY:
1. Data Encryption: Encrypt sensitive user data such as passwords,
personal information, and identification documents to prevent

15. Tic Tac Toe Game Page - 15 -
unauthorized access in case of a data breach. Use strong encryption
algorithms and secure key management practices.
2. Secure Authentication: Implement robust authentication mechanisms
such as multi-factor authentication (MFA) to verify the identity of users
before granting access to the system. This helps prevent unauthorized
access even if login credentials are compromised.
3. Access Control: Enforce strict access control policies to limit access to
sensitive data and system functionalities based on users' roles and
permissions. Regularly review and update access rights to ensure least
privilege access.
4. Audit Trails: Maintain detailed audit logs of user activities, system
events, and data modifications to track and monitor user actions within
the system. This helps detect suspicious behavior and facilitates
forensic analysis in case of security incidents.
5. Secure Communication: Use secure communication protocols such as
HTTPS to encrypt data transmitted between clients and servers,
protecting against eavesdropping and man-in-the-middle attacks.
6. Regular Security Audits: Conduct regular security audits and
vulnerability assessments to identify and address potential security
weaknesses in the system. Perform penetration testing to simulate real-
world attacks and validate the effectiveness of security controls.
7. Data Backup and Disaster Recovery: Implement robust data backup
and disaster recovery mechanisms to ensure data availability and
integrity in case of system failures, natural disasters, or cyber attacks.
Regularly test backup and recovery procedures to verify their
effectiveness.
8. Security Training: Provide security awareness training to system users
and administrators to educate them about common security threats,
best practices for safeguarding sensitive information, and procedures
for responding to security incidents.
9. Patch Management: Keep the system and all software components up
to date with the latest security patches and updates to mitigate known
vulnerabilities and protect against exploitation by attackers.
10. Incident Response Plan: Develop and maintain an incident response
plan outlining procedures for detecting, responding to, and recovering
from security incidents. Designate specific roles and responsibilities for
incident response team members and establish communication
channels for reporting and escalating incidents.

16. Tic Tac Toe Game Page - 16 -
RELIABILITY: We assure that the project is completely
authenticated in order to enhance security and corruptions of
database as well as the software.

17. Tic Tac Toe Game Page - 17 -
2.2 Objective of system
 The main objective of on-line game is to efficiently
evaluate the candidate thoroughly through a fully
automated system that not only saves lot of time but
also gives fast results.
 To reduce paper work & time required to prepare a
online work.
 To reduce errors while calculating the Quantity &
Amount.
 Save time for next trade.
 To provide accurate reports.
 Easy to maintain.
 Manual work is reduced.

18. Tic Tac Toe Game Page - 18 -
2.3 User requirements
Requirements analysis in systems engineering and software
engineering, encompasses those tasks that go into determining
the needs or conditions to meet for a new or altered product,
taking account of the possibly conflicting requirements of the
various stakeholders, such as beneficiaries or users.
Requirements analysis is critical to the success of a
development project. Requirements must be documented,
actionable, measurable, testable, related to identified business
needs or opportunities, and defined to a level of detail sufficient
for system design. Requirements can be architectural,
structural, behavioral, functional, and non-functional.
The development of project needs some requirement to make the
project perform better and achieves the goal of project. In
developing Online game, the capabilities of computer and
hardware plays a big impact on project quality. The project
maker should determine the minimum requirements of
hardware and also software to be used to develop a good and
attractive project.
There are two phases of requirement analysis as given below
1) Primary Research: Identifying the user requirements
conducting a survey based on a logicalize.
2) Secondary Research: Comparing the indentified
requirements with already existing software having
similar functionalities.

19. Tic Tac Toe Game Page - 19 -
2.4 Feasibility Study
Technical Feasibility:-
As we know that technical feasibility centers on
the existing computer system (hardware, software, etc.)
and to what extent it can support the proposed
addition. But in this case the situation is different.
Here there is no existing system at all. Everything
needs to be purchased. So each and every office should
have the following for their infrastructure –
a) Client/Server architecture.
b) A good communication media based network.
a. Various System and Application Software installed
on the system.
c) SQL Server 2005.
d) Dot NET Frame work.
a. On Server there should be Windows NT/2000 as
operating system.
e) On clients Windows 9x/2000/XP running on them.
f) Printers (Laser Printer).

20. Tic Tac Toe Game Page - 20 -
Thus, after fulfilling the above requirement the
technical feasibility will hold for the Stock Monitoring
System.
Technical
User needs a web-based system, which will remove all the
above-mentioned Problems that, the user is facing. The user
wants a web-based system, which will reduce the bulk of
paperwork, provide ease of work, flexibility, fast record finding,
modifying, adding, removing and generating the reports.
This software will definitely reduce the delay in Buying and
Selling of Stocks. The cost of the software is justifiable in
context of this great achievement. So we can conclude that the
economic feasibility holds for Scheme Monitoring System and in
monetary terms allocating fund for the project is not a
restriction for them
BehavioralFeasibility:-
As we know that people are inherently resistant to
change and computers have been known to facilitate
change but in spite of these Game System is
behaviorally feasible with its user and employees other
than the users. On the introduction of new system.

21. Tic Tac Toe Game Page - 21 -
3
CHAPTER
ANALYSIS AND
DESIGN
As we are using Android Studio for developing this application
we are designing our application concept. So UML (Unified
Modeling Language) is the best way for represent this project. In
this Chapter we will explain this project by UML concepts and
also database specifications. Diagrams such as the Use Case
Diagram, Class Diagram, and Module Hierarchy Diagram etc.
you will see in this chapter
 Use Case Diagram
 Class Diagram
 Activity Diagram
 Sequence Diagram
 Module Hierarchy Diagram
 Component Diagram
 Deployment Diagram
 Web Site Map Diagram
 User Interface Design
 Table Specification
 Test Procedure and Implementation

22. Tic Tac Toe Game Page - 22 -
3.1 Use Case Diagram
Definitions and Symbols:
Use Case Diagram: Use-case diagrams graphically depict system
behavior (use cases). These diagrams present a high level view
of how the system is used as viewed from an outsider’s (actor’s)
perspective. A use-case diagram may depict all or some of the
use cases of a system.
Actors:
Use Case Name:
Association:
-------------------------->
Actor Name

23. Tic Tac Toe Game Page - 23 -
Initial requirements from use-cases:
1. The system should be internationalized, should be
capable of being used by people of different origins.
2. The system should be secure.
3. The system should be able to provide the services
uninterruptedly and equitably for a reasonably large
group of people.
4. The system should let the users set their preferences for
the stocks in their portfolio.
5. The system should be available all the time.
6. The system database must be protected from illegitimate
access
7. 3.1.1 System Use CaseDaigram

24. Tic Tac Toe Game Page - 24 -
3.2 Class Diagram
Definitions and Symbols of Class Diagram:
Class:
A class is a set of objects that share a common structure and
common behavior (the same attributes, operations,
relationships and semantics). A class is an abstraction of real-
world items. When these items exist in the real world, they are
instances of the class and are referred to as objects [1] [2] [3].
Graphical Depiction:
A class icon is drawn as a 3-part box, with the class name in
the top part, a list of attributes (with optional types and values)
in the middle part, and a list of operations (with optional
argument lists and return types) in the bottom part [1] [2] [3].
Dependency:

25. Tic Tac Toe Game Page - 25 -
3.2.1 System Class Diagram
This class diagram represents whole system that is in stock
exchange market web application. We have divided this into
three parts which are as follow:

26. Tic Tac Toe Game Page - 26 -

27. Tic Tac Toe Game Page - 27 -
3.3 Activity Diagram
Activity diagram depict the activities and responsibilities of
elements that make up a system. Activity modeling is a
specialized type of behavioral modeling concerned with modeling
the activities and responsibilities of elements3.3
Description
Once registered with the system, User has to login each time
he/she wants to use the service.
Primary Actors
System administrator.
Pre-condition.
there are no pre condition to play game.

28. Tic Tac Toe Game Page - 28 -
3.4 Sequence Diagram
A sequence diagram shows elements as they interact over time,
showing an interaction or interaction instance. Sequence
diagrams are organized along two axes: the horizontal axis
shows the elements that are involved in the interaction, and the
vertical axis represents time proceeding down the page. The
elements on the horizontal axis may appear in any order [1].
3.4.1 System Sequence Diagram
In this diagram we are showing an overview of whole system
that how it is going to work. There is investor in the picture who
plays role to initiate this activity with the help of graphical user
interface. Database is centralizing from where investors can
gain their information’s. Explanation is in figure as shown
below.

29. Tic Tac Toe Game Page - 29 -

30. Tic Tac Toe Game Page - 30 -
3.6 Component Diagram
A component diagram describes the components which are the parts of the
system that exists when the system is executing [2].
Figure 3.25Component Diagram

31. Tic Tac Toe Game Page - 31 -
4
CHAPTER
IMPLEMENTATION
4.1input screen
Following are the user interface screen shots of the system
modules.
3.10.1 Main Home

32. Tic Tac Toe Game Page - 32 -

33. Tic Tac Toe Game Page - 33 -
While the game is running

34. Tic Tac Toe Game Page - 34 -

35. Tic Tac Toe Game Page - 35 -
Result

36. Tic Tac Toe Game Page - 36 -

37. Tic Tac Toe Game Page - 37 -

38. Tic Tac Toe Game Page - 38 -
6
CHAPTER
USER MANUAL
For any system to be successful it is important that the
intended user find the system easy to operate. The purpose of
the user manual is to make user acquainted with the system
and help user understand the system and operate it
conveniently. The manual contain several screenshots that
describes how to use the entire system.
 Purpose
 Menu Explanation
 Forms and Report Specification

39. Tic Tac Toe Game Page - 39 -
6.1 PURPOSE
For any system to be successful it is important that the
intended user find the system easy to operate. The purpose of
the user manual is to make user acquainted with the system
and help user understand the system and operate it
conveniently. The manual contain several screenshots that
describes how to use the entire system.
REQUIREMENTS: -
1. Computer system
2. Internet connection
3. User must have some knowledge of computer.
6.2 MENU EXPLANATION
1. Question No: -Here we are displaying the question no.
2. Score: -This is report that gives information about score
3. Submit: -Submit your answer

40. Tic Tac Toe Game Page - 40 -
6.3. Forms and Report Specification
In this section we are showing how Forms and output works.
6.3.1Home Page
Following is the screen shot of Home page with login control at
left hand side
Summary
In this chapter we learned how to use effectively stock exchange
market and there is each and every menu explanation which
guide user throughout the whole system. Arrow represent which
are the buttons and fields that user should use.

41. Tic Tac Toe Game Page - 41 -
7
DRAWBACKS AND
LIMITATIONS
This part of documentation will explain drawbacks and
limitation that are in Stock Exchange Market Application.
Drawbacks
1. As we are using web service by Third Party Company we
don’t have live values as it is 20 minutes late quotes.
2. System requires a high speed broadband internet
connection.

42. Tic Tac Toe Game Page - 42 -
Limitation
1. Mutual funds, equity, commodity markets are not
handled by this system.
2. There are only two exchange which we are handling in
this system.
3. No Only single user concept is here till now.

43. Tic Tac Toe Game Page - 43 -
8
PROPOSED
ENHANCEMENTS
 The main aim of our project is create a good interaction
between the student and teacher.
 We are trying to do the project at best level to satisfy all
the end users
 (i.e, student/faculty).
 In our future we are decided to provide more security to
our website which may not be hacked.
 And we give the choice to student to add their name
under the faculty who they wish and get advice for their
betterment.
 It will be more empowering.
 Next we are aiming to provide some online classes in to
our website.

44. Tic Tac Toe Game Page - 44 -

45. Tic Tac Toe Game Page - 45 -
9
CONCLUSIONS
This part concludes game application in brief explanation and
also specifies operation performed in the application.
Conclusions
This online game system provides facility to conduct online
quizworld wide. It saves time as it allows number of userto give
the exam at a time and displays the results as the test gets over,
so no need to wait for the result. It is automatically generated by
the server. Administrator has a privilege to create, modify and
delete the test papers and its particular questions. User can
register, login and give the test with his specific id, and can see
the results as well.

46. Tic Tac Toe Game Page - 46 -
10
BIBLIOGRAPHY
The Bibliography chapter contains all the reference books,
websites or other reference material details used in order to
make this report worthwhile.
Bibliography
a.http://phplens.com/phpeverywhere/node/view/15
b. http://www.mysql.com/why-mysql/
c. http://student.bu.ac.bd/~shadid/
d.http://www.android.com/

47. Tic Tac Toe Game Page - 47 -
11
ANNEXURE
This section of report specifies Input and Output Forms as
report and also some sample code which is describes in this
section.
 Technology used
 Sample Code

48. Tic Tac Toe Game Page - 48 -
Technology used
Android Studio
Android Studio is the official integrated development
environment (IDE) for Android application development. It is
based on the IntelliJ IDEA, a Java integrated development
environment for software, and incorporates its code editing and
developer tools.
To support application development within the Android
operating system, Android Studio uses a Gradle-based build
system, emulator, code templates, and Github integration.
Every project in Android Studio has one or more modalities with
source code and resource files. These modalities include
Android app modules, Library modules, and Google App Engine
modules.
Android Studio uses an Instant Push feature to push code and
resource changes to a running application. A code editor assists
the developer with writing code and offering code completion,
refraction, and analysis. Applications built in Android Studio
are then compiled into the APK format for submission to the
Google Play Store.
JAVA:
NetBeans is an open-source Integrated Development
Environment written in Java. Development of NetBeans has

49. Tic Tac Toe Game Page - 49 -
really accelerated since it became part of the Apache project.
The NetBeans IDE supports the development of
all Java application types (Java SE, JavaFX, web, EJB and
mobile applications) out of the box

50. Tic Tac Toe Game Page - 50 -
11.2 Sample Code
//MAIN_ACTIVITY/ JAVA CODE//
package com.example.tictactoe;
import androidx.appcompat.app.AppCompatActivity;
import android.os.Bundle;
import android.view.View;
import android.widget.ImageView;
import android.widget.TextView;
public class MainActivity extends AppCompatActivity {
booleangameActive = true;
//Player Representation
//0 - x
//1 - o
int activePlayer = 0;
int[] gameState = {2, 2, 2, 2, 2, 2, 2, 2, 2};
//state meanings:
//0 - x
//1 - o
//2 - Null
int[][] winPositions = { {0, 1, 2}, {3, 4, 5}, {6, 7, 8},
{0, 3, 6}, {1, 4, 7}, {2, 5, 8},
{0, 4, 8}, {2, 4, 6}};
public void playerTap(View view)
{
ImageViewimg = (ImageView) view;
int tappedImage =
Integer.parseInt(img.getTag().toString());
if(!gameActive)
{
gameReset(view);
}
if(gameState[tappedImage] == 2) {
gameState[tappedImage] = activePlayer;
img.setTranslationY(-1000f);
if (activePlayer == 0) {
img.setImageResource(R.drawable.x);

51. Tic Tac Toe Game Page - 51 -
activePlayer = 1;
TextView status = findViewById(R.id.status);
status.setText("O's turn - Tap to Play");
} else {
img.setImageResource(R.drawable.o);
activePlayer = 0;
TextView status = findViewById(R.id.status);
status.setText("X's turn - Tap to Play");
}
img.animate().translationYBy(1000f).setDuration(300);
}
//check if any player has won
for(int[] winPosition: winPositions)
{
if(gameState[winPosition[0]] ==
gameState[winPosition[1]] &&
gameState[winPosition[1]] == gameState[winPosition[2]] &&
gameState[winPosition[0]]!=2)
{
//somebody has won! - find out who!
String winnerStr;
gameActive = false;
if(gameState[winPosition[0]] == 0)
{
winnerStr = "X has Won";
}
else
{
winnerStr = "O has Won";
}
//Update the status bar for winner
announcement
TextView status = findViewById(R.id.status);
status.setText(winnerStr);
}
}
}
public void gameReset(View view)
{
gameActive = true;
activePlayer = 0;
for(int i=0; i<gameState.length; i++)

52. Tic Tac Toe Game Page - 52 -
{
gameState[i]= 2;
}
((ImageView)findViewById(R.id.imageView0)).setImageResou
rce(0);
((ImageView)findViewById(R.id.imageView1)).setImageResou
rce(0);
((ImageView)findViewById(R.id.imageView2)).setImageResou
rce(0);
((ImageView)findViewById(R.id.imageView3)).setImageResou
rce(0);
((ImageView)findViewById(R.id.imageView4)).setImageResou
rce(0);
((ImageView)findViewById(R.id.imageView5)).setImageResou
rce(0);
((ImageView)findViewById(R.id.imageView6)).setImageResou
rce(0);
((ImageView)findViewById(R.id.imageView7)).setImageResou
rce(0);
((ImageView)findViewById(R.id.imageView8)).setImageResou
rce(0);
TextView status = findViewById(R.id.status);
status.setText("X's turn - Tap to Play");
}
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);
}
}