C E R T I F I C A T E

This is to certify that

Aarjjya Suhana Mohanty
has successfully completed her
Computer science project titled
CYBER CAFE
Under the supervision and guidance of
Rashmi Ma’am
(Computer science teacher)
in the partial fulfilment of the computer
science practical
assessment conducted during the
academic year
2024-25

EXAMINER TEACHER
___________ _____________
 ACKNOWLEDGEMENT
I would like to express my immense gratitude to
my computer science teacher RASHMI MA’AM for
the help and guidance he provided for completing
this project.
I also thank my parents who gave their ideas and
inputs in making this project. Most of all I thank
our school management, for providing us the
facilities and opportunity to do this project.
Lastly, I would like to thanks my classmates who
have helped me in this project. Their support
made this project fruitful.

~Aarjjya Suhana Mohanty

 INDEX
CONTENT PAGE NO

Certificate 2

Acknowledgement 3

Introduction 5

Objectives 5

Proposed System 5

SDLC 6

System concept 7
development phase

Flow chart 12

Source code 18

Output 21

Testing 22
 INTRODUCTION
The cyber cafe management system is developed with a view of providing a
better experience for customers in modern cyber cafes. It clears the doubts of
the customers and helps the owner of the cyber cafe in maintaining a solid
record of the customers and ensuring the paying of bills. It also helps in
providing feedbacks of our cyber cafe. This is a project which helps us to
understand the importance of computers in our daily life because without
them there would have been no cyber cafes.

OBJECTIVES OF THE PROJECT

The objective of this project is to let the students apply the programming
knowledge into a real- world situation/problem and exposed the students how
programming skills helps in developing a good software.
1. Write programs utilizing modern software tools.
2. Apply object oriented programming principles effectively when developing
small to medium sized projects.
3. Write effective procedural code to solve small to medium sized problems.
4. Students will demonstrate a breadth of knowledge in computer science, as
exemplified in the areas of systems, theory and software development.
5. Students will demonstrate ability to conduct a research or applied Computer
Science project, requiring writing and presentation skills which exemplify
scholarly style in computer science.

PROPOSED SYSTEM
Today one cannot afford to rely on the fallible human beings of be really wants
to stand against today's merciless competition where not to wise saying "to err
is human" no longer valid, it's outdated to rationalize your mistake. So, to keep
pace with time, to bring about the best result without malfunctioning and
greater efficiency so to replace the unending heaps of flies with a much
sophisticated hard disk of the computer.
One has to use the data management software. Software has been an ascent in
atomization various organisations. Many software products working are now in
markets, which have helped in making the organizations work easier and
efficiently.
Data management initially had to maintain a lot of ledgers and a lot of paper
work has to be done but now software product on this organization has made
their work faster and easier. Now only this software has to be loaded on the
computer and work can be done.
This prevents a lot of time and money. The work becomes fully automated and
any information regarding the organization can be obtained by clicking the
button.
Moreover, now it's an age of computers of and automating such an
organization gives the better look.

SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)

The systems development life cycle is a project management technique that

divides complex projects into smaller, more easily managed segments or
phases.
Segmenting projects allows managers to verify the successful completion of
project phases before allocating resources to subsequent phases.
Software development projects typically include initiation, planning, design,
development, testing, implementation, and maintenance phases. However, the
phases may be divided differently depending on the organization involved.

SYSTEM CONCEPT DEVELOPMENT PHASE

The System Concept Development Phase begins after a business need or
opportunity is validated by the Agency/Organization Program Leadership and
the Agency/Organization CIO.
The purpose of the System Concept Development Phase is to:
* Determine the feasibility and appropriateness of the alternatives.
* Identify system interfaces.
* Identify basic functional and data requirements to satisfy the business need.
* Establish system boundaries; identify goals, objectives, critical success
factors, and performance measures.
* Evaluate costs and benefits of alternative approaches to satisfy the basic
functional requirements
* Assess project risks
* Identify and initiate risk mitigation actions, and develop high-level technical
architecture, process models, data models, and a concept of operations. This
phase explores potential technical solutions within the context of the business
need.
* It may include several trade-off decisions such as the decision to use COTS
software products as opposed to developing custom software or reusing
software components, or the decision to use an incremental delivery versus a
complete, onetime deployment.
* Construction of executable prototypes is encouraged to evaluate technology
to support the business process. The System Boundary Document serves as an
important reference document to support the Information Technology Project
Request (ITPR) process.
* The ITPR must be approved by the State CIO before the project can move
forward.
 REQUIREMENTS ANALYSIS PHASE
This phase formally defines the detailed functional user requirements using
high-level requirements identified in the Initiation, System Concept, and
Planning phases. It also delineates the requirements in terms of data, system
performance, security, and maintainability requirements for the system. The
requirements are defined in this phase to a level of detail sufficient for systems
design to proceed. They need to be measurable, testable, and relate to the
business need or opportunity identified in the Initiation Phase. The
requirements that will be used to determine acceptance of the system are
captured in the Test and Evaluation Masterplan.
The purposes of this phase are to:
*Further define and refine the functional and data requirements and document
them in the Requirements Document,
* Complete business process reengineering of the functions to be supported
(i.e., verify what information drives the business process, what information is
generated, who generates it, where does the information go, and who
processes it),
* Develop detailed data and process models (system inputs, outputs, and the
process.
* Develop the test and evaluation requirements that will be used to determine
acceptable system performance.

DESIGN PHASE
The design phase involves converting the informational, functional, and
network requirements identified during the initiation and planning phases into
unified design specifications that developers use to script programs during the
development phase. Program designs are constructed in various ways. Using a
top-down approach, designers first identify and link majorprogram
components and interfaces, then expand design layouts as they identify and
link smaller subsystems and connections. Using a bottom-up approach,
designers first identify and link minor program components and interfaces,
then expand design layouts as they identify and link larger systems and
connections. Contemporary design techniques often use prototyping tools that
build mock-up designs of items such as application screens, database layouts,
and system architectures. End users, designers, developers, database
managers, and network administrators should review and refine the
prototyped designs in an iterative process until they agree on an acceptable
design.
Audit, security, and quality assurance personnel should be involved in the
review and approval process. During this phase, the system is designed to
satisfy the functional requirements identified in the previous phase. Since
problems in the design phase could be very expensive to solve in the later
stage of the software development, a variety of elements are considered in the
design to mitigate risk. These include:
* Identifying potential risks and defining mitigating design features.
* Performing a security risk assessment.
* Developing a conversion plan to migrate current data to the new system.
* Determining the operating environment.
* Defining major subsystems and their inputs and outputs.
* Allocating processes to resources.
* Preparing detailed logic specifications for each software module. The result is
a draft System Design Document which captures the preliminary design for the
preliminary design for the system.
* Everything requiring user input or approval is documented and reviewed by
the user. Once these documents have been approved by the Agency CIO and
Business Sponsor, the final System Design Document is created to serve as the
Critical/Detailed Design for the system.
* This document receives a rigorous review by Agency technical and functional
representatives to ensure that it satisfies the business requirements.
Concurrent with the development of the system design, the Agency Project
Manager begins development of the Implementation Plan, Operations and
Maintenance Manual, and the Training Plan.
 DEVELOPMENT PHASE
The development phase involves converting design specifications into
executable programs. Effective development standards include requirements
that programmers and other project participants discuss design specifications
before programming begins. The procedures help ensure programmers clearly
understand program designs and functional requirements. Programmers use
various techniques to develop computer programs. The large transaction
oriented programs associated with financial institutions have traditionally been
developed using procedural programming techniques. Procedural programming
involves the line-by-line scripting of logical instructions that are combined to
form a program. Effective completion of the previous stages is a key factor in
the success of the Development phase. The Development phase consists of:
Translating the detailed requirements and design into system components.
Testing individual elements (units) for usability.
Preparing for integration and testing of the IT system .

INTEGRATION AND TEST PHASE

Subsystem integration, system, security, and user acceptance testing is
conducted during the integration and test phase. The user, with those
responsible for quality assurance, validates that the functional requirements,
as defined in the functional requirements document, are satisfied by the
developed or modified system. OIT Security staff assess the system security and
issue a security certification and accreditation prior to
installation/implementation.
Multiple levels of testing are performed, including:
Testing at the development facility by the contractor and possibly supported by
end users
Testing as a deployed system with end users working together with contract
personnel
Operational testing by the end user alone performing all functions.
Requirements are traced throughout testing, a final Independent Verification &
Validation evaluation is performed and all documentation is reviewed and
accepted prior to acceptance of the system.

OPERATIONS AND MAINTENANCE PHASE

The system operation is ongoing. The system is monitored for continued
performance in accordance with user requirements and needed system
modifications are incorporated. Operations continue as long as the system can
be effectively adapted to respond to the organization's needs. When
modifications or changes are identified, the system may re-enter the planning
phase.
The purpose of this phase is to:
* Operate, maintain, and enhance the system.
* Certify that the system can process sensitive information.
* Conduct periodic assessments of the system to ensure the functional
requirements continue to be satisfied.
* Determine when the system needs to be modernized, replaced, or retired.
FLOW CHART
SOURCE CODE
OUTPUT
 TESTING
Software Testing is an empirical investigation conducted to provide
stakeholders with information about the quality of the product or service
under test[1] , with respect to the context in which it is intended to operate.
Software Testing also provides an objective, independent view of the software
to allow the business to appreciate and understand the risks at implementation
of the software. Test techniques include, but are not limited to, the process of
executing a program or application with the intent of finding software bugs.
It can also be stated as the process of validating and verifying that a
software program/application/product meets the business and technical
requirements that guided its design and development, so that it works as
expected and can be implemented with the same characteristics. Software
Testing, depending on the testing method employed, can be implemented at
any time in the development process, however the most test effort is employed
after the requirements have been defined and coding process has been
completed.

TESTING METHODS
Software testing methods are traditionally divided into black box testing
and white box testing. These two approaches are used to describe the point of
view that a test engineer takes when designing test cases.

BLACK BOX TESTING

Black box testing treats the software as a "black box," without any
knowledge of internal implementation. Black box testing methods include:
equivalence partitioning, boundary value analysis, all-pairs testing, fuzz testing,
model-based testing, traceability matrix, exploratory testing and specification-
based testing.

SPECIFICATION-BASED TESTING
Specification-based testing aims to test the functionality of software
according to the applicable requirements. [16] Thus, the tester inputs data into,
and only sees the output from, the test object. This level of testing usually
requires thorough test cases to be provided to the tester, who then can simply
verify that for a given input, the output value (or behaviour), either "is" or "is
not" the same as the expected value specified in the test case. Specification-
based testing is necessary, but it is insufficient to guard against certain risks

ADVANTAGES AND DISADVANTAGES

The black box tester has no "bonds" with the code, and a tester's
perception is very simple: a code must have bugs. Using the principle, "Ask and
you shall receive," black box testers find bugs where programmers don't. But,
on the other hand, black box testing has been said to be "like a walk in a dark
labyrinth without a flashlight," because the tester doesn't know how the
software being tested was actually constructed.
That's why there are situations when (1) a black box tester writes many
test cases to check something that can be tested by only one test case, and/or
(2) some parts of the back end are not tested at all. Therefore, black box testing
has the advantage of "an unaffiliated opinion," on the one hand, and the
disadvantage of "blind exploring," on the other.

WHITE BOX TESTING

White box testing, by contrast to black box testing, is when the tester has
access to the internal data structures and algorithms (and the code that
implement these)
Types of white box testing:-
The following types of white box testing exist:
*api testing - Testing of the application using Public and Private APIs
* Code coverage - creating tests to satisfy some criteria of code coverage.
For example, the test designer can create tests to cause all statements in
the program to be executed at least once.
* fault injection methods.
* mutation testing methods.
* static testing - White box testing includes all static testing.
 CODE COMPLETENESS EVALUATION
White box testing methods can also be used to evaluate the
completeness of a test suite that was created with black box testing methods.
This allows the software team to examine parts of a system that are rarely
tested and ensures that the most important function points have been tested.
Two common forms of code coverage are:
* Function Coverage: Which reports on functions executed and
* Statement Coverage: Which reports on the number of lines executed to
complete the test.
They both return coverage metric, measured as a percentage