Embed Size (px)
Citation preview
1. INTRODUCTION
ORGANISATION PROFILE
skdotCom Technologies has a rich background in Software
Development and continues its entire attention on achieving transcending
excellence in the Development and Maintenance of Software Projects and
Products in Many Areas. Some of them are ERP, Banking, Manufacturing,
Insurance and Laying Emphasis on the Multimedia Projects. These projects
are prevalent and have been distributed and implemented for clients world
over. Major software Development Park at Kodambakkam, Chennai, India.
I. Genesis
Elucidating the Aborigines of the Company, skdotCom Technologies,
was initially dotCom IT Jobs Consultancy.
After stabilizing the skdotCom Products, Mr. P. Sivakumar M.C.A
started giving Counseling Services in the name of skdotCom Agency,
privately handled several Projects for leading Companies like Alstom, MRL
and Spencers. DSEL has confronted challenges and rooted itself has a niche
player in the Multimedia and the Business Software Segment. The Level of
performed has been exemplary leaving it to nothing than the best of
benchmark.
The indispensable factors, which give DSEL the competitive
advantages over others in the market may be slated as :
Performance
Pioneering efforts
Client satisfaction
Innovative concepts
Constant Evaluations
Improvisation
Cost Effectiveness
II. Comparison Mission Statement
“To help customer optimize their investments in information
technology, to help them gain a competitive edge in the market place.”
III. Quality policy
“To help our stock holders by regularly reviewing and improving our
process.”
IV. Infrastructure
Nested in an area with built-in area of 2,400 sq.ft. The park has encountered itself with computing resources that include from IBM. Besides, it also houses HP/9000, Sun Sparch, DEC Alpha System and over 500 IBM PS/VP nodes over a Heterogeneous Fiber Optic Network. Operating system is used varied from MVS and Aix through OS/400 and OS/2 to SOLARIS, UNIX and Windows with range of RDBMS, Languages and Case tools.
Major Functions / Activities at skdotCom
Only a few years ago, the World Wide Web was a very design
unfriendly place. But with the advent of Images, Web Pages have become
Interactive. This inter-activity is still limited. In its endeavor to make the
Internet more Interactive Exciting, skdotCom Technologies has set up the
Internet Team.
1.1 Synopsis
SMS TOPUP aims to customize the existing pre-paid system offered by a pre-paid
card Agent to the requirements of a Bank, say, ICICI and a Service provider, say, Airtel
and integrate it in their existing enterprise system. The system will become the base
system and foundation of complete wireless commerce framework. The primary audience
is the bank and service providers. Ultimately, all members of the Project Team are the
intended audience. The product must be a web-based and work as stand-alone product.
In practical, our project makes a customer not to venture outside anywhere from his
sitting room for recharging the mobile, that is, from his seat itself, he can able to perform
recharge applications through a single message. This facility is what we are providing
through our project. The product must be platform independent and it must use link to its
home page. This software would satisfy the needs of the clients such, by its security
aspects and necessary controls that are adopted by the Programmer and save the
messages that has been sent over.
2. SYSTEM ANALYSIS
2.1 FEASIBILITY STUDY
During the feasibility study, the feasibility of the project – the likelihood of the
proposed system is analyzed.
The feasibility study was carried out on the overall integrated package. Three key
consideration in involved in the feasibility analysis are Operational, Technical and
Economical.
Operational Feasibility
The main objective here is to find out whether
The system will work once it is developed and installed.
There is sufficient support for the project from the management.
The current business methods are acceptable to the users.
An investigation is conducted and as a result the following conclusions are derived.
There is sufficient support form the managerial level
The current methods are done manually and take lot of time.
The persons involved in the current working system are met and
discussions are held with them to evolve a system with which they
have good participations and interest.
Technical feasibility
Technological feasibility analyses the following areas.
Technology and manpower is available are not.
Capacity to hold the data that is required to use the new system.
Provision to respond to users regardless of their number and
location.
Provision for further expansion.
Guarantee of accuracy, reliability, ease of access and data security.
An investigation is conducted and as a result the following conclusions are derived.
The necessary technology to implement the proposed system is
available in the organization.
Main hardware equipment such as computers with the required
Capacities is also available.
Hence the system is technically feasible.
Economical Feasibility
Issues to be considered in the economical feasibility are
Financial benefits must equal or exceed the costs.
The solution should be cost effective.
Must be worth to pursue the project.
2.2 EXISTING SYSTEM
In the modern world, cell phones have been used by majority of the people around
the world. The normal procedure for cell phone activation Pre paid system takes on
with;
1. Buying the SIM card from the dealer
2. Scratch the card.
3. Type the 13 digit number
4. After these procedures only, prepaid system exists in a cell phone.
This is what happens in the existing system. This is not at all a problem for the
customers, but, in the fast moving world, every one is working like a machine. So, for
making their work to move in a smooth manner without tension and for saving their
precious time, we are introducing a system called SMS TOPUP system.
2.3 PROPOSED SYSTEM
In the proposed system, the customers have to make a SMS for recharging the SIM card.
The SMS contains the details of
1. Mobile Number.
2. Account Number.
3. PIN Number.
4. Amount for which the recharge is to be done.
After SMS has been sent to the dealer, he make contacts with the specified service
provider and specified bank and finishes the job.
3. System Configuration
HARDWARE REQUIREMENT:
Minimum 1.1 GHz PROCESSOR should be on the computer. 128 MB RAM. 20 GB HDD. 1.44 MB FDD. 52x CD-ROM Drive. MONITORS at 800x600 minimum resolution at 256 colors
minimum. I/O, One or two button mouse and standard 101-key keyboard.
SOFTWARE REQUIREMENT:
Operating System : Windows 95/98/2000/NT4.0. Technology : JAVA, J2ME Database : SQLServer Database Connectivity : JDBC.
3.3 About the Software
JAVA:
Java is used as front-end tool for developing the project. To run Java there
is no need to have any particular operating system, as it is platform independent. This
must have certain hardware and software installed on your computer. The key
considerations were summed up by the Java team in the following list of buzzwords:
Simple
Security
Portability
Object-oriented
Robust
Multithreaded
Architecture-Neutral
Interpreted
High Performance
Distributed
Dynamic
THE JAVA 2 ENTERPRISE EDITION
The Java 2 Platform, Enterprise Edition (J2EE), has rapidly established a
new programming model for developing distributed applications. This model is based on
well-defined components that can automatically take advantage of sophisticated platform
services. These components can be developed according to standard guidelines,
combined into applications, deployed on a variety of compatible server products, and
reused for maximum programmer productivity. This model is intended to both
standardize and simplify the kind of distributed applications required for today's
networked information economy.
J2EE Platform Benefits
With features designed to expedite the process of developing distributed
applications, the J2EE platform offers several benefits:
Simplified architecture and development
Freedom of choice in servers, tools, and components
Integration with existing information systems
Scalability to meet demand variations
Flexible security model
HYPER TEXT MARKUP LANGUAGE
HTML was specifically developed to use along with the Hyper Text
Transfer Protocol (HTTP) to encode documents for display on the World Wide Web.
HTML is defined in the HTML Standard, currently Version 4.0x. HTML
standards are recommended by the World Wide Web Consortium, W3C . W3C also
oversees the standardization of technologies related to the World Wide Web and
publishes the HTTP (Hypertext Transfer Protocol) standards. HTML is initials for Hyper
Text Markup Language. HTML is pronounced one letter at a time as if you are spelling
the word HTML. It is not pronounced as "hit mill" and it is NOT a programming
language. HTML cannot be used to write programs and it cannot control the precise
layout of a web page.
Web browsers are used to view HTML documents. Two popular web
browsers are the Netscape Navigator 4.x and the Microsoft Internet Explorer 5.x.
Browsers control the layout of a web page
JavaScript:
JavaScript enables you to embed commands in an HTML page.
JavaScript is powerful and simple. HTML provides a good deal of
flexibility to page authors, but HTML by itself is static; after being
written, HTML documents can’t interact with the user other than by
presenting hyperlinks. Scripting languages act as the glue that binds
every thing together. JavaScript mainly provides a fairly complete set
of built- in functions and commands, enabling you to perform math
calculations, manipulates strings, play sounds, open new windows and
new URLs, and access and verify input to your web forms.
JavaScript can also set the attributes, or properties , of web page
elements and other objects present in the browser.
This way you can change the behavior of plugs–in or other
objects without having to rewrite them. JavaScript commands
Macromedia Dreamweaver Macromedia Dreamweaver2.0 is one of the HTML Editor
It also includes DHTML effects
It is used to connect the forms to Servlets
It is used to Hyperlinks the web pages
It is used to create Templates
It is used to attach Sound files and Animation files along with our
Source.
The JavaServer Pages(JSP):
JavaServer Pages ™ technology is the Java ™ platform
technology for building applications containing dynamic Web
content such as HTML, DHTML, XHTML and XML. The
JavaServer Pages technology enables the authoring of Web pages
that create dynamic content easily but with maximum power and
flexibility.
Advantages: Write Once, Run Anywhere ™ propertiesHigh quality tool supportReuse of components and tag librariesSeparation of dynamic and static contentSupport for scripting and actionsWeb access layer for N-tier enterprise application architecture(s)
JSP page:
A JSP page is a text-based document that describes how to
process a request to create a response. The description intermixes
template data with some dynamic actions and leverages on the Java
Platform.The features in the JSP technology support a number of
different paradigms for authoring of dynamic content. JSP pages can be used in
combination with Servlets, HTTP, HTML, XML, Applets,JavaBeans
components and Enterprise JavaBeans components to implement a broad
variety of application architecture(s) or models.
Maximum performance and scalability through its unique design with
the Windows’NT multi-threaded architecture.
Central and easy-to-use the Graphical User Interface (GUI).
Automatic authentication of users by the Operating System.
ENTERPRISE JAVABEAN (EJB):
EJB is a standard server side component model for component
transaction monitors.It automatically takes in to account many of the
requirements of business systems-security,resourse
pooling,persistence,concurrency and transasction integrity.
Overall goals
The Enterprise JavaBeans (EJB) architecture has the following goals:
• The Enterprise JavaBeans architecture will be the standard
component architecture for building distributed object-oriented business
applications in the Java programming language. The Enterprise JavaBeans
architecture will make it possible to build distributed applications by
combining components developed using tools from different vendors.
• The Enterprise JavaBeans architecture will make it easy to write
applications. Application developers will not have to understand low-level
transaction and state management details, multi-threading, connection
pooling, and other complex low-level APIs.
• Enterprise JavaBeans applications will follow the “Write Once, Run Anywhere” philosophy of the Java programming language. An enterprise Bean can be developed once, and then deployed on multiple platforms without recompilation or source code modification.
• The Enterprise JavaBeans architecture will address the
development, deployment and runtime aspects of an enterprise application’s
life cycle.
• The Enterprise JavaBeans architecture will define the contracts
that enable tools from multiple vendors to develop and deploy components
that can inter operate at runtime.
• The Enterprise JavaBeans architecture will be compatible with
existing
server platforms. Vendors will be able to extend their existing products to
support Enterprise JavaBeans.
• The Enterprise JavaBeans architecture will be compatible with other
Java programming language APIs.
• The Enterprise JavaBeans architecture will provide interoperability
between enterprise Beans and Java 2 Platform Enterprise Edition (J2EE)
components as well as non-Java programming language applications.
• The Enterprise JavaBeans architecture will be compatible with the
CORBA protocols.
Enterprise Bean Provider
The Enterprise Bean Provider is the producer of enterprise beans.
The system output is an ejb-jar file that contains one or more enterprise
beans. The Bean Provider is responsible for the Java classes that implement
the enterprise bean’s business methods, the definition of the bean’s remote
and home interfaces and the bean’s deployment descriptor.
The deployment descriptor includes the structural information of the
enterprise bean and declares all the enterprise bean’s external dependencies.
Application Assembler
The Application Assembler combines enterprise beans into larger deployable application units. The input to the Application Assembler is one or more ejb-jar files produced by the Bean Provider(s). The
Application Assembler outputs one or more ejb-jar files that contain the enterprise beans along with their application assembly instructions. The Application Assembler inserts the application assembly instructions into the deployment descriptors. The Application Assembler can also combine enterprise beans with
other types of application components (JSP) when composing an
application. The EJB specification describes the case in which the
application assembly step occurs before the deployment of the enterprise
beans. However, the EJB architecture does not preclude the case that
application assembly is performed after the deployment of all or some of the
enterprise beans.
Deployer
The Deployer takes one or more ejb-jar files produced by a Bean
Provider or Application Assembler and deploys the enterprise beans
contained in the ejb-jar files in a specific operational environment. The
operational environment includes a specific EJB Server and Container. The
Deployer is an expert at a specific operational environment and is
responsible for the deployment of enterprise Beans.The Deployer uses tools
supplied by the EJB Container Provider to perform the deployment tasks.
The deployment process is typically two-stage:
• The Deployer first generates the additional classes and interfaces
that enable the container to manage the enterprise beans at runtime. These
classes are container-specific.
• The Deployer performs the actual installation of the enterprise beans
and the additional classes and interfaces into the EJB Container.
EJB Server Provider
The EJB Server Provider is a specialist in the area of distributed
transaction management, distributed objects, and other lower-level system-level
services. A typical EJB Server Provider is an OS vendor, middleware vendor, or
database vendor. The current EJB architecture assumes that the EJB Server
Provider and the EJB Container Provider roles are the same vendor. Therefore,
it does not define any interface requirements for the EJB Server Provider.
EJB Container Provider:
The EJB Container Provider provides
• The deployment tools necessary for the deployment of enterprise
beans.
• The runtime support for the deployed enterprise bean instances.
The focus of a Container Provider is on the development of a scalable, secure,
transaction-enabled container that is integrated with an EJB Server. The
Container Provider insulates the enterprise Bean from the specifics of an
underlying EJB Server by providing a simple, standard API between the
enterprise Bean and the container. This API is the Enterprise JavaBeans
component contract. The Container Provider typically provides support for
versioning the installed enterprise Bean components.The Container Provider
typically provides tools that allow the system administrator to monitor manage
the container and the Beans running in the container at runtime.
Persistence Manager Provider
The Persistence Manager interacts with the Container to receive
notifications related to the lifecycle of the managed beans. The current EJB
architecture, however, does not architect the full set of SPIs between the
Container and the Persistence Manager. These interfaces are currently left to
the Container Provider and Persistence Manager Provider.
System Administrator
The System Administrator is responsible for the configuration and
administration of the enterprise’s computing and networking infrastructure
that includes the EJB Server and Container. The System Administrator is
also responsible for overseeing the wellbeing of the deployed enterprise
beans applications at runtime.
SYSTEM ANALYSIS AND DESIGN
The given diagram is the basic diagram of our project. It represents the components of
our project. It briefly tells the modules of our project
In short, a customer (client mobile) will contact the dealer regarding Recharging the
SIM .Then, the dealer will make contacts with the bank and service provider for making
the cell recharged. This will be the overview of our project.
1 Project Architecture
For doing this job, we need three servers, namely;
Agent Server - makes connections between bank,service provider and client
Bank Server - Banks
Service Provider - Mobile Service Provider
Project Architecture:
.
Client Mobile Agent Server
Service ProviderBank Server
Customer Agent Server
Service Provider Bank
4. System Design
4.1 NORMALIZATIONThe normal forms are used to ensure that various types of anomalies and are not
introduced inconsistencies into the database.
Unnormalized form
An Unnormalized relation contains non-atomic values i.e. each rows
may contain multiple set of values for some of the columns these multiple
values in a single row are also called non-atomic values. There are no tables in
unnormailzed form.
First Normal Form
A relation scheme is said to be in the first normal form (1NF) if the
values in the domain if each attribute of the relation are atomic. In other words
only one value is associated with each attribute and the value is not a set of
values or list of values. All the tables here are atomic.
Second Normal Form A relation is in Second Normal Form (2NF) if it is in the first normal form and if all nonprime attributes are fully functionally dependant on the relation key(s). All tables satisfy the second normal form.
4.2 Table Design
Service Provider Customer Details
Field Name Constraint Data type Width
Mobile Id Primary Key Varchar2 20
Name Varchar2 20
Address Varchar2 20
Balance Number 20
Service Provider Transaction Details
Field Name Constraint Data type Width
Transaction Id Primary Key Varchar2 20
Mobile Id Varchar2 20
RechargeAmount Number 20
TransDate Varchar2 20
Bank Customer Details
Field Name Constraint Data type Width
AccountNo Primary Key Varchar2 20
PinNo Varchar2 20
Name Varchar2 20
Address Varchar2 20
Balance Number 20Bank Transaction Details
Field Name Constraint Data type Width
Transaction Id Primary Key Varchar2 20
FromAccountNo Varchar2 20
ToAccountNo Varchar2 20
Amount Number 20
TransDate Varchar2 20Dealer Customer Details
Field Name Constraint Data type Width
Mobile Id Primary Key Varchar2 20
Name Varchar2 20
Address Varchar2 20
Service Provider Transaction Details
Field Name Constraint Data type Width
Transaction Id Primary Key Varchar2 20
Mobile Id Varchar2 20
AccountNo Varchar2 20
Status Varchar2 20
Amount Number 20
RequestDate Varchar2 20
ResponseDate Varchar2 20
No
No
Yes
Yes
Start
Customer’s InputPhone No., Account No.,
PIN No., Amount
Is Reg. User
Valid Account
No
Abort
Abort
Yes
Yes
Recharge is doneTransaction ID is given
Stop
NoAbort
NoAbortValid
PIN No
Valid Min Balance
Data Flow Diagram
Level 0:
Data base store data and result
accno,skey
display user Bank
screen
level 1:
reg
accno,skey
accno,skey valid
accno,skey amount,to
accno
amount,to accno
cust
Verifyuser
Mobile
transfer
update
Level 2: Mobile Recharge
Table cust
To_accno
to_accno amount amount table
cust
Balance table cust
userVerify toaccno
Verifybalance
Performtransfer
screen
5. System Analysis
SYSTEM DESCRIPTION
SMS or Short Message Service allows Cellular or Mobile GSM phones to send
and receive Text Messages. SMS is a widely used service for brief communication and
the data sent using SMS services is confidential in nature and is desired not to be
disclosed to a third party. The use of SMS is a convenient and fast means of
communication with cellular telephone and pagers.
This can be alphanumeric and more recently graphical. A sent SMS message is
stored at an SMS Center (SMSC) until the receiver’s phone receives it. The receiver can
identify the sender by his/her telephone number that is included in the message itself.
SMS supports several input mechanisms that allow interconnection with different
message sources and destinations including voice-mail systems, Web-based messaging
and E-mail integration.
SMS CHARACTERISTICS
The cost of sending SMS messages is lower than other data-oriented mobile
services such as WAP. Mobile service in-curstwo kinds of cost: the one-time cost of
purchasing a mobile device; and the ongoing cost of using the services. Nowadays,
almost all mobile phones are SMS enabled but WAP phones are still relatively expensive.
The cost of sending a SMS message is low and relatively much cheaper than accessing
Internet via WAP.
Convenience of “anytime and anywhere”
SMS messaging has two special characteristics: “anytime” and “anywhere”
availability. A switched-on mobile device is able to receive or send a message at
“anytime” regard-less of whether a voice or data call is in progress. Messages sent to a
switched-off phone are guaranteed to deliver when the handset is on again because SMS
messages are users. One application is in the selective advertising business for
promotional purpose. For example, restaurant operators can entice customers by sending
them advertisements and promotional information messages when they are in the vicinity
of restaurants. “Personal” characteristic;
To determine the possible success factors of emerging SMS commerce, we first need
to understand the contributing factors to the existing success of SMS messaging. To-ward
this end, we performed an extensive content analysis of the extant literature on SMS
messaging in several countries. Cost-effective and interoperable wireless infrastructure,
support for “location-awareness”.
The Modules of our Project are, User Interface
1. Mobile GUI.
2. Agent Server GUI.
3. Service Provider Server GUI.
Transactional components.
1. Agent Component
a) Registration.
b) Validity.
c) Transaction.
2. Bank Component
a) Registration.
b) Validity.
c) Transaction.
3. Service Provider Component
a) Registration.
b) Validity.
c) Transaction.
Web Components
1. Agent Admin Control Panel.
2. Bank Admin Control Panel.
3. Service Provider Admin Control Panel.
USER INTERFACE:
The module is named as User interface because it is fully designed
for the purpose of each and every user working for recharging the sim card. This
job makes user friendlier with the computer, cell phones, etc. This module is
developed using Java 2 Standard Edition, which is simply called as J2SE.
The User Interface module is developed with three sub contents, namely;
I. Mobile GUI: The client is provided with a GUI to interact with the Server
The mobile phone operations to be carried out by the client has been
designed with forms and these forms are designed using Java
MIDlet packages which includes,
javax.microedition.midlet.
javax.microedition.lcdui.
javax.microedition.io.This interface consists of five sections, namely;
1. Recharge:
The Recharge section is used by the user for entering the mobile
number, Bank Account PIN number and the amount for which he wants to
recharge the SIM card.
2. Customer Care:
On completion of each transaction, the client is provided with a
Transaction ID, which he can use to check the status of the transactions made
by him. With this, the users can clear their doubts and other queries.
This is called as Customer Care services.
3. Balance:
Balance section is also used by the client for viewing the balance
made in their transactions.
4. Help:
Help section gives the details for how to make use of this interface.
II. Agent Server GUI: The Agent Server User Interface has been developed using J2SE.
This server is used by the agent, who makes connection between service
provider, bank and client. This server is used for
1. Starting the Server.
2. Stopping the Server.
3. Viewing Transactions with the needed details.
III. Bank Server GUI: The Bank Server User Interface has also been developed using
J2SE. This server is used by the bankers , who have been dealing transactions
with both service provider and client. This server is used for
1. Starting the Server.
2. Stopping the Server.
3. Viewing Bank Transactions with the needed details.
TRANSACTION COMPONENTS:
First of all, components are manageable and discrete chunk
of logic. Transaction details are useful for the transactions that have been carried
out by the client, bank and service provider for recharging the sim card. This
module has been developed using the J2EE Technology. The components of this
transaction are;
I. Agent Components: This component manages the transactions that are likely to be
carried out by the agent. This comprises of the following sections,
1. Registration:
Registration section deals with the registration of the persons,
who have bought the SIM from the Agent
2. Validity:
Validity section deals with the validation of the client, which
clears that whether the client is a registered user or not.
3. Transaction:
After the Client has been considered as a registered and validated
user, he/she is eligible for making furthermore transaction. This is explained in
the transaction section.
II. Bank Components: This component manages the transactions that are likely to be
carried out by the bank. This comprises of the following sections,
1. Registration:
Registration section deals with the registration of the clients for
creating a new Account. A client can utilize this software, if he/she is having the
account in the recognized bank. If he/she is not a registered user, then he/she is
not capable of making any transactions.
2. Validity:
Validity section deals with the validation of the client, which
clears that whether the client is a registered user or not by checking whether the
given PIN(Personal Identification Number) is valid or not.
3. Transaction:
After the Client has been considered as a registered and validated
user, he/she is eligible for making furthermore transaction. This is explained in
the transaction section.
III. Service Provider Components: This component manages the transactions that are likely to be
carried out by the service provider. This comprises of the following sections,
1. Registration:
Registration section deals with the registration of the clients who
are all using the service provider’s services. A client can utilize this software, if
he/she is provided with the service of the particular service provider. If he/she is
not a registered user, then he/she is not capable of making any transactions.
2. Validity:
Validity section deals with the validation of the client, which
clears that whether the client is a registered user or not by checking whether the
given Mobile number is a valid service provider number or not.
3. Transaction:
After the Client has been considered as a registered and validated
user, he/she is eligible for making furthermore transaction. This is explained in
the transaction section.
WEB COMPONENTS:
This component acts as Graphical User Interface (GUI)
to the administrators of the bank, service provider and agent. This module has been
developed using the Java Server Pages(JSP), which is a java based server side scripting
technology that consists of a text document which when provided with a request,
processes it and provides response. This comprises of the following sections,
I. Agent Control Panel:
This is the control panel designed for the agent administrator, who will
maintain all the transactions that is likely to be carried out in the agent panel. The
control panel consists of three functions,
1. Registration:
Registration section deals with the registration of the clients
who are all using the agent’s help services. If he/she is not a registered user, then
he/she is not capable of making any transactions.
2. Transaction List:
The administrator has to view the daily transactions made by
his/her clients. This lists has been given under transaction list.
3. View Registered Users:
The administrator has another important function, that is, he
/she has to view the users list regularly by checking whether he/she is a registered
user or not. This function is carried out by viewing registered users.
II. Bank Control Panel:This is the control panel designed for the administrator, who will maintain
all the transactions that is likely to be carried out in the bank panel. The control
panel consists of three functions,
1. Registration:
Registration section deals with the registration of the clients
who are all using the banks help services. If he/she is not a registered user, then
he/she is not capable of making any transactions.
2. Transaction List:
The administrator has to view the daily transactions made by
his/her clients. The transaction may be debit or credit. This lists has been given
under transaction list.
3. View Registered Users:
The administrator has another important function, that is, he
/she has to view the users account details. The customer is a valid client, if he is
provided with the perfect balance amount This function is carried out by viewing
registered users.
III. Service Provider Control Panel: This is the control panel designed for the administrator, who will maintain
all the transactions that is likely to be carried out in the service provider panel. The
control panel consists of three functions,
1. Registration:
Registration section deals with the registration of the clients
who are all using the service provider’s help services. If he/she is not a
registered user, then he/she is not capable of making any transactions.
2. Transaction List:
The administrator has to view the daily transactions made by
his/her clients. The transaction may be view the users account details for which
the mobile has been recharged and also the mobile number. This includes the
users those who aren’t capable of making any recharges because of less amount.
This lists has been given under transaction list.
3. View Registered Users:
The administrator has another important function, that is, he
/she has to view the user’s details. The customer is a valid client, if he is provided
with the perfect service provider’s services. This function is carried out by
viewing registered users.
6. System Testing And Implementation
System Testing:
The system once finished has to go through a series of testing in order to ensure that it works the way it ought to. The various types of testing measures to be taken are:
Test to see if the requirements are taken care of. Test to see if all the inputs are handled effectively. Test the system by traversing all the paths and discover my surprises. Check if errors and the exceptions have been handled properly. See if validations of input data are taken care of.
Types of Tests:
There are six types of test a software product must satisfy:
1. Unit Test2. Functional Test3. Performance Test4. Stress Test and5. Structural Test6. System Test
Functional Test, Performance Test and Stress Test are known as Black box testing. Structural Test is referred as White box or Glass Box testing.
1.Unit Testing:
Unit testing focuses verification effort on the smallest unit of software design. Unit Testing is considered as an equivalent to coding step. After the source level code has been developed, reviewed and verified for correct syntax, unit test case design
begins. In most of the applications, a driver is nothing more than a main program that accepts test case data, passes such data to the module to be tested and prints the relevant results.
2.Functional Testing:
Functional Testing involves testing the system under typical operating condition, typical input values and for typical expected results. The functional boundaries specifies boundary within which the system can function. three types of functional tests are done
Checking the documented functions. Checking with maximum values. Checking with valid input.
3.Performance Testing:
Performance Testing is conducted to identify the bottlenecks in the system and to fine-tune the overall performance of the system.
4.Stress Testing:
Stress Testing involves overloading the system in various ways and observing the behavior. The system is tested with high network traffic and more number of clients. Stress test provides valuable insight about the strengths and weakness of a system.
5.Structural Testing:
Structural Testing are concerned with examining the internal processing logic of a program and traversing particular execution paths.
6.System Testing:
System Testing involves two kinds of activities
1.Integration Testing and 2. Acceptance Testing
1.Integration Testing:
Integrating all the functionalities since some functions work perfectly when run alone tests the system.
Integration Testing is of two types(a) Top down Integration Testing and(b) Bottom-Up Integration testing.
(a) Top down Integration Testing:
In Top down Integration the top of the hierarchy is tested then one or two immediately subordinate routines are tested.
(b)Bottom-Up Integration Testing:
First the modules at the very bottom, which have no subordinates, are tested then these are combined with higher-level modules for testing.
2.Acceptance Testing:
Acceptance Testing involves planning and execution of functional tests, performance tests and stress tests in order to demonstrate that the implemented system satisfies its requirements.
QUALITY ASSURANCE
The aim of this step is to maintain or to ensure the quality of the system developed. The quality assurance goals in the system life cycle involves
1.Quality factors specification: - This was done to determine the factors that lead to high quality of a system.
a. Correctness- The extent to which a program meets System specification.
b. Reliability – The degree to which a program meets system specification.
c. Efficiency - The amount of computer resources required by the entire program to perform a function.
d. Usability – The effort required learning and operating the system.
e. Maintainability – The ease with which the program errors are located and corrected.
f. Testability - The effort required to test a program to ensure its correct performance.
g. Portability – The ease of transporting a program from one hardware configuration to another.
h. Accuracy - The required precision in input editing, computation and output.
i. Error Tolerance – Error detection and correction versus error avoidance.
j. Expandability - Ease of adding or expanding existing databases.
k. Access Controls and Audit – Control of access to the system and the extent to which that access can be audited.
l. Communication – How useful the input and output of the system are.
1.Software Requirements Specification: - This was done to generate the required documents that provide the technical specification for the design and development of the software.
2. Software Design Specification: - This was done in order to provide the functions and features described in the previous stage.
3.Software Testing and Implementation: - This was done to provide necessary software adjustment for the system to continue to comply with the original specifications.
Quality Assurance is the review of software and related documentation for correctness, accuracy, maintainability, reliability, and expendability. This also includes assurances that the system meets the specifications and requirements for its intended use performance.
Implementation:
The above said testing can be done virtually. In order to implement the VB .Net for Knowledge Based Decision Support System. Implementation includes all those activities that take place to convert from an old system to a new one.
Three aspects of implementation are:
1.Training Personnel
2.Conversion
3.Point Implementation Review
TRAINING:
The quality of training received by the personnel involved with the system
in various capacities helps or hinders, and may even prevent, the successful
implementation of an information system. Both system operators and users need training.
Training System Operators:
The training ensured that they were able to handle all possible operations, both routine
and extraordinary. Training also involved run procedures, which involves working
through the sequence of activities needed to use a new system on an ongoing basis.
CONVERSION:
Conversion is the process of changing from an old system to a new one. There are
basically four conversion methods:
Parallel Systems-offers greatest security.
Direct Cutover- Presents the highest risk.
Pilot Approach
Phase-In method
The approach followed for implementing the system was the Pilot Approach. The
working version of the system was implemented in one regional office, so that the
employees were aware that they were piloting a new system and that changes could be
made to improve the system.
The system would be installed throughout the organization using the phase in
methods. This approach had the advantage of providing a sound training ground before
full implementation.
Post Implementation Review:
After the system is implemented and conversion is complete, review of the
system is usually conducted by users and analysts alike. It is important to determine
whether the system is working, how it has been accepted and whether adjustments are
needed. The review is also important to gather information for the maintenance of the
system.
Review Questions: - The most fundamental concern during the post implementation review is
determining whether the system has met its objective, that is analysts want to know whether
the performance level of users has improved and if the system is producing the result intended.
7.Conclusion and Future Scope
SMS based recharge system are not isolated system, but system with a strong interdependence of existing internet payment system. SMS based recharge system is an extra option to existing payment methods and the mobile phone can be considered as another tool for carrying out payments. A lot of requirements need to be fulfilled if the new recharge system shall be able to compete with the existing payment systems. This thesis has focused on the requirements for the client technology in the mobile phone. When using the mobile phone as a payment tool, the phone can act as a terminal. In this situation the data handling and transmitting meets a lot of challenges. A bigger change for network externalities is present if all the requirements from the critical success factors are met and accepted by the actors. Therefore they often approach less significant markets even though the mobile marketplace is global.
A. APPENDICES
A.1 BIBLIOGRAPHY
REFERENCES
1] Michael Peirce, Donal O'Mahony “Multi-Party Payments for Mobile Services”, Copyright. IEEE 2000.
[2] Joris Claessens , Valentin Dem,Danny De Cock, Bart Preneel,Joos Vandewalle “On the Security of Today’s On-line Electronic Banking Systems”, Dec’2001 [3] Joris Claessens, Bart Preneel and Joos Vandewalle “Combining World Wide Web and wireless security”, Feb’2002.
[4]J.Burgett1,S.Hussain1,C.M.Jonker2,A.Razaq1,K.Silz,Personalized,Automated Recharge of Prepaid Mobile Phones” 1AMS Inc,51-55 Gresham street, London EC2V 7JH, [email protected] 2 Department of AI, Vrije Universiteit, De Boelelaan 1081a,1081 HV Amsterdam.
[5]Simon Buckingham www.YES2SMS.com,“success 4 SMS “ , Feb.2001. [6] Hunter, J., and Crawford, W., (1998), Java Servlet Programming, O’Reilly and Associates.
ANNEXURE-A.
1. Abbreviations OOPS Object Oriented Programming Concepts TCP/IP Transmission Control Protocol/Internet Protocol JDBC Java Data Base Connectivity EIS Enterprise Information Systems BIOS Basic Input/Output System JNDI Java Naming and Directory Interface ORDBMS Object Relational Database Management
System
A.2 ONLINE RESOURCES
www.jsptags.com
www.java.sun.com/products/jsp/resources.html
www.roseindia.net
