repository and search engine for alumni of collage.doc

7/27/2019 Repository and search engine for alumni of collage.doc

1/63

Repository and Search Engine for Alumini of College

Chapter 1:Introduction

1.1 Purpose of the Project

This project is aimed at developing the Automobile Store and Service Centre. The

system is an online application that can be accessed throughout the organization and

outside customers as well with proper login provided, which will give better service to the

customers.

1.2 Scope of the Project

This system can be used as the Office of Alumni and College elations see!s to protect

the privacy of its alumni and friends, and thus, endeavors to safeguard the use of information in

its custody. To that end, the Office of Alumni and College elations provides constituent

information to re"uestors only under the conditions.

1.!"er"ie# of the Project

Overall description consists of bac!ground of the entire specific re"uirement. #t also gives

e$planation about actor and function which is used. #t gives e$planation about architecture

diagram and it also gives what we are assumed and dependencies. #t also support specific

re"uirement and also it support functional re"uirement, supplementary re"uirement other than

actor which is used. #t also gives inde$ and appendices. #t also gives e$planation about any doubt

and "ueries.

Once a student graduates from the institute, his%her professional life or career

begins, with higher education playing an important role in establishing himself%herself in

the profession. #n respect of College, it has been our e$perience that from the very

beginning, the alumni have maintained personal contacts with one another, rather than use

the channel of Alumni Association.

The advancements in information technology have certainly helped in creating

new resources such as alumni web pages, list servers etc., so as to permit greater

interactions between the alumni. The College Alumni Association has been "uite active in

this respect and has revived the interest among the Alumni to remain in touch.

&


2/63


Chapter 2: System Analysis

2.1 Study of the system

2.1.1 E$isting System and its %imitations:

The '$isting system is a computerized system but which is maintained at

individual databases i.e in e$cel sheets, it(s a time delay process. And maintaining all the

records in '$cel sheets is difficult. #f they want any record they has to search all the

records. #t doesn(t provide multiple user accessibility and also doesn(t have different user

privileges. So the system is not accessible for all the employees of the organization.

%imitations in E$isting System :

The current system is not completely complete computerized and manual system

in entering students and staff data and handling it.

There is no centralized database maintenance

There is no easy access to the particular students record

The student cannot easily navigate through the database

2.1.2 Proposed System and its Ad"antages:

The )roposed system is a computerized system but which is maintained at

Centralized databases i.e. in automated forms it(s a very fast process. And maintaining all

the records in online systems database which ma!es it very easy to access and retrieve

data from the database. #f they want any record they can easily search all the records. #t

provides multiple user accessibility and also has different user privileges. So the system is

accessible for all the employees of the organization.

Ad"antages o"er E$isting System :

#t is completely automated system in handling the college database

This system provides centralized database maintenance

This system provides easy access to the particular students account or his

complete details

This system provides student to easily navigate through the application for more

information in a most secure manner.

*


3/63


&odules:

Student

+ser can egister to Alumni

Students can login to the system

+pdate the )rofile

Students can see all students information in the alumni

They can see the events details

They can also send messages to their friends

Students also can see the campus interview details

Admin users

as full access to all the modules of this system.

esponsible for the accounts of all students.

+pdate, modify or delete event details

+pdate, modify or delete campus interviews details

)repares and submits also -aily reports, user reports, event reports, etc.

Reports:

All fre"uently used reports at the clic! of a button

All reports can be previewed, printed, e$ported to '$cel%ord etc., or can be

fa$ed or emailed

'ormal users/

as restricted access. i.e., 0ormal users have access to some of the modules only

i.e. user can search the list of all their friends.

They cannot send messages to their batch mates

(ser Interface:

Soothing 1raphical +ser #nterface with Conte$t Sensitive elp

Totally 2enu -riven, with 3eyboard Shortcuts for fre"uently used forms

All reports for specified period selected using calendar

2.2 )easi*ility Study

A feasibility study is a high level capsule version of the entire system analysis and

design process. The study begins by classifying the problem definition. 4easibility is to

5


4/63


determine if it(s worth doing. Once an acceptance problem definition has been generated,

the analyst develops a logical model of the system. There are three paths in feasibility

study.

2.2.1 Economic )easi*ility:

'conomic feasibility attempts * weigh the costs of developing and implementing a

new system, against the benefits that would accrue from having the new system in place.

This feasibility study gives the top management the economic justification for the new

system.

A simple economic analysis which gives the actual comparison of costs and

benefits are much more meaningful in this case. #n addition, this proves to be a useful

point of reference to compare actual costs as the project progresses. There could be

various types of intangible benefits on account of automation. These could include

increased customer satisfaction, improvement in product "uality better decision ma!ing

timeliness of information, e$pediting activities, improved accuracy of operations, better

documentation and record !eeping, faster retrieval of information, better employee

morale.

2.2.2 !perational )easi*ility:

)roposed project is beneficial only if it can be turned into information systems

that will meet the organizations operating re"uirements. Simply stated, this test of

feasibility as!s if the system will wor! when it is developed and installed. Are there major

barriers to #mplementation6 ere are "uestions that will help test the operational

feasibility of a project/#s there sufficient support for the project from management from

users6 #f the current system is well li!ed and used to the e$tent that persons will not be

able to see reasons for change, there may be resistance.Are the current business methods

acceptable to the user6 #f they are not, +sers may welcome a change that will bring about

a more operational and useful systems.ave the user been involved in the planning and

development of the project6 'arly involvement reduces the chances of resistance to the

system and in general and increases the li!elihood of successful project.Since the

proposed system was to help reduce the hardships encountered. #n the e$isting manual

system, the new system was considered to be operational feasible.

2.2. +echnical )easi*ility:

'valuating the technical feasibility is the tric!iest part of a feasibility study. This

is because, .at this point in time, not too many detailed design of the system, ma!ing it

7


5/63


difficult to access issues li!e performance, costs on 8on account of the !ind of technology

to be deployed9 etc. A number of issues have to be considered while doing a technical

analysis.

+nderstand the different technologies involved in the proposed system before

commencing the project we have to be very clear about what are the technologies that are

to be re"uired for the development of the new system. 4ind out whether the organization

currently possesses the re"uired technologies. #s the re"uired technology available with

the organization6

2. Soft#are Re,uirement Specification

2..1 )unctional Re,uirements:

:ogin to the system through the first page of the application.

Change the password after login to the application.

See his%her details and change it.

elp from the system.

4ollowing is a list of functionalities of the system. 2ore functionality that you

find appropriate can be added to this list. And, in places where the description of

functionality is not ade"uate, you can ma!e appropriate assumptions and proceed.

A person should be able to

Clic! on a button or lin! to be ta!en to the specific application.

The first page of the application should provide the user 8student only9 with the

options of saving his%her details in the database and searching for alumni.

The page through which the student enter his%her details should allow saving of

user details li!e name, year of passing, roll number, contact number, present

address, permanent address, etc. This page will be having * buttons Save and

Cancel.

The save page should have proper validation before allowing the user to save user

details into the database.

The cancel button should ta!e the user bac! to the home page 8first page9.

The search page should allow search on the basis of name of the user or roll

number. )artial search should be allowed.

2..2 Performance Re,uirements:

;


6/63


Access Control for -ata #hich re,uire user Authentication:

The following commands specify access control identifiers and they are typically

used to authorize and authenticate the user 8command codes are shown in parentheses9

(ser 'ame (ser/:

The user identification is that which is re"uired by the server for access to its file

system. This command will normally be the first command transmitted by the user after

the control connections are made 8some servers may re"uire this9.

Pass#ord Pass/:

This command must be immediately preceded by the user name command, and,

for some sites, completes the user


7/63


Chapter / System -esign

.1 (&% -iagrams:

The unified modeling language allows the software engineer to e$press an

analysis model using the modeling notation that is governed by a set of syntactic semantic

and pragmatic rules.

A +2: system is represented using five different views that describe the system

from distinctly different perspective. 'ach view is defined by a set of diagram, which is

as follows.

(ser &odel ie#:

This view represents the system from the users perspective.

The analysis representation describes a usage scenario from the endusers

perspective.

Structural model "ie#:

#n this model the data and functionality are arrived from inside the system.

This model view models the static structures.

eha"ioral &odel ie#:

#t represents the dynamic of behavioral as parts of the system, depicting the

interactions of collection between various structural elements described in the user

model and structural model view.

Implementation &odel ie#:

#n this the structural and behavioral as parts of the system are represented as they

are to be built.

En"ironmental &odel ie#:

#n this the structural and behavioral aspects of the environment in which the

system is to be implemented are represented.

+2: is specifically constructed through two different domains they are/

+2: Analysis modeling, which focuses on the user model and structural model

views of the system.

+2: design modeling, which focuses on the behavioral modeling,

E


8/63


implementation modeling and environmental model views.

+se case -iagrams represent the functionality of the system from a user(s point of

view.+se cases are used during re"uirements elicitation and analysis to represent the

functionality of the system.

.1.1 Class -iagrams:

Class diagrams describe the structure of the system in terms of classes and objects.

The servlet api class diagram will be as follows.

F

DS)/ #mplicit Objects


9/63


G


10/63


&?


11/63


.1.2(se3case -iagram :

&&


12/63


(SE!)+0ES4S+E&:

Administrator (se Case:

&*


13/63


Student5Alumni (se Case:

&5


14/63


6uest (seCase

&7


15/63


.1. Se,uence -iagrams

&;


16/63


Se,uence -iagram )or Alumni:

&


17/63


.1.7 Component -iagram :

&E


18/63


-eployment -iagram:

&F


19/63


E 3 R -iagrams:

&G


20/63


Chapter 7: Coding and Implementation

7.1 +echnologies (sed:

7.1.1 0+&%0yper +e$t &ar8up %anguage/:

T2:, an initialism of yperte$t 2ar!up :anguage, is the predominant mar!up

language for web pages. #t provides a means to describe the structure of te$tbased

information in a document H by denoting certain te$t as headings, paragraphs, lists, and

so on H and to supplement that te$t with interactive forms, embedded images, and other

objects. T2: is written in the form of labels 8!nown as tags9, surrounded by angle

brac!ets.

asic 0+&% +ags:

IJ K Specifies comments

IAKLLL.I%AK Creates hyperte$t lin!s

[email protected]%@K 4ormats te$t as bold

I@#1KLLL.I%@#1K 4ormats te$t in large font.

I@O-MKLI%@O-MK Contains all tags and te$t in the T2: document

IC'0T'K...I%C'0T'K Creates te$t

I--KLI%--K -efinition of a term

I-:K...I%-:K Creates definition list

I4O0TKLI%4O0TK 4ormats te$t with a particular font

I4O2K...I%4O2K'ncloses a fillout form

I4A2'K...I%4A2'K -efines a particular frame in a set of frames

INKLI%NKCreates headings of different levels8 & 9

I'A-K...I%'A-K Contains tags that specify information about a document

IK...I%K Creates a horizontal rule

IT2:KLI%T2:K Contains all other T2: tags

I2'TAK...I%2'TAK )rovides metainformation about a document

ISC#)TKLI%SC#)TK Contains clientside or serverside script

ITA@:'KLI%TA@:'K Creates a table

IT-KLI%T-K #ndicates table data in a table

ITKLI%TK -esignates a table row

ITKLI%TK Creates a heading in a table

*?


21/63


Ad"antages:

A T2: document is small and hence easy to send over the net. #t is small

because it does not include formatted information.

T2: is platform independent.

T2: tags are not casesensitive.

7.1.29a"aScript5&%:

DavaScript is a scriptbased programming language that was developed by

0etscape Communication Corporation. DavaScript was originally called :ive Script and

renamed as DavaScript to indicate its relationship with Dava. DavaScript supports the

development of both client and server components of ebbased applications. On theclient side, it can be used to write programs that are e$ecuted by a eb browser within

the conte$t of a eb page. On the server side, it can be used to write eb server

programs that can process information submitted by a eb browser and then update the

browser(s display accordingly

'ven though DavaScript supports both client and server eb programming, we

prefer DavaScript at Client side programming since most of the browsers supports it.

DavaScript is almost as easy to learn as T2:, and DavaScript statements can be included

in T2: documents by enclosing the statements between a pair of scripting tags

ISC#)TSK.. I%SC#)TK.

ISC#)T :A01+A1' P QDavaScriptRK

DavaScript statements

I%SC#)TK

ere are a few things we can do with DavaScript/

>alidate the contents of a form and ma!e calculations.

Add scrolling or changing messages to the @rowser(s status line.

Animate images or rotate images that change when we move the mouse over

them.

-etect the browser in use and display different content for different browsers.

-etect installed plugins and notify the user if a plugin is re"uired.

e can do much more with DavaScript, including creating entire application.

*&


22/63


Ad"antages

DavaScript can be used for Severside and Clientside scripting.

#t is more fle$ible than >@Script.

DavaScript is the default scripting languages at Clientside since all the browsers

supports it.

&% ; etensi*le &ar8up %anguage:

B2: is a mar!up language for documents containing structured information.

Structured information contains both content 8words, pictures, etc.9 and some indication

of what role that content plays 8for e$ample, content in a section heading has a different

meaning from content in a footnote, which means something different than content in a

figure caption or content in a database table, etc.9. Almost all documents have some

structure.

A mar!up language is a mechanism to identify structures in a document. The

B2: specification defines a standard way to add mar!up to documents.

The '$tensible 2ar!up :anguage 8B2:9 is a generalpurpose mar!up language. #t is

classified as an e$tensible language because it allows its users to define their own tags. #ts

primary purpose is to facilitate the sharing of structured data across different information

systems, particularly via the #nternet. #t is used both to encode documents and serialize

data.

The following is a wellformed B2: document/

Iboo!KThis is a boo!.... I%boo!K

The root element can be preceded by an optional B2: declaration. This element

states what version of B2: is in use 8normally &.?9 it may also contain informationabout character encoding and e$ternal dependencies.

I6$ml versionP=&.?= encodingP=+T4F=6K

The specification re"uires that processors of B2: support the pan+nicode

character encodings +T4F and +T4& 8+T45* is not mandatory9. The use of more

limited encodings, such as those based on #SO%#'C FF;G, is ac!nowledged and is widely

used and supported. Comments can be placed anywhere in the tree, including in the te$t if

the content of the element is te$t or N)C-ATA.

B2: comments start with IJ and end with K. Two dashes 89 may not appear

**


23/63


anywhere in the te$t of the comment.

7.1. 9a"a +echnology:

#nitially the language was called as Qoa!R but it was renamed as QDavaR in &GG;.

The primary motivation of this language was the need for a platformindependent 8i.e.,

architecture neutral9 language that could be used to create software to be embedded in

various consumer electronic devices.

Dava is a programmer(s language.

Dava is cohesive and consistent.

'$cept for those constraints imposed by the #nternet environment, Dava gives the

programmer, full control.

4inally, Dava is to #nternet programming where C was to system programming.

Importance of 9a"a to the Internet:

Dava has had a profound effect on the #nternet. This is because Dava e$pands the

+niverse of objects that can move about freely in Cyberspace. #n a networ!, two

categories of objects are transmitted between the Server and the )ersonal computer. They

are/ )assive information and -ynamic active programs. The -ynamic, Self

e$ecuting programs cause serious problems in the areas of Security and probability. @ut,

Dava addresses those concerns and by doing so, has opened the door to an e$citing new

form of program called the Applet.

9a"a can *e used to create t#o types of programs:

App lic ati ons and Appl ets / An application is a program that runs on our

Computer under the operating system of that computer. #t is more or less li!e one creating

using C or C. Dava(s ability to create Applets ma!es it important. An Applet is an

application designed to be transmitted over the #nternet and e$ecuted by a Dava

compatible web browser. An applet is actually a tiny Dava 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. #t can react to the user input and dynamically

change.

)eatures of 9a"a Security:

'very time you that you download a QnormalR program, you are ris!ing a viral

infection. )rior to Dava, most users did not download e$ecutable programs fre"uently, and

*5


24/63


those who did scan them for viruses prior to e$ecution. 2ost users still worried about the

possibility of infecting their systems with a virus. #n addition, another type of malicious

program e$ists that must be guarded against. This type of program can gather private

information, such as credit card numbers, ban! account balances, and passwords. Dava

answers both these concerns by providing a QfirewallR between a networ! application and

your computer.

Porta*ility:

4or programs to be dynamically downloaded to all the various types of platforms

connected to the #nternet, some means of generating portable e$ecutable code is

needed .As you will see, the same mechanism that helps ensure security also helps create

portability. #ndeed, Dava(s solution to these two problems is both elegant and efficient.

+he yte code:

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

the output of Dava compiler is @yte code. @yte code is a highly optimized set of

instructions designed to be e$ecuted by the Dava runtime system, which is called the Dava

>irtual 2achine 8D>29. That is, in its standard form, the D>2 is an interpreter for byte

code.Translating a Dava program into byte code helps ma!es it much easier to run a

program in a wide variety of environments. The reason is, once the runtime pac!age

e$ists for a given system, any Dava program can run on it.

Although Dava was designed for interpretation, there is technically nothing about Dava that

prevents onthefly compilation of byte code into native code. Sun has just completed its

Dust #n Time 8D#T9 compiler for byte code. hen the D#T compiler is a part of D>2, it

compiles byte code into e$ecutable code in real time, on a piecebypiece, demand basis.

#t is not possible to compile an entire Dava program into e$ecutable code all at once,

because Dava performs various runtime chec!s that can be done only at run time. The D#T

compiles code, as it is needed, during e$ecution.

9a"a irtual &achine 9&/:

@eyond the language, there is the Dava virtual machine. The Dava virtual machine

is an important element of the Dava technology. The virtual machine can be embedded

within a web browser or an operating system. Once a piece of Dava code is loaded onto a

*7


25/63


machine, it is verified. As part of the loading process, a class loader is invo!ed and does

byte code verification ma!es sure that the code that(s has been generated by the compiler

will not corrupt the machine that it(s loaded on. @yte code verification ta!es place at the

end of the compilation process to ma!e sure that is all accurate and correct. So byte code

verification is integral to the compiling and e$ecuting of Dava code.

!"erall -escription:

)icture showing the development process of DA>A )rogram

Dava programming uses to produce byte codes and e$ecutes them. The first bo$

indicates that the Dava source code is located in a. Dava file that is processed with a Dava

compiler called javac. The Dava compiler produces a file called a. class file, which

contains the byte code. The .Class file is then loaded across the networ! or loaded locally

on your machine into the e$ecution environment is the Dava virtual machine, which

interprets and e$ecutes the byte code.

9a"a Architecture:

Dava architecture provides a portable, robust, high performing environment for

development. Dava provides portability by compiling the byte codes for the Dava >irtual

2achine, which is then interpreted on each platform by the runtime environment. Dava is

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

across the planet.

Compilation of code:

hen you compile the code, the Dava compiler creates machine code 8called byte

code9 for a hypothetical machine called Dava >irtual 2achine 8D>29. The D>2 is

supposed to e$ecute the byte code. The D>2 is created for overcoming the issue of

portability. The code is written and compiled for one machine and interpreted on all

machines. This machine is called Dava >irtual 2achine.

*;

9a"a Source 9a"a *yte code 9a"a&

Dava .Class


26/63


Compiling and interpreting 9a"a Source Code:

Simple

Dava was designed to be easy for the )rofessional programmer to learn and to use

effectively. #f you are an e$perienced C programmer, learning Dava will be even easier.

@ecause Dava inherits the C%C synta$ and many of the object oriented features of C.

2ost of the confusing concepts from C are either left out of Dava or implemented in a

cleaner, more approachable manner. #n Dava there are a small number of clearly defined

ways to accomplish a given tas!.

!*ject3!riented

Dava was not designed to be sourcecode compatible with any other language. This

allowed the Dava team the freedom to design with a blan! slate. One outcome of this was

a clean usable, pragmatic approach to objects. The object model in Dava is simple and

easy to e$tend, while simple types, such as integers, are !ept as highperformance non

objects.

Ro*ust

The multiplatform environment of the eb places e$traordinary demands on a

program, because the program must e$ecute reliably in a variety of systems. The ability to

create robust programs was given a high priority in the design of Dava. #t chec!s your

code at compile time and run time.Dava virtually eliminates the problems of memory

management and deallocation, which is completely automatic. #n a wellwritten Dava

program, all run time errors can and should be managed by your program.

*


27/63


-uring runtime the Dava interpreter tric!s the byte code file into thin!ing that it is

running on a Dava >irtual 2achine. #n reality this could be a #ntel )entium indows G;

or SunSAC station running Solaris or Apple 2acintosh running system and all could

receive code from any computer through #nternet and run the Applets.

9a"a Collections:

A collection H sometimes called a container H is simply an object that groups

multiple elements into a single unit. Collections are used to store, retrieve, manipulate,

and communicate aggregate data. Typically, they represent data items that form a natural

group, such as a po!er hand 8a collection of cards9, a mail folder 8a collection of letters9,

or a telephone directory 8a mapping of names to phone numbers9.

#f you


28/63


#nterfaces/ These are abstract data types that represent collections. #nterfaces allow

collections to be manipulated independently of the details of their representation. #n

objectoriented languages, interfaces generally form a hierarchy.

Implementations:

These are the concrete implementations of the collection interfaces. #n essence,

they are reusable data structures.

Algorithms:

These are the methods that perform useful computations, such as searching and

sorting, on objects that implement collection interfaces. The algorithms are said to be

polymorphic/ that is, the same method can be used on many different implementations of

the appropriate collection interface. #n essence, algorithms are reusable functionality.

enefits of the 9a"a Collections )rame#or8:

The Dava Collections 4ramewor! provides the following benefits/

Reduces programming effort:

@y providing useful data structures and algorithms, the Collections 4ramewor!

frees you to concentrate on the important parts of your program rather than on the low

level =plumbing= re"uired to ma!e it wor!. @y facilitating interoperability among

unrelated A)#s, the Dava Collections 4ramewor! frees you from writing adapter objects or

conversion code to connect A)#s.

Increases program speed and ,uality:

This Collections 4ramewor! provides high performance, high"uality

implementations of useful data structures and algorithms. The various implementations of

each interface are interchangeable, so programs can be easily tuned by switching

collection implementations. @ecause you


29/63


was little consistency among these ad hoc collections subA)#s, so you had to learn each

one from scratch, and it was easy to ma!e mista!es when using them. ith the advent of

standard collection interfaces, the problem went away.

Reduces effort to design ne# APIs:

This is the flip side of the previous advantage. -esigners and implementers don


30/63


-escription:

A -@2S is a comple$ set of software programs that controls the organization, storage,

management, and retrieval of data in a database. A -@2S includes/

A modeling language to define the schema of each database hosted in the -@2S,

according to the -@2S data model.

The four most common types of organizations are the hierarchical, networ!,

relational and object models. #nverted lists and other methods are also used. A

given database management system may provide one or more of the four

models. The optimal structure depends on the natural organization of the

application


31/63


may be authorized to view only payroll data, while others are allowed access

to only wor! history and medical data.

#f the -@2S provides a way to interactively enter and update the database, as

well as interrogate it, this capability allows for managing personal databases.

A transaction mechanism, that ideally would guarantee the AC#- properties, in order

to ensure data integrity, despite concurrent user accesses 8concurrency control9, and

faults 8fault tolerance9.

#t also maintains the integrity of the data in the database.

The -@2S can maintain the integrity of the database by not allowing morethan one user to update the same record at the same time. The -@2S can help

prevent duplicate records via uni"ue inde$ constraints for e$ample, no two

customers with the same customer numbers 8!ey fields9 can be entered into the

database. See AC#- properties for more information 8edundancy avoidance9.

hen a -@2S is used, information systems can be changed much more easily as

the organization%:

Structured Uuery :anguage 8SU:9 is the language used to manipulate relational

databases. SU: is tied very closely with the relational model. #n the relational model, data

5&


32/63


is stored in structures called relations or tables.SU: statements are issued for the purpose

of/

-ata definition: -efining tables and structures in the database 8--: used to create, alter

and drop schema objects such as tables and inde$es9.

-ata manipulation: +sed to manipulate the data within those schema objects 8-2:

#nserting, +pdating, -eleting the data, and Uuerying the -atabase9.

A schema is a collection of database objects that can include/ tables, views,

inde$es and se"uences

:ist of SU: statements that can be issued against an Oracle database schema are/

A%+ER Change an e$isting table, view or inde$ definition 8--:9

A(-I+ Trac! the changes made to a table 8--:9

C!&&E'+ Add a comment to a table or column in a table 8--:9

C!&&I+ 2a!e all recent changes permanent 8-2: transactional9

CREA+E Create new database objects such as tables or views 8--:9

-E%E+E -elete rows from a database table 8-2:9

-R!P -rop a database object such as a table, view or inde$ 8--:9

6RA'+ Allow another user to access database objects such as tables or views

8--:9

I'SER+ #nsert new data into a database table 8-2:9

'o A(-I+ Turn off the auditing function 8--:9

RE!?E -isallow a user access to database objects such as tables and views

8--:9

R!%%AC? +ndo any recent changes to the database 8-2: Transactional9

SE%EC+ etrieve data from a database table 8-2:9

+R('CA+E -elete all rows from a database table 8can not be rolled bac!9

8-2:9

(P-A+E Change the values of some data items in a database table 8-2:9

5*


33/63


9a"a Ser"er Pages 9SP/:

Dava server )ages is a simple, yet powerful technology for creating and

maintaining dynamiccontent web pages. @ased on the Dava programming language, Dava

Server )ages offers proven portability, open standards, and a mature reusable componentmodel .The Dava Server )ages architecture enables the separation of content generation

from content presentation. This separation not eases maintenance headaches it also

allows web team members to focus on their areas of e$pertise. 0ow, web page designer

can concentrate on layout, and web application designers on programming, with minimal

concern about impacting each other(s wor!.

7.1.@ e* ser"er5Application ser"ere

A Dava Server )ages file may be accessed in at least two different ways. A client(s

re"uest comes directly into a Dava Server )age. #n this scenario, suppose the page

accesses reusable Dava @ean components that perform particular welldefined

computations li!e accessing a database. The result of the @eans computations, called

result sets is stored within the @ean as properties. The page uses such @eans to generate

dynamic content and present it bac! to the client.

Steps in the e$ecution of a 9SP Application:

The client sends a re"uest to the web server for a DS) file by giving the name of

the DS) file within the form tag of a T2: page.

This re"uest is transferred to the Dava ebServer. At the server side Dava

ebServer receives the re"uest and if it is a re"uest for a jsp file server gives this re"uest

to the DS) engine.

DS) engine is program which can under stands the tags of the jsp and then it

converts those tags into a Servlet program and it is stored at the server side. This Servletis loaded in the memory and then it is e$ecuted and the result is given bac! to the

DavaebServer and then it is transferred bac! to the result is given bac! to the

DavaebServer and then it is transferred bac! to the client.

55


34/63


Applications Ser"er:

An application server is a software engine that delivers applications to client

computers or devices, typically through the #nternet and using the yperte$t Transfer

)rotocol. Application servers are distinguished from web servers by the e$tensive use of

serverside dynamic content and fre"uent integration with database engines.

Common features:

Application server products typically bundle middleware to enable applications to

intercommunicate with dependent applications, li!e web servers, database management

systems, and chart programs. Some application servers also provide an A)#, ma!ing them

operating system independent. )ortals are a common application server mechanism by

which a single point of entry is provided to multiple devices.

Dava application servers

57


35/63


9a"a EE Ser"ers

4ollowing the success of the Dava platform, the term application server sometimes

refers to a Dava )latform'nterprise 'dition 8D*''9 or Dava '' ; application server.

Among the better !nown Dava 'nterprise 'dition application servers are eb:ogic

Server 8@'A9, D@oss 8ed at9, ebSphere 8#@29, Dun 8Adobe9, Apache 1eronimo

8Apache 4oundation, based on #@2 ebSphere9, Oracle OC7D8Oracle Corporation9, Sun

Dava System Application Server 8Sun 2icrosystems9 and 1lassfish Application Server

8based on Sun Dava System Application Server9.

Chapter


36/63


Screen


37/63


Screen


38/63


Screen


39/63


Screen


40/63


Screen


41/63


Screen


42/63


Screen


43/63


Screen


44/63


Screen


45/63


Screen


46/63


Screen


47/63


Screen


48/63


Screen


49/63


Screen


50/63


Screen


51/63


Screen


52/63


Screen


53/63


Screen


54/63


Software Testing is the process used to help identify the correctness,

completeness, security, and "uality of developed computer software. Testing is a process

of technical investigation, performed on behalf of sta!eholders, that is intended to reveal

"ualityrelated information about the product with respect to the conte$t in which it is

intended to operate. This includes, but is not limited to, the process of e$ecuting a

program or application with the intent of finding errors. Uuality is not an absolute it is

value to some person. ith that in mind, testing can never completely establish the

correctness of arbitrary computer software testing furnishes a criticism or comparison

that compares the state and behaviour of the product against a specification. An important

point is that software testing should be distinguished from the separate discipline of

Software Uuality Assurance 8SUA9, which encompasses all business process areas, not

just testing.

There are many approaches to software testing, but effective testing of comple$

products is essentially a process of investigation, not merely a matter of creating and

following routine procedure. One definition of testing is =the process of "uestioning a

product in order to evaluate it=, where the ="uestions= are operations the tester attempts to

e$ecute with the product, and the product answers with its behavior in reaction to the

probing of the testerVcitation neededW. Although most of the intellectual processes of

testing are nearly identical to that of review or inspection, the word testing is connoted to

mean the dynamic analysis of the productHputting the product through its paces. Some

of the common "uality attributes include capability, reliability, efficiency, portability,

maintainability, compatibility and usability. A good test is sometimes described as one

which reveals an error however, more recent thin!ing suggests that a good test is one

which reveals information of interest to someone who matters within the project

community.#n general, software engineers distinguish software faults from software failures.

#n case of a failure, the software does not do what the user e$pects. A fault is a

programming error that may or may not actually manifest as a failure. A fault can also be

described as an error in the correctness of the semantic of a computer program. A fault

will become a failure if the e$act computation conditions are met, one of them being that

the faulty portion of computer software e$ecutes on the C)+.

Software testing may be viewed as a subfield of Software Uuality Assurance but

typically e$ists independently 8and there may be no SUA areas in some companies9. #n

;7


55/63


SUA, software process specialists and auditors ta!e a broader view on software and its

development. They e$amine and change the software engineering process itself to reduce

the amount of faults that end up in the code or deliver faster.

egardless of the methods used or level of formality involved the desired result of testing

is a level of confidence in the software so that the organization is confident that the

software has an acceptable defect rate. hat constitutes an acceptable defect rate depends

on the nature of the software. An arcade video game designed to simulate flying an

airplane would presumably have a much higher tolerance for defects than software used

to control an actual airliner.

A problem with software testing is that the number of defects in a software

product can be very large, and the number of configurations of the product larger still.

@ugs that occur infre"uently are difficult to find in testing. A rule of thumb is that a

system that is e$pected to function without faults for a certain length of time must have

already been tested for at least that length of time. This has severe conse"uences for

projects to write longlived reliable software.

A common practice of software testing is that it is performed by an independent

group of testers after the functionality is developed but before it is shipped to the

customer. This practice often results in the testing phase being used as project buffer to

compensate for project delays. Another practice is to start software testing at the same

moment the project starts and it is a continuous process until the project finishes.

Another common practice is for test suites to be developed during technical support

escalation procedures. Such tests are then maintained in regression testing suites to ensure

that future updates to the software don


56/63


programmers 8often with pair programming in the e$treme programming methodology9.

Of course these tests fail initially as they are e$pected to. Then as code is written it

passes incrementally larger portions of the test suites. The test suites are continuously

updated as new failure conditions and corner cases are discovered, and they are integrated

with any regression tests that are developed.

+nit tests are maintained along with the rest of the software source code and

generally integrated into the build process 8with inherently interactive tests being

relegated to a partially manual build acceptance process9.

The software, tools, samples of data input and output, and configurations are all

referred to collectively as a test harness.


57/63


made available to the open public to increase the feedbac! field to a

ma$imal number of future users.

#t should be noted that although both Alpha and @eta are referred to as testing it is

in fact use emersion. The rigors that are applied are often unsystematic and many of the

basic tenets of testing process are not used. The Alpha and @eta period provides insight

into environmental and utilization conditions that can impact the software.

After modifying software, either for a change in functionality or to fi$ defects, a

regression test reruns previously passing tests on the modified software to ensure that the

modifications haven


58/63


The most common term for a collection of test cases is a test suite. The test suite

often also contains more detailed instructions or goals for each collection of test cases. #t

definitely contains a section where the tester identifies the system configuration used

during testing. A group of test cases may also contain prere"uisite states or steps, and

descriptions of the following tests.Collections of test cases are sometimes incorrectly

termed a test plan. They might correctly be called a test specification. #f se"uence is

specified, it can be called a test script, scenario or procedure.

A sample testing cycle:

Although testing varies between organizations, there is a cycle to testing/

&. e"uirements Analysis/ Testing should begin in the re"uirements phase of the

software development life cycle.

-uring the design phase, testers wor! with developers in determining what aspects

of a design are testable and under what parameter those tests wor!.

*. Test )lanning/ Test Strategy, Test )lan8s9, Test @ed creation.

5. Test -evelopment/ Test )rocedures, Test Scenarios, Test Cases, Test Scripts to

use in testing software.

7. Test '$ecution/ Testers e$ecute the software based on the plans and tests and

report any errors found to the development team.

;. Test eporting/ Once testing is completed, testers generate metrics and ma!e final

reports on their test effort and whether or not the software tested is ready for

release.

. etesting the -efects

Chapter =: Conclusion

The Respiratory and Search Engine for Alumni of College is a webbased

;F


59/63


application for primarily providing training to the Accountants who provide customized

solutions to meet organizational needs.

This application software has been computed successfully and was also tested

successfully by ta!ing Qtest casesR. #t is user friendly, and has re"uired options, which can

be utilized by the user to perform the desired operations.

The software is developed using Dava as front end and Oracle as bac! end in

indows environment. The goals that are achieved by the software are/

#nstant access.

#mproved productivity.

Optimum utilization of resources.

'fficient management of records.

Simplification of the operations.

:ess processing time and getting re"uired information.

+ser friendly.

Chapter @: )uture Enhancements

;G


60/63


#t is not possible to develop a system that ma!es all the re"uirements of the user. +ser

re"uirements !eep changing as the system is being used. Some of the future

enhancements that can be done to this system are/

As the technology emerges, it is possible to upgrade the system and can be

adaptable to desired environment.

@ecause it is based on objectoriented design, any further changes can be easily

adaptable.

@ased on the future security issues, security can be improved using emerging

technologies.

Attendance module can be added

sub admin module can be added

i*liography:

?


61/63


Core DavaX * >olume ## Advanced - Cay S. ortsman

)earson 'ducation Sun 2icrosystems 1ary Cornell

ead 4irst Servlets Y DS) - 'ric 4reeman

O(eilly S)- 'lisabeth

4reeman

The @oo! of DavaScript *nd'dition - thau

S)-

'ffective Dava )rogramming :anguage

1uide

- Doshua @loch

)earson 'ducation Sun 2icrosystems

Dava -atabase @est )ractices - 1eorge eese

O(eilly S)-

eal orld eb Services

O(eilly S)--

ill #verson

D@oss A -evelopers 0oteboo! - 0orman ichards

O(eilly S)- Sam 1riffith

Referred sites:

http:55###.#schools.com

http:55###.ja"a*eginner.com

http:55###.jsptut.com

http:55programmingtutorials.com

http:55gee8mantra.com

http:55###.ja"a#orld.com

http:55###.free#e*schools.com

http:55###.j2ee.masslight.com

&
http://www.w3schools.com/http://www.javabeginner.com/http://www.jsptut.com/http://programmingtutorials.com/http://geekmantra.com/http://www.javaworld.com/http://www.freewebschools.com/http://www.j2ee.masslight.com/http://www.w3schools.com/http://www.javabeginner.com/http://www.jsptut.com/http://programmingtutorials.com/http://geekmantra.com/http://www.javaworld.com/http://www.freewebschools.com/http://www.j2ee.masslight.com/


62/63


*


63/63


repository and search engine for alumni of collage.doc

Documents