FEASIBILITY STUDY:

Feasibility study is conducted once the problem is clearly understood. Feasibility

study is a high level capsule version of the entire system analysis and design
process. The objective is to determine quickly at a minimum expense how to solve
a problem. The purpose of feasibility is not to solve the problem but to determine
if the problem is worth solving.

The system has been tested for feasibility in the following points.

1. Technical Feasibility

2. Economical Feasibility

3. Operational Feasibility.

1. Technical Feasibility

The project entitles "Courier Service System” is technically feasibility because of

the below mentioned feature. The project was developed in Java which Graphical
User Interface.

It provides the high level of reliability, availability and compatibility. All

these make Java an appropriate language for this project. Thus the existing
software Java is a powerful language.

2. Economical Feasibility

The computerized system will help in automate the selection leading the profits
and details of the organization. With this software, the machine and manpower
utilization are expected to go up by 80-90% approximately. The costs incurred of
not creating the system are set to be great, because precious time can be wanted
bymanually.

3. Operational Feasibility

In this project, the management will know the details of each project where he may
be presented and the data will be maintained as decentralized and if any inquires
for that particular contract can be known as per their requirements and necessaries.

Implementation:

Implementation is the stage where the theoretical design is turned into a working
system. The most crucial stage in achieving a new successful system and in giving
confidence on the new system for the users that it will work efficiently and
effectively.

The system can be implemented only after thorough testing is done and if it is
found to work according to the specification.

It involves careful planning, investigation of the current system and its constraints
on implementation, design of methods to achieve the change over and an
evaluation of change over methods a part from planning. Two major tasks of
preparing the implementation are education and training of the users and testing of
the system.

The more complex the system being implemented, the more involved will be the
systems analysis and design effort required just for implementation.

The implementation phase comprises of several activities. The required hardware

and software acquisition is carried out. The system may require some software to
be developed. For this, programs are written and tested. The user then changes
 over to his new fully tested system and the old system is discontinued.

INTRODUCTION TO HTML4.0
What is the World Wide Web?

The World Wide Web is a network of information resources. The Web relies on
three mechanisms to make these resources readily available to the widest possible
audience.

1. A uniform naming scheme for locating resources on the Web (e.g. URLs)
2. Protocols, for access to named resources over the Web (e.g. HTTP)
3. Hypertext, for easy navigation among resources (e.g.HTML)

The ties between the three mechanisms are apparent throughout this specification

What is HTML?
To publish information for global distribution, one needs a universally understood
language, a kind of publishing mother tongue that all computers may potentially
understand. The publishing language used by the World Wide Web is HTML
(from Hyper Text Markup Language). HTML gives authors the means to
- Publish online documents with headings, text, tables, lists, photos, etc.
- Retrieve online information via hypertext links, at the click of a button
- Design forms for conducting transactions with remote services, for use in
searching for information, making reservations, ordering products etc.
- Include spread - sheets, video clips, sound clips, and other applications directly in
their documents.
A brief history of HTML:

HTML was originally developed by Tim Berners-Lee while at CERN, and

popularized by the Mosaic browser developed at NCSA. During the course of the
1990s it has blossomed with the explosive growth of the Web during this time.
HTML has been extended in a number of ways. The Web depends on Web page
authors and vendors sharing the same conventions for HTML. This has motivated
joint work on specifications for HTML.
HTML 2.0 (November 1995) was developed under the aegis of the Internet
Engineering Task Force (IETF) to codify common practice in late 1994. HTML
(1993) and ([HTML.30]) (1995) proposed much richer versions of HTML, despite
never receiving consensus in standards discussions, these drafts led to the adoption
of a range new features. The efforts of the World Wide Web Consortium’s
HTML working group to codify common in 1996 resulted in HTML 3.2 (January
1997). Most people agree that HTML documents should work well across
different browsers and platforms. Achieving interoperability lowers costs to
content providers since they must develop only one version of a document. If the
effort is not made, there is much greater risk that the Web will devolve into a
proprietary world of incompatible formats, ultimately reducing the Web’s
commercial potential for all participants.
SOFTWARE METHODOLOGY

The software methodology followed in this project includes the object-oriented

methodology and the application system development methodologies. The
description of these methodologies is given below.
Application System Development – A Life cycle Approach

Although there are a growing number of applications (such as decision support

systems) that should be developed using an experimental process strategy such as
prototyping, a significant amount of new development work continue to involve
major operational applications of broad scope. The application systems are large
highly structured. User task comprehension and developer task proficiency is
usually high. These factors suggest a linear or iterative assurance strategy. The
most common method for this stage class of problems is a system development life
cycle modal in which each stage of development is well defined and has
straightforward requirements for deliverables, feedback and sign off. The system
development life cycle is described in detail since it continues to be an appropriate
methodology for a significant part of new development work.

The basic idea of the system development life cycle is that there is a well-defined
process by which an application is conceived and developed and implemented. The
life cycle gives structure to a creative process. In order to manage and control the
development effort, it is necessary to know what should have been done, what has
been done, and what has yet to be accomplished. The phrases in the system
development life cycle provide a basis for management and control because they
define segments of the
 flow of work, which can be identified for managerial purposes and specifies the
documents or other deliverables to be produced in each phase.

The phases in the life cycle for information system development are described
differently by different writers, but the differences are primarily in the amount of
necessity and manner of categorization. There is a general agreement on the flow
of development steps and the necessity for control procedures at each stage.

The information system development cycle for an application consists of three

major stages.

1) Definition.
2) Development.
3) Installation and operation.

The first stage of the process, which defines the information requirements for a
feasible cost effective system. The requirements are then translated into a physical
system of forms, procedures, programs etc., by the system design, computer
programming and procedure development. The resulting system is test and put into
operation. No system is perfect so there is always a need for maintenance changes.
To complete the cycle, there should be a post audit of the system to evaluate how
well it performs and how well it meets the cost and performance specifications.
The stages of definition, development and installation and operation can therefore
be divided into smaller steps or phrases as follows.
Definition

Proposed definition : preparation of request for proposed applications.

Feasibility assessment : evaluation of feasibility and cost benefit of proposed
system.
Information requirement analysis : determination of information needed.

Design
Conceptual design : User-oriented design of application development.
Physical system design : Detailed design of flows and processes in applications
processing system and preparation of program specification.
Development
Program development : coding and testing of computer programs.
Procedure development : design of procedures and preparation of user
instructions.

Installation and operation

Conversion : final system test and conversion.

Operation and maintenance : Month to month operation and maintenance
Post audit : Evaluation of development process,application
system and results of use at the completion of the each phase, formal approval
sign-off is required from the users as well as from the manager of the project
development.
 Testing
Testing is a process of executing a program with the indent of finding an error.
Testing is a crucial element of software quality assurance and presents ultimate
review of specification, design and coding.

System Testing is an important phase. Testing represents an interesting anomaly

for the software. Thus a series of testing are performed for the proposed system
before the system is ready for user acceptance testing.

A good test case is one that has a high probability of finding an as

undiscovered error. A successful test is one that uncovers an as undiscovered error.

Testing Objectives:

Testing is a process of executing a program with the intent of finding an error

A good test case is one that has a probability of finding an as yet undiscovered
error
A successful test is one that uncovers an undiscovered error

Testing Principles:

All tests should be traceable to end user requirements

Tests should be planned long before testing begins
Testing should begin on a small scale and progress towards testing in large
Exhaustive testing is not possible
To be most effective testing should be conducted by a independent third party
The primary objective for test case design is to derive a set of tests that has the
highest livelihood for uncovering defects in software. To accomplish this objective
two different categories of test case design techniques are used. They are

White box testing.

Black box testing.

White-box testing:

White box testing focus on the program control structure. Test cases are
derived to ensure that all statements in the program have been executed at least
once during testing and that all logical conditions have been executed.

Block-box testing:

Black box testing is designed to validate functional requirements without regard to

the internal workings of a program. Black box testing mainly focuses on the
information domain of the software, deriving test cases by partitioning input and
output in a manner that provides through test coverage. Incorrect and missing
functions, interface errors, errors in data structures, error in functional logic are the
errors falling in this category.

Testing strategies:

A strategy for software testing must accommodate low-level tests that are
necessary to verify that all small source code segment has been correctly
implemented as well as high-level tests that validate major system functions
against customer requirements.

Testing fundamentals:
 Testing is a process of executing program with the intent of finding error. A
good test case is one that has high probability of finding an undiscovered error. If
testing is conducted successfully it uncovers the errors in the software. Testing
cannot show the absence of defects, it can only show that software defects present.

Testing Information flow:

Information flow for testing flows the pattern. Two class of input provided
to test the process. The software configuration includes a software requirements
specification, a design specification and source code.

Test configuration includes test plan and test cases and test tools. Tests are
conducted and all the results are evaluated. That is test results are compared with
expected results. When erroneous data are uncovered, an error is implied and
debugging commences.

Unit Testing:

Unit testing is essential for the verification of the code produced during the
coding phase and hence the goal is to test the internal logic of the modules. Using
the detailed design description as a guide, important paths are tested to uncover
errors with in the boundary of the modules. These tests were carried out during the
programming stage itself. All units of ViennaSQLwere successfully tested.

Integration testing :

Integration testing focuses on unit tested modules and build the program
structure that is dictated by the design phase.

System testing:
 System testing tests the integration of each module in the system. It also
tests to find discrepancies between the system and it’s original objective, current
specification and system documentation. The primary concern is the compatibility
of individual modules. Entire system is working properly or not will be tested here,
and specified path ODBC connection will correct or not, and giving output or not
are tested here these verifications and validations are done by giving input values
to the system and by comparing with expected output. Top-down testing
implementing here.

Acceptance Testing:

This testing is done to verify the readiness of the system for the implementation.
Acceptance testing begins when the system is complete. Its purpose is to provide
the end user with the confidence that the system is ready for use. It involves
planning and execution of functional tests, performance tests and stress tests in
order to demonstrate that the implemented system satisfies its requirements.

Tools to special importance during acceptance testing include:

Test coverage Analyzer – records the control paths followed for each test case.

Timing Analyzer – also called a profiler, reports the time spent in various regions
of the code are areas to concentrate on to improve system performance.

Coding standards – static analyzers and standard checkers are used to inspect code
for deviations from standards and guidelines.

Test Cases:
 Test cases are derived to ensure that all statements in the program have been
executed at least once during testing and that all logical conditions have been
executed.
Using White-Box testing methods, the software engineer can drive test cases that

 Guarantee that logical decisions on their true and false sides.

 Exercise all logical decisions on their true and false sides.
 Execute all loops at their boundaries and with in their operational bounds.
 Exercise internal data structure to assure their validity.
The test case specification for system testing has to be submitted for review before
system testing commences.