Cyber Cafe Management

Cyber Caf Management System 2016
Software Requirement Specification

For
Cyber Caf Management System
Prepared by
1. Rathod Bhoomika K.
2. Shaikh Amreen A.
3. Solanki Unnati R.
140283107027
140283107029
140283107030
L. D. College of Engineering
Department of Computer Engineering
CERTIFICATE
Date: 04/04/2016
This is to certify that the dissertation entitled Cyber Caf Management System
has been carried out by Rathod Bhoomika(140283107027) , Shaikh Amreen
(140283107029) , Solanki Unnati (140283107030) under my guidance in fulfillment of the
degree of Bachelor of Engineering in Computer Engineering (6th Semester) of L.D. College
of Engineering affiliated with Gujarat Technological University, Ahmadabad during the
academic year 2016.
Guide:
Prof. V.B.Vaghela
CE Department
Prof. D A Parikh
Head of the Department
Acknowledgement
Here we gladly present the project on Cyber Cafe Management System as part of
the 6th Semester B.E. in computer Engineering. At this time of submitting this
report we use this opportunity to mention those people who with us along the work.
I would like to thank my supervisor, Mr. V.B.Vaghela sir for his guidance and
comments on various aspects of this project and for thoughtful contribution in my
effort.
Other known and unknown persons who helped me in my work also deserve
Thanks for their co-operation. Last but not the least; I am very thankful to my
friends for providing me a valuable assistance during my work.
TABLE OF CONTENTS
1. Introduction....6
1.1
1.2
1.3
1.4
Purpose..6
Document Convention.6
Intended Audience and Reading Suggestion...6
Project Scope..7
2. Overall Description.......8
2.1 Product Perspective8
2.2 Product Features.8
2.3 User classes and Characteristics...9
2.4 Operating Environment..9
2.5 Design Constraints.9
2.6 User Documentation..10
2.7 Assumptions and Dependencies..10
3.
Functional Requirements.......11
4.
External Interface Requirements......18

4.1 GUI.18
4.2 Hardware Interface.18
4.3 Software Interface..18
5.
Non Functional Requirements....19

5.1 Performance Requirements19
5.2 Safety Requirements..19
5.3 Security19

5.4
Software Quality Attributes20
6.
Preliminary Schedule21
7.
Operational Scenario.21
8.
Diagram......26
9.
Testing.................................................................................................27
10 Preliminary schedule...........................................................................32
11. Preliminary Budget.33
12. Cost Estimation..34
13. References ..35
Appendix A: Glossary37
1. Introduction
1.1 Purpose of Requirements document
This software requirements specification (SRS) specifies the requirements of the
cyber caf management system which will be used in college internet laboratories
or internet cafes. This document will be used for the clients to ensure all
specifications and requirements and conductive as mentioned by the software
engineer to design the system.
1.2 Document conventions
Main section titles
Font: Times new roman face: bold Size: 14
Sub section titles
Font: Times new roman face: bold Size: 12
Other text explanations
Font: Times new roman face: bold Size:12
1.3 Intended audience and reading suggestions
Clients: The user of the system will get a clear idea of a software and hardware
requirements to be engaged.
Lab technicians: They will be in a position to attain the various features that are
enabled in the software there by including new definitions for a security
Developers: project developers have a advantage of quickly understanding the
methodology enabled and personalizing the product.
Students: The project shows an infinite path in the field of security in the internet
labs. There is a always perspective of development.
The authors would suggest clients to go through the requirement section
thoroughly before installing the software. The lab technicians are expected to have
a certain knowledge in the terms used and hence can go for the security issues

directly. Students and developers can utilize the documentation as a resource in
developing the project to a new product.
1.4 Scope of development project
The modern colleges have a internet facilities that are not secure and based
on costly software for maintaining users. Security system is not that efficient also.
Many firewalls and tracking software are used for security purposes that reduce the
total efficiency of the internet system.CYBER CAFE MANAGEMENT SYSTEM
software will deliver an open source operating system with inbuilt features for
accessing secure internet. The software also has a accounting and monitering
module to trace and keep track of various internet activities. The targeted users are
internet labs in colleges and internet cafes.
1.5 Definitions, Acronyms and Abbreviations
1.
2.
3.
4.
5.
6.
7.
8.
9.
SRS: Software Requirement Specification

CYBER CAFE MANAGEMENT SYSTEM
Client /user: Internet user at the internet access point
Server: A system that runs in linux always monitoring the actions.
RAM : Random access memory.
SQL: Structured query language
HTTP: Hyper text transfer protocol
UserID: Unique username issued to each user to login
Password: Unique word given to each user as a secret code
2. Overall Descriptions
2.1 Product perspective
The client will be given internet access only by the knowledge of the
server. When a client is accessing internet the server will be tracking the user name
and account details of the user logged in.
There is option also for the user to view the account details of the user.
2.2 Product function
The CYBER CAFE MANAGEMENT SYSTEM client should running on

the client system so as to track the account details of the user.the server will only
respond to those systems where the client is running.

2.3 User classes and characteristics
General users: they will be position to permit access to the users in the internet
and acknowledge their account status.
Administrators: they are the core users able to add the new users to the system
and permit them to access the internet resources. they can also view in real time
what a user performing right now. they can also get the overall report of the user
sessions.
Employees: They login at the client level and this is to get access to the internet at
the client level. They can also view their account status in the client sysyem.
2.4 Operating system
Particulars
Operating system
Processor
Hard disk
RAM
Client system
Windows 2000
prof/Linux
Pentium 4,1.2GHz
40GB
256MB
Server system
Linux
Pentium 4,2GHz
100GB
512MB
2.5 Design and implementation constraints

Each user must keep their password as confidential. More over the user must
have individual ID for creating a login in the CYBER CAFE MANAGEMENT
SYSTEM.
Only Administrator can control user addition and deletion in the CYBER
CAFE MANAGEMENT SYSTEM system. Also this group could only create
reports.
2.6 User documentation
The product is under development stage and requires a complete
implemented prototype to explain the user documentation.once the prototype is
designed and implemented online manuals can be provided.

2.7 Assumptions and dependencies
Initially only two locations are connected to the CYBER CAFE
MANAGEMENT SYSTEM
Each location is always connected whether an operator is logged
On at the remote location or not
Each user must have a user ID and password
There is only one administrator
Server must always run under Linux system
Internet connection is must.
Proper browsers must be installed.
Text readers should be installed to view the help files.
2.8 Overview of data requirements
Inputs: user must give his ID and password to access the internet.
Request from the user to view his account details
Outputs: user account details from the server
Details of various logins
2.9 General constraints, assumptions, dependencies, guidelines
---NOT APPLICABLE--2.10 User view of the product
The user screens that the user would finally be seeing could only be
displayed at end of the whole projects. Once the project is implemented the
samples of the used and the dramatic sceneries can be depicted.
10
3. System Features
3.1 Authentication
3.1.1 Descriptions and priority
The system offers access to internet at client level and access to server
resources at server level only by validating the user with the unique username and
password.
3.1.2 Stimulus/response sequences
The stimulus/response for the different classes of users are:
1. Users: login
2. Administrator: Adding new accounts, giving account status,
getting & sending reports.
3.1.3 Functional requirements
All system should have the client for program running. The server
Should identify individual systems by their names.
R1 Registration
Description: This function registers the newly arrived customer. The user provides
all the personal details like contact, email, id, address etc. to the system. It stores
details in database & generates error message if error is already registered.
R 1.1: Select new registration option
Input: Select Personal Details option.
Output: User prompted to enter personal details.
R 1.2: Select Id proof option

Input: Select ID Proof option.
Output: User prompted to upload ID proof.
11

Processing: User Id for the customer is generated.
R 1.3: Set password option (on terminal).

Input: Set password option.
Output: User prompted to enter password & successfully registered.
R2 Login
Description: Username & password is provided to the system. If valid, this
function allows user to access the internet otherwise error message is displayed.
Forget password facility is also provided for the user.
R 2.1: Enter username and password
Input: Enter username and password option.
Output: User prompted to enter username and password.
Processing: The user logins successfully if username and password are valid
otherwise error message is displayed.
R 2.1: Select forget password option

Input: Select forget password option
Output: User prompted to answer security questions.
Processing: If security answers are correct than user is allowed reset
password otherwise error message is displayed.
12

R3 Employee Management & Access Control
Description: It provides unique logins to every Employee working in a cafe. It
avoids unauthorized access of the application by providing Unique Employee
logins. Admin can add/delete employee records as well as grant various
authorities.
R 3.1: Add employee details
Input: Select add employee option
Output: User prompted enter employee details.
R 3.2: Modify employee details

Input: Select edit/delete employee option
Output: User prompted modify employee details.
R 3.3: Grant/Revoke authorities

Input: Select Grant/Revoke authorities option
Output: User prompted to provide authorities.
R 3.3.1: Type of report
Input: Select Type of report generation option
Output: Different types of report selected to authorize employee.
R 3.3.2:Customer record modification.
Input: Select Customer record modify/delete option
Output: Option selected.
Processing: On selecting the option, the employee can modify/delete
customers record otherwise he cannot.
13

R4 Product Sales Management
Description: Products and Services sold in your cafe can be defined in the
system. Every purchase is accounted in the system against an invoice. Cafe
Employee cannot change the Sale Price for their profits.
R 4.1: Add Product details

Input: Select add product details option
Output: User prompted enter product details.
R 4.2: Stock add/modify

Input: Select edit/delete product details option
Output: Modify the quantity, name or other details of the product.
Processing: The changes are updated in the database.
R5 Website Blocking
Description: Website blocking feature enables you to prevent Users from
surfing unwanted websites in your Cafe. These websites typically have adult or
objectionable content or are banned under government rules. Using this feature
you can block a complete website and avoid potential legal problems. It also
helps maintain a clean environment in your Cafe, in which all types of Users are
comfortable surfing.
R 5.1: Website blocking

Input: Select which website to block.
Output: Website blocked.
14

R6 Website Tracking
Description: It keeps a track of websites browsed by the Cafe Users if the
Website Tracking feature is enabled. It is used to keep a check on the websites
accessed by Cafe Users. The tracked websites are categorized by Date,
Terminal, and User and stored as plain text file on the server. You can check
these sites and block unwanted sites using the Website blocking feature.
R 6.1: Website tracking

Input: Select which website to track.
Output: Website tacking enabled.
R 6.2: Browse to save folder

Input: Select Browse to save folder option.
Output: Path specified.
R 6.3: Browse to save folder

Input: Select Browse to save folder option.
Output: Path specified.
R7 Membership package
Description: Membership Packages provide an easy solution to charge regular
Cafe Users, who like to pay in advance or buy bulk surfing time. These
packages can be created in advance and be sold to regular Users. It enables you
to reward your regular Users with a discounted price.
15

R 7.1: Membership package
Input: Select membership package & customer.
Output: User prompted to select the customer and specified package.
R8 Bandwidth Monitor
Description: It gives you the option to set download limits for each User
Session. You can set an alert to inform Cafe Users, whenever the download
limit is exceeded. You can Monitor Bandwidth consumed in your cafe. You
can block websites that download more data, ensuring fair share of bandwidth
consumption.
R 8.1: Enable Bandwidth monitor

Input: Select Enable Bandwidth monitor option.
Output: Bandwidth enabled.
Processing: It monitors the amount of data being downloaded by each Cafe
User. It displays the total data downloaded on the Caf-Server.
R 8.2: Total Download Limit

Input: Set Total download limit option.
Output: Mb set.
R9 Accounting System
Description: This function provides an easy way to manage your daily cash
transactions. It maintains an invoice for each cash transaction. This data is
reflected in extensive Financial Reports.
16

R 9.1: Payment details
Input: Select Payment details option
Output: Payment done & generates payment receipt.
Processing: Calculates the payment charges as if total net usage, downloads,
no. pages printed, pages scanned etc. and generates receipt accordingly.
R 9.2: Amount Credit/Debit

Input: User prompted to enter amount for credit/debit.
Output: Amount Credited/Debited.
Processing: The credited/debited amount is displayed to the user during next
session.
R10 Reports
Description: It provides a useful set of reports which will help a cafe to analyze
and optimize their cafe business. Reports provide information on Financial
Accounts, User Activity, Products & Services, Printers & Terminal usage.
R 10.1: Select type of report

Input: Select Type of report option.
Output: Generates the selected report.
17
4. External interface requirements

4.1 User interface
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.
New registrations: 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 or she can access internet.
User Account: this enables the user to view the account status
Of their account.
4.2 Hardware interfaces
The server is directly connected to the client systems.also the client has to
access to the database for accessing the account details and storing the login time.
The client access to the database in the server is only read only.
4.3 Software interfaces
CYBER CAFE MANAGEMENT SYSTEM is a multi-user, multi-tasking
environment. It environment.
It enables the user to interact with the server and attain access to the internet and
also leaves a record in the inbuilt database. It uses java servlets as the front end
programming tool and SQL as the backend application tool.
4.4 Communication interfaces
The CYBER CAFE MANAGEMENT SYSTEM uses java Servlets and
hence require HTTP for transmission of data. More over this allows easy
interaction between the various clients and the server.
18
5. Other non-Functional Requirements

5.1 Performance Requirements
The important aspects of CYBER CAFE MANAGEMENT SYSTEM
software is time constrain. CYBER CAFE MANAGEMENT SYSTEM software
system is real time and hence should be performed in minimum requirements.
The accountability is a vital feature and this could only be assured if the
system is working in full capability. So uninterrupted power supply is needed.
5.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.
5.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.
5.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.
5.5 Business Rules
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.
5.6 Special Requirements
5.6.1 Backup and Recovery
19

Keeps backups of all data files in a separate directory/drive.
Frequently auto-save information, in the case of a lost network
connection, the browser or the system crashing, etc.
5.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.
5.6.3 Data retention
Maintaining a log file for each user logging ina nad also maintaining
the account details of the users who have finished the account could be
obtained from cyber caf reports.
5.6.4 User training
Clients must be trained to operate the cyber caf software in creating
new accounts and performing report operations.
5.6.5 Installation
A Conductive environment for the efficient running of the cyber caf
recommended. The server should be handled with great care and all
unauthorized access should be restricted.
20
6. PRELIMINARY SCHEDULE:
The system has to be implemented within 6 months.
7. OPERATIONAL SCENARIO:
This system consist of student database, staff database, servers, various complain
databases etc.
The major actors in this system are:General users: They will be position to permit access to the users in the internet
and acknowledge their account status.
Administrators: They are the core users able to add the new users to the system
and permit them to access the internet resources. They can also view in real time
what a user performing right now. They can also get the overall report of the user
sessions.
Employees: They login at the client level and this is to get access to the internet at
the client level. They can also view their account status in the client system.
Scenario:
Initial Situation:
A registered customer logins using User-ID and password and surfs.
Normal flow of events:
In Cyber Cafe Management System, initially the customer visits the caf. If he
is not registeres, then he must provide login credentials along with proof and
registered himself. He will then create a password on specified terminal using
ID provided by employee.
21

On other hand if user is registered, then he will login into his account and
access the net or takes an printout of necessary document.
What can go wrong:
If the registered user forgets the password & on pressing Forget Password
option he is provided with security questions, but still if user is enable to answer
these questions.
If the newly arrived customer forgets to bring th Id proof, he will not be
allowed to access the net.
Printing issue while print command senr by user due to some technical problem
The customer faces difficulty in accessing the internet & the available
employess will help him.
Other activities:
Caf owner sales different computer accessories useful for customer.
System state on completion:
The customer [ays the bill for surfing, priting or purchasing any product.
22

Use-Case diagram
Registration
Provide details ID
proofs
Registration
Customer
Employee
Login
Assign Terminal &

gives userid
Surfing and printing
User play games

surfs web
Web Blocking
Customer
Admin
Net usage
Employee
Printing and
Scanning
23
Payment
Net Usage
Website Accessed
Employee
Customer
Payment
Calcullate bill and

gives time slot warn
Report
Payment history
Collection report
Admin
Employee
Terminal usage
Web Tracking
Printing report
24
Cyber caf management system

Registration
login
customer
provideed details
& Id proofs
Admin
Assign terminal
and gives userid
surfing and
printing
website blocking
payment
Report
25
employee
8. Diagrams
8.1 Class Diagram:
26

8.2 Sequence Diagram:
27
9. Testing
9.1 About Testing:

Testing is a process that requires more efforts than any other software
engineering activity. Testing is a set of activities that can be planned in advance
and conducted systematically.
This may lead to have many undetected errors in the system being developed.
Hence performing testing by adopting systematic strategies in very much essential
in during development of software.
Various testing strategies for conventional software are :1. Unit Testing :In this type of testing techniques are applied to detect the errors from each
software component individually .
2. Integration testing :It focuses on issues associated with the verification and program construction
as components begin interacting with one another.
3. Validation testing :It provides assurance that the software validation criteria (established during
requirement analysis) meets all functional , behavioral and performance
requirements .
4. System testing :In system testing all system elements forming the system is tested as a whole.
28

9.2 White Box Testing
In this testing the internals of software are tested to make sure that they operate
according to specifications and designs.
The test case for Online Academic System is as following:-
Test
case
Id
Test case
Name
Login
Test case
Description
Test steps
In this case
user will try
to login in the
system in
order to use
the use the
system
functionality.
Website
In this test
Blocking
case ,Admin
and tracking Can block or
track the
website.
In this step,
the user will
enter user
name and
password and
then click on
the login
button.
In this step ,
the user can
not block
websites.
Bandwidth
Monitor
Accounting
29
It gives you
the option to
set download
limits for
terminals.
Maintains an
invoice for
each cash
transaction.
Test
case
Test
Defect
status case
severity
(pass/ priority
fail)
Pass
1
Pass
User cannot
use internet
exceeding
usage limit.
pass
Valid
payment.
Pass
9.3 Black Box Testing

Its also called as behavioral testing. It focuses on functional requirement of the
system. As per the name suggests in black box testing it is tested whether the input
is accepted properly and output is correctly produced.
Equivalence Partitioning: In this technique, if an input condition requires a specific a range, one valid
and two invalid equivalence classes are defined.
If an input condition requires a specific value, one valid and two invalid
equivalence classes are defined.
If an input condition specifies member of a set, one valid and two invalid
equivalence classes are defined.
If an input condition is a Boolean, one valid and two invalid equivalence
classes are defined.
Equivalence Partitioning for Cyber Cafe Management System is :Log in Module:
Input conditions:- Valid username, valid password
Test values:- 1.(Bhoomika, bhumu123)
2.(nnn,nn)
Website Blocking/Tracking Module:

Input conditions :- (Website name, No of days )
Test values :- 1.(www.facebook.com,15)
2.(xyz.com,-3)
30
Accounting Module:
Input conditions :- (Invoice No,Customer_Id,Cust_Name,
Items, Quantity)
Test values :- 1.(001,C01,Unnati,Pen-drive,2)
2.(xyz,-1,-456,1,-1)
Bandwidth Monitor Module:

Input conditions :- (limit)
Test values :- 1.(1GB)
2.(-1000MB)
Boundary Value Analysis (BVA) : Boundary value analysis is done to check boundary conditions.
Using boundary value analysis , instead of focusing on input
conditions only, the test cases from the output domains are also
derived.
It is a complement to the equivalence partitioning.
31
10 . Preliminary Schedule
The Application should be completed within a specific time period depending on

each module.
The deadline of the particular modules is given as per the below given table :Modules
Requirement gathering
Designing & planning
Developing
Testing
Maintenance
32
Deadline
12-20 days
3week
2 months
3 week
-
11. Preliminary Budget
The total funding of the software is around 5-6 lakhs.

Task
Employees salary
Hardware
Software
Licensing
Maintenance
33
Expenses(Rs.)
85,000
2,00,000
90,000
50,000
1,00,000
12. Cost Estimation
Function Point calculation

Function points (FP) measure size in terms of the amount of functionality in a
system. Function points are computed by first calculating an unadjusted function
point count (UFC). Counts are made for the following categories
Number of user inputs

Number of user outputs
Number of user inquiries
Number of files
Number of external interfaces
Once this data has been collected, a complexity rating is associated with each
count according to Table
TABLE 1: Function point complexity weights.
Measurement parameter
Number of user inputs

Number of user outputs
Number of user inquiries
Number of files
Number of external
interfaces
Count
Weighting factor
10
8
5
20
15
Simple Averag Compl

e
ex
3
6
4
5
7
4
3
4
6
7
15
10
5
7
10
40
32
30
200
150
UFP=452
34

Table 2. Components of the technical complexity factor.
F1
F2
F3
F4
F5
F6
F7
F8
F9
F10
F11
F12
F13
F14
Total
Component
Reliable back-up and
recovery
Data communication
Distributed functions
Performance
Heavily used
configuration
Online data entry
Operational ease
Online update
Complex interface
Complex processing
Reusability
Installation ease
Multiple sites
Facilitate change
Function Point = UFP * [ 0.65 + 0.01 * ( Fi ) ]

= 452* [ 0.65 + 0.01 * 40 ]
= 452* [ 0.65 + 0.40 ]
= 452 * 1.05
FP=474.6
A review of historical data indicates
1. Average Productivity is 10 FP/Person Month.
2. Average labour cost id 20000
35
Rate
5
3
3
3
2
5
4
3
1
3
1
3
3
1
40

Calculation:
1. Cost per function point
= (20000 / 10) = 2000
2. Total Estimated project cost = (474 * 909) = 430866

3. Total Estimated Effort
36
= ( 474 / 10) = 47.4 Person/Month
13. REFERENCES:
Websites:
http://www.linuxlinks.com
http://www.tldp.org
http://www.reallylinux.com
Appendix A: Glossary
Terms
Definitions
User
Someone who interacts with the System.
Admin/administrator
System administrator who is given specific permission

for managing and controlling the system.
Cyber Cafe Management System
HMS
Rector
People appointed by the Hostel Manager for

monitoring and checking of the work done by the user.
Stakeholder
Any person who has interaction with the system who

is not a developer.
37

Cyber Cafe Management

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Cyber Cafe Management

Încărcat de

Drepturi de autor:

Formate disponibile

Cyber Caf Management System 2016

Software Requirement Specification

Cyber Caf Management System 2016

Cyber Caf Management System 2016

Cyber Caf Management System 2016

External Interface Requirements......18

Non Functional Requirements....19

Cyber Caf Management System 2016

Software Quality Attributes20

Cyber Caf Management System 2016

Cyber Caf Management System 2016

SRS: Software Requirement Specification

Cyber Caf Management System 2016

The CYBER CAFE MANAGEMENT SYSTEM client should running on

Cyber Caf Management System 2016

2.5 Design and implementation constraints

Cyber Caf Management System 2016

Cyber Caf Management System 2016

R 1.2: Select Id proof option

Cyber Caf Management System 2016

R 1.3: Set password option (on terminal).

R 2.1: Select forget password option

Cyber Caf Management System 2016

R 3.2: Modify employee details

R 3.3: Grant/Revoke authorities

Cyber Caf Management System 2016

R 4.1: Add Product details

R 4.2: Stock add/modify

R 5.1: Website blocking

Cyber Caf Management System 2016

R 6.1: Website tracking

R 6.2: Browse to save folder

R 6.3: Browse to save folder

Cyber Caf Management System 2016

R 8.1: Enable Bandwidth monitor

R 8.2: Total Download Limit

Cyber Caf Management System 2016

R 9.2: Amount Credit/Debit

R 10.1: Select type of report

Cyber Caf Management System 2016

4. External interface requirements

Cyber Caf Management System 2016

5. Other non-Functional Requirements

Cyber Caf Management System 2016

Cyber Caf Management System 2016

Cyber Caf Management System 2016

Cyber Caf Management System 2016

Assign Terminal &

Surfing and printing

User play games

Cyber Caf Management System 2016

Calcullate bill and

Cyber Caf Management System 2016

Cyber caf management system

Cyber Caf Management System 2016

Cyber Caf Management System 2016

Cyber Caf Management System 2016

9.1 About Testing:

Cyber Caf Management System 2016

Cyber Caf Management System 2016

9.3 Black Box Testing

Website Blocking/Tracking Module:

Cyber Caf Management System 2016

Bandwidth Monitor Module: