ARTICLE INFORMATION SYSTEM

BAKTAVATCHALAM.G (08MW03)

MASTER OF ENGINEERING

Branch: SOFTWARE ENGINEERING

of Anna University

May 2009

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

PSG COLLEGE OF TECHNOLOGY
(Autonomous Institution)
COIMBATORE – 641 004
 PSG COLLEGE OF TECHNOLOGY
(Autonomous Institution)
COIMBATORE – 641 004

ARTICLE INFORMATION SYSTEM

Bona fide record of work done by

BAKTAVATCHALAM.G (08MW03)

MASTER OF ENGINEERING

Branch: COMPUTER SCIENCE AND ENGINEERING

of Anna University, Coimbatore.

May 2009
 Acknowledgement

ACKNOWLEDGEMENT

We wish to express our sincere gratitude to our respected Principal Dr. R.

Rudramoorthy for having given us the opportunity to undertake our project.

We also wish to express our sincere thanks to Dr. S. N. Sivanandam, Professor

and Head of the Department of Computer Science and Engineering, for his
encouragement and support that he extends towards our project work.

We extend our sincere thanks to our internal guide, Mr. M. GowriSankar,

Lecturer, Department of Computer Science and Engineering, for his guidance and
help rendered for the successful completion of our project.

i
 SYNOPSIS

The Article Information System has been developed for easily maintaining the
information about articles and customers in the article system and to help customers to
search and view articles without visiting the library. This system replaces current manual
process of maintaining records of articles and publishing new articles about the customers
which are highly time consuming.

The Article Information system has an online catalogue using which the
customers can login, search, and publishes articles online. Customers can search articles
by title, author name and keywords. The members can view their user account. One
member is allowed only to view only subscribed articles. Unregistered members can
search for articles. New members can join by filling an online registration form.

Reviewers can login, search, accept and reject articles which are submitted by the
customers online. Each customer is subscribed to a particular period and if it expires then
he must obtain a new subscription. Single customer may possess different types of
subscription as they need.

i
 TABLE OF CONTENTS

1. Introduction..............................................................................................................1
2. Requirement Analysis….........................................................................................2
2.1. Vision and Scope................................................................................3

2.2. Software Requirement Specifications…............................................9

2.3. Use Cases….......................................................................................18

2.4. Test Plan…........................................................................................27

2.5. Prototype...........................................................................................30

3. Design…...............................................................................................................35
4. System Implementation….....................................................................................35
5. Testing……………………………………………………………………………
5.1. JUnit Test Cases…..............................................................................46

5.2. HTTP unit Test Cases…....................................................................47

5.3. Load & Performance Testing….........................................................50

5.3. Using WinRunner..............................................................................52

6. Conclusion & Future Enhancements…...................................................................55

ii
 1. INTRODUCTION

This chapter provides a brief overview of the problem definition, objectives and
significance of the project and an outline of this report.

1.1 PROBLEM DEFINITION

The Article Information System provides improvements to the manual Article
System for Customers who are needs the Articles from online which are secured by
authentication and accessed from anywhere. Unlike current manual article system, we reduce the
complexity of articles maintenance and searching for needed articles...

1.2 OUTLINE OF THE PROJECT

The rest of the report is structured as follows. Chapter 2 discusses the
requirements for the development of the system and an analysis on the feasibility of the system.
Chapter 4 presents the overall design of the system. Chapter 5 discusses the implementation
details. Chapter 6 explains various testing procedures conducted on the system. The last section
summarizes the project.
 2. REQUIREMENT ANALYSIS

This section describes the hardware and software specifications for the development of
the system and an analysis on the feasibility of the system. This section includes:

2.1 Vision and Scope

2.2 Software Requirement Specification

2.3 Usecases

2.4 Test Plan

2.5 Prototype
Vision and Scope Document
for

Article Information System

Version 1.0 Approved

Prepared by G.BAKTAVATCHALAM

PSG College of Technology

21-01-2009
 Vision and Scope for Article Information System Page iv

Table of Contents

Table of Contents................................................................................................................iv
Revision History.................................................................................................................iv
1. Business Requirements...................................................................................................i
1.1. Background.............................................................................................................i
1.2. Business Opportunity..............................................................................................i
1.3. Business Objectives and Success Criteria...............................................................i
1.4. Customer or Market Needs.....................................................................................i
1.5. Business Risks.........................................................................................................i
2. Vision of the Solution.....................................................................................................i
2.1. Vision Statement....................................................................................................ii
2.2. Major Features.......................................................................................................ii
2.3. Assumptions and Dependencies.............................................................................ii
3. Scope and Limitations...................................................................................................ii
3.1. Scope of Initial Release..........................................................................................ii
3.2. Scope of Subsequent Releases..............................................................................iii
3.3. Limitations and Exclusions...................................................................................iii
4. Business Context..........................................................................................................iii
4.1. Stakeholder Profiles..............................................................................................iii
4.2. Project Priorities....................................................................................................iv
4.3. Operating Environment.........................................................................................iv

Revision History

Name Date Reason For Changes Version

G.Baktavatchalam 21-01-2009 Initial Draft 1.0
Vision and Scope for Article Information System Page i

1. Business Requirements
1.1. Background
Nowadays the Articles which are produced and collected in an Article Organization are increased
day by day and the amount of information residing in that Organization is growing indefinitely. So the
Manual Article Systems and its Maintenance is critical one.

1.2. Business Opportunity

The customers may face difficult of Article subscriptions and submissions which are done
manually and it very difficult to find older articles. Also the customers need to wait till the arrival of
current month Article which is subscribed and sent through postal and it may lead to some delay.

Nowadays many online public digital library systems are available, but they do not consider the
private subscriptions and its security issues. But we provide a better security of various levels of
subscriptions of various levels of customers.

Our system provide better organization of articles and the specialized searching that finds needed
customer articles.

1.3. Business Objectives and Success Criteria

This system overcomes the drawbacks of existing manual article systems. So it is beneficial to
currently subscribed customers and the customers who are wish online subscriptions.

This system is successful if there is some increase of number of subscribed customers compare to
current customers count. Also our system is an additional one and it not replaces our old manual
system, so that there is no loss of current customers.

1.4. Customer or Market Needs

In our new system we consider various levels of customers who are subscribe articles as per their
need. For Example Students, Researchers and Educational Organizations … The customers may need the
articles which are posted previous older years.

Also the management needs the better way of organizing, collecting, publishing the articles

1.5. Business Risks

Major business risk is associated with customer acceptance if they did not get their needed articles.
Another major risk is converting and categorizing hardcopy of articles into our systematic representation
of articles.
Vision and Scope for Article Information System Page ii

2. Vision of the Solution

2.1. Vision Statement
This Article Information System provides improvements to the manual Article System for
Customers who are needs the Articles from online which are secured by authentication and accessed
from anywhere. Unlike current manual article system, we reduce the complexity of articles maintenance
and searching for needed articles. In future this system will improved to wide range of Organizations
and better adaptation and maintenance to growing articles and better customer offers and facilities like
Credit Card subscriptions, Systematic approval of Articles ...

2.2. Major Features

FE-1: Free Registration for Viewing some Information about Articles

FE-2: Secured Subscription for various levels of customers for various Articles

FE-3: Searching needed articles

FE-4: Submission of Articles for Publishing

2.3. Assumptions and Dependencies

AS-1: Searching is adaptable for existing articles and forthcoming Articles

AS-2: Subscription is provided as per the cost of articles and subscriptions actually done using postal
and its pass code is given to our new system for accessing the articles.

AS-3: Free registered users only see the limited information about the Articles.

3. Scope and Limitations

3.1. Scope of Initial Release

Feature Release 1
FE-1 Provides viewing of Title & Abstract

FE-2 Using Subscription code

FE-3 Using title, author

FE-4 Using Subscription code

 Vision and Scope for Article Information System Page iii

3.2. Scope of Subsequent Releases

Release Features
Publisher codes for publishing, different level of subscription codes for article
2
accessing, enhanced search using article contents

3 Enhanced searching using month & year of articles

3.3. Limitations and Exclusions

LI-1: This system will not provides other Online Digital Library Articles

4. Business Context
4.1. Stakeholder Profiles

Major Value
Stakeholder Attitudes Major Interests Constraints

See product as
increase Richer feature set than
Executives avenue to 25%
d competitors; time to
increase in market
revenue market
share

Publish research
Educational and Institutional
articles, keep
Research Users relationshi
updates on latest
p
articles

Manage the newly

Management
Maintenance published articles,
Users
maintain the old
articles
 Vision and Scope for Article Information System Page iv

Existing Increased Get inside of

Customers subscription different types of
s articles

4.2. Project Priorities

Dimension Driver Constraint Degree of Freedom

Schedule release 1 planned to be
available within 1 month,
release 2&3 by next 4
weeks; overrun of up to 3
weeks acceptable without
sponsor review
Features All features scheduled for
release 1.0 must be
fully operational
Quality 95% of user acceptance tests
must pass; all security tests
must pass; compliance with
corporate security standards
must be demonstrated for all
secure transactions
Staff Projected team size is half-
time project manager, 2
developers, and half-time
tester; additional half-time
developer and half-time
tester will be available if
necessary
Cost budget overrun up to 15%
acceptable without sponsor
review

4.3. Operating Environment

 Web based access will helps the users who are widely distributed geographically and
the users in various locations need to access the system
 The articles from multiple locations need to be combined if the need of more Organizations
 High Speed Internet and Intranet needed to process the articles and searching
Vision and Scope for Article Information System Page v

Software Requirements
Specification
for

Article Information System

Version 1.1 Approved

Prepared by G.BAKTAVATCHALAM

PSG College Of Technology

21-01-2009
Table of Contents

Table of Contents................................................................................................................vi
Revision History.................................................................................................................vi
1. Introduction....................................................................................................................i
1.1 Purpose.....................................................................................................................i
1.2 Document Conventions............................................................................................i
1.3 Intended Audience and Reading Suggestions..........................................................i
1.4 Project Scope............................................................................................................i
1.5 References................................................................................................................i
2. Overall Description.......................................................................................................ii
2.1 Product Perspective.................................................................................................ii
2.2 Product Features......................................................................................................ii
2.3 User Classes and Characteristics............................................................................iii
2.4 Operating Environment..........................................................................................iii
2.5 Design and Implementation Constraints................................................................iii
2.6 User Documentation...............................................................................................iii
2.7 Assumptions and Dependencies.............................................................................iii
3. System Features............................................................................................................iv
3.1 Free Registration for Viewing some Information about Articles...........................iv
3.2 Secured Subscription for various levels of customers for various Articles............iv
3.2 Searching needed articles.......................................................................................iv
3.2 Submission of Articles for Publishing....................................................................iv
4. External Interface Requirements...................................................................................v
4.1 User Interfaces.........................................................................................................v
4.2 Hardware Interfaces................................................................................................vi
4.3 Software Interfaces.................................................................................................vi
4.4 Communications Interfaces....................................................................................vi
5. Other Nonfunctional Requirements..............................................................................vi
5.1 Performance Requirements.....................................................................................vi
5.2 Safety Requirements...............................................................................................vi
5.3 Security Requirements............................................................................................vi
5.4 Software Quality Attributes....................................................................................vi
6. Other Requirements.....................................................................................................vii
Appendix A: Glossary.......................................................................................................vii
Appendix B: Analysis Models...........................................Error! Bookmark not defined.
Appendix C: Issues List.....................................................................................................vii

Revision History
Name Date Reason For Changes Version
G.Baktavatchalam 28-01-09 Initial draft 1.0
5. Introduction
5.1. Purpose
This SRS describes the software functional and nonfunctional requirements for release 1.0 of the
Article Information System (AIS). This document is intended to be used by the members of the project
team that will implement and verify the correct functioning of the system. Unless otherwise noted, all
requirements specified here are high priorities and committed for release 1.0.

5.2. Document Conventions

DC-1: Every Requirement Statement has its own Priority

DC-2: High Level Requirements are inherited by Detailed Requirements

5.3. Intended Audience and Reading Suggestions

IA-1: Developers

IA-2: Testers

IA-3: Project Managers

IA-4: Documentation Writers

IA-5: Users

RS-1: Beginning with the overview sections and proceeding through the sections

Those are most relevant to each Reader Type

5.4. Project Scope

The Article Information System provides a way in which the Customers may publish, view and
search the articles in a Systematic Way with Various levels of Subscriptions and Authentications. A
detailed project description is available in the Article Information System Vision and Scope Document [1].
The section in that document titled “Scope of Initial and Subsequent Releases” lists the features that are
scheduled for full or partial implementation in this release.

5.5. References
1. Wiegers, Karl. Cafeteria Ordering System Vision and Scope Document,
www.processimpact.com/projects/COS/COS_vision_and_scope.doc

2. Wiegers, Karl. Process Impact Intranet Development Standard, Version 1.3,

www.processimpact.com/corporate/standards/PI_intranet_dev_std.doc
3. Zambito, Christine. Process Impact Business Rules Catalog,
www.processimpact.com/corporate/policies/PI_business_rules.doc

6. Overall Description
6.1. Product Perspective
The Article Information System overcomes current manual maintenance and it provides Systematic
approach to manage and maintain the Article System. The context diagram in Figure 1 illustrates the
external entities and system interfaces for release 1.0. The system is expected to evolve over several
releases.

Management Users Maintain Marketing

Executives

Article Information System

Publish, Subscribe

Finding, Subscribe

Educational and
Latest Topics Existing Customers
Research Users Search

Article Storage
System

Figure 1 Context diagram for release 1.0 of the Article Information System

6.2. Product Features

This Article Information System includes the Major Features of Free Registration for viewing
some Information about Articles, Secured Subscription for various levels of customers for various
Articles, Searching needed articles and Submission of Articles for Publishing
6.3. User Classes and Characteristics
Executives See product as avenue to 25% increase in market share

Educational and
Publish research articles, keep updates on latest articles
Research Users

Management
Manage the newly published articles, maintain the old articles
Users

Existing
Get inside and try different types of articles
Customers

6.4. Operating Environment

OE-1: The Article Information System shall operate with the Web browsers which are
Java Enabled
OE-2: The Article Information System shall operate on any server with Apache Tomcat
Web Server.
OE-3: The Article Information System shall permit user access from the Intranet and, if
a user is authorized for outside access through the firewall, from an Internet
connection at the user’s home.

6.5. Design and Implementation Constraints

CO-1: The system’s design, code, and maintenance documentation shall conform to the
Process Impact Intranet Development Standard, Version 1.3 [2]
CO-2: The system shall use the Standard Oracle database engine
CO-3: All HTML code shall conform to the HTML 4.0 standard
CO-4: All programming Code is written in J2EE and J2SE

6.6. User Documentation

UD-1: The system shall provide an online hierarchical and cross-linked help system in
HTML that describes and illustrates all system functions
UD-2: This system provides online help manual for Searching and Publishing Articles
and provides samples for easy understanding

6.7. Assumptions and Dependencies

AS-1: This system is accessible at any time in any day.
DE-1: The operation of the AIS depends on manual subscription code which is posted to
the customer to access the Articles
7. System Features
7.1. Free Registration for viewing Information about Articles
3.1.1 Description and Priority
The Customers who want to see the information about some Articles with free of
cost and they can also search for their desired Articles. The free registrations only give
the Article Abstract. It is an Extra Benefit Feature and it is very useful for customers and
they can able to view Article Information before Subscription. Priority = High.
3.1.2 Stimulus/Response Sequences
Stimulus: Customer request for Registration
Response: System now prompts for Personal Details and a Password for
Registration
Stimulus: Customer needs to give Personal Details and a Password for
Registration
Response: System now gives a Temporary Low Level Subscription Code and
its validity period
3.1.3 Functional Requirements
REQ-1: Free Registration

REQ-2: Validity Period Allotment for Free Subscription

7.2. Secured Subscription for various Levels of Customers for various
Articles
3.1.1 Description and Priority
The Customers who wants to subscribe more number of different Article Areas
then they need to subscribe into various levels as per their need and it will increase the
subscription cost. Priority = High.
3.1.2 Stimulus/Response Sequences
Stimulus: Customer request for Registration
Response: System now prompts for Personal Details and the Subscription Code
and Password for Registration
Stimulus: Customer needs to give Personal Details and the Subscription Code
and Password for Registration
Response: System now gives validity period and display Subscription Level
Details
3.1.3 Functional Requirements
REQ-1: Registration

REQ-2: Validity Period Allotment for Subscription

REQ-3: Customer Subscription Level

 7.3. Searching Needed Articles
3.1.1 Description and Priority
The Customers may search for Articles with Specified Keywords or Article
Contents. No need of Login/Subscription/Registration for searching. Priority = High.
3.1.2 Stimulus/Response Sequences
Stimulus: Customer request for Searching
Response: System now prompts for Keywords or Article Contents for articles
finding
Stimulus: Customer enters Keywords or Article Contents for articles finding
Response: System now display the relevant Articles information related to input
Queries
3.1.3 Functional Requirements
REQ-1: Based on Title, Author Name, Issue Date
REQ-2: Based on Keywords

7.4. Submission of Articles for Publishing

3.1.1 Description and Priority
The Customers may submit their Articles for Publication. The Management will
review the Articles and publish those Articles. Priority = High.
3.1.2 Stimulus/Response Sequences
Stimulus: Customer request for Publishing
Response: System now prompts subscription code and password
Stimulus: Customer now enters subscription code and password
Response: System now prompts for article (one per time)
Stimulus: Customer now uploads the article file
Response: System now stores the article and displays success message to
customer
3.1.3 Functional Requirements
REQ-1: Uploading

REQ-2: Making Review and Assign Priority based on Subscription Level

REQ-2: Mail/Inform the customers if their Article is published

8. External Interface Requirements

8.1. User Interfaces
UI-1: The Article Information System screen displays shall conform to the
Process Impact Internet Application User Interface Standard, Version 2.0
[4].
UI-2: The system shall provide a help link from each displayed HTML page to explain
how to use that page.
 UI-3: The Web pages shall permit complete navigation and item selection using the
keyboard alone, in addition to using mouse and keyboard combinations.

8.2. Hardware Interfaces

No hardware interfaces have been identified.

8.3. Software Interfaces

SI-1: Article Storage System
SI-1.1: Storing/Retrieving the customers subscriptions and Validity
SI-1.2: Storing/Retrieving the customers Registration details

8.4. Communications Interfaces

CI-1: RSA Encryption Algorithm is used when accessing user’s personal details

9. Other Nonfunctional Requirements

9.1. Performance Requirements
PE-1: The system should accommodate 200+ users concurrently
PE-2: All Web pages generated by the system shall be fully downloadable in no more
than few seconds over a low speed modem connection
PE-3: Responses to search queries shall take no longer than 5 seconds to load onto the
screen after the user submits the query
PE-4: The system shall display confirmation messages to users within 4 seconds after
the user submits information to the system

9.2. Safety Requirements

No safety requirements have been identified.

9.3. Security Requirements

SE-1: Users shall be required to log in to the System for all operations except Searching
SE-2: All customers detail accessing should posses RSA Encryption

9.4. Software Quality Attributes

Availability : This System shall be available to users on 99% in 24x7 basis
Robustness : If the connection between the user and the system is broken prior to an
subscription being either confirmed or canceled, the System shall enable the user
to recover an incomplete order.
Usability : This system should be very easy one to use
10. Other
Requirements Appendix
A: Glossary

AIS : Article Information System

SCODE : Subscription Code

Appendix C: Data Dictionary

CUSTOMER ( name, password, subscription code, address, phone )

SUBSCRIPTION ( subscription code, description, validity )

PUBLICATION ( customer name, article title, published date, contents, Priority )

ARTICLE ( author name, article title, published date, contents )

 Use Cases
for

Article Information System,

Release 1.0
Version 1.0 Approved

Prepared by G.BAKTAVATCHALAM

PSG College of Technology

February 25, 2009

Revision History

Name Date Reason For Changes Version

The various user classes identified the following use cases and primary actors for the Article Information
System:

Primary Actor Use Cases

Customers 1. Search For Articles
2. Subscribe For Articles
3. Submit Article For Review
4. Login For accessing Subscribed
Articles and View the Articles
Reviewers 5. Review the Articles
 Use Case ID: 1

Use Case Name: Search For Articles

Created By: Bakthavatchalam.G Last Updated By:

Date Created: Feb 25, 2009 Date Last Updated:

Actors: Customers

Description: The customers may search for new/old articles with the specification of
author/issue date/title/keywords

Preconditions: All the information’s about the Articles(new & old) should be available

Postconditions: The Search History dumped into Storage for Future Analysis

Normal Flow: 1.0 Search Using Author

1.The System displays the Search box for author name input
2.User types the author name and do searching
3.The System search the articles which are submitted by the given author
4.Then it will display the resulted articles to Users screen
5.User now view the articles relevant to his request and view the article one
by one
Alternative Flows: 1.1 Search Using Issue Date

1. The System displays the Search box for date input

2. User types the date and do searching
3. The System search the articles which are submitted on the month & year
of given date
4. Then it will display the resulted articles to Users screen
5. User now view the articles relevant to his request and view the article one
by one
1.2 Search Using Title

1. The System displays the Search box for title input

2. User types the title and do searching
3. The System search the articles which are contains the given title
4. Then it will display the resulted articles to Users screen
5. User now view the articles relevant to his request and view the article one
by one
1.3 Search Using Keywords

1. The System displays the Search box for keyword input

2. User types the keywords and do searching
3. The System search the articles which are contains the given keywords
4. Then it will display the resulted articles to Users screen
 5. User now view the articles relevant to his request and view the article one
by one
Exceptions: 1.0.E.1 If user gives an Invalid Date (at step 1.1)

1. System gives Error Message as Invalid Date Format/Date Not Exist.

1.0.E.2 Author Name is not Found (at step 1.0)

1. System gives Error Message as No Author Found.

Includes: None

Priority: High

Frequency of Use: Approximately 200+ times per day

Business Rules: None

Special Requirements: 1. The System must know the latest and old articles and its details.

Assumptions: 1. If the user is not logged then System only allows the minimal information
about articles.
Notes and Issues: 1. System must know the user is a Guests or Subscribed Customers

Use Case ID: 2

Use Case Name: Subscribe For Articles

Created By: Bakthavatchalam.G Last Updated By:

Date Created: Feb 25, 2009 Date Last Updated:

Actors: Customers

Description: The Article Management System provides multilevel Subscriptions and the
subscription code.

Preconditions: The Subscription Codes and corresponding Users must available

Postconditions: User’s detail has been saved.

 Normal Flow: 1.0 Registration

1. The System requests for user name, address, phone, password, subcode
2. User must enter the correct values and submit.
3. Now the system checks for subcode format and existence, then it will store
the user’s information along with validity period (generated by System
based on subcode).
4. The System informs the user as Information was saved.
5. Now the User can able to view subscribed articles and to post article for
publication
Alternative Flows: None

Exceptions: 1.0.E.1 Invalid Subscription Code (at step 1)

1. System informs user that given code is invalid format or not exist.

Includes: None

Priority: High

Frequency of Use: Approximately 20 times per week

Business Rules: None

Special Requirements: 1. The Subcode should be in a specified fixed format

Assumptions: 1. The Subscribed User got the subcode via postal and he must enter the
same code here to view articles online
Notes and Issues: None

Use Case ID: 3

Use Case Name: Submit Article For Review

Created By: Bakthavatchalam.G Last Updated By:

Date Created: Feb 25, 2009 Date Last Updated:

Actors: Customers

Description: The Subscribed Users may have an opportunity to publish their articles. To
publish the Article user must submit the article for reviewing. After review the
article is published.
 Preconditions: User Must log in to our System to do this.

Postconditions: The Submitted article directed to Reviewing Section.

Normal Flow: 1.0 Submit Article

1. The System requests for Article contents with title

2. User now paste the Article in the box provided and submit it
3. Now the system dump the article into storage for contents analysis and re
direct the article to Review Section.
Alternative Flows: None

Exceptions: 11.0.E.1 Invalid Article Format (at step 1)

1. System informs that Article is not Valid Format.

Includes: None

Priority: High

Frequency of Use: Approximately 2 times per month by one user

Business Rules: None

Special Requirements: 1. Article should be in given Fixed Format

Assumptions: None

Notes and Issues: None

Use Case ID: 4

Use Case Name: Login For accessing Subscribed Articles and View the Articles

Created By: Bakthavatchalam.G Last Updated By:

Date Created: Feb 25, 2009 Date Last Updated:

Actors: Customers
 Description: The Subscribed Users may login into their account to see updated articles and
any information regarding to his article submission or to do submission.

Preconditions: User Must register in to our System to do this.

Postconditions: The Submitted article directed to Reviewing Section.

Normal Flow: 1.0 Login

1. The System requests for Subcode and password

2. User now enters the Subcode and password in the boxes provided and
submit it
3. Now the system verifies account and collect articles related to this account
and also collect any information to this account.
4. Now System displays the info to the user.
Alternative Flows: 1.1 Submit the Article

1.2 Logout

1.3 View the Article

Exceptions: 11.0.E.1 Invalid User Information (at step 1)

1. System informs that Subcode or password is not Valid.

Includes: None

Priority: High

Frequency of Use: Approximately 2 times per day by one user

Business Rules: None

Special Requirements: 2. Article should be in given Fixed Format

Assumptions: None

Notes and Issues: None

Use Case ID: 5

 Use Case Name: Review the Articles

Created By: Bakthavatchalam.G Last Updated By:

Date Created: Feb 25, 2009 Date Last Updated:

Actors: Reviewer

Description: The Subscribed Users may have an opportunity to publish their articles. To
publish the Article user must submit the article for reviewing. After review the
article is published. Now the reviewer views the each Article and do
accept/reject.

Preconditions: Reviewer Must log in to our System to do this.

Postconditions: The Submitted articles are available.

Normal Flow: 1.0 Review Article

5. The System lists all Article titles

6. Now reviewer click on article and click on view
7. Now the system displays article contents.
8. Now reviewer does accept/reject the article.
9. System saves modified status.
Alternative Flows: None

Exceptions: None

Includes: None

Priority: High

Frequency of Use: Approximately 20 times per month

Business Rules: None

Special Requirements: 3. Article should be in given Fixed Format

Assumptions: None

Notes and Issues: None

 TEST PLAN
Project Number: 08MW03

Project Name: Article Information System

A web application which enable the article library members to search for
Description: articles, subscribe and view books online. The customer can search new
articles and publish new articles.

Project Manager: G.BAKTAVATCHALAM

Date Updated:

Project Test Plan

Overview

Test plan objectives To ensure that the Online Library Management System will:
- Function consistently and reliably in accordance with
current business operations.
- Meet or exceed user requirements and technical specifications.
- Not adversely impact other systems or the existing
technology environment.
Testing Assumptions - It is assumed that there are few reviewers and customers whose
personal details, username and password are already stored in
the database.
- The subscription codes of each customer are assumed to be unique.
Risks & Contingencies The following risks apply to the testing process and may impact either the
proposed date of readiness for the deployment of Article Information System,
or the comprehensive level of testing that can be performed in each of the
Functional Units:
- The actual deployment of Article Information System may take longer
to perform than anticipated, as the admin is also using the same
database for maintenance.

Test Scope

Features to be Tested All features, forms, reports and interfaces affected by the
Article Information System will be tested. These include:
- Login forms
- User manual
 - Online help
- Logout
- Articles for session
- Database used for both authentication and validation
Features Not to be Tested - Data integrity and system functionality contained within the
Conventional Article Information System and which is not Online
Article Information System dependant, will not be tested under
the scope of this project.

Test Methodologies

Testing Approach The following approach will be used to test the Online
Library Management System
- Article Information System integration & system testing will be
conducted to provide an initial stable testing environment as
follows:
 Integration Testing: Ensure operability of Article
Information System application within each of the new
modules.
 System Testing: Ensure that all the test databases
are accessible for testing.
- Test cases and associated scripts for user acceptance testing
are created.
- For testing the functional specification the unit testing is
performed by the developer using JUnit.
- After Integration, system and acceptance testing user sign-off
is performed.
- Once user sign-off is received, then the actual deployment
is performed.
Test Documents The following test documents will be created and maintained throughout
the project lifecycle:
- Article Information System Test Plan
- Master test case lists for each of the following functional units:
Login, Search, Subscribe, Review, Publish, Update status,
Logout.
- Test case scripts for each test case recorded in the master test case list
- Log of all problems encountered during the testing phase of
the project
Test Case Pass/Fail Each Test Case will be evaluated against the acceptance criteria as
Criteria outlined in the test case scripts to determine if the test passed or failed. In
the case of a failure, the tester will assign a severity to the problem using
the appropriate priority rating system established within Tracker for each
application.
Suspension/Resumption Test Cases that do not run to completion will be evaluated on a case by
Criteria case basis to determine if the testing must start over or resume at the
point where the failure occurred. In extremely long test cases,
checkpoints will be established for resumption in the middle of a test case
where appropriate. In general, a test may be resumed in the middle when
the error is not critical.
Problem Errors identified through testing will be logged. Resolve the problem
Logging/Resolution according to the deemed severity level, and update the master test case
list. Once the problem has been fixed, record the resolution into the
database.
 The failed test case will then be retested using the same test case script
that detected the error in order to verify that the problem has been
rectified.

Resources

Environmental Needs In order to conduct comprehensive end-to-end system and user testing are the
networked system where the functional and non-functional testing is
performed.

Staffing Requirements Developer

Testing Activity Dependencies Timeframe

Preparation of the testing None Mar – Apr

environment

Integration & System Testing environment has been Apr 14

testing set up

Establishment of Test Plan None Apr 14

and Testing Templates

Updating of Functional None Start Apr 14, 2009

Unit Master Test Case Lists
and Test Case Scripts

Actual Testing (execution - Testing environment Start Apr 14, 2009

of Test Case Scripts)
Final Functional User
Acceptance Testing &
Sign-off
has been set up
- Integration &
System Testing has
been completed
- Test Case Scripts
have been developed
- Deployment of Online Apr 21 , 2009
Library
Management system
 Prototype
for

Article Information System

Version 1.0 Approved

Prepared by G.BAKTAVATCHALAM

PSG College Of Technology

25-02-2009
Help Page

Home Page
Article Submission

Subscription
Reviewing

Search
User’s Home
 System Design
for

Article Information System,

Release 1.0
Version 1.0 Approved

Prepared by G.BAKTAVATCHALAM

PSG College of Technology

February 18, 2008

Revision History

Name Date Reason For Changes Version

Use Case Diagram:

Using Article Details Using Article Contents

Search for Articles

Guest User

Subscribe for Articles

Customer
Login

Submit Articles for Publishing

Reviewer

View Articles
 Class Diagram:

Review ArticleUtil

getReqArticles() accept() validateArticles() store()

Login
reject()
subcode : String pwd : String

validate() Article
DBUtil id
title author idate
storeUserInfo() storeHelpInfo() storeArticle() getArticles() getUserInfo() keywords[] contents
getHelpInfo()

SubCodeUtil
checkCodeFormat() getCode()
getInfo() setInfo()

Account DynHelp
Search
cname addr phone pwd scode
getHelpInfo() setHelpInfo()
Registration
usingTitle() usingAuthor() usingIDate() usingKeys()
getUserInfo() validate() store()

getInfo() setInfo()

ServerManager
Articles keys[]
serverReader serverWriter ClientManager
getArticles() getKeys() search() sendResults()

distribute() sendArticles() sendKeys() getACount()

Sequence Diagram:

Login:

Customer AIS DBManager

1: Enter Subcode and pwd

2: validate code

3: illegal 4: getUserInfo
Format
5: UserInfo

6: validate user
7: invalid user

8: Re-direct to home
Register:

Customer AIS DBManager

1: Submit All Info

2: verify all info

3: invalid info
4: store

5: success

6: display status

Review:

Reviewer AIS DBManager

1: Requested Articles

2: Req Articles

3: Articles
4: Articles

5: accept/reject
Search:

Customer AIS DBManager

1: author/idate/title/contents
2: getArticles

3: Searching

5: formatted info 4: Article Result

Set

Help:

Customer AIS DBManager

1: req help topic

2: req help info
3: search

4: help info
5: formatted help
Collaboration Diagram:

Login:

2: validate code
6: validate user
Customer
1: Enter Subcode and pwd

AIS
3: illegal Format
7: invalid user 4: getUserInfo
8: Re-direct to home

5: UserInfo DBManager

Register:

2: verify all info

1: Submit All Info

Customer AIS
4: store
3: invalid info
6: display status
5: success DBManager
Review:

5: accept/reject

DBManager
Reviewe1r : Requested Articles 2: Req Articles

AIS
3: Articles
4: Articles

Search:

AIS
1: author/idate/title/contents
3: Searching
2: getArticles
Customer 5: formatted info
4: Article Result Set
DBManager

Help:

Customer
1: req help topic

AIS 3: search

5: formatted help 2: req help info

4: help info
DBManager
Activity Diagram:

CustomerAISDBManager

invalid
Verify code
Login code & pwd verify user

invalid code
valid user
display articles retrieve articles
get articles
articles
result set
format articles

send article article verify send for publish store

author/idate/keys/title
search search finding articles
get articles

result set
show articles formatting articles
Component Diagram:

AIS Crawler

DB
Manager

Deployment Diagram:

Crawler
AIS

Distributed Network
 6. TESTING

6.1. JUNIT TEST CASES

A unit test is a programmer-written test for a single piece of functionality in an

application. JUnit test cases are Java classes that contain one or more unit test methods, and these
tests are grouped into test suites. You can run tests individually, or you can run entire test suites.

Test Scenario

S.No Test Scenario ID Test Scenario Description

1 TS1.1 Username and Password Match

2 TS1.2 Invalid Username and Password

3 TS1.3 Username and Password blank

4 TS2.1 Valid Subscription number

5 TS2.2 Invalid Subscription number

6 TS2.3 Subscription number null

7 TS3.1 Valid title

8 TS3.2 Invalid title

9 TS3.3 Title null

10 TS4.1 Valid author name

6.2. HTTPUNIT TEST CASES

With HTTPUnit, Java programs can access servers directly, without the need for a web
browser. HTTPUnit provides an API for interacting with HTML, submitting forms, following
hyperlinks, setting cookies and many other tasks associated with web browsers.

Test Scenario:

S. No Test Scenario Id Test Scenario Description

1 TS1.1 Check link from index page to login page

2 TS1.2 Check link from index page to Register page

3 TS1.3 Check link from login page to Reviewer page

4 TS1.4 Check link from home page to search page

5 TS1.5 Check link from login page to useraccount page

Sample Test Code:

import
com.meterware.httpunit.*;
import junit.framework.*;

public class ExampleTest extends TestCase

{ public static void main(String
args[]) {
junit.textui.TestRunner.run( suite() );
}

public static Test suite() {

return new TestSuite( ExampleTest.class );
}

public ExampleTest( String name )

{ super( name );
}

public WebResponse tryGetResponse(WebConversation

conversation,WebRequest request) throws Exception {
WebResponse
response=null; try {
response = conversation.getResponse( request );
} catch (HttpNotFoundException nfe) {
System.err.println("The URL '"+request.getURL()+"' is not active any
more");
 t row nfe;
h }
return response;
}

public void testWelcomePage() throws Exception

{ WebConversation conversation = new
WebConversation();
WebRequest request = new
GetMethodWebRequest( "http://localhost:8080/AIS/index.jsp" ); WebResponse response
= tryGetResponse(conversation, request );

WebForm forms[] = response.getForms();

assertEquals( 1, forms.length );
assertEquals( 1, forms[0].getParameterNames().length );
assertEquals( "name", forms[0].getParameterNames()
[0] );
}

public void testBadLogin() throws Exception

{ WebConversation conversation = new
WebConversation();
WebRequest request = new GetMethodWebRequest( " http://localhost:8080/AIS/login.jsp" );

WebResponse response = tryGetResponse(conversation,

request ); WebForm loginForm = response.getForms()[0];
request = loginForm.getRequest();
response = conversation.getResponse( request );
assertTrue( "Login not rejected", response.getText().indexOf( "Invalid" ) != -1 );
}

public void testGoodLogin() throws Exception

{ WebConversation conversation = new
WebConversation();
WebRequest request = new GetMethodWebRequest( " http://localhost:8080/AIS/login.jsp" );

WebResponse response = tryGetResponse(conversation,

request ); WebForm loginForm = response.getForms()[0];
request = loginForm.getRequest();
request.setParameter( "admin", "psg1" );
response = conversation.getResponse( request
);
assertTrue( "Login not accepted", response.getText().indexOf( "Invalid" ) != -1 );

assertEquals( "Login", "Succeeded", response.getTitle() );

}
}
 Test Cases:

S.No Test case ID +/- Short Description Steps to Expected Obtained

follow results result

+ Check link from Click LOGIN Forwarded to Forwarded

index page to login login page to login
1 TC1.1 page page

+ Check link from Click Registration Registration

index page to REGISTER form should form should
2 TC1.2 Register page be displayed be displayed

Check link from Reviewer Reviewer

index page to page should page is
3 TC1.3 + Click Search
Reviewer page display displayed

Check link from Click Search Search page Search page

home page to should be is displayed
search page displayed
4 TC1.4 +

Check link from Useraccount Useraccount

home page to page should page is
5 TC1.5 + Click
useraccount page be displayed displayed
Useraccount
6.3. LOAD AND PERFORMANCE TESTING

The load and performance testing is done using the tool Load-Runner and the results
obtained are shown below. The system is simulated for 30 vusers.

Running Vusers
 Hits per Second

Transaction Summary
 Overall Report

6.4. USING WINRUNNER

Mercury WinRunner is the powerful test automation solution for the enterprise. It helps
you automate the testing process, from test development to execution. You create adaptable and
reusable test scripts that challenge the functionality of your application. Prior to a software
release, you can run these tests in a single overnight run—enabling you to detect defects and
release software of superior quality.

You can also convert existing WinRunner tests to scripted components, or create new scripted
components. Scripted components are part of Business Process Testing in Mercury Quality
Center, which utilizes a keyword-driven methodology for testing applications. Scripted
components are reusable modular scripts that can be created in WinRunner, and then used in
business process tests.

SAMPLE TEST SCRIPTS:

#
_login set_window("_login",86);
edit_set("subcode","admin");
obj_type("subcode","<kTab>");
 password_edit_set("pwd","c9faca5c644fe0f0");
button_press("Login");

# Article Information System

set_window("Article Information System",14);
button_press("Close Login");
button_press("Open Search");

# _search
set_window("_search",5);
edit_set("keys","the");
button_press("Search");

# search
set_window("search",6);
button_press("example3");

#
view set_window("view",1);
button_press("Close");

# search
set_window("search",4);
button_press("gmb");

#
view set_window("view",1);
button_press("Close");

# Article Information System

set_window("Article Information System",2);
button_press("Close Search");
in_check_gui("_login", "list1.ckl", "gui1",
1); set_window("view");

#Checklist for window

"_login" V 8.2
_login: "WEB.GVF" 0 0 1
{
}3
"{class: \"edit\", MSW_class: \"html_edit\", html_name: \"subcode\", tag:
\"subcode\"},disp_tag:\"[html_edit] subcode\"": "STND.GVF" 4 14 1
{
Compare: "AT" %"As Text" $STND.GVF, *1408,
}0
"{class: \"edit\", MSW_class: \"html_edit\", html_name: \"pwd\",
tag: \"pwd\"},disp_tag:\"[html_edit] pwd\"": "STND.GVF" 4 14 1
{
 Compare: "AT" %"As Text" $STND.GVF, *1408,
}0
"{class: \"push_button\", MSW_class: \"html_push_button\", html_name: \"Login\", tag:
\"Login\"},disp_tag:\"[html_push_button] Login\"": "STND.GVF" 7 18 1
{
Enabled: "" $STND.GVF, *1280,
}0

DSN=gmb;UID=scott;PWD=tiger1;SERVER=cseora;
select * from cust_ais

Line Event Result Details Time

3 start GUI capture --- gui1 344824:24:38

3 end GUI capture OK gui1 344824:24:38
 7. CONCLUSION

Thus the Article Information system was implemented successfully. This will help the
customers to search, view and publish articles online. Also the reviewer can do accept/reject for
submitted articles. This system helps Article System to remove the various bottlenecks in
maintaining manual records and also the members need not go to the article library for searching
articles.

Future Enhancement:

This Article Information system can be extended for Distributed Library. The search can
be further refined by categorizing based on various factors like education, entertainment etc. The
system can be further enhanced by providing facility for online payment of registration charges
using credit cards, automatically sending emails to customers intimating overdue and cancelled
reservation.