Online Mobile Recharge Documentation

A MiniProject Report

On

e-Library Management

Dissertation submitted in partial fulfillment of the requirements

For the award of degree of

BACHELOR OF TECHNOLOGY

In

COMPUTER SCIENCE & ENGINEERING

By

K.Sneha Silvia (05A21A0515)

D.Harish Phanendra (05A21A0558) P.Chandana (05A21A0526)

M.G.K.Alekya (05A21A0550) P.Kamlesh Kumar(05A21A0557)

Under the esteemed guidance of

Mr. P.RAVI KIRAN, M.Tech

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

SWARNANDHRA COLLEGE OF ENGINEERING & TECHNOLOGY

(Affiliated to JNTU, Hyderabad)

NARSAPUR – 534 280

2008

SWARNANDHRA COLLEGEOF ENGINEERING & TECHNOLOGY

SEETHARAMAPURAM, NARSAPUR – 534 280 W.G.DT (A.P)(Affiliated in JNTU, Hyderabad)

Department of

COMPUTER SCIENCE AND ENGINEERING

Certificate

This is to certify that miniproject entitled “Online Mobile Recharge” is bonafide work of K.SnehaSilvia (05A21A0515),P.Chandana(05A21A0526),D.HarishPhanendra(05A21A0558),P.Kamlesh(05A21A0557),M.G.K.Alekya (05A21A0550) of IV B.Tech submitted in partial fulfillment of the requirement for the award of Bachelor of Technology degree from J.N.T.University,Hyderabad in COMPUTER SCIENCE AND ENGINEERING during the academic year 2007-2008.

Internal Guide Headof theDepartment P.Ravi Kiran, M.Tech. Dr. G.V.S.Raju, Assoc. Professor Professor Dept. of C.S.E. Dept. of C.S.E

ACKNOWLEDGEMENT

I extend my heartfelt gratitude and my sincere thanks to Mr.S. Ramesh Babu Garu, Secretary & Correspondent of our college for making necessary arrangement for doing the project.

I wish to express my gratitude to Dr.M.Muralidhar Rao garu, principal, for giving us permission to carry out the project.

I express my deep sense of gratitude and sincere thanks to Dr.G.V.S.Raju Garu, H.O.D, CSE Department for his valuable suggestions and guidances in regarding the software analysis, design and also for his continuous effort in the successful completion of the project.

My deep gratitude to my internal guide and also my project coordinator Mr. P.Ravi Kiran.I thanks her for dedication, guidance, council and keen interest at every stage of the project.

Last but not least, I am debited to all people who have contributed in some way or the other in the completion of this project work.

K.Sneha Silvia

P.Chandana M.G.K.Alekya

P.Kamlesh Kumar

D.Harish Phanendra

DECLARATION

I here by declare that the entire project work embodied in this dissertation during the period of April 2008 entitled “ONLINE MOBILE RECHARGE” submitted by me in partial

fulfillment of the requirements for the award of the degree of Bachelor of Technology, in the department of Computer Science and Engineering, Jawaharlal Nehru Technological University, is a bonafide record of the project work carried out by me independently. As per my knowledge, no part of this work has been submitted previously by me at any other university for the award of any degree or diploma.

K.Sneha Silvia

P.Chandana

M.G.K.Alekya

P.Kamlesh Kumar

D.Harish Phanendra

INDEX

1. Abstract

2. Introduction

3. Problem Description

4. Technology Overview

A) Introduction to .net Frame Work

B) Introduction to Active Server Pages.net

C) Introduction to SQL SERVER

5. System Specifications

6. System Design

7. System Testing and Implementation

8. Screens

9. Conclusion

10. Bibliography

ONLINE MOBILE RECHARGE

Abstract:

The Project “ONLINE MOBILE

RECHARGE” gives us the information about all the mobile service

providers. This application provides us the complete information in

a service provider wise. The major advantage of this proposed

system is to have the recharging facility of any service provider

under one roof. It contains 3 major modules that are Admin, User

and Visitor. Admin module contains all the details of the users like

when it was created and what all the transactions done by the user,

detailed information of the user can be accessed or can be

manipulated by the administrator. User module consists of how to

create the user and how to access the service provider and any time

he can have the complete information of his account, when he had

updated his balance and how the balance has been utilized that can

be viewed in the form of reports. Visitor is the module where he can

visit the proposed system and can have the complete information of

all the service providers.

Team

Members

Internal Guide K.Sneha Silvia

(05A21A0515)

P.RaviKiran M.Tech

M.G.K.Alekya(05A21A0550)

P.Kamlesh

Kumar(05A21A0557)

P.Chandana(05A21A0526)

D.Harish

Phanendra(05A21A0558)

INTRODUCTION TO PROJECT

There are many service providers for the pre-paid mobile users,

which can be recharged frequently. This proposed application helps

the mobile user to recharge his mobile of any service provider under

one roof.

The Project ‘ONLINE MOBILE RECHARGE’ gives us the

information about all the mobile service providers. This application

provides us the complete information in a service provider wise.

Suppose, any airtel customer wants to have the information of all the

schemes and services of airtel he/she can have the information and

according to his convenience he can recharge the mobile from the

same application. The major advantage of this proposed system is

to have the recharging facility of any service provider under one

roof. It is going to contain 3 major modules that are Admin, User

and Visitor. Admin module contains all the details of the users like

when it was created and what all the transactions done by the user,

detailed information of the user can be accessed or can be

manipulated by the administrator. User module consists of how to

create the user and how to access the service providers and any time

he can have the complete information of his account, when he had

updated his balance and how the balance has been utilized that can

be viewed in the form of reports. Visitor is the module where he

can visit the proposed system and can have the complete

information of all the service providers.

INTRODUCTION TO MODULES

There are 4 modules in this project. They are briefed as follows

Service Provider Admin User

o Individualo Shop Keeper

Visitor

Service Provider:

Service Provider is the one who is nothing but the mobile

service provider like all the companies who are giving the mobile

connections come under this module. The functionality of this

module is to make the mobile recharging of their company basing

on the availability of balance in the admin account. Request comes

from the user and it is going to be verified at the admin for the

availability of balance and then the request is forwarded to the

service provided to make the mobile recharge. After receiving the

request service provider is going to check the available balance and

then they go for processing the request.

Admin:

Admin is the one who monitors all users and user transactions.

Admin also monitors all the Service Providers. Admin has to

maintain the balances with Service Providers, monitors all the user

accounts, and amounts paid by the user and amounts paid to Service

Providers. When the request given by the user admin checks the

available balance in the user account then request is forwarded to

the Service Provider from there user request gets processed. Admin

haves the complete information related to user and all the

information related to the schemes and other information of

different recharge coupons provided by the Service Providers. All

the data is maintained at the Admin level. Admin is having the

rights to restrict any user.

User

There are 2 categories in the user Module

Individual

Shopkeeper

Individual

Any person who wants to utilize the services of

ONLINE MOBILE RECHARGE at any time from any

where they should get registered in this application. After

getting registered user can recharge the mobile at any time and

from any where. For this user has to furnish the required

information and get registered. Individual user is able to make

recharge to his particular mobile only. He can have the

complete information of all the service providers recharging

coupons.

Shop Keeper

The retailers now who are providing the recharge to the

end users become the user as Shop Keeper. Shop Keeper can

be registered as a user and make the recharges to any number

of mobiles of any kind of Service Provider. This particular

user can have the margin of some amount in this recharge

process.

Visitor:

Visitor is the one who visits the ONLINE MOBILE

RECHARGE application and have the complete information

related to the Service Providers and can make the mobile recharge

by entering the bank details or by giving the credit card details.

Problem Description

The following are the drawbacks of the existing System.

Time Delay

User has to access or utilize all services offered by all the service

providers. Since all the services are offered by different

organizations it takes lot of time to make recharges of each and

every organization.

Redundancy

There are different recharging coupons available for each and every

service provider but the problem is shop keeper has to maintain all

the things and has to be given to the customer what they are looking

for. Shop Keeper should have the knowledge of all the coupons

available. It is very difficult for any one to maintain these many

numbers of coupons.

Accuracy

Since there is much service providers and so many recharge coupons

of each and every service providers there is a problem for the shop

keeper to maintain all the coupons and the problem with the

individual user that they have to make the manual recharging facility

and it ultimately becomes a headache to all kind of users.

TECHNOLOGY OVERVIEW

Introduction to Microsoft.NET Framework:

The .NET Framework is a new computing platform that simplifies

application development in the highly distributed environment of the

Internet. The .NET Framework is designed to fulfill the following

objectives:

To provide a consistent object-oriented programming environment whether object code is stored and executed locally, executed locally but Internet-distributed, or executed remotely.

To provide a code-execution environment that minimizes software deployment and versioning conflicts.

To provide a code-execution environment that guarantees safe execution of code, including code created by an unknown or semi-trusted third party.

To provide a code-execution environment that eliminates the performance problems of scripted or interpreted environments.

To make the developer experience consistent across widely varying types of applications, such as Windows-based applications and Web-based applications.

To build all communication on industry standards to ensure that code based on the .NET Framework can integrate with any other code.

The .NET Framework has two main components: the common

language runtime and the .NET Framework class library. The

common language runtime is the foundation of the .NET

Framework. You can think of the runtime as an agent that manages

code at execution time, providing core services such as memory

management, thread management, and remoting, while also

enforcing strict type safety and other forms of code accuracy that

ensure security and robustness. In fact, the concept of code

management is a fundamental principle of the runtime. Code that

targets the runtime is known as managed code, while code that does

not target the runtime is known as unmanaged code. The class

library, the other main component of the .NET Framework, is a

comprehensive, object-oriented collection of reusable types that you

can use to develop applications ranging from traditional command-

line or graphical user interface (GUI) applications to applications

based on the latest innovations provided by ASP.NET, such as Web

Forms and XML Web services.

Features of the Common Language Runtime

The common language runtime manages memory, thread execution,

code execution, code safety verification, compilation, and other

system services. These features are intrinsic to the managed code

that runs on the common language runtime.

With regards to security, managed components are awarded varying

degrees of trust, depending on a number of factors that include their

origin (such as the Internet, enterprise network, or local computer).

This means that a managed component might or might not be able to

perform file-access operations, registry-access operations, or other

sensitive functions, even if it is being used in the same active

application.

The runtime enforces code access security. For example, users can

trust that an executable embedded in a Web page can play an

animation on screen or sing a song, but cannot access their personal

data, file system, or network. The security features of the runtime

thus enable legitimate Internet-deployed software to be

exceptionally featuring rich.

The runtime also enforces code robustness by implementing a strict

type- and code-verification infrastructure called the common type

system (CTS). The CTS ensures that all managed code is self-

describing. The various Microsoft and third-party language

compilers generate managed code that conforms to the CTS. This

means that managed code can consume other managed types and

instances, while strictly enforcing type fidelity and type safety.

. NET Framework Class Library

The .NET Framework class library is a collection of reusable

types that tightly integrate with the common language runtime. The

class library is object oriented, providing types from which your

own managed code can derive functionality. This not only makes

the .NET Framework types easy to use, but also reduces the time

associated with learning new features of the .NET Framework. In

addition, third-party components can integrate seamlessly with

classes in the .NET Framework.

For example, the .NET Framework collection classes implement a

set of interfaces that you can use to develop your own collection

classes. Your collection classes will blend seamlessly with the

classes in the .NET Framework.

As you would expect from an object-oriented class library, the .NET

Framework types enable you to accomplish a range of common

programming tasks, including tasks such as string management, data

collection, database connectivity, and file access. In addition to

these common tasks, the class library includes types that support a

variety of specialized development scenarios. For example, you can

use the .NET Framework to develop the following types of

applications and services:

Console applications.

Scripted or hosted applications.

Windows GUI applications (Windows Forms).

ASP.NET applications.

XML Web services.

Windows services.

For example, the Windows Forms classes are a comprehensive set

of reusable types that vastly simplify Windows GUI development. If

you write an ASP.NET Web Form application, you can use the Web

Forms classes.

Introduction to Active Server Pages (ASP).NET:

ASP.NET is a programming framework built on the common

language runtime that can be used on a server to build powerful

Web applications. ASP.NET offers several important advantages

over previous Web development models:

Enhanced Performance. ASP.NET is compiled common language

runtime code running on the server. Unlike its interpreted

predecessors, ASP.NET can take advantage of early binding, just-in-

time compilation, native optimization, and caching services right out

of the box. This amounts to dramatically better performance before

you ever write a line of code.

World-Class Tool Support. A rich toolbox and designer in the

Visual Studio integrated development environment complement the

ASP.NET framework. WYSIWYG editing, drag-and-drop server

controls, and automatic deployment are just a few of the features

this powerful tool provides.

Power and Flexibility. Because ASP.NET is based on the common

language runtime, the power and flexibility of that entire platform is

available to Web application developers. The .NET Framework

class library, Messaging, and Data Access solutions are all

seamlessly accessible from the Web. ASP.NET is also language-

independent, so you can choose the language that best applies to

your application or partition your application across many

languages. Further, common language runtime interoperability

guarantees that your existing investment in COM-based

development is preserved when migrating to ASP.NET.

Simplicity. ASP.NET makes it easy to perform common tasks, from

simple form submission and client authentication to deployment and

site configuration. For example, the ASP.NET page framework

allows you to build user interfaces that cleanly separate application

logic from presentation code and to handle events in a simple,

Visual Basic - like forms processing model.

Manageability. ASP.NET employs a text-based, hierarchical

configuration system, which simplifies applying settings to your

server environment and Web applications. Because configuration

information is stored as plain text, new settings may be applied

without the aid of local administration tools. This "zero local

administration" philosophy extends to deploying ASP.NET

Framework applications as well. An ASP.NET Framework

application is deployed to a server simply by copying the necessary

files to the server. No server restart is required, even to deploy or

replace running compiled code.

What is ASP.NET Web Forms?

The ASP.NET Web Forms page framework is a scalable common

language runtime-programming model that can be used on the

server to dynamically generate Web pages.

Intended as a logical evolution of ASP (ASP.NET provides syntax

compatibility with existing pages), the ASP.NET Web Forms

framework has been specifically designed to address a number of

key deficiencies in the previous model. In particular, it provides:

The ability to create and use reusable UI controls that can

encapsulate common functionality and thus reduce the amount

of code that a page developer has to write.

The ability for developers to cleanly structure their page logic

in an orderly fashion (not "spaghetti code").

The ability for development tools to provide strong

WYSIWYG design support for pages (existing ASP code

is opaque to tools).

ASP.NET Web Forms pages are text files with an. aspx file name

extension. They can be deployed throughout an IIS virtual root

directory tree. When a browser client requests. aspx resources, the

ASP.NET runtime parses and compiles the target file into a .NET

Framework class. This class can then be used to dynamically

process incoming requests. (Note that the .aspx file is compiled only

the first time it is accessed; the compiled type instance is then reused

across multiple requests).

An ASP.NET page can be created simply by taking an existing

HTML file and changing its file name extension to .aspx (no

modification of code is required). For example, the following

sample demonstrates a simple HTML page that collects a user's

name and category preference and then performs a form postback to

the originating page when a button is clicked:

INTRODUCTION TO SQL SERVER 2005:

DATABASE:

A database management, or DBMS, gives the user access to

their data and helps them transform the data into information. Such

database management systems include dBase, paradox, IMS, and

Sql. These systems allow users to create, update and extract

information from their database.

A database is a structured collection of data. Data refers to the

characteristics of people, things and events. Sql stores each data

item in its own fields. In Sql, the fields relating to a particular

person, thing or event are bundled together to form a single

complete unit of data, called a record (it can also be referred to as

raw or an occurrence). Each record is made up of a number of

fields. No two fields in a record can have the same field name.

During a Sql Database design project, the analysis of your

business needs identifies all the fields or attributes of interest. If

your business needs change over time, you define any additional

fields or change the definition of existing fields.

Sql Tables:

Sql stores records relating to each other in a table. Different

tables are created for the various groups of information. Related

tables are grouped together to form a database.

Primary Key:

Every table in Sql has a field or a combination of fields that

uniquely identifies each record in the table. The Unique identifier is

called the Primary Key, or simply the Key. The primary key

provides the means to distinguish one record from all other in a

table. It allows the user and the database system to identify, locate

and refer to one particular record in the database.

Relational Database:

Sometimes all the information of interest to a business

operation can be stored in one table. Sql makes it very easy to link

the data in multiple tables. Matching an employee to the department

in which they work is one example. This is what makes Sql a

relational database management system, or RDBMS. It stores data

in two or more tables and enables you to define relationships

between the tables and enables you to define relationships between

the tables.

Foreign Key:

When a field is one table matches the primary key of another

field is referred to as a foreign key. A foreign key is a field or a

group of fields in one table whose values match those of the primary

key of another table.

Referential Integrity:

Not only does Sql allow you to link multiple tables, it also

maintains consistency between them. Ensuring that the data among

related tables is correctly matched is referred to as maintaining

referential integrity.

Data Abstraction:

A major purpose of a database system is to provide users with

an abstract view of the data. This system hides certain details of

how the data is stored and maintained. Data abstraction is divided

into three levels.

Physical Level:

This is the lowest level of abstraction at which one describes

how the data are actually stored.

Conceptual Level:

At this level of database abstraction all the attributed and what

data are actually stored is described and entries and relationship

among them.

View level:

This is the highest level of abstraction at which one describes

only part of the database.

FEATURES OF SQL (RDBMS):

SQL is the leading database management system (DBMS)

because it is the only Database that meets the uncompromising

requirements of today’s most demanding information systems.

From complex decision support systems (DSS) to the most rigorous

online transaction processing (OLTP) application, even application

that require simultaneous DSS and OLTP access to the same critical

data, Sql leads the industry in both performance and capability

SQL is a truly portable, distributed, and open DBMS that

delivers unmatched performance, continuous operation and support

for every database.

SQL RDBMS is high performance fault tolerant DBMS which

is specially designed for online transactions processing and for

handling large database application.

SQL with transactions processing option offers two features

which contribute to very high level of transaction processing

throughput, which are

The row level lock manager PL/SQL a procedural language extension to SQL

SYSTEM SPECIFICATIONS

Hardware Requirements

Processor : Intel Pentium III or more

Ram : 256 MB or more

Cache : 512 KB

Hard disk : 16 GB hard disk recommended for primary partition

Software Requirements

Operating system : Windows 2000 /XP or later

Front End Software : ASP.NET (C# .NET)

Back End Software : SQL – SERVER

Servers : IIS Server

SYSTEM DESIGN

UML DIAGRAMS:

ER-Diagrams

The entity Relationship Diagram (ERD) depicts the

relationship between the data objects. The ERD is the notation

that is used to conduct the date modeling activity the attributes

of each data object noted is the ERD can be described resign a

data object descriptions.

The set of primary components that are identified by the ERD

are

Data object Relationships

Attributes Various types of indicators.

The primary purpose of the ERD is to represent data objects

and their relationships.

Use case Diagrams:

A use case is a set of scenarios that describing an interaction

between a user and a system. A use case diagram displays the

relationship among actors and use cases. The two main components

of a use case diagram are use cases and actors.

An actor is represents a user or another system that will interact with

the system you are modeling. A use case is an external view of the

system that represents some action the user might perform in order

to complete a task.

They are helpful in exposing requirements and planning the project.

Start by listing a sequence of steps a user might take in order to complete an action.

Browse catalog and select items.

Gives the required information.

Gives the payment information.

Receive conformation from the Service Provider.

The Amount will be decreased in the user account.

These steps would generate this simple use case diagram

logs in and check for the balance of all the shopkeepers

updates the balance given by the service provider

administrator

logs in and check for the balance of all the shopkeepers

updates the balance given by the service provider

Sequence Diagrams:

Sequence diagrams can be used to explore the logic of a complex operation, function or procedure. They are called sequence diagrams because sequential nature is shown via ordering of message. First message starts at the top and the last message ends at bottom. The important aspect of a sequence diagram is that it is time-ordered. This means that the exact sequence of the interactions between the objects is represented step by step. Different objects in the Sequence diagram interact with each other by passing “messages”.

sd Class ModelEA 7.0 Unregistered Trial Version EA 7.0 Unregistered Trial Version EA 7.0 Unregistered Trial Version EA 7.0 Unregistered Trial Version

EA 7.0 Unregistered Trial Version EA 7.0 Unregistered Trial Version EA 7.0 Unregistered Trial Version EA 7.0 Unregistered Trial Version
































admin shop keeper individual visitor

logs in()

logs in()

logs in()

checks for the packages()

checks for the packages provided by the admin or service provider()

recharges the mobile()

recharges the mobile()

checks for the packages and recharges the mobiles if required()

Class Diagrams:

Class diagrams are widely used to describe the types of objects

in a system and their relationships. Class diagrams model class

structure and contents using design elements such as classes,

packages and objects. Class diagrams describe three different

perspectives when designing a system, conceptual, specification,

and implementation. These perspectives become evident as the

diagram is created and help solidify the design.

Classes are composed of three things: a name, attributes, and

operations. Below is an example of a class. Classes are composed

of three things: a name, attributes, and operations. Below is an

example of a class.

Association

State chart Diagram

A state chart transition diagram shows the state space of a

given class, the events that cause a transition from one state to

another and the actions that result from a state change.

State chart transition diagram is used to show:

The state space of a given class

The events that cause a transition from one state to

another

The actions that result from a state change

Each state chart diagram is associated with one class or with a

higher-level state diagram. A state diagram is a directed graph of

states connected by transitions.

Deployment Diagram

Andhra bank data base tables ICICI Bank data base Tables

Administrator data base

DataBase Tables:

Day Transactions Service numbers

Airtel data base Tables

SYSTEM TESTING & IMPLEMENTATION

SYSTEM TESTING

During system testing the system is used experimentally to ensure

that the software does not fail, i.e., it will run according to its

specifications and in the way the users expect.

Testing is the major quality control measure employed for

software development. Its basic function is to detect errors in the

software. During requirement analysis and design, the output is a

document that is usually textual and non-executable. After

Coding phase, computer programs are available that can be

executed for testing purpose. This implies that, testing not only

has to uncover errors introduced during coding phases. Thus, the

goal of testing is to cover requirement, design or coding errors in

the program.

The starting point of testing is Unit testing. In this a module is

tested separately and is often performed by the code itself

simultaneously with the coding of the module. The purpose is to

exercise the different parts of the module code to detect coding

errors. After this, modules are gradually integrated into

subsystems, which are then integrated themselves too eventually

from the entire system. During integration of module, Integration

Testing is performed. The goal of this is to detect design errors,

while focusing on testing the interconnection between modules.

After the system is put together, System Testing is performed.

Here the system is tested against the system requirements to

observe, whether all requirements are satisfied and the system

performs as specified by the requirement specification. Finally,

Acceptance testing is performed to demonstrate the operation of

the system to the client, on the real environment with the client’s

live data.

For testing to be successful, proper selection of test care is essential. There are two ]

different approaches to select test cases. The software or the module to be tested is

treated as a black box, and the test cases are decided based on the specifications of the

system or the module. For this reason, this form of testing is also called “ Black Box

Testing “. The focus here is on Testing the external behaviour of the system. In

structural testing, the test cases are decided based on the logic of the module to be tested.

A common approach here is to achieve some type of coverage of the statements in the

code. One common coverage criterion of the statement coverage, which requires that

test cases be selected for testing, is sometimes called “glass box testing”. The two

forms of testing are complementary, one tests the external behaviour, and the other tests

the internal structure.Often structural testing is used only for lower levels of testing,

while functional testing is used for higher levels

SAMPLE SCREENSHOTS

HOME PAGE

INDIVIDUAL REGISTRATION

The individual user who wishes to recharge his mobile online must first furnish all the

details by completing the registration process online.

RECHARGATION COMPLETED PAGE

This is the webpage which is used as the recharge page for individual user mobile recharge

by the individual user. After the user enters the recharge amount it validates with the

database and returns acknowledgement whether his mobile is recharged or not.

Conclusion:

Online Mobile Recharge project provides all the

information related to all the Service Providers and also gives the

facility of making the recharging for all the Service Providers under

one application at any time and from anywhere. It is beneficial for

both individual user and also the people who are into business like

the shop keepers. It also provides the complete information of all the

recharge coupons of different Service Providers to all users.

BIBLOGRAPHY:

The following books were referred during the analysis and

execution phase of the project

SQL THE COMPLETE REFERENCE

By Sql Press

SOFTWARE ENGINEERING

By Roger.S.Pressman

Professional ASP.NET

By Wrox

Web References:

www.wikipedia.com

www.asp.net

www.micrsoft.com

www.computer science tutorial.com

www.net tutorials.com

http://www.net/

http://www.computer/

http://www.micrsoft.com/

http://www.asp.net/

http://www.wikipedia.com/

Online Mobile Recharge Documentation

Documents

Transcript of Online Mobile Recharge Documentation