mobile doc

8/17/2019 Mobile Doc

1/29

COMPUTERIZED MOBILE STORE MANAGEMENT SYSTEM

1. Economical Feasiili!"

#. Tec$nical Feasiili!"

%. O&e'a!ional Feasiili!"

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

1 Cos! !o con()c! a *)ll s"s!em in+es!i,a!ion

2 Cos! o* $a'(-a'e an( so*!-a'e *o' !$e class o* a&&lica!ion ein, consi(e'e(

3 Bene*i!s in !$e *o'm o* 'e()ce( cos!s o' *e- cos!l" e''o's.

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

organiation. The implementation will incur no extra cost. There is no additional cost involved inmanpower requirements for the proposed system. The system also reduces manual file

maintenance wor! and employs fewer people. Thus in the long run, it is beneficial and so is

economically feasible.

TECNICAL 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. "uring 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. "oes the necessary technology exits to do

#


2/29


what is suggested.

1 "oes the proposed equipment have the technical capacity to hold the data required to use

new system$

2 %ill the proposed system provide adequate response to inquiries, regardless of number or

location of users$

3 Can system be expand of developed

4 &re there technical guarantees of accuracy reliability, ease of access and security$

OPERATIONAL FEASIBILITY

#.%.1 SOFT/ARE RE0UIREMENTS

'perating system ( %indows )amily

)ront-*nd ( +&&

ac!-*nd ( 'racle i

#.%.# ARD/ARE RE0UIREMENTS

/rocessor ( Intel /entium III

0am ( 1234

5ard "is! ( 167

#.2 P'ocess Mo(els

8oftware systems come and go through a series of passages that account for their

inception, initial development, productive operation, up!eep, and retirement from one generation

to another. This article categories and examines a number of methods for describing or

modeling how software systems are developed. It begins with bac!ground and definitions of

traditional software life cycle models that dominate most textboo! 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 organiing

software *ngineering projects and technologies.

In contrast to software life cycle models, software process models often represent a

networ!ed sequence of activities, objects, transformations, and events that embody strategies for

1


3/29


accomplishing software evolution. 8uch models can be used to develop more precise and

formalied descriptions of software life cycle activities. Their power emerges from their

utiliation of a sufficiently rich notation, syntax, or semantics, often suitable for computational

processing.

8oftware process networ!s can be viewed as representing multiple interconnected

tas! chains 9:ling #;1, 7ag #;


4/29


#.2.1. /a!e'*all Mo(el

'ne such approach=process used in 8oftware "evelopment is ?The %aterfall 4odel?. %aterfall

approach was first /rocess 4odel to be introduced and followed widely in 8oftware *ngineeringto ensure success of the project. In ?The %aterfall? approach, the whole process of software

development is divided into separate process phases. The phases in %aterfall model are(

0equirement 8pecifications phase, 8oftware "esign, Implementation and Testing

4aintenance. &ll 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 ?%aterfall

4odel?. &ll the methods and processes underta!en in %aterfall 4odel are more visible.

Fi,#.2.1./a!e'*all Mo(el

The stages of ?The %aterfall 4odel? are(

Re3)i'emen! Anal"sis 4 De*ini!ion &ll possible requirements of the system to be developed

are captured in this phase. 0equirements are set of functionalities and constraints that the end-

user 9who will be using the system< expects from the system. The requirements are gathered

from the end-user by consultation, these requirements are analyed for their validity and the

B


5/29


possibility of incorporating the requirements in the system to be development is also studied.

)inally, a 0equirement 8pecification document is created which serves the purpose of guideline

for the next phase of the model.

S"s!em 4 So*!-a'e Desi,n efore a starting for actual coding, it is highly important to

understand what we are going to create and what it should loo! li!e$ The requirement

specifications from first phase are studied in this phase and system design is prepared. 8ystem

"esign 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.

Im&lemen!a!ion 4 Uni! Tes!in, 'n receiving system design documents, the wor! 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. *ach unit is developed and tested for its

functionalityD this is referred to as Enit Testing. Enit testing mainly verifies if the modules=units

meet their specifications.

In!e,'a!ion 4 S"s!em Tes!in, &s 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 chec! if all modules=units coordinate between each other

and the system as a whole behaves as per the specifications. &fter successfully testing the

software, it is delivered to the customer.

O&e'a!ions 4 Main!enance This phase of ?The %aterfall 4odel? is virtually never ending

phase 9ery long


6/29


#< &s it is very important to gather all possible requirements during the 0equirement 7athering

and &nalysis phase in order to properly design the system, not all requirements are received at

once

1< 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 9related to a phase< are solved during the same phase.

%. DESIGN

8G8T*4 "*8I7F /hase follows system analysis phase. "esign is maintaining a record

proof design division and providing a blue print for the implementation phase. "esign is the

bridge between system analysis and system implementation.

8ystem design is transition from a use oriented, document oriented to programmers are database

personals. The design is a solution, a Hhow 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. "esign goes through logical and

physical stages of development, logical design reviews the presentJs physical system, prepare

input and output specification, detail the implementation plan and prepare a logical design

wal!through.

The database tables are designed by analying 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, careJs to be ta!en 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.

OB5ECTI6ES OF DESIGN

3


7/29


8ystem design is li!e a blue print for a building, it specifies all the features that are to be

in finished product. "esign 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.

PYSICAL 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

8ystem 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. "uring

the system design the logical model converted into the physical system.

& 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 Computeried 4obile 8tore 4anagement 8ystem database tables, input screens

and output report design etc. were designed.

The database tables were designed with necessary fields. The redundancy and duplication

K


8/29


of fields are avoided.

&ll the input screens in this system are user Lfriendly and understandable format. &lso

the sies of all the screens are standardied.

4enus designed in this system are brief, compact and self explanatory. The menus are

sharp and any novice user can invo!e the system .popup menus are also used to invo!e various

sub menus.

%.# DATABASE NORMALIZATIONS

Formaliation is a technique of separating redundant fields and brea!ing up a large table

into smaller ones. &ll the tables have been normalied up to the third normal form. Formaliation 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.

Formaliation is carried for following reasons(

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

represented.

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

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

4 To reduce the need to restructure or recognie data when new application requirements

arise.

;


9/29


5 These attempts to remove redundant data avoid data inconsistencies and prevent update

anomalies.

This results in a simpler or more natural data model. & normalied database more clearly

reflects the entities and relationships in the real world.

0elational 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

& relation is said to be in #F) if all the underline domain of attributes contain simple

indivisible values.

#. SECOND NORMAL FORM

The 1F) is based on the concept of full functional dependency. & relation is said to be in

1F) and every non !ey attribute is functionally dependency on candidate !ey of the table.

%. TIRD NORMAL FORM

The AF) is based on the concept of transitive dependency. & relation in 1F) is said to be

in AF) if every non !ey attribute is non-transitively dependent on the primary !ey.

%.% DATADICTIONARY

&fter carefully understanding the requirements of the client, the entire data storage

requirements are divided into tables. The below tables are normalied to avoid any anomalies

during the course of data entry.


10/29


%.7.7. CLASS RESPONSIBILITY COLLABORATION 8CRC9 CARDS:

ClsC)s!ome'

0esponsibility Collaboration

#. &dd the Customer. 4obile /hone

1. 8earch the Customer 4obile /hone

A.Epdate the Customer 4obile /hone

B."elete the Customer 4obile /hone

ClsBill


Calculate the ill for Customer. 4obile /hone, Customer.

ClsMoileP$one


#. &dd new 4obile /hone. Customer

1. 8earch 4obile /hone. Customer

A. Epdate 4obile /hone. Customer

B."elete 4obile /hone Customer

ClsSalesRe&o'!s


#. "aily 0eports Customer, ill, 4obile /hone

#6


11/29


1. 4onthly 0eports Customer, ill, 4obile /hone

A. Gearly 0eports Customer, ill, 4obile /hone

%.7.; COLLABORATION DIAGRAM

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

particular.

#. Nogin 1. 8elect A. /erform the

Type of action &ction

to be /erform 8elected

Fi,%.7.; Collao'a!ion (ia,'am *o' Moile P$one !'ansac!ion

2. IMPLIMENTATION

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

8ystem

&dmin

##


12/29


operational one. &part from planning, the major tas!s of preparing for implementation or

education and training of users. Implementation includes following activities(-

1 'btaining and installing the system hardware.

2 /roviding user access to the system.

3 Creating and updating the database.

4 Training the users on the new database.

5 "ocumenting the system for its users.

6 *valuating the operation and use of the system.

Im&lemen!a!ion Me!$o(s:

There are four basic methods of implementation(-

1 "irect conversion

2 /arallel conversion

3 /ilot conversion

4 /hasing conversion

Di'ec! Con+e'sion:

Desc'i&!ion

In this method the new one replaces the old system. This ma!es organiation to fully rely

on the new system.

A(+an!a,es:

This method provides experience and live test before implementation.

Disa(+an!a,es:

This method may give the impression that the old system is unreliable and not error free.

P$ase( Con+e'sion:

#1


13/29


Desc'i&!ion:

In this method, the system is implemented gradually across all users.

A(+an!a,es:

It allows some users to ta!e advantages of the system early. It allows training and

installing without unnecessary use of resources.

Disa(+an!a,es:

& long phase-in causes user problems whether the project goes well9over enthusiasm< or

not 9resistance or lac! of fair trail


14/29


Im&o'!ance o* 5a+a !o !$e In!e'ne!

+ava has had a profound effect on the Internet. This is becauseD +ava expands the

Eniverse of objects that can move about freely in Cyberspace. In a networ!, two categories of

objects are transmitted between the 8erver and the /ersonal computer. They are( /assive

information and "ynamic active programs. The "ynamic, 8elf-executing programs cause serious

problems in the areas of 8ecurity and probability. ut, +ava addresses those concerns and by

doing so, has opened the door to an exciting new form of program called the &pplet.

5a+a can e )se( !o c'ea!e !-o !"&es o* &'o,'ams

&pplications and &pplets( &n application is a program that runs on our Computer under

the operating system of that computer. It is more or less li!e one creating using C or COO. +avaJs

ability to create &pplets ma!es it important. &n &pplet is an application designed to be

transmitted over the Internet and executed by a +ava Lcompatible web browser. &n applet is

actually a tiny +ava program, dynamically downloaded across the networ!, just li!e an image.

ut the difference is, it is an intelligent program, not just a media file. It can react to the user

input and dynamically change.

Fea!)'es O* 5a+a

Sec)'i!"

*very time you that you download a Hnormal program, you are ris!ing a viral infection.

/rior to +ava, most users did not download executable programs frequently, and those who did

scanned them for viruses prior to execution. 4ost 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, ban! account balances, and passwords. +ava answers both these concerns by providing

a Hfirewall between a networ! application and your computer.

%hen you use a +ava-compatible %eb browser, you can safely download +ava applets without

fear of virus infection or malicious intent.

Po'!aili!"

)or 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 .&s you

will see, the same mechanism that helps ensure security also helps create portability. Indeed,

+avaJs solution to these two problems is both elegant and efficient.

#B


15/29


T$e B"!e co(e

The !ey that allows the +ava to solve the security and portability problems is that the

output of +ava compiler is yte code. yte code is a highly optimied set of instructions

designed to be executed by the +ava run-time system, which is called the +ava irtual 4achine

9+4


16/29


5a+a A'c$i!ec!)'e

+ava architecture provides a portable, robust, high performing environment for

development. +ava provides portability by compiling the byte codes for the +ava irtual 4achine,

which is then interpreted on each platform by the run-time environment. +ava is a dynamic

system, able to load code when needed from a machine in the same room or across the planet.

Com&ila!ion o* co(e

%hen you compile the code, the +ava compiler creates machine code 9called byte code<

for a hypothetical machine called +ava irtual 4achine 9+4


17/29


"uring run-time the +ava interpreter tric!s the bytecode file into thin!ing that it is

running on a +ava irtual 4achine. In reality this could be a Intel /entium %indows 2 or

8un8&0C station running 8olaris or &pple 4acintosh running system and all could receive code

from any computer through Internet and run the &pplets.

Sim&le

+ava was designed to be easy for the /rofessional programmer to learn and to use

effectively. If you are an experienced COO programmer, learning +ava will be even easier.

ecause +ava inherits the C=COO syntax and many of the object oriented features of COO. 4ost

of the confusing concepts from COO are either left out of +ava or implemented in a cleaner, more

approachable manner. In +ava there are a small number of clearly defined ways to accomplish a

given tas!.

O?ec!:O'ien!e(

+ava was not designed to be source-code compatible with any other language. This

allowed the +ava team the freedom to design with a blan! slate. 'ne outcome of this was a clean

usable, pragmatic approach to objects. The object model in +ava is simple and easy to extend,

while simple types, such as integers, are !ept as high-performance non-objects.

Ro)s!

The multi-platform environment of the %eb 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 +ava. +ava is strictly typed languageD it

chec!s your code at compile time and run time.

+ava virtually eliminates the problems of memory management and deallocation, which is

completely automatic. In a well-written +ava program, all run time errors can Land should Lbe

managed by your program.

/$a! Is 5DBC@

+"C is a +ava &/I for executing 8PN statements. 9&s a point of interest, +"C is a

trademar!ed name and is not an acronymD nevertheless, +"C is often thought of as standing for

+ava "atabase Connectivity. It consists of a set of classes and interfaces written in the +ava

programming language. +"C provides a standard &/I for tool=database developers and ma!es it

possible to write database applications using a pure 5a+a API.

#K


18/29


Esing +"C, it is easy to send 8PN statements to virtually any relational database. 'ne

can write a single program using the +"C &/I, and the program will be able to send 8PN

statements to the appropriate database. The combinations of +ava and +"C lets a programmer

write it once and run it anywhere.

/$a! Does 5DBC Do@

8imply put, +"C ma!es it possible to do three things(

*stablish a connection with a database

8end 8PN statements

/rocess the results.

+"C versus '"C and other &/Is

&t this point, 4icrosoft>s '"C 9'pen "atabase Connectivity< &/I 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.

8o why not just use '"C from +ava$ The answer is that you can use '"C from +ava, but

this is best done with the help of +"C in the form of the +"C-'"C ridge, which we will

cover shortly. The question now becomes ?%hy do you need +"C$? T$e'e a'e se+e'al

ans-e's !o !$is 3)es!ion

'"C is not appropriate for direct use from +ava because it uses a C interface. Calls from

+ava to native C code have a number of drawbac!s in the security, implementation, robustness,

and automatic portability of applications.

& literal translation of the '"C C &/I into a +ava &/I would not be desirable. )or example,

+ava has no pointers, and '"C ma!es copious use of them, including the notoriously error-

prone generic pointer ?void Q?. Gou can thin! of +"C as '"C translated into an object-

oriented interface that is natural for +ava programmers.

'"C is hard to learn. It mixes simple and advanced features together, and it has complex

options even for simple queries. +"C, on the other hand, was designed to !eep simple thingssimple while allowing more advanced capabilities where required.

& +ava &/I li!e +"C is needed in order to enable a ?pure +ava? solution. %hen '"C is

used, the '"C driver manager and drivers must be manually installed on every client machine.

%hen the +"C driver is written completely in +ava, however, +"C code is automatically

installable, portable, and secure on all +ava platforms from networ! computers to mainframes.

#;


19/29


T-o:!ie' Mo(el

The +"C &/I supports both two-tier and three-tier models for database access.

In the two-tier model, a +ava applet or application tal!s directly to the database. This requires a

+"C driver that can communicate with the particular database management system being

accessed. & user>s 8PN statements are delivered to the database, and the results of those

statements are sent bac! to the user. The database may be located on another machine to which

the user is connected via a networ!. 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 networ! 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

8PN statements to the database. The database processes the 8PN statements and sends the results

bac! to the middle tier, which then

)ig. Two-tier &rchitecture

sends them to the user. 4I8 directors find the three-tier model very attractive because

the middle tier ma!es it possible to maintain control over access and the !inds of updates that

can made to corporate data. &nother advantage is that when there is a middle tier, the user can

employ an easy-to-use higher-level &/I which is translated by the middle tier into the

#


20/29


appropriate low-level calls. )inally, in many cases the three-tier architecture can provide

performance advantages.

T$e main (isa(+an!a,es o* !$e #:!ie' mo(el a'e as *ollo-s

8calability( a !ey concern with the 1-tier model is scalability. &pplication 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 Narge database servers. The chief

reason is that each client requires its own connection and each connection requires C/E and

memory. &s the number of connections increases,

The database performance degrades. /oor Nogic 8haring( Traditional two-tier

architectures !eep business logic on the client. %hen logic is in the client, it is usually more

difficult to re-use logic between applications and amongst tools.

&pplication "istribution( &pplication changes have to be distributed to each client. %hen there

are a large number of users, this entails considerable administrative overhead.

0emote Esage( 0emote users 9e.g. customers


21/29


is, the ridge native library, the '"C driver manager library, the '"C driver library, and the

database client library


22/29


'raclei quic!ly and completely assesses the overall health and e-business infrastructure. 8etting

a new standard for high availability, 'raclei introduces powerful new functionality in areas of

disaster recovery, system fault recovery, and planned downtime.

'raclei offers the most secure Internet platform for protecting company information throughmultiple layers of security for data, users, and companies. Included are features for building

internet-scale applications, for providing security for users, and for !eeping data from different

hosted user communities separate.

In 'raclei /N=8PN supports the complete range of syntax for 8PN statements, such as IF8*0T,

E/"&T*, "*N*T* and so on. It also provides more consistent error chec!ing.

O'aclei A&&lica!ion Se'+e'

0ecognied as the leading application server for database driven websites, 'raclei

application server offers the industry most innovative and comprehensive set of middle-tier-

services.

Continued innovation with comprehensive middle-tier services, ranging from self-service

enterprise portals, to e-stores and supplier exchange, sustains the 'raclei application server at

the industryJs preferred application server for database driven websites.

The new caching technology in 'raclei can dramatically increase website performance,

scalability and availability greater number of users can be provided with more personalied,

dynamic web content without adding more application or database servers.

Information in any database or Internet application is easily available through 'raclei support

for each wireless devices specific mar!up language is no longer necessary. 'raclei application

server has built-in reporting and ad hoc query functionality to derive business intelligence after

web site deployment.

Embedded SQL Statements

11


23/29


The term embedded SQL refers to 8PN statements placed within an application program.

ecause it houses the 8PN 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 'racle data, you use the IF8*0T, E/"&T*, "*N*T*, and 8*N*CTstatements. IF8*0T adds rows of data to database tables, E/"&T* modifies rows, "*N*T*

removes unwanted rows, and 8*N*CT retrieves rows that meet your search condition. The

powerful 8*T 0'N* statement lets you dynamically manage database privileges. & role is a

named group of related system and=or object privileges granted to users or other roles. 0ole

definitions are stored in the 'racle data dictionary. Gour applications can use the 8*T 0'N*

statement to enable and disable roles as needed.

7. TESTING AND PERFORMANCE E6ALUATYION

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.

:nowing 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 lac!

ox testing.

:nowing the internal wor!ing 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 ox testing

7.1 TESTING TECNI0UES

7.1.1 /ITE BO TESTING =GLASS:BO TESTING>

1A


24/29


%hite 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(

1 7uarantee that all independent paths within a module have been exercised at least once.

2 *xercise all decision on their true and false sides.

3 *xecute all loops at their boundaries and within their operational bounds

4 *xercise internal data structures to ensure their validity.

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

eases where it will needed. 8o in this project wor! we defined test cases that are the targets to

reach to built the software.

7.1.# BLAC BO TESTING

lac! 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. blac! box testing attempts to find errors in the following categories(

1

Incorrect or missing functions2 Interface errors

3 *rrors in data structures or external database access

4 /erformance errors

5 Initialiation and termination errors

%hite box testing is performed early in the testing processD lac! box testing is applied

during later stages of testing , lac! box.

Testing purposely disregarded control structure and focused on the information domain.

y using this testing in my project wor! I will find what is the error will occur in future

and what are the solutions and how to interface error, it will wor! on through out the p6rocess

for chec!ing of maintenance of material.

1B


25/29


7.1.#.1TEST CASES

Tes!

Case I(

Tes! Case

Desc'i&!ion

Ac!ions !o e

Pe'*o'me(

E&ec!e(

6al)e

Ac!)al

6al)e

Res)l!

# Nogin /age

alidation

5ome /age needs

to be 'pen

5ome /age Esername,

/assword

8uccess

1 &dding 4obile

/hones

4obile /hone

needs to store in

the database

4obile "etails

8uccessfully

saved

8ave /hone

"etails

8uccess

A 8earch 4obile

/hones

4obile /hone

needs to be search

4obile "etails

%ill "isplayed

8earch /hone

"etails

8uccess

B &dd Customer Customer "etails

needs store in the

database

Customer

"etails will be

stored in the

database

&dd

Customer

"etails

8uccess

2 8earch Customer Customer "etails

need to be 8earch

Customer

"etails will

"isplayed

&dd

Customer

"etails

8uccess

3 ill 7eneration ill needs to

7enerate

ill will be

7enerated

7enerate ill 8uccess

K 8ales 0eports 0eports need to be

7enerate

0eports will be

7enerated

7enerate

0eport

8uccess

12


26/29


7.# 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.

8oftware testing is one element of verification and validation. erification 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 .*ach test step is

accomplished through a series of systematic test technique that assist in the design of test cases.

%ith testing step, the level of abstraction with which software is considered is broadened.

7.#.1 UNIT TESTING

Enit 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.

7.#.# 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. 8cope of testing

summaries 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.

7.#.% 6ALIDATION TESTING

alidation testing demonstrates tractability to software requirements.

alidation succeeds when the software function in a manner that can be reasonably expected by

13


27/29


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

configuration review.

7.#.2 SYSTEM TESTING

8ystem 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 Lbased system.

'nce the system has been developed it has to be tested. In the present system we have to

ta!e care of valid property and assessment numbers i.e. there should not exists any duplicate

number in each case. Care should be ta!en 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. Fecessary messages and prompts should

appear as needed to necessitate the users and ma!e him alert if the invalid actions and help him

to redo the required action. &ll 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 thesystem so that any uncovered errors can be traced out.

)or unit testing, I rested each module, as they are wor!ing well independently, went for

integration testing. I integrated all the modules and after integration also they gave same results.

)or validation I chec!ed for all different type of inputs and they gave correct results, and did the

total process will satisfy the total validations that will chec!ed and find out the results.

1K


28/29


1;


29/29


.#. Bilio,'a&$"

#. )'0 Fet eans IF8T&NN&TI'F

www.netbeans.org

1. )'0 "*/N'G4*FT &F" /&C:IF7 'F 8*0*0

www.developer.com

www.#2seconds.com

A. 0oger 8./ressman,

8')T%&0* *F7IF**0IF7-&/0&CTITI'F*0J8 &//0'&C5,166#

4c 7raw-5ill international *dition,8tates.

B. )'0 +ava,8wings,+dbc

The Complete 0eference +ava1 8ixth *dition, by Faughton 8childt, Tata 4c7raw 5ill

*dition.

www.javatutorials.com

www.google.comwww.!odejava.org

2. 0yan :.8tephens, 0onald 0. /lew, ryan 4organ, and +eff /er!ins

8PN in 1# "ays, 8econd *dition, Techmedia.
http://www.javatutorials.com/http://www.google.com/http://www.kodejava.org/http://www.google.com/http://www.kodejava.org/http://www.javatutorials.com/

mobile doc

Documents