CONTENTS

1. PROBLEM STATEMENT AND ARCHITECTURE

1.1 PROBLEM STATEMENTS
1.2 PROJECT DESCRIPTION AND DETAILS
1.3 TEAM ARCHITECTURE
1.4 DEFINITION , ACRONYM AND ABBREVIATION
2. SPECIFIC REQUIREMENTS
2.1 FUNCTIONAL REQUIREMENTS
2.2 NON FUNCTIONAL REQUIREMENTS
3. REQUIREMENT ANALYSIS
3.1 PROCESS MODEL (DFD)
3.2 DATA DICTIONARY
3.3 MINI SPECIFICATION
4. HIGH LEVEL DESIGN
4.1 SOFTWARE ARCHITECTURE
4.2 SCREEN DESIGN ( USER INTERFACE)
4.3 REPORT LAYOUT
5. LOW LEVEL DESIGN
5.1 FUNCTIONS DETAILS DESCRIPTION AND PROTOTYPE
5.2 DATA TYPE AND DATA STRUCTURE
5.3 ALGORITHM / FLOWCHART / PSEUDOCODE DESIGN
5.4 UNIT TEST PLAN
6. TESTING REPORT
7. BIBLIOGRAPHY
 CYBER-CAFE MANAGEMENT SYSTEM
1. PROBLEM STATEMENT AND TEAM
ARCHITECTURE

1.1 PROBLEM STATEMENT

The purpose of this is based on working of cyber cafe management. The cyber
cafe currently maintains record manually, due to manual method the processing
is not up to the mark and inefficient. This project is undertaken to automate
cyber cafe management system. It aims managing multiple clients who can log
in and use its facilities, this activity involves adding of new user along with the
modification and deletion of user’s details. Here basically there are two types of
users one is the server user i.e. administrator who have the right to monitor each
and every client or customer and other is the client user who can browse if he is
authenticated. Once client user mentions their system requirement and time
needed software should allot him a terminal where he starts the session. In case
no terminal is free, software should tell him the waiting time and terminal no.,
while the server user has the right to permit the client user and have access to all
computers working under the cafe.Also, one entry should be made once and
further the entries are fetched as required, this makes system more efficient. The
user can only login if they are authorised to do so.
This include all types of cost which includes system usage, printing/scanning or
carrying a device (pen drive, CDs etc) inside a cafe, here users can pay the
amount through credit card, cash or net banking. And net charges are also
applicable.Usage of hardware devices such as for printing/scanning or carrying
a device (pen drive, CDs etc) inside a café are chargeable. The amount of
system usage and net charges are also applicable.
At the end of the day, the owner must be able to see his / her total revenue, here
users can pay the amount through credit card, cash or net banking.Also, if there
is a regular customer they can have membership card which give them a benefit
of free usage according to the duration of the membership card. Customisable
pricing with prepaid and post-paid accounts, prepaid codes, refills is also
available. Periodic discounts will be given on specific days or times, traffic and
group discounts, time bonuses or points system.
1.2 PROJECT DESCRIPTION AND DETAILS
This project is intended to be used in a Cyber Cafe.
All Cyber Cafes have some basic needs likeable to control the systems that are
being rented to the customers and are charged on timely basis. Nowadays it may
also require to save some details of the customers for security reasons. When a
customer enters a cyber cafe, he has to be allotted a PC and the start time is
noted. At any time, the administrator should be able to see the status of any PC,
other activities of customer like using hardware devices should be recorded.
When customer is done he/she can submit on the form to generate the bill.
This basically consists of two types of users:
i)The Server User
The Server User is the administrator of the Server Machine who has the right to
monitor each and every clientor customer. He solely controls the server
machine. This involves:
 Taking inputs of total no. Of systems present at the cafe along with their
details include system no, its type (gaming or browsing etc)
 Taking details of printers available
 Defining rates for various activities involving browsing internet, playing
games, taking printouts and scanning and rates of various devices
(dispersive) taken inside the internet cafe.
(After configuration)
 Booking details including managing working hours of the user i.e. the
data about the member that when he logs in the computer as client and
what time he spends. It also manages the details of the client
membership; its duration and the details of the offers being presented
through the membership card which will be further useful in payment
procedure.
 Calculating the total bill by fetching details from the client login and its
membership card and its benefits.
 Showing the details of revenue on daily basis.
 ii)The Client User
The Client User is the customer for the cyber. He can login to the client system
and start browsing only if he is authenticated otherwise the Admin user can log
him in remotely.
 The user provided with remarkable facilities of adding, printing, saving,
scanning, deleting as well as editing the data that has been entered
currently or in the past.

MODULE DESCRIPTION:
1.CUSTOMER MANAGEMENT:
This module should implement the user creation and management. The users could
be given a username and password and also they could be given a prepaid account
by which they can browse until they finish the amount in their accounts. This
comprises of following submodules:
i)Entry/Search of Customer details.
ii)Assign/Login Customer ID.
iii)Viewing/Editing Customer details.
2.SYSTEM MANAGEMENT:
This module checks the status of all the systems and assigns the system to the
customer according to their availability and time plan of the customer also they are
given the option to further increase their time plan. This comprises of following
submodules:
i)Check status of all systems.
ii)Assign system to the user.
iii)Modify the current time plan for the user.
3.BILLING:
This module should produce bills depending upon the user activity and hence
generate a report comprising all the requests, regarding the customers session.
Here, the postpaid customer makes full payment, comprising charges for his
browsing time as well as other services seeked such as items purchased,
refreshments, scanning, printing etc,. While the prepaid customer will pay for the
extra services seeked other than browsing time as the due deduction for browsing
will be done through his account.This has following submodules:
i)Prepaid/Postpaid customer.
ii)Bill generation according to time plan.
iii)Discounts.

1.3 TEAM ARCHITECTURE

 ANALYSIS- Urja, Aditi, Soumya
 DESIGN- - Urja, Aditi, Soumya
 CODING/IMPLEMENTATION- Urja
 DOCUMENTATION- Urja, Aditi, Soumya
 TESTING- Urja, Aditi, Soumya

1.4 DEFINITION, ACRONYM AND ABBREVIATION

 RAM- Random Access Memory
 User ID- The unique identity issued to every user
 DFD- The data flow diagram
 2. SPECIFICATION REQUIREMENTS

2.1 FUNCTIONAL REQUIREMENTS

All system should have the client for program running. Following are the
functionalities according to their modules.

2.1.1 CUSTOMER MANAGEMENT

NO. REQUIREMENT ESSENTIAL DESCRIPTION OF REMARKS

OR THE
DESIRABLE REQUIREMENT
OR
OPTINAL
RS1 Entry of customer Essential Adding a customer by
details. entering his/her details.
RS2 Searching for Essential Searching if customer
existing customer. is already a member.
RS3 Continuation of Essential Executed after the This part occurs if
above ongoing completion of above customer already
process. requirement. exists.
RS4 Assign customer ID Essential Executed after the This is executed
for new customer. result of RS2. when a customer is
not present in the
records.
RS5 View/Edit customer Desirable Depends entirely on
details. the administrator.
RS6 Deleting customer Desirable Memory management.
details.

2.1.2 SYSTEM MANAGEMENT

NO. REQUIREMENT ESSENTIAL DESCRIPTION OF REMARKS

OR THE
DESIRABLE REQUIREMENT
OR
OPTINAL
RS1 Status of all the Essential Administrator should Necessary for
systems. know the current status system allocation
of all the systems. to the user.
RS2 Assigning of system Essential Based on the status of
. the system whether
 free or not.
RS3 Assigning of time Essential The time the user is
plan. going to invest on the
system.
RS4 Assigning of Essential If all the systems are
minimum waiting busy considering the
time if system is worstcase scenario
busy. minimum waiting time
is allocated for the
systems.
RS5 Further increment of Desirable Depends on the user
time plan. will.

2.1.3 BILLING MANAGEMENT

NO. REQUIREMENTS ESSENTIAL DESCRIPTION OF REMARKS

OR THE
DESIRABLE REQUIREMENT
OR
OPTINAL
RS1 Prepaid/Postpaid Essential Checking what kind of
customer. account does the
customer has.
RS2 Bill generation. Essential This is generated
according to the time
plan of the user.
RS3 Browsing charges. Essential Mentioned explicitly. Made for postpaid
type only.
RS4 Hardware charges Essential In case if user uses
printer, hard disk etc.
RS5 Discounts Desirable Available according to
regularity of customer
and occasions.
2.2 NON-FUNCTIONAL REQUIREMENT
The non-functional requirements elaborate the performance characteristics of
the system. Following fall in this category:
2.2.1 PERFORMANCE REQUIREMENTS
The important aspects of CYBER CAFE MANAGEMENT SYSTEM
softwareis time constrain. This software is real time and hence should be
performed in minimum requirements.
The accountability is avital feature and this could only be assured if the system
is working in full capability. So uninterrupted power supply is needed.
2.2.2 SAFETY REQUIREMENTS
The data handled in the cyber cafe system is very vital. The server should
always be confirmed to run properly and data are saved to the database at
consecutive intervals.
Power is a significant feature and the power supply should be always taken care
of. An uninterrupted power supply is always recommended.
2.2.3 SECURITY REQUIREMENTS
The security system features from having a login for all the users to access the
software. The login details will be used in the system also. So, the chances of
the software getting intruded are very less.
2.2.4 SOFTWARE REQUIREMENTS
The source code of the product is going to be open as this is going to be open
source software. It will be free for further modifications and improvements.
2.2.5 BUSINESS RULES
The illegal duplication of the reports should be strictly dealt with the
administrator, should have full details of the user while a user is getting
registered to the system.
2.2.6 SPECIAL REQUIREMENT
2.2.6.1 Backup and Recovery
 Keeps backups of all the data files in a separate directory drive.
 Frequently auto-save information, in case of a lost network connection,
the browser or system crashing, etc.
2.2.6.2 Data migration
The concept of data migration is important to ensure that the data that is being
entered and stored today could be accessed. After even several years.
2.2.6.3 Data retention
Maintain a log file for each user logging in and also maintain the account details
of the users who have finished the account could be obtained from cyber cafe
reports.
2.2.6.4 User training
Clients must ne trained to operate the cyber cafe software in creating new
accounts and performing report operations.
2.2.6.5 Installation
A conductive environment for the efficient running of the cyber cafe
recommended. The server should be handled with great care and all
unauthorized access should be restricted.
 3. REQUIREMENT ANALYSIS

3.1 PROCESS MODEL(DATA FLOW DIAGRAM(DFD))

A DFD or bubble chart is used to depict the data flow taking place in the
system. This helps to understand what activities make up the system, what data
enters and what leaves the system.
A DFD is a graphical tool which provides a mechanism for functional
modelling as well as information flow modelling.

-LEVEL 0
-LEVEL 1

-LEVEL 2.1
-LEVEL 2.2

-LEVEL 2.3
3.2 DATA DICTIONARY
A data dictionary has many advantages. The most obvious is documentation; it
is a valuable reference in any organization. Another advantage is improving
analystuser communication by establishing consistent definition of various
elements, teamsand procedures. Also, data dictionary is an important step in
building database.

NO. FIELD NAME DESCRIPTION DATA TYPE

1 Customer The end user of the Char
system.
2 Admin The owner of the Char
system, in charge of
cafe.
3 Billing The total amount of Int
money at the end of
the session of the
user.
4 Username The customer Char
name.
5 Password The security code A combination a set of
given to identify the characters and integers
user. not exceeding in total 8
bytes.

3.3 MINI SPECIFICATIONS

This has the minimum software and hardware requirements for the cyber cafe
management system.
 SOFTWARE SPECIFICATION:
 OPERATING SYSTEM-Any windows based Operating
System.

 HARDWARE SPECIFICATIONS:
 PROCESSOR-Pentium IV processor, intel core i3 and i5.
 RAM-256 MB or above.
 HARD DISK- 40 GB or above.
 MONITOR-NORMAL or above.
 KEYBOARD-NORMAL or above.
 4. HIGH LEVEL DESIGNS

4.1 SOFTWARE ARCHITECTURE

The basic logic in software architecture is to specify the logic for the different
modules that has been specified during system design. Specifying the logic will
require developing an algorithm that will implement the given specifications.
 Login Screen: This is for the administrator to get into the software. It
requires a user name and password.
 Account Details: This shows the account status of various users with their
login times.
 Adding new customer: This utility is to create new users or clients in the
cyber cafe management system.
 Reports: This is used to generate reports of the login and account details
of users.
 User login (client side): The user has to give a username and password by
which he/she can be authenticated and can further access the network.
 User account: This enables the user to view their account status.
4.2 SCREEN DESIGNS
The main screen of the user shows these choices-:
1. Customer management
2. System management
3. Billing and
4. Exit
4.2.1 CUSTOMER MANAGEMENT
In this firstly login needs to be done which take us to another interface if
information entered matches. It will contain another set of options to choose
including-
1. Record details- this carry all the details of the customers along with their
timeplan, requests, billing details etc. This also keeps records of the user
personal details including name, phone no., email address, personal address etc.
2. Entry/edit menu-this provide entry of new user along with the display, search,
modification and deletion of the existing users.
3. Back to main menu-this will take you to the main interface.
4. Exit
4.2.2 SYSTEM MANAGEMENT
This will take us to another interface including-
1. Display system status- this carry details of all systems in running and free
state which helps in allotting terminals to new users and calculating waiting
time if no system is in free state.
2. Enter/edit system details- this provide entry of a new systems and other
hardware devices like printers, scanners etc along with the display, search,
modifications and deletion of existing system details.
3. Back to main menu
4. Exit
4.2.3 BILLING
1. Calculate bill- this will calculate the bill by taking information from other
modules like customer type, time plan, other requests from the customers,
devices brought in etc., these all details are taken and calculation is done
according to the type(prepaid/postpaid) of the customer. This billing will also
depend on the discounts availed by the customers.
2. Display bill details- this show a receipt form bill which contain details of
every charges applied for user access.
3. Back to main menu
4. Exit
4.3 REPORT LAYOUT
SCREEN 1-

SCREEN 2-
SCREEN 3-
 5. LOW LEVEL DESIGNS

5.1 FUNCTIONAL DETAILS, DESCRIPTION AND

PROTOTYPE:
Functions are made according to the module division and each function is easily
accessible by another module functions.
-Functions including under customer management are-:
1. void input(struct customer *s)- for getting details of the customers.
2. void writecustomer()-keeps record of all existing and previous users.
3. void displayall()-display all customers altogether
4. void displaysp(int n)-this displays record of the searched customer
,searching of a customer is done through customer id.
5. void modifycustomer()-this function modifies customer personal details if
any of the personal detail needs to be changed like address,phone no.,or
time plans etc.
6. void deletecustomer()-this deletes record of the customer.
7. void paymenttotal()-this function will generate the final bill for the
customer.
-Functions including under system management are-:
1. void input(struct system *s)-input system details.
2. void write_system()-enters new system details.
3. void display_all()-display all system details along with the running
system , free systems and waiting time.
4. void display_sp(int n)-display details of searched system.
6. void modify_customer()-modification of system details.
7. void delete_customer()-deletion of system details.
8. void waiting_time()-this function will calculate the waiting time
according to the customer entered details and time plan .
-Functions including under billing are-:
1. void getcost()-this will receive every type of charge details from
customer details .
2. void charges()-this function will keep record of predefined charges of
browsing, printing/scanning ,devices brought in individual charges etc.
3. void calculate_bill()-this function will apply accordingly charges of
utilization from the cafe along with the prepaid/postpaid implementation.
4. void payment_total()-directly generate bill as per calculations and
displayed in customer interface.

5.2 DATA TYPE AND DATA STRUCTURE

Database structure is the process of producing a detailed data model of a
database. This logical data model contains all the needed logical and physical
design choices and physical storage parameters needed to generate a design in a
Data definition language which can then be used to create a database.
TABLE 1: ENTRY OF USER
FIELD NAME KEY DATATYPE SIZE DESCRIPTION
USER ID PRIMARY CHAR 12 The id given to the
KEY user
PASSWORD PRIMARY CHAR + INT 8 The unique
KEY passcode of every
id

TABLE 2: PAYMENT
FIELD KEY DATA SIZE DESCRIPTION
NAME TYPE
RECEIPT PRIMARY INT 12 RECEIPT NO.
NO. KEY
AMOUNT INT 20 TOTAL
MONEY
DATE PRIMARY INT 8 DATE
KEY
TIME PRIMARY INT 12 TIME
KEY
USER ID FOREIGN CHAR 12 The id assigned
KEY to the user
5.3 ALGORITHM/FLOWCHART/PSEUDO CODE DESIGN
Here are the pseudocodes of some functions-:
1. function to keep records of customer
void write_customer()
{ struct customer data;
file = fopen("customer.dat", "ab");
printf("\n\nPlease enter the details of customer \n");
input(&data); //input() is another functions which takes customer details
fwrite(&data, sizeof(data), 1, file);
fclose(file);
printf("\ncustomer Record Has Been Created ");
}

2. function to display customer detail for particular customer accessed

through customer id
void display_sp(int n)
{
struct customer data;
int flag = 0;
file = fopen("customer.dat", "rb");
while ((fread(&data, sizeof(data), 1, file)) > 0)
{ if (data.cust_no == n)
{
display(data); //display is another function that display customer
details
flag = 1;}}
fclose(file);
if (flag == 0)
 printf("\nRecord not exist");}
3. function to modify customer details
void modify_customer()
{
struct customer data;
int no, found = 0;

printf("\nTo Modify ");

printf("\nPlease Enter the customer id of the customer to be modified: ");
scanf("%d", &no);
file = fopen("customer.dat", "rb+");
while ((fread(&data, sizeof(data), 1, file)) > 0 && found == 0)
{
if (data.cust_no == no)
{
display(data);
printf("\nPlease enter the new details of customer \n");
input(&data);
fseek(file, - (long)sizeof(data), 1);
fwrite(&data, sizeof(data), 1, file);
printf("\n Record Updated");
found = 1;
}
}
fclose(file);
if (found == 0)
printf("\n Record Not Found ");
}

4. function to delete customer detail

void delete_customer()
{ int no;
struct customer data;
FILE *file2;
printf("\n\nDelete Record");
printf("\nPlease Enter the customer id of the customer to be deleted: ");
scanf("%d", &no);
 file = fopen("customer.dat", "rb");
file2 = fopen("temp.dat", "wb");
rewind(file);
while ((fread(&data, sizeof(data), 1, file)) > 0)
{ if (data.cust_no != no)
{
fwrite(&data, sizeof(data), 1, file2);
}
}
fclose(file2);
fclose(file);
remove("customer.dat");
rename("temp.dat", "customer.dat");
printf("\nRecord deleted.");
}
Similar functions are required for the system details entry/edit.
5.4 UNIT TEST PLAN

SR NAME OF UNIT TO BE DESCRIPTION

NO. TESTED

1. Customer management module  The user does not enter customer id,
it is decided by the software itself.
 Customer name should not be
accepted a null value.
 Customer name must be less than
twenty characters.
 Address should not be accepted a
null value.
 Address must be less than thirty five
characters.
 Phone number must accept only 6 to
12 characters.
 E-mail must be less than thirty five
character and valid.

2. System management module  The user does not enter system no; it
is decided by the software itself.
 Computer name must be twenty
characters.
 Modification and deletion of details .

3. Billing module  Calculation must be clear for bill

generation.
 Prepaid and postpaid users are
considered separately.
 6.TESTING REPORT

SR NO. NAME OF TEST DESCRIPTION

PLAN

1. In login  Check incorrect

password.
2. In output module  Searching and display
of the customer details
must be clear.
 Allotment of time
plan.
 Allotment of terminal
and customer id.
 Getting waiting time if
all systems are in
running or used state.
 Bill generation in
accordance with
discounts,
memberships and
other criteria.
 7.BIBLIOGRAPHY

Books reffered-
- The C programming language by Dennis M. Richie
- C:How to program by Paul deitel
Websites reffered-
- www.sanfoundry.com
- www.slideshare.com
- www.lucidchart.com
- www.youtube.com
 ACKNOWLEDGEMENT

It is a matter of great pleasure for me to present this report of 4 weeks industrial

training. Through this report , I would like to acknowledge numerous people
whose consistent support and guidance has been the standing pillar in
architecture of this report.
To begin with my sincere thanks to Dr. S.S. THAKUR , Principle of my
college for giving us the opportunity to undergo industrial training. I express
thanks to Dr. PRASHANT KUMAR JAIN HOD, Department of Information
Technology, who gave encouragement and valuable suggestions throughout the
training .I am very much thankful to all the team members for their motivation
and understanding , who did their best to bring improvements through their
suggestion and teamwork abilities.
Also lastly I would like to thank our parents, who encouraged me to extend my
reach. With their help and support, we have been able to complete this work.
 INTRODUCTION ABOUT THE INDUSTRY

Intec Infonet Pvt. Ltd. Founded in 1991, is a leading provider of information

and communication technology services, offering systems & network
integration, software applications, managed IT services, design & consulting
services.
During the two decades of consistent growth, their strength has been building
and managing Information & communication Technology, application &
infrastructure solutions for a broad range of organizations, including small &
medium enterprises, educational institutes, large corporate as well as public
sector companies and government organizations.
They have an outstanding team of professionals, exceptional customer service
and strong relationships with technology partners as well as customers.
Intec Infonet employs over 250 highly motivated professionals. Their teams of
exceptionally skilled, talented, committed and hard working professionals have
some of the highest technical accreditations and are always geared up to deliver
a consistent and exceptional experience to clients. Intec Infonet is headquartered
at New Delhi and has grown consistently over the years adding regional offices
across India to serve its wide-spread client base.
They at Intec bring together the best of the breed products & technologies from
global leaders and assists customers in implementing the best ICT and
infrastructural solutions in order to meet their current as well as future growth
requirements. Intec prides itself for offering the best in class service to their
customer and for taking a vendor neutral approach to technology which helps in
delivering an optimized solution based on the client's requirements.