COMPUTERIZED MOBILE STORE MANAGEMENT SYSTEM

1. Economical Feasibility
2. Technical Feasibility
3. Operational Feasibility

ECONOMICAL FEASIBILITY
Cost-benefit-analysis is among the most important information contained in a feasibility
study, which is an assessment of economic justification for a computer-based system project
cost-benefit analysis delineates costs for projects development and weighs them against tangible
and intangible of system.
To develop system technically for the use it need financial benefits or exceeds the costs or
made equal. The questions raised for the purpose of estimating are

Cost to conduct a full system investigation

Cost of hardware and software for the class of application being considered

Benefits in the form of reduced costs or few costly errors.

In this proposed system, since the hardware and software are already available in the

organization. The implementation will incur no extra cost. There is no additional cost involved in
manpower requirements for the proposed system. The system also reduces manual file
maintenance work and employs fewer people. Thus in the long run, it is beneficial and so is
economically feasible.

TECHNICAL FEASIBILITY
Technical feasibility is a study of function performance and constraints that may affect
the ability to achieve an acceptable system. It is frequently the most difficult area to assess at this
stage of system development process. During technical analysis, the analyst evaluates the
technical merits of the system concept, while at the same time collecting additional information
about performance, reliability, maintainability and reducibility, the main technical issues usually
raised during feasibility stage of investigation include. Does the necessary technology exits to do

COMPUTERIZED MOBILE STORE MANAGEMENT SYSTEM

what is suggested.
1

Does the proposed equipment have the technical capacity to hold the data required to use
new system?

Will the proposed system provide adequate response to inquiries, regardless of number or
location of users?

Can system be expand of developed

Are there technical guarantees of accuracy reliability, ease of access and security?

OPERATIONAL FEASIBILITY
2.3.1 SOFTWARE REQUIREMENTS:
Operating system

Windows Family

Front-End

JAVA

Back-End

Oracle 9i

2.3.2 HARDWARE REQUIREMENTS

Processor

Intel Pentium III

Ram

256MB

Hard Disk

20GB

2.4 Process Models

Software systems come and go through a series of passages that account for their
inception, initial development, productive operation, upkeep, and retirement from one generation
to another. This article categorizes and examines a number of methods for describing or
modeling how software systems are developed. It begins with background and definitions of
traditional software life cycle models that dominate most textbook discussions and current
software development practices. This is followed by a more comprehensive review of the
alternative models of software evolution that are of current use as the basis for organizing
software Engineering projects and technologies.
In contrast to software life cycle models, software process models often represent a
networked sequence of activities, objects, transformations, and events that embody strategies for

COMPUTERIZED MOBILE STORE MANAGEMENT SYSTEM

accomplishing software evolution. Such models can be used to develop more precise and
formalized descriptions of software life cycle activities. Their power emerges from their
utilization of a sufficiently rich notation, syntax, or semantics, often suitable for computational
processing.
Software process networks can be viewed as representing multiple interconnected
task chains (Kling 1982, Gag 1989). Task chains represent a non-linear sequence of actions that
structure and transform available computational objects (resources) into intermediate or finished
products. On-linearity implies that the sequence of actions may be non-deterministic, iterative,
accommodate multiple/parallel alternatives, as well as partially ordered to account for
incremental progress. Task actions in turn can be viewed a non-linear sequences of primitive
actions which denote atomic units of computing work, such as a user's selection of a command or
menu entry using a mouse or keyboard. Wino grad and others have referred to these units of
cooperative work between people and computers as "structured discourses of work"
(Winograd1986), while task chains have become popularized under the name of "workflow"
(Bolder 1998).Task chains can be employed to characterize either prescriptive or descriptive
action sequences Prescriptive task chains are idealized plans of what actions should be
accomplished, and in what order. For example, a task chain for the activity of object-oriented
software design might include the following task actions:
_ Develop an informal narrative specification of the system.
_ Identify the objects and their attributes.
_ Identify the operations on the objects.
Process Models Types:
1 Prescriptive Model
2. The waterfall Model
3. Incremental Process Models
3.1. Incremental Model
3.2. RAD Model
4. Evolutionary Process Models
4.1. Prototyping
4.2. Spiral Model
4.3. The Concurrent Development Model

COMPUTERIZED MOBILE STORE MANAGEMENT SYSTEM

2.4.1. Waterfall Model

One such approach/process used in Software Development is "The Waterfall Model". Waterfall
approach was first Process Model to be introduced and followed widely in Software Engineering
to ensure success of the project. In "The Waterfall" approach, the whole process of software
development is divided into separate process phases. The phases in Waterfall model are:
Requirement Specifications phase, Software Design, Implementation and Testing &
Maintenance. All these phases are cascaded to each other so that second phase is started as and
when defined set of goals are achieved for first phase and it is signed off, so the name "Waterfall
Model". All the methods and processes undertaken in Waterfall Model are more visible.

Fig2.4.1.Waterfall Model
The stages of "The Waterfall Model" are:
Requirement Analysis & Definition: All possible requirements of the system to be developed
are captured in this phase. Requirements are set of functionalities and constraints that the enduser (who will be using the system) expects from the system. The requirements are gathered
from the end-user by consultation, these requirements are analyzed for their validity and the

COMPUTERIZED MOBILE STORE MANAGEMENT SYSTEM

possibility of incorporating the requirements in the system to be development is also studied.
Finally, a Requirement Specification document is created which serves the purpose of guideline
for

the

next

phase

of

the

model.

System & Software Design: Before a starting for actual coding, it is highly important to
understand what we are going to create and what it should look like? The requirement
specifications from first phase are studied in this phase and system design is prepared. System
Design helps in specifying hardware and system requirements and also helps in defining overall
system architecture. The system design specifications serve as input for then expanse of the
model.
Implementation & Unit Testing: On receiving system design documents, the work is divided in
modules/units and actual coding is started. The system is first developed in small programs
called units, which are integrated in the next phase. Each unit is developed and tested for its
functionality; this is referred to as Unit Testing. Unit testing mainly verifies if the modules/units
meet their specifications.
Integration & System Testing: As specified above, the system is first divided in units which are
developed and tested for their functionalities. These units are integrated into a complete system
during Integration phase and tested to check if all modules/units coordinate between each other
and the system as a whole behaves as per the specifications. After successfully testing the
software,

it

is

delivered

to

the

customer.

Operations & Maintenance: This phase of "The Waterfall Model" is virtually never ending
phase (Very long). Generally, problems with the system developed (which are not found during
the development life cycle) come up after its practical use starts, so the issues related to the
system are solved after deployment of the system. Not all the problems come in picture directly
but they arise time to time and needs to be solved; hence this process is referred as Maintenance.
There are some disadvantages of the Waterfall Model.

COMPUTERIZED MOBILE STORE MANAGEMENT SYSTEM

1) As it is very important to gather all possible requirements during the Requirement Gathering
and Analysis phase in order to properly design the system, not all requirements are received at
once
2) The problems with one phase are never solved completely during that phase and in fact many
problems regarding a particular phase arise after the phase is signed off, these results in badly
structured system as not all the problems (related to a phase) are solved during the same phase.

3. DESIGN
SYSTEM DESIGN Phase follows system analysis phase. Design is maintaining a record
proof design division and providing a blue print for the implementation phase. Design is the
bridge between system analysis and system implementation.
System design is transition from a use oriented, document oriented to programmers are database
personals. The design is a solution, a how to approach to the creation of a new system. This is
composed of several steps. It provides the understanding and procedural details necessary for
implementing the system recommended in the feasibility study. Design goes through logical and
physical stages of development, logical design reviews the presents physical system, prepare
input and output specification, detail the implementation plan and prepare a logical design
walkthrough.
The database tables are designed by analyzing various functions involved in the system
and the format of the fields is also designed. The fields in the database table should be avoided
because it affects the storage areas of the system, cares to be taken to encode the lengthy names.
Then in the input and the output screen design, the design should be made user friendly. The
menu should be precise and compact.

OBJECTIVES OF DESIGN

COMPUTERIZED MOBILE STORE MANAGEMENT SYSTEM

System design is like a blue print for a building, it specifies all the features that are to be
in finished product. Design states how to accomplish objectives determined in the analysis phase.

LOGICAL DESIGN
The system of an information system produces the details that state how a system will
meet the requirements identified during system analysis. This stage is logic design.
The system of an information system produces the details that state how a system will
meet the requirements identified during system analysis. This stage is logic design.

PHYSICAL DESIGN
The process of development program software is referred to as physical design. In this
stage the logical design elements are specified which sort the business activities. The physical
design ensures the system features to meet the user requirements.

DESIGN PROCESS
System flow chart is a high level picture of the physical system. In the structure analysis,
we begin by constructing the logical model of a system often using the dataflow diagram. During
the system design the logical model converted into the physical system.
A system flowchart is traditional tool for describing a physical system. The basic idea is
to provide a symbol to represent at level, each discrete component in the system program, files,
pages, procedures and so on.

DESIGN PRINCIPLES
The system design is the last phase that indicates the final system and its process in the
design phase of Computerized Mobile Store Management System database tables, input screens
and output report design etc. were designed.
The database tables were designed with necessary fields. The redundancy and duplication
7

COMPUTERIZED MOBILE STORE MANAGEMENT SYSTEM

of fields are avoided.
All the input screens in this system are user friendly and understandable format. Also
the sizes of all the screens are standardized.
Menus designed in this system are brief, compact and self explanatory. The menus are
sharp and any novice user can invoke the system .popup menus are also used to invoke various
sub menus.

3.2 DATABASE NORMALIZATIONS

Normalization is a technique of separating redundant fields and breaking up a large table
into smaller ones. All the tables have been normalized up to the third normal form.
Normalization is the process of simplifying the relationship between the data elements in
the record. Through this technique, a collection of the data in a record structure is replaced by
successive record structure that is simpler and more predictable and therefore more manageable.
Normalization is carried for following reasons:

To structure the data so that any pertinent relationship between entities can be
represented.

To permit simple retrieval of data in response to query and report requests.

To simplify the maintenance of the data through up dates, insertions and deletions

To reduce the need to restructure or recognize data when new application requirements
arise.

COMPUTERIZED MOBILE STORE MANAGEMENT SYSTEM

5

These attempts to remove redundant data avoid data inconsistencies and prevent update
anomalies.
This results in a simpler or more natural data model. A normalized database more clearly

reflects the entities and relationships in the real world.

Relational data theory outlines five normal forms, of which three normal forms are used
popularly for designing for designing relation tables.
The rules and methods of first three normal forms are given below.
1. FIRST NORMAL FORM
A relation is said to be in 1NF if all the underline domain of attributes contain simple
indivisible values.
2. SECOND NORMAL FORM
The 2NF is based on the concept of full functional dependency. A relation is said to be in
2NF and every non key attribute is functionally dependency on candidate key of the table.
3. THIRD NORMAL FORM
The 3NF is based on the concept of transitive dependency. A relation in 2NF is said to be
in 3NF if every non key attribute is non-transitively dependent on the primary key.

3.3 DATADICTIONARY
After carefully understanding the requirements of the client, the entire data storage
requirements are divided into tables. The below tables are normalized to avoid any anomalies
during the course of data entry.

COMPUTERIZED MOBILE STORE MANAGEMENT SYSTEM

3.5.5. CLASS RESPONSIBILITY COLLABORATION [CRC] CARDS:ClsCustomer:

Responsibility

Collaboration

1. Add the Customer.

2. Search the Customer
3.Update the Customer
4.Delete the Customer

Mobile Phone
Mobile Phone
Mobile Phone
Mobile Phone

ClsBill:
Responsibility

Collaboration

Calculate the Bill for Customer.

Mobile Phone, Customer.

ClsMobilePhone:
Responsibility

Collaboration

1. Add new Mobile Phone.

2. Search Mobile Phone.
3. Update Mobile Phone.
4.Delete Mobile Phone

Customer
Customer
Customer
Customer

ClsSalesReports:
Responsibility

Collaboration

1. Daily Reports

Customer, Bill, Mobile Phone

10

COMPUTERIZED MOBILE STORE MANAGEMENT SYSTEM

2. Monthly Reports
3. Yearly Reports

Customer, Bill, Mobile Phone

Customer, Bill, Mobile Phone

3.5.6 COLLABORATION DIAGRAM

Collaboration diagram represents collaboration which is a set of objects related in a
particular.

Admin

1. Login

2. Select

3. Perform the

Type of action

Action

to be Perform

Selected

System

Fig3.5.6: Collaboration diagram for Mobile Phone transaction

4. IMPLIMENTATION
Implementation is the process of converting a new or revised system design into an

11

COMPUTERIZED MOBILE STORE MANAGEMENT SYSTEM

operational one. Apart from planning, the major tasks of preparing for implementation or
education and training of users. Implementation includes following activities:-

Obtaining and installing the system hardware.

Providing user access to the system.

Creating and updating the database.

Training the users on the new database.

Documenting the system for its users.

Evaluating the operation and use of the system.

Implementation Methods:There are four basic methods of implementation:1

Direct conversion

Parallel conversion

Pilot conversion

Phasing conversion

Direct Conversion:Description:
In this method the new one replaces the old system. This makes organization to fully rely
on the new system.
Advantages:This method provides experience and live test before implementation.
Disadvantages:This method may give the impression that the old system is unreliable and not error free.
Phased Conversion:-

12

COMPUTERIZED MOBILE STORE MANAGEMENT SYSTEM

Description:In this method, the system is implemented gradually across all users.
Advantages:It allows some users to take advantages of the system early. It allows training and
installing without unnecessary use of resources.
Disadvantages:A long phase-in causes user problems whether the project goes well(over enthusiasm) or
not (resistance or lack of fair trail).

4.1. SOFTWARE TECHNOLOGIES USED AND IMPLIMENTATION:Communication or Database Connectivity Tier

The Communication architecture is designed by concentrating on the Standards of
Servlets and Enterprise Java Beans. The database connectivity is established by using the Java
Data Base Connectivity.
The standards of three-tire architecture are given major concentration to keep the standards of
higher cohesion and limited coupling for effectiveness of the operations.
Features of The Language Used
In my project, I have chosen Java language for developing the code.
About Java
Initially the language was called as oak but it was renamed as Java in 1995. The
primary motivation of this language was the need for a platform-independent (i.e.,
architecture neutral) language that could be used to create software to be embedded in
various consumer electronic devices.
Java is a programmers language.
Java is cohesive and consistent.
Except for those constraints imposed by the Internet environment, Java gives the
programmer, full control.
Finally, Java is to Internet programming where C was to system programming.
13

COMPUTERIZED MOBILE STORE MANAGEMENT SYSTEM

Importance of Java to the Internet
Java has had a profound effect on the Internet. This is because; Java expands the
Universe of objects that can move about freely in Cyberspace. In a network, two categories of
objects are transmitted between the Server and the Personal computer. They are: Passive
information and Dynamic active programs. The Dynamic, Self-executing programs cause serious
problems in the areas of Security and probability. But, Java addresses those concerns and by
doing so, has opened the door to an exciting new form of program called the Applet.
Java can be used to create two types of programs
Applications and Applets: An application is a program that runs on our Computer under
the operating system of that computer. It is more or less like one creating using C or C++. Javas
ability to create Applets makes it important. An Applet is an application designed to be
transmitted over the Internet and executed by a Java compatible web browser. An applet is
actually a tiny Java program, dynamically downloaded across the network, just like an image.
But the difference is, it is an intelligent program, not just a media file. It can react to the user
input and dynamically change.
Features Of Java
Security
Every time you that you download a normal program, you are risking a viral infection.
Prior to Java, most users did not download executable programs frequently, and those who did
scanned them for viruses prior to execution. Most users still worried about the possibility of
infecting their systems with a virus. In addition, another type of malicious program exists that
must be guarded against. This type of program can gather private information, such as credit card
numbers, bank account balances, and passwords. Java answers both these concerns by providing
a firewall between a network application and your computer.
When you use a Java-compatible Web browser, you can safely download Java applets without
fear of virus infection or malicious intent.
Portability
For programs to be dynamically downloaded to all the various types of platforms
connected to the Internet, some means of generating portable executable code is needed .As you
will see, the same mechanism that helps ensure security also helps create portability. Indeed,
Javas solution to these two problems is both elegant and efficient.

14

COMPUTERIZED MOBILE STORE MANAGEMENT SYSTEM

The Byte code
The key that allows the Java to solve the security and portability problems is that the
output of Java compiler is Byte code. Byte code is a highly optimized set of instructions
designed to be executed by the Java run-time system, which is called the Java Virtual Machine
(JVM). That is, in its standard form, the JVM is an interpreter for byte code.
Translating a Java program into byte code helps makes it much easier to run a program in
a wide variety of environments. The reason is, once the run-time package exists for a given
system, any Java program can run on it.
Although Java was designed for interpretation, there is technically nothing about Java
that prevents on-the-fly compilation of byte code into native code. Sun has just completed its Just
In Time (JIT) compiler for byte code. When the JIT compiler is a part of JVM, it compiles byte
code into executable code in real time, on a piece-by-piece, demand basis. It is not possible to
compile an entire Java program into executable code all at once, because Java performs various
run-time checks that can be done only at run time. The JIT compiles code, as it is needed, during
execution.
Java, Virtual Machine (JVM)
Beyond the language, there is the Java virtual machine. The Java virtual machine is an
important element of the Java technology. The virtual machine can be embedded within a web
browser or an operating system. Once a piece of Java code is loaded onto a machine, it is
verified. As part of the loading process, a class loader is invoked and does byte code verification
makes sure that the code thats has been generated by the compiler will not corrupt the machine
that its loaded on. Byte code verification takes place at the end of the compilation process to
make sure that is all accurate and correct. So byte code verification is integral to the compiling
and executing of Java code.
Overall Description
Picture showing the development process of JAVA Program
Java programming uses to produce byte codes and executes them. The first box indicates
that the Java source code is located in a. Java file that is processed with a Java compiler called
javac. The Java compiler produces a file called a. class file, which contains the byte code. The.
Class file is then loaded across the network or loaded locally on your machine into the execution
environment is the Java virtual machine, which interprets and executes the byte code.

15

COMPUTERIZED MOBILE STORE MANAGEMENT SYSTEM

Java Architecture
Java architecture provides a portable, robust, high performing environment for
development. Java provides portability by compiling the byte codes for the Java Virtual Machine,
which is then interpreted on each platform by the run-time environment. Java is a dynamic
system, able to load code when needed from a machine in the same room or across the planet.
Compilation of code
When you compile the code, the Java compiler creates machine code (called byte code)
for a hypothetical machine called Java Virtual Machine (JVM). The JVM is supposed to execute
the byte code. The JVM is created for overcoming the issue of portability. The code is written
and compiled for one machine and interpreted on all machines. This machine is called Java
Virtual Machine.
Compiling and interpreting Java Source Code

PC Compiler

Source
Code
..
..

Byte code
Macintosh
Compiler

..
SPARC

Java

Java
Interpreter
(PC)

(Platform
indepen
dent)

Java
Interpreter
(Macintosh)

Java
Interpreter
(Sparc)

Compiler

16

COMPUTERIZED MOBILE STORE MANAGEMENT SYSTEM

During run-time the Java interpreter tricks the bytecode file into thinking that it is
running on a Java Virtual Machine. In reality this could be a Intel Pentium Windows 95 or
SunSARC station running Solaris or Apple Macintosh running system and all could receive code
from any computer through Internet and run the Applets.
Simple
Java was designed to be easy for the Professional programmer to learn and to use
effectively. If you are an experienced C++ programmer, learning Java will be even easier.
Because Java inherits the C/C++ syntax and many of the object oriented features of C++. Most
of the confusing concepts from C++ are either left out of Java or implemented in a cleaner, more
approachable manner. In Java there are a small number of clearly defined ways to accomplish a
given task.
Object-Oriented
Java was not designed to be source-code compatible with any other language. This
allowed the Java team the freedom to design with a blank slate. One outcome of this was a clean
usable, pragmatic approach to objects. The object model in Java is simple and easy to extend,
while simple types, such as integers, are kept as high-performance non-objects.
Robust
The multi-platform environment of the Web places extraordinary demands on a program,
because the program must execute reliably in a variety of systems. The ability to create robust
programs was given a high priority in the design of Java. Java is strictly typed language; it
checks your code at compile time and run time.
Java virtually eliminates the problems of memory management and deallocation, which is
completely automatic. In a well-written Java program, all run time errors can and should be
managed by your program.
What Is JDBC?
JDBC is a Java API for executing SQL statements. (As a point of interest, JDBC is a
trademarked name and is not an acronym; nevertheless, JDBC is often thought of as standing for
Java Database Connectivity. It consists of a set of classes and interfaces written in the Java
programming language. JDBC provides a standard API for tool/database developers and makes it
possible to write database applications using a pure Java API.

17

COMPUTERIZED MOBILE STORE MANAGEMENT SYSTEM

Using JDBC, it is easy to send SQL statements to virtually any relational database. One
can write a single program using the JDBC API, and the program will be able to send SQL
statements to the appropriate database. The combinations of Java and JDBC lets a programmer
write it once and run it anywhere.
What Does JDBC Do?
Simply put, JDBC makes it possible to do three things:
Establish a connection with a database
Send SQL statements
Process the results.
JDBC versus ODBC and other APIs
At this point, Microsoft's ODBC (Open Database Connectivity) API is that probably the most
widely used programming interface for accessing relational databases. It offers the ability to
connect to almost all databases on almost all platforms.
So why not just use ODBC from Java? The answer is that you can use ODBC from Java, but
this is best done with the help of JDBC in the form of the JDBC-ODBC Bridge, which we will
cover shortly. The question now becomes "Why do you need JDBC?" There are several
answers to this question:
ODBC is not appropriate for direct use from Java because it uses a C interface. Calls from
Java to native C code have a number of drawbacks in the security, implementation, robustness,
and automatic portability of applications.
A literal translation of the ODBC C API into a Java API would not be desirable. For example,
Java has no pointers, and ODBC makes copious use of them, including the notoriously errorprone generic pointer "void *". You can think of JDBC as ODBC translated into an objectoriented interface that is natural for Java programmers.
ODBC is hard to learn. It mixes simple and advanced features together, and it has complex
options even for simple queries. JDBC, on the other hand, was designed to keep simple things
simple while allowing more advanced capabilities where required.
A Java API like JDBC is needed in order to enable a "pure Java" solution. When ODBC is
used, the ODBC driver manager and drivers must be manually installed on every client machine.
When the JDBC driver is written completely in Java, however, JDBC code is automatically
installable, portable, and secure on all Java platforms from network computers to mainframes.
18

COMPUTERIZED MOBILE STORE MANAGEMENT SYSTEM

Two-tier Model
The JDBC API supports both two-tier and three-tier models for database access.
In the two-tier model, a Java applet or application talks directly to the database. This requires a
JDBC driver that can communicate with the particular database management system being
accessed. A user's SQL statements are delivered to the database, and the results of those
statements are sent back to the user. The database may be located on another machine to which
the user is connected via a network. This is referred to as a client/server configuration, with the
user's machine as the client, and the machine housing the database as the server. The network can
be an Intranet, which, for example, connects employees within a corporation, or it can be the
Internet.
In the three-tier model, commands are sent to a "middle tier" of services, which then send
SQL statements to the database. The database processes the SQL statements and sends the results
back to the middle tier, which then

Fig. Two-tier Architecture

sends them to the user. MIS directors find the three-tier model very attractive because
the middle tier makes it possible to maintain control over access and the kinds of updates that
can made to corporate data. Another advantage is that when there is a middle tier, the user can
employ an easy-to-use higher-level API which is translated by the middle tier into the

19

COMPUTERIZED MOBILE STORE MANAGEMENT SYSTEM

appropriate low-level calls. Finally, in many cases the three-tier architecture can provide
performance advantages.
The main disadvantages of the 2-tier model are as follows:
Scalability: a key concern with the 2-tier model is scalability. Application performance can be
expected to degrade rapidly when the number of concurrent users reaches a threshold between a
few hundred and one thousand users. This is true even for Large database servers. The chief
reason is that each client requires its own connection and each connection requires CPU and
memory. As the number of connections increases,
The database performance degrades. Poor Logic Sharing: Traditional two-tier
architectures keep business logic on the client. When logic is in the client, it is usually more
difficult

to

re-use

logic

between

applications

and

amongst

tools.

Application Distribution: Application changes have to be distributed to each client. When there
are a large number of users, this entails considerable administrative overhead.
Remote Usage: Remote users (e.g. customers), probably do not want to install your application
on their clients -- they would prefer "thin" clients where minimal (or no)
Client software installation is required.
Database Structure: other applications that access your database will become
dependent on the existing database structure. This means that it is more difficult to redesign the
database since other applications are intimate with the actual database structure.
JDBC Driver Types
The JDBC drivers that we are aware of at this time fit into one of four categories:
JDBC-ODBC bridge plus ODBC driver
Native-API partly-Java driver
JDBC-Net pure Java driver
Native-protocol pure Java driver
JDBC-ODBC Bridge
If possible, use a Pure Java JDBC driver instead of the Bridge and an ODBC driver. This
completely eliminates the client configuration required by ODBC. It also eliminates the potential
that the Java VM could be corrupted by an error in the native code brought in by the Bridge (that

20

COMPUTERIZED MOBILE STORE MANAGEMENT SYSTEM

is, the Bridge native library, the ODBC driver manager library, the ODBC driver library, and the
database client library).
What Is the JDBC- ODBC Bridge?
The JDBC-ODBC Bridge is a JDBC driver, which implements JDBC operations by
translating them into ODBC operations. To ODBC it appears as a normal application program.
The Bridge implements JDBC for any database for which an ODBC driver is available. The
Bridge is implemented as the
sun.jdbc.odbc Java package and contains a native library used to access ODBC. The Bridge is a
joint development of Intersolv and JavaSoft.

ORACLE 9i:
Introduction to Oracle 9i
Oracle is a purely Object Oriented - Relational Database Management System (RDBMS)
application. Oracle9i is designed to optimize traditional performance, Internet and Intranet
applications and to stimulate the emerging hosted application. Oracle9i new features help
management to host the services software for anyone to access it from anywhere. The three
components of the Oracle9i are as follows:

Oracle9i Database
Oracle9i Application Server
Oracle9i Developer suit.
Oracle9i Database Features
The Oracle9i database introduces the following advanced and automated design features that
refine Oracle9i applications server and Oracle9i developer suit to optimize performance for
application and the emerging hosted application market. Oracle9i real application clusters
provide out-of-the-box, linear scaling transparency, compatibility with all applications without
redesign, and the ability to rapidly add notes and disks.
An integrated system management product creates a complete view of all critical components
that drive e-business processes. From the client and application server to the database and host,

21

COMPUTERIZED MOBILE STORE MANAGEMENT SYSTEM

Oracle9i quickly and completely assesses the overall health and e-business infrastructure. Setting
a new standard for high availability, Oracle9i introduces powerful new functionality in areas of
disaster recovery, system fault recovery, and planned downtime.
Oracle9i offers the most secure Internet platform for protecting company information through
multiple layers of security for data, users, and companies. Included are features for building
internet-scale applications, for providing security for users, and for keeping data from different
hosted user communities separate.
In Oracle9i PL/SQL supports the complete range of syntax for SQL statements, such as INSERT,
UPDATE, DELETE and so on. It also provides more consistent error checking.

Oracle9i Application Server

Recognized as the leading application server for database driven websites, Oracle9i
application server offers the industry most innovative and comprehensive set of middle-tierservices.
Continued innovation with comprehensive middle-tier services, ranging from self-service
enterprise portals, to e-stores and supplier exchange, sustains the Oracle9i application server at
the industrys preferred application server for database driven websites.
The new caching technology in Oracle9i can dramatically increase website performance,
scalability and availability greater number of users can be provided with more personalized,
dynamic web content without adding more application or database servers.
Information in any database or Internet application is easily available through Oracle9i support
for each wireless devices specific markup language is no longer necessary. Oracle9i application
server has built-in reporting and ad hoc query functionality to derive business intelligence after
web site deployment.
Embedded SQL Statements

22

COMPUTERIZED MOBILE STORE MANAGEMENT SYSTEM

The term embedded SQL refers to SQL statements placed within an application program.
Because it houses the SQL statements, the application program is called a host program, and the
language in which it is written is called the host language.
To manipulate and query Oracle data, you use the INSERT, UPDATE, DELETE, and SELECT
statements. INSERT adds rows of data to database tables, UPDATE modifies rows, DELETE
removes unwanted rows, and SELECT retrieves rows that meet your search condition. The
powerful SET ROLE statement lets you dynamically manage database privileges. A role is a
named group of related system and/or object privileges granted to users or other roles. Role
definitions are stored in the Oracle data dictionary. Your applications can use the SET ROLE
statement to enable and disable roles as needed.

5. TESTING AND PERFORMANCE EVALUATYION

Testing is process of executing a program with the intent of finding an error .If testing is
conducted successfully, it uncover errors in the software .testing demonstrates that software
functions appear to be wording according to specifications, and performance requirements
appear to have been net. In addition, data collected as testing is conducted provide a good
indication of software reliability of defects, it can only show that software defects are present.
The software testing is one of the two ways.
Knowing the specified function that a product has been designed to perform, test cab be
connected that demonstrate each function is fully operational. This test approach is called Black
Box testing.
Knowing the internal working of a product, test can be performed to ensure that the
internal operation of the product performs according to specification and all internal components
have been adequately exercised, This test approach is called white Box testing

5.1 TESTING TECHNIQUES

5.1.1 WHITE BOX TESTING (GLASS-BOX TESTING):

23

COMPUTERIZED MOBILE STORE MANAGEMENT SYSTEM

White box testing is a test case design methods that uses control structure of the
procedural design to derive test cases, using white box testing methods, the test cases should:

Guarantee that all independent paths within a module have been exercised at least once.

Exercise all decision on their true and false sides.

Execute all loops at their boundaries and within their operational bounds

Exercise internal data structures to ensure their validity.

By using white box testing we can identify what are the errors and we can define the test

eases where it will needed. So in this project work we defined test cases that are the targets to
reach to built the software.

5.1.2 BLACK BOX TESTING:

Black box testing method focuses on the functional requirements of the software. this
testing enables to derive sets of input conditions that will fully exercise all functional
requirements of a program. black box testing attempts to find errors in the following categories:

Incorrect or missing functions

Interface errors

Errors in data structures or external database access

Performance errors

Initialization and termination errors

White box testing is performed early in the testing process; Black box testing is applied

during later stages of testing , Black box.

Testing purposely disregarded control structure and focused on the information domain.
By using this testing in my project work I will find what is the error will occur in future
and what are the solutions and how to interface error, it will work on through out the p0rocess
for checking of maintenance of material.

24

COMPUTERIZED MOBILE STORE MANAGEMENT SYSTEM

5.1.2.1TEST CASES:
Test

Test

CaseActions to beExpected

Case Id Description

Performed

Actual

Value

Result

Value

Login

PageHome Page needsHome Page

Validation
to be Open
Password
Adding
MobileMobile
PhoneMobile DetailsSave PhoneSuccess
Phones

Username,

needs to store inSuccessfully

Success

Details

the database
saved
MobileMobile
PhoneMobile DetailsSearch PhoneSuccess

Search

Phones
Add Customer

needs to be search Will Displayed Details

Customer DetailsCustomer
Add

Success

needs store in theDetails will beCustomer

database
5

Search Customer Customer

stored in theDetails
database
DetailsCustomer

need to be Search Details

needs

Displayed
toBill will

Add
willCustomer

Details
beGenerate Bill Success

Bill Generation

Bill

Sales Reports

Generate
Generated
Reports need to beReports will beGenerate
Generate

Generated

25

Success

Report

Success

COMPUTERIZED MOBILE STORE MANAGEMENT SYSTEM

5.2 TESTING STRATEGIES

Testing is set of activities that can be planned in advanced and conducted systematically,
a strategy for software testing must accommodation low level tests that are necessary to verify
that a small that validate major system function against customer requirements.
Software testing is one element of verification and validation. Verification refers to the
set of activities ensure that software correctly implements as specific function .validation refers
to a different set of activities that ensure that the software that the software that has been builds is
traceable to customer requirements.
The objective of software testing to uncovers .to fulfill this objective, a series of test steps
unit, integration, validation and system tests are planned and executed .Each test step is
accomplished through a series of systematic test technique that assist in the design of test cases.
With testing step, the level of abstraction with which software is considered is broadened.

5.2.1 UNIT TESTING:

Unit testing focuses verification effort on the smallest unit of software design module.
The unit test always white box oriented .The tests that data occur as part of unit testing are
testing the module interface, examining the local data structures, testing the boundary conditions
execution all the independent paths and testing error handling paths.

5.2.2 INTERGATION TESTING:

Integration testing is a systematic technique or construction the program structure while
at the same time conducting tests to uncover errors associated with interfacing. Scope of testing
summarizes the specific functional performance, and internal design characteristics that are to be
tested. It employs top-down testing and bottom-up testing methods for this case.

5.2.3 VALIDATION TESTING:

Validation testing demonstrates tractability to software requirements.
Validation succeeds when the software function in a manner that can be reasonably expected by

26

COMPUTERIZED MOBILE STORE MANAGEMENT SYSTEM

the customer. The major elements of the process are alpha and data testing along the
configuration review.

5.2.4 SYSTEM TESTING:

System testing validates software once it has been incorporated into a larger system
.software is incorporated with other system elements and a series of system integration and
validation tests are conducted .system testing is actually a series of different test whose primary
purpose is to fully exercise the computer based system.
Once the system has been developed it has to be tested. In the present system we have to
take care of valid property and assessment numbers i.e. there should not exists any duplicate
number in each case. Care should be taken that the appropriate data is retrieved in response to the
queries.
The main thing, which should be considered, is the user interface. we have to see whether
the user finds any difficulty in executing the system. Necessary messages and prompts should
appear as needed to necessitate the users and make him alert if the invalid actions and help him
to redo the required action. All the above cases any more are tested by providing the required
data as input to the system so that any more tested by providing the required data as input to the
system so that any uncovered errors can be traced out.
For unit testing, I rested each module, as they are working well independently, went for
integration testing. I integrated all the modules and after integration also they gave same results.
For validation I checked for all different type of inputs and they gave correct results, and did the
total process will satisfy the total validations that will checked and find out the results.

27

COMPUTERIZED MOBILE STORE MANAGEMENT SYSTEM

28

COMPUTERIZED MOBILE STORE MANAGEMENT SYSTEM

7.2. Bibliography:
1. FOR Net Beans INSTALLATION
www.netbeans.org
2. FOR DEPLOYMENT AND PACKING ON SERVER
www.developer.com
www.15seconds.com
3. Roger S.Pressman,
SOFTWARE ENGINEERING-APRACTITIONERS APPROACH,2001
Mc Graw-Hill international Edition,States.
4. FOR Java,Swings,Jdbc
The Complete Reference Java2 Sixth Edition, by Naughton Schildt, Tata McGraw Hill
Edition.
www.javatutorials.com
www.google.com
www.kodejava.org
5. Ryan K.Stephens, Ronald R. Plew, Bryan Morgan, and Jeff Perkins
SQL in 21 Days, Second Edition, Techmedia.

29