“JOURNAL SERVER”

Project submitted in partial fulfillment of the requirements for

the

award of the Degree of

Master of Computer Applications

of

SASTRA

Submitted by

“ANJANA.N”
Register No: 011170719

Under the Supervision and Guidance of

Shri. N. SENTHIL ANAND

DEPARTMENT OF COMPUTER APPLICATIONS

School of Computing
SASTRA University
(A university U/s 3 of the UGC Act, 1956)
Thanjavur – 613 401
April – 2011

i
 DEPARTMENT OF COMPUTER APPLICATIONS
School of Computing
SASTRA University
(A university U/s 3 of the UGC Act, 1956)
Thanjavur – 613 401

Bonafide Certificate

Certified that this project report entitled

“JOURNAL SERVER”

Is a bonafide record of work done by

“ANJANA.N”
Register No: 011170719

In partial fulfillment of the requirements for award of the

Degree of Master of Computer Applications
During the year 2009-2011

Internal Guide Associate Dean, CA

Submitted for Project Viva-voce examination held on _________

Internal Examiner External Examiner

ii
iii
 ACKNOWLEDGEMENT

My heartfelt gratitude and thanks to my parents and my friends without whose

unconstrained support, I could not have made this career in Computer Science &

Technology

I would like to express my heartfelt gratitude to the Mentor of this Esteemed

University Prof. R. SETHURAMAN, Vice-Chancellor, SASTRA University for his

valuable encouragement.

I express our heartfelt gratitude to Dr. S. N. SRIVASTAVA, Registrar,

SASTRA University for granting us to take up this project.

I am very grateful to Prof. P. KALYANARAMAN, Dean, School of

Computing, SASTRA University for permitting me to undertake this project. I extend

my thanks to DR. S. GOPALAKRISHNAN, Professor and Associate Dean,

Department of Computer Applications, SASTRA University, Thanjavur, Whose

motivation and valuable advice has served me in good stead.

I am pleased convey my gratitude to Mr. PARTHASARATHI

BYRAPURAM, Project Manager HP GLOBAL SOFT PRIVATE LIMITED,

Chennai for providing me this opportunity to do my project at HP GLOBAL SOFT

PRIVATE LIMITED, Chennai.

“Guidance is the first step that leads to success”

It gives me great pleasure to express my profound thanks to my Internal guide

Shri. N. SENTHIL ANAND, Department of Computer Applications, SASTRA

University, for his continual support and enduring guidance through out my project

tenure.

iv
 With profound indebtedness I thank Mr. S. ANAND SARANATH and Mr.

NARASIMHA PUVVADA my External guides, HP GLOBAL SOFT PRIVATE

LIMITED, Chennai for their constant encouragement and expert guidance throughout

the project.

I also thank my team members who have helped in successful completion of

the Project.

I also convey my thanks to all those who have contributed either directly or

indirectly for the successful completion of this project.

v
 SYNOPSIS

Purpose of the project:

“Journal Server” is a web based Application. The journal server maintains the

adding, reviewing, deleting the journals contained in it. The authors can track the

progress of their submissions, access reviewer comments, revise and resubmit articles

This application provides the users with improved and finely grained indexing

of searching the content. It helps a lot in the field of research. This application aims to

provide the most complete and reliable source of information on current

developments in the field of science. The emphasis will be on publishing quality

articles rapidly and freely available worldwide.

Scope of the project:

• The project titled “JOURNAL SERVER” will consist of scientific journals

being published.

• These journals are submitted in the pdf format.

• Audio/video format of articles are not supported and could be extended in

future.

• This project started on January, 2011 and will be completed by April, 2011.

• It has four stake holders such as reader, author, reviewer and editor.

vi
 ABSTRACT

“JOURNAL SERVER” aims at publishing the Scientific journals at free of

cost. This project deals with online uploading, reviewing, publishing and also offline

reading which can be obtained through download. Journal server is a web based

application that is developed in Java 1.5, JBoss 5.1 as application server and oracle

10g XE as database. Journal server serves with the aim of providing FREE online

access and helps the leading academics and researchers make their work visible and

accessible to diverse new audiences around the world. Journal articles may be

accessed directly from the journal or from archives listing. The journal will support

documents in pdf format only. It is user friendly and provides ease of use to the

readers.

The reader could search for the journals by using the title of the journal, name

of the author or keyword or a combination of them. The reader may get articles based

on the search criteria. From this list he/she can choose to view online or download the

article.

The author can submit articles only after registering himself to the journal

server.The submitted articles are viewed by the editor and sent for review. The author

can see the review comments of his/her article.

Today, in our current scope, discipline is not taken into account. In future,

journal server provides access to,

• Support Disciplines

• Rating of documents

• Audio/video format information

• E-alerts.
Chapter No. Contents Page No.

Introduction
1.0 a) Introduction to the Company
b) Background of the Project
2.0 Software Project Plan
Software Requirements Specification
a) Functional requirements
b) Non Functional Requirements
3.0
• Resources requirements
• Security requirements

System analysis
a) Software Requirement specification
b) Identified modules and use cases
c) Use case Diagram
d) Use case specification
4.0 e) Class diagram
f) State transition diagram
g) E-R diagram
h) Domain model
i) Sequence model

Design
5.0
a) Input design( Sample)
Testing
a) Unit testing
6.0
b) Integration testing
c) Validation testing
Implementation
7.0 a) Problem Faced
b) Lessons Learnt
8.0 Future Plans
9.0 Conclusion
10.0 References\Bibliography
vii
viii
INTRODUCTION
1.1. INTRODUCTION TO HEWLETT PACKARD

Mission statement of Hewlett Packard

"To provide products, services and solutions of the highest quality and deliver

more value to our customers that earns their respect and loyalty."

Vision statement of Hewlett Packard

"To view change in the market as an opportunity to grow; to use our profits

and our ability to develop and produce innovative products, services and solutions

that satisfy emerging customer needs."

About us:

Hewlett Packard was founded in 1939. Corporate headquarters is in Palo

Alto, California. Léo Apotheker is the CEO and President. Hewlett Packard is a

technology company that operates in more than 170 countries around the world. It

explores how technology and services can help people and companies address their

problems and challenges, and realize their possibilities, aspirations and dreams. We

apply new thinking and ideas to create simpler, valuable and trusted experiences with

technology. It ship more than 1 million printers per week. We ship 48 million PC

units annually. One out of every three servers shipped worldwide is from Hewlett

Packard.

-2-
 1.2 BACKGROUND OF THE PROJECT

“JOURNAL SERVER” aims at publishing the Scientific journals at free of

cost. This project deals with online uploading, reviewing, publishing and also offline

reading which can be obtained through download. The submitted articles will be

reviewed by three levels of reviewers and based upon their result the articles would be

published or rejected.

Journal server is a web based application which is developed in java, JBOSS

as application server and oracle as database. Journal server serves with the aim of

providing FREE online access and we are helping leading academics and researchers

make their work visible and accessible to diverse new audiences around the world

.Journal articles may be accessed by direct link from the journal to an archived listing.

The contents of the journals are provided in the text format. It is user friendly and

provides ease of use to the readers.

In Future journal server provides access, search and browse the content in a

variety of ways for different discipline of journals. Get e-alerts for new content on

desired subject keywords. It also supports audio / video format of journals.

-3-
SOFTWARE PROJECT PLAN
 2.0 SOFTWARE PROJECT PLAN

Project Starting Date: 27/01/2011

Project Finishing Date: 18/04/2011

Description of the Task No of Days to No of hours to

Complete Complete

Business Description 3 24

Software Requirement gathering 15 120

Analysis and design 16 128

Coding & Testing 20 160

Implementation 10 80

Documentation 6 48

Total 70
560

-5-
SOFTWARE REQUIREMENT
SPECIFICATION
3.0 SOFTWARE REQUIREMENT SPECIFICATION
3.1 Functional requirements

• This application supports only for the publication of scientific journals.

• This application facilitates the users of searching article by author name or

title or keyword.

• This application provides text format in which the articles are displayed.

• This application allows the user to download only 5 journals per day.

• It also allows the users to post their comments related to the article and the

valuable comments are taken in consideration for review.

• For publishing article in this application the author must register themselves.

• This application expects metadata from the author which includes Title,

Abstract and Discipline.

• In this application the editor alone is allowed to publish the Journal.

• This application allows the editor to assign reviewers based on their resume

posted, which is related to current journal in process.

• This application ensures whether the uploaded article is in the specified format

and it is evaluated by the editor.

• The editor updates the check status.

• This application supports 3 levels of reviews for publishing quality journals.

• The published journal must be available for quarter year.

• Journal server must be online 24/7 a day on the internet

 -7-

3.2. Non-functional requirement

• The journal server must be online 24/7 a day on the internet.

• The published journal must be available for quarter year.

• The system should respond to any request in 2 seconds.

• The system shall ensure that data is protected from unauthorized access.

• HP L1506 Pentium-based PC with a standard or better keyboard, mouse and

monitor.

• Performance requirements: response time, throughput, reliability, availability

of components.

• Security: only authorized access for changing data.

3.2.1 Resources requirement

3.2.1.1 Software requirements

Operating System : Windows XP

Language : JAVA 1.5

Data Bases : Oracle10G XE

Front End : JSP

Server : Jboss 5.1

 -8-

3.2.1.2 Hardware requirements

Processor : Any Processor above 2.4 GHZ

Ram : 2 G.B.

Hard Disk : 80 GB.

Input device : Standard Keyboard and Mouse.

Output device : VGA and High Resolution Monitor.

3.2.2 Security requirement

Only authorized users are allowed to submit article to the journal server.

Unauthorized users cannot access journal server easily.

 -9-

SYSTEM ANALYSIS
 4.0 SYSTEM ANALYSIS
4.1 Software requirement specification

4.1.1 READER

• The reader chooses a way to search the journal server. The choices are by

Author, Title and Keyword.

• If the search is by Author, the system creates and presents an alphabetical

list of authors.

• If the search is by Title, the system creates and presents an alphabetical

list of journals in the journal server.

• If the search is by Keyword, the system creates and presents the journals

related to the keyword given by the author.

• After search is complete, the reader may also download the respective

journal for later reference.

4.1.2 AUTHOR

• The author needs to be registered with the journal server before

submitting articles to the journal server.

• The author submits the article and is also allowed to read others

articles.

• The author provides metadata about the journal which he submits.

• The author enters the article in the specified format and submits to the

Journal Server.
 • After passive review of the article by the editor the article is being sent

for review.

• The author could view the review comments of his/her article.

-11-

4.2 IDENTIFIED MODULES AND USE CASES:

4.2.1 MODULES:

• Reader

• Author

4.2.2 USE CASES:

• Search by author

• Search by title

• Search by keyword

• Download journal

• Register author

• Login author

• Submit article

• Submit reworked article

 • View review comments

-12-
4.3 Use case diagram

4.3.1 USE CASE DIAGRAM FOR READER

 -13-

4.3.2 USE CASE DIAGRAM FOR AUTHOR

 -14-

4.4 Use case specification

1. Search by author

1.1 Use case name:

Search by author

1.2 Description:

The reader searches for the required journal from the journal server by using
the name of the author.

1.3 Actors:

Reader

1.4 Pre condition:

None

1.5 Post Condition

Successful retrieval

1.6 Basic flow: Successful Retrieval

 1.6.1 The reader searches for the required journal by using the name of the
author

1.6.2 The journal is retrieved.

1.7 Alternate Flow:

1.7.1 If the journal specified by the reader is not found in the journal server it
will be displayed as “Journal not found”.

-15-

2. Search by title

2.1 Use case name:

Search by title

2.2 Description:

The reader searches for the required journal from the journal server by using
the title of the journal.

2.3 Actors:

Reader

2.4 Pre condition:

None

2.5 Post Condition

Successful retrieval

2.6 Basic flow: Successful Retrieval

 2.6.1 The reader searches for the required journal by using the
title of the journal.

2.6.2 The journal is retrieved.

2.7 Alternate Flow:

2.7.1 If the journal specified by the reader is not found in the journal server it
will be displayed as “Journal not found”.

-16-

3. Search by keyword

3.1 Use case name:

Search by keyword

3.2 Description:

The reader searches for the required journal from the journal server by using
the keyword of the journal.

3.3 Actors:

Reader

3.4 Pre condition:

None

3.5 Post Condition

Successful retrieval

3.6 Basic flow: Successful Retrieval

 3.6.1 The reader searches for the required journal by using the
keyword of the journal.

3.6.2 The journal is retrieved.

3.7 Alternate Flow:

3.7.1 If the journal specified by the reader is not found in the journal server it
will be displayed as “Journal not found”.

-17-

4. Download journal

4.1 Use case name:

Download journal

4.2 Description:

The reader searches for the required journal from the journal server and
downloads.

4.3 Actors:

Reader

4.4 Pre condition:

None

4.5 Post Condition

Successful download

4.6 Basic flow:

 4.6.1 The reader searches for the required journal by using the options such as
name of the author, name of the journal or keyword about the journal.

4.6.2 The journal is retrieved.

4.6.3 The reader downloads the journal and keeps it for his/her later reference.

4.7 Alternate Flow:

4.7.1 If the journal specified by the reader is not found in the journal server it
will be displayed as “Journal not found”.

-18-

5. Register author

5.1 Use case name:

Register author

5.2 Description:

The author needs to be registered before submitting articles to the journal

server. After successful registration he is allowed to submit his/her article.

5.3 Actors:

Author

5.4 Pre condition:

None

5.5 Post Condition

Successful Registration

5.6 Basic flow:

 5.6.1 The author registers himself/herself with the journal server.

5.6.2 The author is successfully registered.

5.6.3 The author submits his/her article to the journal server.

5.7 Alternate Flow:

5.7.1 If the registration is not successful the author cannot submit his/her
article to the journal server.

-19-

6. Login author

6.1 Use case name:

Login author

6.2 Description:

The author after registration, logs in to the journal server.

6.3 Actors:

Author

6.4 Pre condition:

None

6.5 Post Condition

Successful login

6.6 Basic flow: Successful Login

6.6.1 The author enters his/her username and password.

 6.6.2 The journal server logs in the author.

6.7 Alternate Flow:

6.7.1 If the author fails to provide the correct user name and password, the
journal server displays the message as “Login failed”.

-20-

7. Submit Article

7.1 Use case name:

Submit article

7.2 Description:

The author submits his/her journal to the journal server.

7.3 Actors:

Author

7.4 Pre condition:

The author should have been registered before submitting his/her journal.

7.5 Post Condition

Successful submission

7.6 Basic flow: Successful Submission

7.6.1 The author registers himself/herself in the journal server.

 7.6.2 The author uploads his/her journal onto the journal server.

7.6.3 The author after uploading, clicks the submit button and the journal gets
submitted.

7.7 Alternate Flow:

7.7.1 If the journal doesn’t get submitted in the journal server it displays as
“Journal is not submitted”.

-21-

8. Submit reworked article

8.1 Use case name:

Submit reworked article

8.2 Description:

The author submits his/her reworked article to the journal server.

8.3 Actors:

Author

8.4 Pre condition:

The author should have been submitted his/her article before rework is
carried on.

8.5 Post Condition:

Successful submission

8.6 Basic flow:

8.6.1 The author uploads his/her article onto the journal server.
 8.6.2 The author receives his/her article back for rework.

8.6.3 The author after reworking the article submits back to the journal server.

8.7 Alternate Flow:

8.7.1 If the article doesn’t gets submitted in the journal server. It displays as
“Article not submitted”.

-22-

9. View review comments

9.1 Use case name:

View review comments.

9.2 Description:

The author views the review comments given to his/her article after review.

9.3 Actors:

Author

9.4 Pre condition:

The author should have been submitted his/her article before review.

9.5 Post Condition

Successful view.

9.6 Basic flow:

9.6.1 The author submits his/her article for review.

 9.6.2 The author views his/her review comments given to his/her article after
review

9.7 Alternate Flow:

9.7.1 If the article doesn’t receive any review comments so far journal server
displays as “No review comments so far”.

-23-

4.5 Class diagram

 -24-

4.6 State transition diagram

 -25-

4.7 E-r diagram

 Name

Author ID

Status Submitted by AUTHOR E-mail ID

Journal ID Author

Name
Name
Reviewed by
JOURNAL REVIEWER
Reviewer ID

Pages

Designation

Volume
Date of Published by Assigned by
publishing

By title
Downloaded by
Searched by
EDITOR
By author
name

By keyword
READER

-26-

4.8 Domain model

 -27-

4.9 Sequence diagram

4.9.1 AUTHOR REGISTRATION

-28-

4.9.2 AUTHOR LOGIN

 -29-

4.9.3 SUBMIT ARTICLE AND REWORKED ARTICLE

 -30-

4.9.4 VIEW REVIEW COMMENTS

-31-
DESIGN

5.0 DESIGN
5.1 Front end design

5.1.1 HOME PAGE

JOURNALSERVER
Welcome to Journal Server

WelcomeW
toelcometo
Journal Journa
serverl server

• “JOURNAL SERVER ” aims publishing the

Scientific journals at free of cost .
Journals • This project deals with online uploading , reviewing ,
publishing and also offline reading which can be
obtained through download

Search Journals

Articles User Name

All Fields
Author
Password
Key word
Search Articles
Title
Register Login

-33-

5.1.2 REGISTRATION PAGE

 JOURNAL SERVER
Registration Page
Author
Author
Reviewer
Reviewer

Name

Name
User Name

User Name
Password

Password
Email id

Email id
Date of birth
Area of interest
Nationality
Date of birth

Nationality

Work Details

Register Cancel
Register Cancel

-34-
5.1.3 ARTICLE SUBMISSION FORM

JOURNALSERVER
Application Title Author Home Page

Submit Article
Submit Article
View Review comments
Title:
Articles to be Reworked
Abstract:
(Not More Than
Change Profile
100 Words)

Logout

Article
Browse

(Only PDF format Supported )

Submit Cancel

-35-

5.1.4 REVIEW COMMENTS FORM

 JOURNAL SERVER
Author Home Page

Submit Articles View Review Comments

View Review Comments

Article Name Article Reviewer Comments Rating

Articles to be Reworked

Change Profile

Logout

OK Cancel

-36-

5.1.5 REWORKED ARTICLES FORM

 JOURNAL SERVER
Author Home Page

Submit Articles
Articles to be Reworked

View Review Comments

Article Name Article Reviewer Comments

Articles to be Reworked

Change Profile

Logout

OK Cancel

-37-

5.1.6 AUTHOR PROFILE FORM

 JOURNAL SERVER
Author Home Page

Submit Articles
Change Profile

View Review Comments

Name:
Articles to be Reworked

User Name:
Change Profile

Logout Password: Edit

Email id:
Edit

Date of Birth
:

Nationality
:

Apply Cancel

-38-
 TESTING

6.0 TESTING

Testing can also be stated as the process of validating and verifying that a

software program/application/product:
 (1) Meets the business and technical requirements that guided its

design and development;

(2) Works as expected; and can be implemented with the same

characteristics.

Depending on the testing method employed, it can be implemented at any time

in the development process. However, most of the test effort occurs after the

requirements have been defined and the coding process has been completed.

-40-

6.1 Unit Testing

 Unit testing is a procedure used to validate that individual units of

source code are working properly. The goal of unit testing is to isolate each part of

the program and show that the individual parts are correct. A unit test provides a

strict, written contract that the piece of code must satisfy. As a result, it affords

several benefits.

Unit testing is typically done by software developers to ensure that the

code they have written meets software requirements and behaves as the developer

intended. Each unit of the System implemented in the source code is checked for

correctness. All error-handling paths are tested.

As far as Journal server concern Registration form, Login form are

taken as independent modules. Each one has been tested successfully with

suitable values.

These type of tests are usually written by developers as they work on code (white-box

style), to ensure that the specific function is working as expected. One function might

have multiple tests, to catch corner cases or other branches in the code. Unit testing

alone cannot verify the functionality of a piece of software, but rather is used to assure

that the building blocks the software uses work independently of each other.

-41-
 6.1.1 Registration page:
Test
S.No Test Condition Test Input Expected Result Actual Result
Result
Message should be
All fields are displayed to show
entered. ‘Registration
Expected
All fields are success’
1. message is Pass
mandatory Error message
displayed
Any one field is should be displayed
left blank. to show
‘Registration failed’
Year with four The cursor should
digits are move to the next
The D.O.B column
entered field. Expected
should be entered Pass
2. Error message message is
with four digits for Only two digits
should be displayed displayed
the year of the year is
to show ‘Enter a
entered
year with four digits’

Enter a record The cursor should

with last name move to the next
of 10 characters field.
Last name may Expected
Pass
3. not exceed 15 Error message message is
characters. Enter a record should be displayed displayed
with last name to show ‘Enter a
of 16 characters name between 1-15
characters’
The cursor should
Numeric value
move to the next
Only Numeric entered
field. Expected
values have to be
4. Error message message is Pass
entered in the
Non-Numeric should be displayed displayed
D.O.B field
value entered to show ‘Enter only
numerals’
6.1.2 Journal server homepage:
 Test
S No Test Condition Test Input Expected Result Actual Result
Result
Message should be
Enter a record displayed showing
with correct ‘Login success’ and
Username and username and should redirect to
Expected
password should password the author’s
1. message is Pass
be entered homepage.
displayed
correctly Error message
Enter a record
should be displayed
with wrong
to show ‘Login
username
failed’
Enter a journal
Error Message that is available The journal should
should be in the journal be retrieved .
Expected
displayed if the server.
2. message is Pass
requesting Error message
Enter a journal displayed
journals are not should be displayed
that is not in the
found. as ‘Journals not
journal server
found’
Enter an article
that is available The article should
Error Message
in the journal be retrieved.
should be Expected
server.
3. displayed if the message is Pass
Error message
requesting articles Enter an article displayed
should be displayed
are not found. that is not in the
as ‘Articles not
journal server
found’
 -43-
6.1.3 Author home page:

Test
S No Test Condition Test Input Expected Result Actual Result
Result
The journal server
All fields are should redirect to
entered. the successive
Expected
All fields are step.
1. message is Pass
mandatory Error message
displayed
Any one field is should be displayed
left blank. to show ‘ Enter all
fields ’
Submit an article Accept the file and
While submitting which is in the displays a message
articles to the pdf format. ‘File uploaded’ Expected
2. journal server it Error Message message is Pass
Submit an article
should be only pdf should be displayed displayed
which is in the
format saying ‘Wrong
text format.
format’

-44-
 6.2 Integration testing

Integration testing is a logical extension of unit testing. In its simplest

form, two units that have already been tested are combined into a component and

the interface between them is tested. A component, in this sense, refers to an

integrated aggregate of more than one unit. In a realistic scenario, many units are

combined into components, which are in turn aggregated into even larger parts of

the program. The idea is to test combinations of pieces and eventually expand the

process to test your modules with those of other groups. Eventually all the

modules making up a process are tested together. Beyond that, if the program is

composed of more than one process, they should be tested in pairs rather than all

at once. Journal server is a web based application. The interface between modules

was tested using appropriate test cases. In the Journal server module every

individual form is integrated.

Integration testing identifies problems that occur when units are

combined. By using a test plan that requires you to test each unit and ensure the

viability of each before combining units, you know that any errors discovered

when combining units are likely related to the interface between units. This

method reduces the number of possibilities to a far simpler level of analysis.

-45-
 6.3 Validation testing

Software validation testing is essentially a task carried out by a software tester.

The aim is to check, if the software has been made in lines with the requirements of

the client. The aim of software testing is to measure the quality of software in terms of

number of defects found in the software, the number of tests run and the system

covered by the tests. These tests are carried out for both the functional and non

functional attributes of the software. When bugs or defects are found with the help of

testing, the bug is logged and the developers team fixes the bug. Once the bug is fixed

and testing is carried out again to ensure that the bug was indeed fixed and no new

defects have been introduced in the software.

-46-

Test
S.No Test Condition Test Input Expected Result Actual Result
Result
The cursor should be
Characters are
moved to the next
entered.
Only character field. Expected
1. should be entered in Error message should message is Pass
the name field Numerals are be displayed to show displayed
entered. ‘Enter only
characters’
The cursor should be
Numerals are
moved to the next
entered.
Only numerals field. Expected
2. should be entered in Error message should message is Pass
the D.O.B field Character is be displayed to show displayed
entered. ‘Enter only
characters’

6.4 Debugging
 Debugging is the process of isolating and correcting the causes of known

errors. Traditional debugging techniques include:

(1) Snapshot dumps which are machine-level representations of the partial

or total program state at a particular point in the execution sequence.

(2) Trace facilities that list changes in selected state components.

(3) Traditional breakpoint facility that interrupts program execution and

transfers control to the programmer’s terminal when execution reaches a

specified break instruction in the source code.

Extensive debugging was done using all three techniques during the course

of the development of the proposed system to identify and correct syntax.

-47-
IMPLEMENTATION

7.0 IMPLEMENTATION
 The process of ensuring that the information system is operational and then

allowing the users to take over its operation for evaluation and application is

called as implementation. The new system may be entirely new, replacing an

existing manual or automated system. It can also be a major modification in an

existing system. The journal server is a new system and it could be extended to a

greater extent in future.

7.1 Problems Faced

As I was new to Jboss environment at the beginning I felt difficult to work and

with the help of my guide I came across it and now it is become easy for me to work

with this oracle forms and reports. I felt difficulty while configuring Jboss. As the

domain was very new to me I felt struck at many situations and persuaded again with

the guidance of my external guides. This is the first time I was working on real time

project. While designing forms I faced some problems. Also I faced problems while I

created submission forms.

7.2 Lessons Learnt

I learnt how to work in an organization, the culture of organization. I also got

an experience to work with a new set of a people and in a group. I learnt new

technologies like Jboss, oracle 10g and got an extended knowledge in java.

7.3. Limitations

Due to the time duration of the project we had limited the registration of the

reader and the editor. We had also restricted the format of the submitting journals to

only pdf format.

-49-
FUTURE PLAN

8.0 FUTURE PLAN

• This application can be easily implemented under various situations.

• We can add new features as and when we require.

o Reusability is possible as and when require in this application.

o There is flexibility in all the modules.

• The format for submission of article is restricted to only pdf format in our

current system.

• This could be extended to text, audio/video etc.,

• The readers are not registered in our current system and they could be made to

register and access journal server in future.

-51-

9.0 Conclusion
 I am proud to say that my project entitled ‘JOURNAL SERVER’ has met its basic

functional needs. I have successfully tested the crude form of my software module .It is

found working efficiently under all circumstances that may arise in the real environment.

The system is highly user friendly and is well efficient to make easy interactions with

users. Even though I have completed this module with all my efforts successfully, it is still

having some limitations. In the future, I will try to overcome all such drawbacks and try to

make this software the best one.

-52-
BIBLIOGRAPHY
 10.0 BIBLIOGRAPHY

10.1 Books

• Java The Complete Reference, Seventh Edition

• Author Name: Herbert Schildt

• JBoss: A Developer's Notebook, 2005

• Author Name: Norman Richards

• Oracle SQL Developer 2.1

• Author Name: Sue Harper

• Jason Price, “Oracle Database 10g SQL”, 1st Edition

• Author Name: Tata McGraw Hill.

10.2 Websites

• http:// www.google.com

• http:// www.oracle.com

• http:// www.devjavasoft.org

• http:// www.docs.jboss.org

• http://www.craiglarman.com

• http://www.objectsbydesign.com

• http://www.agilemodeling.com

• http://www.ibm.com

• http://www.sequencediagrameditor.com

• http://www.comptechdoc.org

• http://www.scribd.com

• http://ungrid.unal.edu.co/
-54-