TITLE OF THE PROJECT

CYBER CAFE MANAGEMENT SYSTEM OF KIRAN CYBER LINK, NAGAON

INTRODUCTION The cyber caf management is a system in which we collect & save all the records of the customers, like..their internet surfing duration, how many pages they have print & any other print related information if they print & when required we take any other information about them. The major objective of this project is to handle the entire caf by it keeping its day to day records for both internet surfing & printing

OBJECTIVES OF PROPOSED SYSTEM

The objectives of the proposed system are: 1> Store data with minimal redundancy. 2> Search record in minimal time. 3> Maintain integrity of the data. 4> No paper work is required. 5> Data security & reliability. 6> Effective, user friendly & computerized management of the cyber caf.

SOFTWARE AND HARDWARE SPECIFICATION

SOFTWARE SPECIFICATION:

OPERATING SYSTEM: WINDOWS XP (SP-2) FRONT-END: VB.NET 2005 BACK-END: MySQL SERVER WOR PROCESSOR: Microsoft Office 2007

HARDWARE SPECIFICATION:

PROCESSOR: Intel Pentium dual core RAM: 1GB RAM HARD DISK: 160 GB hard disk or above OPTICAL DRIVE: DVD-RW (52X) MONITOR: NORMAL KEYBOARD: NORMAL PRINTER: INKJET REMOVEABLE DRIVE: Pen Drive

MINIMUM SOFTWARE AND HARDWARE REQUIREMENS

SOFTWARE SPECIFICATION: OPERATING SYSTEM: ANY WINDOWS BASED OPERATING SYSTEM .NET Framework 2.0 or above BACK-END: MySQL SERVER

HARDWARE SPECIFICATION: PROCESSOR: Pentium IV processor. RAM: 256 MB RAM or above. HARD DISK: 40 GB hard disk or above. MONITOR: NORMAL, or above KEYBOARD: NORMAL, or above MOUSE: NORMAL, or above

REQUIREMENT ANALYSIS

Introduction
Requirement Analysis is the first step in the system development life cycle. This requirement emphasizes on the identification of need. This is a user request to change, improve or automated existing system. During the preparation of the initial information has to receive from users, managers and system developers. This helps in defining what the new system should do. The objective is to decide whether the request is valid and feasible. Asking (Interview) This strategy obtains information from the users by simply asking them about the requirements. It assumes a stable system where users are well informed and can overcome biases in defining their problem. There are three key asking methods: a) Questioning. b) Brainstorming. c) Group Consensus. Module Description: A module is a logically separatable part of a program. It is a program unit that is discrete & identifiable. Modularity is a desirable property of a system. The system I am developing is considered to be modular as it consists of discrete components & each components support a well-defined abstraction. If a change to one component has minimal impact on other components.

Description of each Module: Internet: The internet module have the information of Internet surfing & cost of internet browsing. Printing: The printing module have the information of printing & the cost of printing. Report: The report module have all the information about internet surfing & printing for a particular day or month.

CONTEXT DIAGRAM
Context diagrams are related to Data Flow Diagram, and show the interactions between a system and other actors with which the system is designed to interface. Context diagrams can be helpful in understanding the context which the system will be part of.

CUSTOMER

MAKE PAYMENT ENTER FOR SURF / PRINT

ENTER PRICE LIST

CYBER CAF MANAGEMENT SYSTEM

GET PAYMENT

ADMINSTRATOR

GET CALCULATED AMOUNT

DATA FLOW DIAGRAM (DEFINITION)

Data Flow Diagram was developed by Larry Constantine for expressing system requirements. 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 modeling as well as information flow modeling. DFD symbols:

REPRESENT ENTITY SET

REPRESENT PROCESS

REPRESENT THE DATA FLOW

REPRESENT OF DATA STORAGE

1ST LEVEL DFD

ENTER FOR PRICE CHART PROCES1.0
Store/Update Price Details

ADMINSTRATOR

Enter Price List

Price Details

CUSTOMER

Enter For Surfing

INTERNET SURFING PROCESS 2.0

Store/Update Customer Surfing Details

Customer internet Surfing details

Enter for printing

PRINTOUT PROCESS 3.0

Store/Update Customer printing details

Customer printing details

Read customer printing details Get calculated amount Make payment Get Payment amount

PRINTOUT PROCESS 4.0

Read customer internet surfing details Read price list

Receipt

2nd LEVEL DFD OF INTERNET SURFING PROCESS

Enter Price List

PRICE CHART PROCESS 2.1

Insert

Price Details
Price List Info

Get Price details Enter Info

Administrator
Get Info

INTERNET SURFING PROCESS 2.2

Update

Customer Internet surfing details

Customer

Enter for internet surfing

2nd LEVEL DFD OF PRINTOUT PROCESS

Enter price list

PRICE CHART PROCESS 3.1

Get price details

Price list info

Price Details

Enter Info

Administrator
Get info

PRINTOUT PROCESS 3.2

Insert Customer Printing Details

Price list info

Customer

Enter for printing

ENTITY RELATIONSHIP DIAGRAM (DEFINITION) Data objects are connected to each other in various ways. Object relationship is the cornerstone of any data model. This is represented graphically using ER Diagram. It was proposed by Peter Chen for design of relational database system. A set of primary components are identified for the ER diagram, Data objects, attributes, relationships and various type indicators. The primary purpose of ER diagram is to represent objects and their relationships. The major components of an ER diagram are:

REPRESENT AN ENTITY

REPRESENT AN ATTRIBUTE

REPRESENT KEY ATTRIBUTE

. .

REPRESENT DERIVED ATTRIBUTE

REPRESENT RELATIONSHIP

REPRESENT CARDINALITY

LINKS ATTRIBUTE WITH ENTITY AND ENTITY WITH RELATIONSHIP

MULTI- VALUE ATTRIBUTE

ER DIAGRAM
Tel No

Customer ID

CUSTOMER

C name

E Time
S Time

Makes Internet Surfing

Date

Comes For

Customer_ ID

Rate

Type

Contact Amount

No Of Pages

Date

Printing
Date

Payment

Cat_ID P_Size Customer _ID Price Details Customer ID

Time

Receipt No Cat_ID

Rate

P_Size P_Type

A data dictionary has many advantages. The most obvious is documentation; it is a valuable reference in any organization. Another advantage is improving analyst user communication by establishing consistent definition of various elements, teams and procedures. Also data dictionary is an important step in building database. Data Dictionary of CYBER CAF MANAGEMENT SYSTEM:

SL No 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23

Field Name

Description

Data type

Size Key

Source

Database Structure Chart:

Database structure chart 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 STRUCTURE

TABLE NAME= CUSTOMER INTERNET SURFING DETAILS

TABLE NAME=

FIELD NAME

KEY

DATATYPE

SIZE

DESCRIPTION

TABLE NAME= CUSTOMER PRINTING DETAILS

TABLE NAME= PAYMENT FIELD NAME RECEIPT NO AMOUNT DATE TIME CUSTOMER ID KEY PRIMARY PRIMARY PRIMARY PRIMARY FOREIGN KEY KEY KEY KEY KEY DATATYPE INT MONEY DATE TIME DATE TIME INT SIZE 12 20 18 18 12 DESCRIPTION RECEIPT NO AMOUNT DATE TIME CUSTOMER ID

System Implementation: A crucial phase in the system development life cycle is the successful implementation of the system design. Implementation simply means the system design into operation. This involves installing of hardware, terminal and also training the operation staff. There are three main types of implementation: Implementation of a computer system to replace the manual system. Implementation of a new computer system to replace an existing one. Implementation of a modified application to replace an existing one. After a through testing of the different aspects of the system, the system is ready for implementation. The system is to run in a parallel with existing manual system for days until the concerned becomes fully confident of the new system.

Testing Procedure
The system should always be tested thoroughly before implementation of it as regard to the individual programs, the system as a whole, user acceptance etc. This is because implementing a new system is a major job that requires a lot of manhour and other resources. So an error not detected before implementation may cost a lot. Effectively testing early in the process translates directly into long term cost saving from a reduced number of errors. The purpose of the system testing is to consider all the likely variations to which it will be subjected and then push the system to its limits. It is a tedious but necessary step in system development.

The different types of testing techniques that are used during the development of the system under consideration are as follows:

Module Testing:
Module testing must be carried out during the programming stage itself. Here individual program testing must be carried out during the coding stage itself and the required changes are to be made on the module to ensure the smooth and satisfactory execution of the module in the form of an individual program and the generation of the output in the required form.

String Testing:
Programs are invariably related to one another and interact in a total system. Each program is tested to see whether it conforms to related programs in the system. Each portion of the system is tested against the entire module with both test and live data before the entire system is ready to tested.

Unit Testing:
Unit testing is changes made in an existing or a new program. It is necessary for the verification of the code that would be produce during the code phase. It is mainly to test the internal logic of the module.

Integration Testing:
In integration testing, many unit tested modules are combined into sub systems, which would be then tested. The objective if this testing is to see if the modules can be integrated properly. That is, the prime emphasis is on testing the interfaces between the modules.

System Testing:
The purpose of system testing is to identify and correct errors in the system. As important as this phase is, it is one that is frequently compromised. Typically the project is behind schedule or the user is easier to go directly to conversion. In

system testing performance and acceptance standards are developed. Substandard performance or service interruptions that result in system failure are checked during the test.

Output Testing:
No system could be useful if it does not produce required format. It includes asking the user about the required format of the output that would be displayed on the screen or in a printed form.

User Acceptance Testing:

An acceptance test has the objective selling the user on the validity and reliability of the system. It verifies that the systems procedures operate to system specifications and that the integrity of the vital data is maintained, performance of an acceptance test is actually the users show. User motivation and knowledge are critical for the successful performance of the system. Then a comprehensive test report is prepared that indicates the systems tolerance, performance range, error rate and accuracy.

Future Application & Conclusion:

Future application: It is the fact that improvement & modification can be made with little effort to any system in order to get better services. Now formulas can be incorporated as & when necessary to existing system. It is true that present system whenever implemented, all the information will be available to the users. I hope that the initiation taken in developing the software, will help for future development of the system. Conclusion: No software can be called perfect in the fast moving hitech world. The Cyber Caf Management System seems to be very useful but may be outdated near future . However it is a simple

software, would be adequate for present time for functioning of the firm in proper way. After doing the system analysis & drawing ER diagram, DFD now we can easily develop the caf Management System, which will manage the whole caf efficiently & fast & also Free manual errors.

STRUCTURE CHART

CYBER CAF MANAGEMENT SYSTEM

SURFING

CUSTOMER

PRINTING

PAYMENT