Air Cargo Report

A

Project Report

On

“Air Cargo Management System”

Submitted In Partial Fulfillment of MCA VI Semester of Master of Computer Applications

Rajasthan Technical University, Kota

Submitted by

Guru Dutt Bissa

MCA VI Semester

Guide

Mr. Abhijit Sen GuptaSoftware Engineer, Tata CMC PVT LTD,

Bangalore

Department of Computer Science

Lachoo Memorial College of Science & Technology

Affiliated to Rajasthan Technical University, Kota December 2010

Air Cargo Management System 1

ACKNOWLEDGEMENT

I take this humble opportunity to express my deep sense of gratitude to my project guide

Mr. Abhijit Sen Gupta who in all respect helped me tangibly from the beginning till the

fulfillment of my project .Their expert guidance and inspiration brought completion of

the project.

I would like to thank Mr. Sitaram sir Deputy Manger of CMC PVT LTD, who gives

me this opportunity. I should also like to thank to all my trainers who directly or

indirectly supports me time to time.

Last but not least i would like to express a deep sense of gratitude from the bottom

of my heart to my parents, without whom it was impossible for me to reach at this stage.

Thank you & Regards.

GURU DUTT BISSA


Department of Computer Science

CERTIFICATE

This is to certify that the seminar report entitled

Air Cargo Management System

is prepared by

GURU DUTT BISSA

in fulfillment of the degree of

MCA VI Semester Examination 2011,

under our supervision and guidance.

Prof (Dr) Rajeev Mathur Dr Priyadarshi Patni Director Associate Professor, Computer Science

Date:


INDEX

S No. Contents Page No.

1. INTRODUCTION 7

1.1 Functionality of current system

1.2 Goals of the proposed system

1.3 Modules of the system

1.4 Benefit of computerization

2. SYSTEM REQUIREMENTS

2.1 Hardware Requirements

2.2 Software Requirements

3 SOFTWARE FEATURES

3.1 Introduction to J2EE Platform

3.2 J2EE Framework Security

3.3 J2EE Features

3.4 Application Design-Pattern Specification


4 FEASIBILTY STUDY

4.1 Technical Feasibility.

4.2 Operating Feasibility.

4.3 Economical Feasibility.

5 SYSTEM ANALYSIS 5.1 Analysis of Existing System

5.2 Overview of Proposed System

5.3 Preliminary Design

a) Context Diagram

b) Data Flow Diagram

c) ER Diagram

6. SYSTEM DESIGN

6.1 Data Base Design

6.2 Data Base Schema

7. SYSTEM IMPLEMENTATION

7.1 Screen Layouts and Description

8. SYSTEM TESTING

9. SYSTEM SECURITY

10. FUTURE SCOPE AND CONCLUSION

11. REFERENCES


ABSTRACT

What contribution would the Project make: -

The project would help in effective and systematic record keeping that is storing and

retrieving of useful data. Project will be able to give the report so that management can

make decisions on the basis of those reports.

Scope of the study: -

The main Scope of study: -

1. It should contain all the information of Company and Customer which is in this site.

2. It should contain all the information of Cargo Customer like Personal Detail, Product

Detail, and Cargo Tracking Detail etc.

3. It should process and evaluate Cargo Tariffs and Shipment Tracking by Employees.

4. It should contain information related to Cargo E-booking and Cargo Tracking.

5. It should maintain proper financial records.

6. It should have Administrator for scheduling administrative work of site.


CHAPTER 1

INTRODUCTION TO PROJECT

TITLE OF THE PROJECT: - Air Cargo Management System

Introduction:

Air cargo is the facility which provides flexibility for the customers so that they can transfer their goods from one place to another place. My project is all about to mange the goods, customer’s information as well as tracking of their cargos. When should the cargo be delivered? How to manage stock? Tracking of all the cargos etc.

1.1 Functionality of current system:

• In my project sometime there will be need to do some work manually, but anyway the project is an automated system.

• In this company information is provided to user to know much better about company.

• Cargo tariff and rate information has been provided to user.

1.2 Goals of the proposed system:

• Management of the air cargo.• One of the main goals of the current system is to provide quick transition in

fast paced world and that can be achieved only by computerized system.


1.3Modules of the system :

There are two modules in the system -

1. Customer Module2. Company Module

1. Customer module: It consist of following sub modules

> Cargo E-booking:

In this customer can book his cargo (goods) online and place the order for the delivery of the product. He can specify locations from where he wants to send cargo as well as the location where he wants to send that product. The delivery date has also taken in this so that product can be delivered at time.

>Shipment Tracking

In this module the customer will be able to track their cargo (product), by means of it the customer can know about where is his cargo at specific time? When it is to be delivered? Where it is to be delivered? In case of delay what is the reasons of delay? Etc.

> Login and Registration

For access the website the customer must register himself in the website domain, where he has to fill some personal information so that company can claim the cargo or might contact the customer for further details. After login he can place his orders according to his needs.

> Cargo tariff and rating details

In this module the customer is informed by the website about the tariff and ratings for different cargo on daily basis, so that the customer must be aware of the prices of the transportation of his product. The prices are updated daily as per the real time requirements.


2. Company Module: It consists of the following sub modules

• Stock Management

This module is handled by employee of a company, where he will manage the incoming and outgoing stock. The incoming stock is the stock which has collected by the company from the customer where as the outgoing stock is the stock which has been delivered from the company to another branch of the company (stated at another city). The sub modules are divided into two categories.

>Incoming Stock

>Outgoing Stock

• Customer Management

This module is consisting of customer details regarding of their names, address from where he is sending and the address from where he is sending cargo, phone, product orders etc.

• Tariff and Rating

The employee can update the prices of the tariffs of cargo in this module. He is provided with old rates and according to these rates the cost will be charged from the customer, he can modify the rates with the help of some text boxes and according to the updation it will be reflected to the database.

• Cargo Claim Management

This module is handled by employee of a company, where he will manage whether the product has been claimed or if not when it is to be claimed and what is the reason if delay occurs from company side. The employee can check whether the specific product has been claimed or not?

1.4 Benefit of computerization:

• Processing time is highly saved.• A bigger and efficient database can get a quick overview of various information in a more efficient manner. For example at any given point of time any information can be retrieved.


Chapter 2

SYSTEM REQUIREMENTS

It is recommended that the minimum configuration for clients is as appended below:

Hardware Specification: -

1. Intel Pentium III or equivalent AMD Processor.2. 256 MB RAM.3. 12 GB Hard Disk Space.4. Display Card supporting at least resolution up to 1024 X

768. 5. And VIDEO Ge-Force 2 or more.6. Printer & Internet Connection.

Software Specification: -

1. Windows XP.2. Apache Tomcat 5.5.3. Java Development Kit 1.5.0.


4. Microsoft Access.5. Mail Server Software.

Chapter 3

SOFTWARE FEATURES

3.1 Introduction to J2EE Platform

The J2EE platform defines declarative contracts between those who develop and assemble application components and those who configure applications in operational environments. In the context of application security, application providers are required to declare the security requirements of their applications in such a way that these requirements can be satisfied during application configuration. The declarative security mechanisms used in an application are expressed in a declarative syntax in a document called a deployment descriptor. An application deployer then employs container-specific tools to map the application requirements that are in a deployment descriptor to security mechanisms that are implemented by J2EE containers. The J2EE SDK provides this functionality with deploytool.

Programmatic security refers to security decisions that are made by security-aware applications. Programmatic security is useful when declarative security alone is not sufficient to express the security model of an application. For example, an application might make authorization decisions based on the time of day, the parameters of a call, or the internal state of an enterprise bean or Web component. Another application might restrict access based on user information stored in a database.

J2EE applications are made up of components that can be deployed into different containers. These components are used to build a multitier enterprise application. The


goal of the J2EE security architecture is to achieve end-to-end security by securing each tier.

The tiers can contain both protected and unprotected resources. Often, you need to protect resources to ensure that only authorized users have access. Authorization provides controlled access to protected resources. Authorization is based on identification and authentication. Identification is a process that enables recognition of an entity by a system, and authentication is a process that verifies the identity of a user, device, or other entity in a computer system, usually as a prerequisite to allowing access to resources in a system.

Authorization is not required to access unprotected resources. Because authorization is built upon authentication, authentication is also not needed to access unprotected resources. Accessing a resource without authentication is referred to as unauthenticated or anonymous access.

3.2 J2EE Framework Security

The j2ee security features can be distinguished in following sub topics:

Protecting Web Resources:

You can protect Web resources by specifying a security constraint. A security constraint determines who is authorized to access a Web resource collection, which is a list of URL patterns and HTTP methods that describe a set of resources to be protected. Security constraints can be defined using deploy tool, as described in controlling access to web resources.

If you try to access a protected Web resource as an unauthenticated user, the Web container will try to authenticate you. The container will only accept the request after you have proven your identity to the container and have been granted permission to access the resource.

Authenticating Users of Web Resources:

When you try to access a protected Web resource, the Web container activates the authentication mechanism that has been configured for that resource. You can configure the following authentication mechanisms for a Web resource:

HTTP basic authentication

Form-based authentication


Client-certificate authentication

Using SSL to Enhance the Confidentiality of HTTP Basic and Form-Based Authentication:

Passwords are not protected for confidentiality with HTTP basic or form-based authentication. To overcome this limitation, you can run these authentication protocols over an SSL-protected session and ensure that all message content is protected for confidentiality.

Using Programmatic Security in the Web Tier

Programmatic security is used by security-aware applications when declarative security alone is not sufficient to express the security model of the application. Programmatic security consists of the following methods of the HttpServletRequest interface

3.3 J2EE Features

The Java™ 2 Platform, Enterprise Edition (or J2EE™ Platform) includes features and services that are available as resources to all J2EE applications and modules. The Sun™ Open Net Environment (Sun ONE) Application Server 7, a J2EE 1.3 compliant server, provides access to these resources. This guide describes the following features:

Java™ Database Connectivity (JDBC™) API Transaction Service

Java Naming and Directory Interface™ (JNDI) API

Java™ Message Service (JMS) API

JavaMail™ API

Java™ Database Connectivity (JDBC™) API

The standard way to connect to a database from a J2EE application or module is through a JDBC driver. Sun ONE Application Server supports the core JDBC 3.0 API and the JDBC 2.0 extensions and works with a wide range of JDBC Compliant™ drivers. A JDBC resource associates a JDBC driver and database to a JNDI name that applications and modules can reference.


http://download.oracle.com/docs/cd/E19957-01/817-2177-10/djovervu.html#wp18012





Transaction Service

The purpose of a transaction is to ensure that data is updated in an all-or-nothing fashion in order to preserve data integrity. The transaction service provides transactional resource managers for the JDBC API, the JMS API, and resource adapters (connector modules). In the Sun ONE Application Server, you can configure transactions and reference them using the JNDI API.

Java Naming and Directory Interface™ (JNDI) API

The JNDI API allows application components and clients to look up distributed resources, services, and EJB™ components. The J2EE resources described in this guide are made available through the JNDI API. External JNDI resources and custom resources are also configurable in the Sun ONE Application Server.

Java™ Message Service (JMS) API

The JMS API provides a common way for J2EE applications and modules to create, send, receive, and read messages in a distributed environment. The fully integrated JMS provider for Sun ONE Application Server is the Sun™ Open Net Environment (Sun ONE) Message Queue software. JMS queues, topics, and message destinations are made available through the JNDI API.

JavaMail™ API

The JavaMail API allows J2EE applications to create, send, receive, and read mail messages. The JavaMail API includes support for the IMAP4, POP3, and SMTP mail protocols. JavaMail sessions are made available through the JNDI API.

3.4 Application Design-Pattern Specification

To design the entire system we applied MVC (Model-View-Controller) design pattern which is the Blueprints recommended architectural design pattern for


interactive applications. MVC, described in organizes an interactive application into three separate modules:

1) The application model with its data representation and business logic.2) The second for views that provide data presentation and user input.3) The third for a controller to dispatch requests and control flow.

This pattern follows the following Web-Tier Service Cycle

There are two models in this designing pattern by means of which a web application can be designed. Here we have followed the Model1. This is described as follows.

A Model 1 architecture consists of a Web browser directly accessing Web-tier JSP pages. The JSP pages access Web-tier JavaBeans that represent the application model, and the next view to display (JSP page, servlet, HTML page, and so on) is determined either by hyperlinks selected in the source document or by request parameters. A Model 1 application control is decentralized, because the current page being displayed determines the next page to display. In addition, each JSP page or servlet processes its own inputs (parameters from GET or POST).


Chapter 4

FEASIBILTY STUDY

Feasibility study is conducted to select the best system that meets the performance

requirements. This entails an identification, description, and evaluation of the candidate

system, and the section of the best system for the job.

Many feasibility studies are disillusioning for both user and analyst. First the study often

pre-supposes that when feasibility of the documents is being prepared, the analysis is in

position to evaluate solutions. Second most studies tend to overlook the confusion

inherent in the system development … the constraints and the assumed attitudes. If the

feasibility study is to serve as decision document, it must answer three key questions:

Is there new and better way to do a job that will benefit the user?

What are the cost and saving of the alternatives?

What is recommended?

The most successful system projects are not necessary or most visible in business but

rather those that truly need user expectations. More projects failed because of inflated

expectations than for any other reasons.

Three main considerations are involved in feasibility study:

4.1 Technical Feasibility.


Technical feasibility centers on the current system and to what extent it can support the proposed

system, it includes current computer system specifications such as hardware, software etc. It also

involves financial considerations to accommodate the technical enhancements. If the budget is

serious constraint then the project is judged not feasible.

Though the system is developed in the generalized form, which covers all the procedures and

operations carried out in any Social networking site. The version used in the system is J2EE and

MS-ACCESS Server.

The features embedded in the system are latest and according to the need of the client. Such as

creating profile, adding friends and other feature that are required for social networking site. The

backend used is the latest Microsoft Access version, which also supports to view the database

contents, relationship with the connected database including the primary, foreign key. Any up

gradations needed can be easily made in the source code, thus decreasing the headache of

changing each and every code. If in near future, the latest version of J2EE/ MS-ACCESS to be

installed then , the source code handling the connection of the database can easily be modified.

The codes are easily compatible for the changes, as the latest version doesn't affect the core code.

MS-ACCESS Server can manage large amount of data and is simple and secure. Using J2EE

helps us to design the look of our application and its windows. J2EE full open database

connectivity (JDBC) with MS-Access , Data accessibility, response and output require less time.

4.2 Operating Feasibility:

In this we determine what change will be brought in system, new skills required and other

human organization and political aspects.

Each user can easily use our site. However it is desirable that the user has the basic knowledge of

the computers.

Without making any changes in the rules and regulations of the existing system proposed system

can be easily adopted.

The following areas have been probed to declare the proposed System as operationally

feasible:

1. There is sufficient support for the proposed system from the management and the users

as well.


2. The results produced by the proposed system will be more effective and efficient in terms

of speed.

3. The system will work when it is developed and installed and there are no major barriers

to its implementation within the whole organization. This accounts for the operational

feasibility of the proposed system.

4.3 Economical Feasibility

Economic justification is generally the “bottom line” consideration for most Systems.

For a System to be Economically Feasible a Cost – Benefit Analysis – An assessment of

the Economic justification for a System or the benefits obtained from the system against

the cost incurred to actually develop the system has to be carried out. Actually, the

company doing this all procedure manually and it takes so much time of examiner and

admin so compare of that all cost this project cost is so much small so it is feasible.

4.3.1 Cost Analysis

The cost to conduct investigation was negligible. The cost of essential hardware and software

requirement is not very expensive.

Moreover hardware like Pentium I PC and software like J2EE and MS-Access 2005 are easily

available in the market.

4.3.2 Benefits and Savings

Cost of the maintenance of the proposed system is negligible.

Money is saved as paper work is minimized.

Records are easily entered and retrieved.

The proposed system is fully automated and hence easy to use.

Since benefits out base the cost, hence our project is economically feasible.

Chapter 5


SYSTEM ANALYSIS

5.1 Analysis Of Existing System

In the current working system the user faces so many problems. Some of them are

given below:

Earlier there was no such websites are available who can implement the cargo

management in an efficient way, as there is no such website which manage customer’s

details as well as their product details, which they have ordered earlier.

5.2 Overview of Proposed System

Computer software has become a driving force. It is the engine that drives business

decision-making. The Application is a working demonstration of how to use blueprints

principles in a real application design. This document is an online guide to the design and

the implementation of the application Enterprise Applications with web technology.

Each release of the application maintains consistent design features such as separating

logic and presentation, using web component for control and web pages for presentation,

using business components, and so on.

Computerized Cargo management System is developed to facilitate the General

administration system to manage the information of the customers and company itself.

So, that organization can access accurate information quickly and easily as and when

required, thereby improving its operational efficiency & effectivenessIn today’s

competitive environment, where everybody wants to be on the top, Information plays

very crucial role. As fast as information is accessed and processed, it can give good

results.

Today Internet is the fast way of transferring Data and Information over wide

area, hence I have used internet as a way for exchanging information.


Computerized system helps to fulfill these goals. Computerization of the official

works will help in doing lot of manual work quickly. It will help in easy storage and

access of all information, in short period of time.

Specific Objective of the site :

Objective of doing this project is to enhance my knowledge in the field of E-com

technology using J2EE as a language. Some of the client requirement and objectives of

this site is as under:-

To increase the business of Client.

To make it Global.

To facilitate easy cargo management.

To facilitate company so that it can manage the customers as well as cargos.

To act as a middle men connecting the companies and the customer.

So these are some of the objectives which we have to accomplish.

Features of the site:

It has the features of providing all the information online (through the net). About

the product tariffs and rates and tracking of cargo is also available.

This web site built on 3 Tier Architecture.

The site also includes the electronic mail facility for the users who have registered

themselves.

The site acts as a middle-ware for Cargo Company and customers.

The site has the facility to inform the customer about the updated price of cargo product and positioning of their product.

Chapter 6

SYSTEM DESIGN


The most creative and challenging phase of the system life cycle is system design. The term design describes a final system and the process by which it is developed. It refers to technical specification that would be applied to the system. The design part would require the data design encompassing the data object, the input states and external stimuli affecting the software and the modes of interaction. Design of the manual and online help starts at this level and is given a formal form.The design of object oriented software requires description of objects that form the building blocks of the system and a description of the communication mechanisms that allow data to flow, subsystem and object. Object-oriented design accomplishes all of these things.

It mainly includes following steps:1. Data Flow Diagram2. Flow Chart3. Database Design4. E-R Diagram

6. 1 Data flow Diagram

6.1.1 CONTEXT DIAGRAM


The context diagram is the most abstract data flow representation of a system. It

represents the entire system as a single bubble. This bubble is labeled according to the

main function of the system. The various external entities with which the system interacts

and the data flows occurring between the system and the external entities are also

represented.


6.1.2 FIRST LEVEL DFD

To develop the level 1 DFD, examine the high-level functional requirements. If there are between

three to seven high-level functional requirements, then these can be directly represented as

bubbles in the level 1 DFD. We can then examine the input data to these functions and the data

output by these functions, and represent them approximately in the diagram.


Figure 1. LEVEL 0 DFD

Figure 2 LEVEL 1 DFD

6.3 DATA BASE DESIGN

CUSTOMER:CUSTOMER:


CLAIM MANAGEMENT:


TARIFF AND RATING:TARIFF AND RATING:


PRODUCT DETAILS:PRODUCT DETAILS:


SHIPMENT TRACKING:SHIPMENT TRACKING:


EMPLOYEE LOGIN:EMPLOYEE LOGIN:


CUSTOMER MANAGEMENT:CUSTOMER MANAGEMENT:


STOCK MANAGEMENT:STOCK MANAGEMENT:


6.4 ER DIAGRAM


Chapter 7

SYSTEM IMPLEMENTATION


7.1 Screen Shots

Index.Jsp:

Customer Main Page:


Employee Login Page:


Stock Management:


Customer Details:


Tariff and Rating:



Chapter 8

SYSTEM TESTING

TESTING METHODOLOGY AND TESTING STRATEGIES

There are following rules that can serve well as 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 high probability of finding an as-yet-

undiscovered error.

A successful test is one that uncovers as-yet-undiscovered error.

TESTING STRATEGIES

UNIT TESTING

In unit testing we have testing a single program module in an isolated environment.

Testing of the processing procedures is the main focus. Integration Testing Because of

interfaces among the system modules, we use integration testing. In other word’s it

ensures that the data moving between the modules is handled as intended.

SYSTEM TESTING

During system testing the system is used experimentally to ensure that the software does

not fail i.e. it will run according to its specifications and in the way users expect. Special

test data are input for the processing and the results examine. A limited number of users

try to use it in unforeseen ways. It is preferable to discover any surprise before the

organization implements the system and depend upon it.


In many organizations persons other than those who wrote the original programs

to ensure more complete and unbiased testing and more reliable testing perform testing.

The norms that were followed during the phase were that after the developer of the

software has satisfied regarding every aspect of the software under consideration he is

required to release the program source code. A setup name release is used to copy the

name file from the developers’ user area to a project area in the directory named with

developer user name. Here the entire final testing used to be done by persons other than

the developer himself .if some changes were desired in the program the developer were

required to use another setup. Retrieve, which copied back the latest version of the

program to developer areas.

As in this system data is entered at different levels I considered providing various types

of checks like range check, validity check, completeness check etc. in different data entry

screens according to the requirements.

Since the users are not familiar to the new system the data screens were designed in such

a way that were:

Consistent

Easy to use

Has a fast response time

System testing is the testing of the system against its initial objective. It is done either in a

simulated environment or in live environment.

TEST REVIEW

Test review is the process that ensures that testing is carried out as planned. Test review

decides whether or not the program is ready to be shipper out for implementation

SECURITY TESTING


Security testing attempt to verify that protection mechanism built into a system will, in

fact, protect it form penetration mechanisms.

TYPES OF TESTING TECHNIQUES

White box testing

Black box testing

WHITE BOX TESTING

White box test focus on the program control structure. Test cases are derived to ensure

that all statement in the program has been executed at least once during testing and that

all logical condition has been exercised. Basic path testing, a white box testing, makes

use of program graph to derive the set of linearly independent test that will ensure

coverage.

CODING TESTING

Condition testing is tests case design method that exercise the logical conditions contain

in a program module. A simple condition is a Boolean variable or a relational expression.

BRANCH TESTING

We have used Branch testing that is probably for compound condition, the true and false

(in project i.e. null values) for each branch.

DATA FLOW TESTING

We have used data flow testing due to check the path of program according to the

locations of definitions and uses of variables in the program.

LOOP TESTING

In our project we have use only simple loop. And we have use m pass through the loop

where m<n.


BLACK BOX TESTING

Black box testing focuses on the functional requirements of the software. That is, black-

box testing enable the software engineer to derive set of input conditions that will fully

exercise all functional requirements for a program.

GRAPH-BASE TESTING METHOD

We have used graph-based testing method for removing errors associated with

relationships. The first step in this testing is to understand the objects that are modeled in

software and the relationship that connect these objects.

EQUIVALENCE PARTITIONING

This testing is used for the following reason:

Specific numeric values

Range of values

Set of related values

Boolean condition

BOUNDARY VALUE ANALYSIS

Boundary value analysis is a test case design technique that complements equivalence

partitioning. Rather than selecting any element of equivalence class the selection of test

cases at the edges of the class. Rather than focusing solely on the input condition,

The point of equivalence partitioning as:


An input condition specifies a range boundary by values a and b, test cases should be design with values a and b and just above and just below a and b.

An input condition specific a number of values, test cases should be developed that exercise the minimum and maximum number

ACCEPTENCE TESTING

When the function test was completed, we involved the user to make sure that the system

worked according to the user’s expectation. Thus the user did the final acceptance test.

TEST CASES

TEST CASE DESCRIPTION DESIRED RESULT ACTUAL RESULT

RTest1 Checking of availability of ID which user wants to create

If ID is available then a message is displayed “ID is available “

Otherwise the displayed message “ID already exits”.

If ID is available then a message is displayed “ID is available “

Otherwise the displayed message “ID already exits”.

RTest2 The password which user enters for his/her corresponding ID should be of minimum seven characters with at least one non alphabetic character.

If password is less than seven characters then a message is displayed

“Password should be of minimum seven characters with at least one non alphabetic character.

If password is less than seven characters then a message is displayed

“password should be of minimum seven characters with at least one non alphabetic character


RTest3 The user is supposed to fill all the mandatory fields when he / she register for new user.

If any of the required field is left empty then relatively warning message is displayed.

If any of the required field is left empty then relatively warning message is displayed.

RTest4 All the details which are filled by the user should to be stored to the database.

The details are stored in the database only if all the details are valid and ID is available otherwise their corresponding message(s) is (are) displayed.

The details are stored in the database only if all the details are valid and ID is available otherwise their corresponding message(s) is (are) displayed.

HTest1 All options should be access through home page.

If any user access any option it would be able to roll back , or move foreword

If any user access any option it would be able to roll back , or move foreword

CHTests1 A user can change the password of his / her account.

A user can change the password of his / her account. The user needs to re-enter password and enter new desired password with one confirm password field.

A user can change the password of his / her account. The user needs to re-enter password and enter new desired password with one confirm password field.

BNTest1 A user can navigate through the links or

When a user click on a button or link then it should perform the

When a user click on a button or link then it should perform the


buttons. corresponding functionality.

corresponding functionality.

LSTest1 User ID should display on page.

If a user login through ID and password, it user ID display on page.

If a user login through ID and password, it user ID display on page.

SNTest1 Session expired after specific time.

If user does not use any control or navigate then after specific time his / her session expired.

If user does not use any control or navigate then after specific time his / her session expired.

ADTest1 Advertisement display on screen can be display according to its preference.

If customer wants to give preference to his / her advertisements, it could be given.

If customer wants to give preference to his / her advertisements, it could be given.

Chapter 9


SYSTEM SECURITY

USER ACCESS CONTROL

Security comprises user authentication, implying user identification (against defined

users) and user’s authorization indicating actions and permissions within the application.

The application will incorporate security for all the modules in a hierarchal form. These

levels are required to be identified by the application owners.

The users will be classified in groups and each group will be provided access to identify

screens and reports. This access will be across different modules.

The group authorization right will also define whether they are permitted to view the

information only or can modify it as well.

USER AUTHENTICATION

Every registered user will have a login ID and password. The system administrator, using

the functionality provided by login control module, will create new login Ids and

maintain existing Ids using the user registration screen. Whenever a new user is

registered, a new login ID and password will be created. Users can change their own

passwords. The passwords will not be displayed on the screen while they are being

entered into the application.

USER AUTHORIZATION

For data entry and modification, permissions will be defined for the entry screens.

Administrator and Users both will be having different screens and different access rights.

Administrator would be able to manage different operations and functions whereas a

registered user would be able to access all the features available on the website.


USER SESSION MANAGEMENT

The USERNAME of the user will be displayed on the next page, and any item needed on the

different page will also be maintained using Session management.

Browser Session will expire and terminate user session after a certain period of inactivity. The

following data will be maintained throughout an active session.

EXCEPTION HANDLING

Validations will be enforced at the UI as well as the business layer of application. If

errors occur, appropriate messages will be displayed to the user for taking necessary

action. These errors will be handled by the application using Visual Studio Exception

Handling.

Chapter 10


Conclusions

CONCLUSIONS

There's nothing wrong with using the Internet to find a job. In fact, a company may list jobs that you won't always find in the newspaper. However, don't use it as a cure-all method. Combine your Internet search with traditional job-hunting methods and you may find the job you're looking for.

ADVANTAGES

1. The biggest advantage of a Job portal is that there is no fee for the job seeker. 2. The job seeker just has to select the company he likes and apply to them.

3. The candidate can upload the resume and fill out all the important details about their educational backgrounds, skills and work experience.

4. One of the biggest advantages of a job portal is the fact that you can avoid certain companies or employers. If you don't wish for them to see your profile you can simple blacklist them.

5. A quicker way of doing this would be to procure a program from the net which can search for jobs through all these many sites and show the results in one window.

6. Software of this nature usually keeps the user informed with email alerts and reduces the time spent on job hunting.

LIMITATIONS

1. Wasted Time Online job searches can be a waste of time if you're depending mainly on this tool to find work. To be effective in looking for work, you'll have to network with others. You can do this by attending job fairs, meeting with friends, volunteering in a certain aspect of your field and visiting places to enquire about jobs.

2. Complacency in Resume Preparation While you may enjoy the convenience of online job searches, it becomes easy to not tailor your resume and cover letter to the position you're applying for. When applying online, make sure you've read the job description carefully to avoid sending a generic resume.


3. Job Leads May Be Outdated Some online job searchers think most of the positions they see online are the latest ones. Yet, just like the newspaper job ads, some of the job leads may be outdated. When applying, look at the posting date located next to each position and contact the company if you're not sure.

4. Possibility of Scams Another disadvantage of online job searches is that some job postings seem too good to be true. Signs of a job scam include not needing a lot of work experience and that you can work from home and still make a lot of money. If you find the ad's claims are too extravagant, don't apply.


REFERENCES:

Books:

J2EE: -

1. Microsoft Training Kit For .NET

2. Black Book of J2EE

DBMS: -

1. Database and Management System by Korth.

2. SQL Server 2005 MCSE Edition

Software Engineering: -

1. Roger Pressman, Software Engineering

LIBRARY

MSDN MSDN Library Visual Studio .Net release

The MSDN Library is the essential reference for developers, with more than a

gigabyte of technical programming information; including sample code, documentation,

technical articles, the Microsoft Developer Knowledge Base, and anything else we might

need to develop solutions that implement Microsoft technology.


Documents

Air Cargo Report