SYSTEM ANALYSIS

System analysis is a process of collecting factual data, understand the processes involve, identifying
problem and recommending feasible suggestions for improving the system functioning

The principles of system analysis are applied when an information system or application is first
proposed. The concept of system stress aids in identifying requirements for information system
support and generation application. The following steps are applied in the development of our
project:

Specification of what the new system is it accomplish based on the adequacy of user.

Functional hierarchy showing the functions to be performed by the new system and their
relationship with each other

List of attributes of the entities.

These are the data items, which to be held about each entity.

3.1 PROBLEM ANALYSIS

As the current system is manual the growing demands of the organization, to be incorporated in the
existing system causes performance degradation.

In the current system there is a good chance of committing errors while entering the data. As all the
data are entered manually which requires a lot of time. The problem can be solved by introducing
the proposed system.

So, after consulting our guide, we decided to make the project for developing the software for the
student result management system.

3.2 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

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
erganization. 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 by manually.

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.

INTRODUCTION TO HTML 4.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 spreadsheets, 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. HTMI. has been extended in a number of ways. The Web
depends on Web page authors and 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 IIIMI. 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 to 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
helow

Application System Development A Life evele Approach

Although there are a growing number of applications (such as decision support systems) that should
be developed using att experimental process strategy such as prototyping, a significant amount of
new development work continues 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
ach 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 he
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 segmens 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 cnegorization:
There is a general agreement on the flow of development steps and the necessity for santral
procedures at each stage
The information system development cycle for an application consists of three major stages.

Definition.

Development

Installation and operation.

The first stage of the process, which defines the information requirements for a feasible cost- flective
system. The requirements are then translated into a physical system of forms, procedures, Pograms
ate, by the system design, computer programming and procedure development. The rodting 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
Jefinition, 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 operation: final system test and conversion.

Maintenance: Month to month operation and maintenance

Post audit: Evaluation of development process, application system and results of use at the mpletion
of each phase, formal approval sign-off is required from the users as well as from the Batager of the
project development

TOOLS AND ENVIRONMENT USED