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.
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……………………… Introduction…………………………………………………… ………………………………………………..1 …………………..1 2. Requirement Analysis……………… Analysis………………………………………… ……………………………………………..2 …………………..2 2.1. Vision and Scope..............................………………………………...3 2.2. Software Requirement Specifications……………………………….9 Specifications……………………………….9 2.3. Use Cases……………………… Cases………………………………………………… ……………………………………18 …………18 2.4. Test Plan………………………… Plan…………………………………………………… ………………………………….27 ……….27 2.5. Prototype...……………………… Prototype...………………………………………………… …………………………………30 ………30 3. Design………………………… Design…………………………………………………… …………………………………………………35 ………………………35 4. System Implementation………………………… Implementation……………………………….…………………… …….…………………………35 ……35 5. Testing………………………… Testing…………………………………………………… ………………………………………………… ……………………… 5.1. JUnit Test Cases……………………………………………………..46 Cases……………………………………………………..46 5.2. HTTP unit Test Cases…………………… Cases…………………………………………….....47 ……………………….....47 5.3. Load & Performance Testing…………………………………..……50 Testing…………………………………..……50 5.3. Using WinRunner................……………………………… WinRunner................…………………………………..……52 …..……52 6. Conclusion & Future Enhancements………………………… Enhancements………………………………………………55 ……………………55
ii
1. INTRODUCTION 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 need ed 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 A pproved
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 Subseque nt 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 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 c onsider 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 provided as per the cost of articles and subscriptions actually done using 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 2
Publisher codes for publishing, different level of subscription codes for article 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
Stakeholder
Major Value
Attitudes
Executives
increased revenue
See product as avenue to 25% increase in market share
Educational and Research Users
Institutional relationship
Publish research articles, keep updates on latest articles
Maintenance
Manage the newly published articles, maintain the old articles
Management Users
Major Interests
Richer feature set than competitors; time to market
Constraints
Vision and Scope for Article Information System
Existing Customers
Increased subscriptions
Page iv
Get inside of different types of articles
4.2. Project Priorities Dimension
Driver
Constraint
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
Schedule
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
Degree of Freedom
Projected team size is halftime project manager, 2 developers, and half-time tester; additional half-time developer and half-time tester will be available if necessary budget overrun up to 15% acceptable without sponsor review
Cost
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 A pproved
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 Pu rpose ...................................................... ............................................................................................................ ............................................................... ......... i 1.2 Document Conventions .............................................. .............................................. i 1.3 Intended Audience and Reading Suggestions Sugg estions ....................................... ................... i 1.4 Project Scope ........................................................................................................... i 1.5 References ................................................. ....................................................... ............................................................... ........ i 2. Overall Description ...................................................... ....................................................................................................... ................................................. ii 2.1 Product Produc t Perspective ............................................... .................................................. ii 2.2 Product Features...................................................................................................... Features...................................................................................................... ii 2.3 User Classes and Characteristics .................................................................... ....... iii 2.4 Operating Environment................................................ .......................................... iii 2.5 Design and Implementation Constraints ............................................... ................. iii iii 2.6 User Documentation ............................................ .................................................. iii 2.7 Assumptions and Dependencies Depende ncies ......................................................... ................... iii 3. System Features ............................................... ................................................... ......... iv 3.1 Free Registration for Viewing some Information about Articles .......................... iv iv 3.2 Secured Subscription Sub scription for various levels of customers for various Articles ........... iv 3.2 Searching needed articles ............................................... ........................................ iv 3.2 Submission of Articles for Publishing Pu blishing ............................................ ....................... iv 4. External Interface Requirements 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 Req uirements ........................................ ............................................... .... 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 t he 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
Maintain
Marketing
Executives
Users Article Publish, Subscribe
Information System
Finding, Subscribe
Educational and Research Users
Latest Topics
Search
Existing Customers
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 Research Users Management
Publish research articles, keep updates on latest articles
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: OE-2: OE-3:
The Article Information System shall operate with the Web browsers which are Java Enabled The Article Information System shall operate on any server with Apache Tomcat Web Server. The Article 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 Implementation Constraints CO-1: CO-2: CO-3: CO-4:
The system’s design, code, and maintenance documentation shall conform to the Process Impact Intranet Development Standard, Version 1.3 [2] The system shall use the Standard Oracle database engine All HTML code shall conform to the HTML 4.0 standard All programming Code is written in J2EE and J2SE
6.6. User Documentation Documentation UD-1: UD-2:
The system system shall provide an online hierarchical and cross-linked cross-linked help system in HTML that describes and illustrates all system functions This system provides online help manual for Searching and Publishing Articles and provides samples for easy understanding
6.7. Assumptions and Dependencies AS-1: DE-1:
This system is accessible at any time in any day. 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 a lso search for their desired Articles. The free registrations only give the Article Abstract. It is an Extra Benefit Feature a nd 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: Response: Stimulus: Response: 3.1.3
Customer request for Registration System now prompts for Personal Details and a Password for Registration Customer needs to give Personal Details and a Password for Registration System now gives a Temporary Low Level Subscription Code and its validity period
Functional Requirements
REQ-1: Free Registration 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: Response: Stimulus: Response: 3.1.3
Customer request for Registration System now prompts for Personal Details and the Subscription Code and Password for Registration Customer needs to give Personal Details and the Subscription Code and Password for Registration System now gives validity period and display Subscription Level Details
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: Response:
Customer request for Searching System now prompts for Keywords or Article Contents for articles finding Customer enters Keywords or Article Contents for articles finding System now display the relevant Articles information related to input Queries
Stimulus: Response: 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: Response: Stimulus: Response: Stimulus: Response: 3.1.3
Customer request for Publishing System now prompts subscription code and password Customer now enters subscription code and password System now prompts for article (one per time) Customer now uploads the article file System now stores the article and displays success message to customer
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: UI-2:
The Article Information System screen displays shall conform to the Process the Process Impact Internet Application User Interface Standard, Version 2.0 [4]. 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 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: PE-2: PE-3: PE-4:
The system should accommodate 200+ users concurrently All Web pages generated by the system shall be fully downloadable in no more than few seconds over a low speed modem connection Responses to search queries shall take no longer than 5 seconds to load onto the screen after the user submits the query 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: SE-2:
Users shall be required to log in to the System for all operations except Searching All customers detail accessing should posses RSA Encryption
9.4. Software Quality Attributes Availability : Robustness : Usability :
This System System shall be available to users users on 99% in 24x7 basis If the connection between the user and the system system is broken prior to an subscription being either confirmed or canceled, the System shall enable the user to recover an incomplete order. This system should be very easy one to use
10. Other Requirements Appendix A: Glossary AIS SCODE
: :
Article Information System Subscription Code
Appendix C: Data Dictionary CUSTOMER ( name, password, subscription code, code, address, phone ) SUBSCRIPTION ( subscription code, code, description, validity ) validity ) PUBLICATION ( customer name, article title, published date, date, contents, Priority ) Priority ) ARTICLE ( author name, article title, published date, date, contents )
Use Cases for
Article Information System, Release 1.0 Version 1.0 Approved A pproved
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. 2. 3. 4.
Search For Articles Subscribe For Articles Submit Article For Review Login For accessing Subscribed Articles and View the Articles
Reviewers
5. Review the Articles
Use Case ID: Use Case Name: Created By: Date Created: Actors: Description:
1 Search For Articles Bakthavatchalam.G Feb 25, 2009
Last Updated By: Date Last Updated:
Customers The customers customers may search for for new/old articles with the specification specification of author/issue date/title/keywords
Preconditions: Postconditions: Normal Flow:
All the information’s about the Articles(new & old) should be available available The Search History History dumped into Storage for for Future Analysis Analysis 1.0 Search Using Author
1. 2. 3. 4. 5. Alternative Flows:
The System displays the Search box for author name input User types the author name and do searching The System search the articles which are submitted by the given author Then it will display the resulted articles to Users screen User now view the articles relevant to his request and view the article one by one 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 art icles 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. 2. 3. 4. 5.
The System displays the Search box for t itle input User types the title and do searching The System search the articles art icles which are contains the given title Then it will display the resulted articles to Users screen User now view the articles relevant to his request and view the article one by one 1.3 Search Using Keywords
1. 2. 3. 4.
The System displays the Search box for keyword input User types the keywords keywords and do searching The System search the articles ar ticles which are contains the given keywords Then it will display the resulted articles to Users screen
Exceptions:
5. User now view the articles relevant to his request and view the article one by one 1.0.E.1 If user gives an Invalid Date (at step 1.1) 1. System gives Error Message as Invalid Invalid Date Format/Date Not Exist.
1.0.E.2 Author Name is not Found (at step 1.0)
Includes: Priority: Frequency of Use: Business Rules: Special Requirements: Assumptions: Notes and Issues:
Use Case ID: Use Case Name: Created By: Date Created: Actors: Description:
1. System gives Error Message as No Author Found. None High Approximately 200+ times per day None 1. The System must know the latest and old articles and its details. 1. If the user is not logged logge d then System only allows the minimal information about articles. 1. System must know the user is a Guests or Subscribed Customers
2 Subscribe For Articles Bakthavatchalam.G Feb 25, 2009
Last Updated By: Date Last Updated:
Customers The Article Management Management System provides multilevel Subscriptions and the subscription code.
Preconditions: Postconditions:
The Subscription Codes and corresponding Users must available User’s detail has been saved.
Normal Flow:
Alternative Flows: Exceptions:
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 I nformation was saved. 5. Now the User can able to view subscribed articles and to post article for publication None 1.0.E.1 Invalid Subscription Code (at step 1)
1. System informs user that given given code is invalid format or not exist. Includes:
None
Priority:
High
Frequency of Use: Business Rules: Special Requirements: Assumptions: Notes and Issues:
Use Case ID: Use Case Name: Created By: Date Created: Actors: Description:
Approximately 20 times per week None 1. The Subcode should be in a specified fixed format 1. The Subscribed User got the subcode via postal and he must enter the same code here to view articles a rticles online None
3 Submit Article For Review Bakthavatchalam.G Feb 25, 2009
Last Updated By: Date Last Updated:
Customers The Subscribed Subscribed Users may have an opportunity opportunity to publish their articles. To publish the Article user must submit the article for reviewing. After review the article is published.
Preconditions: Postconditions: Normal Flow:
Alternative Flows: Exceptions:
User Must Must log log in to our our System to do do this. The Submitted article directed to Reviewing Section. 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. None 11.0.E.1 Invalid Article Format (at step 1)
1. System informs informs that Article is not not Valid Valid Format.
Includes:
None
Priority:
High
Frequency of Use: Business Rules: Special Requirements:
Approximately 2 times per month by one one user None 1. Article should be in given Fixed Format
Assumptions:
None
Notes and Issues:
None
Use Case ID: Use Case Name: Created By: Date Created: Actors:
4 Login For accessing accessing Subscribed Articles and View the Articles Bakthavatchalam.G Feb 25, 2009 Customers
Last Updated By: Date Last Updated:
Description:
The Subscribed Subscribed Users may login into their account to see updated articles and any information regarding to his art icle submission or to do submission.
Preconditions: Postconditions: Normal Flow:
Alternative Flows:
User Must Must register in to our System System to do this. The Submitted article directed to Reviewing Section. 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. 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 password is not Valid. Valid.
Includes:
None
Priority:
High
Frequency of Use: Use: Business Rules: Special Requirements:
Approximately 2 times times per per day by one user None 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
Date Created: Actors: Description:
Feb 25, 2009
Last Updated By: Date Last Updated:
Reviewer The Subscribed Subscribed Users may have an opportunity 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: Postconditions: Normal Flow:
Alternative Flows:
Reviewer Must Must log in to our System to do this. this. The Submitted articles are available. 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. None
Exceptions:
None
Includes:
None
Priority:
High
Frequency of Use: Business Rules: Special Requirements:
Approximately 20 times per month None 3. Article should be in given Fixed Format
Assumptions:
None
Notes and Issues:
None
TEST PLAN Project Number: Project Name:
Description:
Project Manager:
08MW03 Article Information System A web application which enable the article library members to search for articles, subscribe and view books online. The customer can search new articles and publish new articles. G.BAKTAVATCHALAM
Date Updated:
Project Test Plan
Overview Test plan objectives
Testing Assumptions
Risks & Contingencies
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. - 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. The following risks apply to the testing process process and may impact 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 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
Features Not to be Tested
-
Online help Logout Articles for session Database used for both authentication and validation 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
Test Documents
Test Case Pass/Fail Criteria
Suspension/Resumption Criteria
Problem Logging/Resolution
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. 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 Each Test Case will be evaluated against the acceptance criteria as outlined in the test case scripts scripts to determine if the test passed 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. Test Cases that do not run to completion will be evaluated on a case by case basis to determine if the testing must start over or resume at the point where the failure occurred. In extremely long test cases, cases, checkpoints will be established for resumption in the middle of a test case where appropriate. In general, a test may be resumed resumed in the middle when the error is not critical. Errors identified through testing will be logged. Resolve the problem 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
Preparation of the testing environment
Integration & System testing
Testing environment has been set up
None
Establishment of Test Plan and Testing Templates
None
Updating of Functional Unit Master Test Case Lists and Test Case Scripts Actual Testing (execution of Test Case Scripts)
None
-
Final Functional User Acceptance Testing & Sign-off
Timeframe
Testing environment has been set up Integration & System Testing has been completed Test Case Scripts have been developed
- Deployment of Online Library Management system
Mar – Apr
Apr 14
Apr 14
Start Apr 14, 2009
Start Apr 14, 2009
Apr 21 , 2009
Prototype for
Article Information System Version 1.0 Approved A pproved
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 A pproved
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 Artic le Contents
Search for Articles Guest User Subscribe for Articles A rticles
Customer Login Submit Articles for Publishing Reviewer View Articles
Class Diagram:
Login subcode : String pwd : String validate()
SubCodeUtil checkCodeFormat() getCode()
Review
ArticleUtil
getReqArticles() accept() reject()
validateArticles() store()
Article
storeUserInfo() storeHelpInfo() storeArticle() getArticles() getUserInfo() getHelpInfo()
Registration getUserInfo() validate() store()
ServerManager Articles keys[] serverReader serverWriter distribute() sendArticles() sendKeys() getACount()
getInfo() setInfo()
Account
Search usingTitle() usingAuthor() usingIDate() usingKeys()
id title author idate keywords[] contents
DBUtil
ClientManager getArticles() getKeys() search() sendResults()
cname addr phone pwd scode getInfo() setInfo()
DynHelp getHelpInfo() setHelpInfo()
Sequence Diagram: Login:
C ustomer
AIS
D BManager
1: Enter Subcode and pwd 2: validate code 3: illegal Format
4: getUserInfo 5: UserInfo UserInfo
7: inv i nvalid alid user 8: Re-direct Re-direc t to home
6: validate user
Register:
C ustomer
A IS
D B Manager
1: Submit S ubmit All Info Info
2: verify all info 3: invalid info
4: store 5: success
6: display status
Review:
Revi ewer
AIS
D BManager
1: Requested Articles 2: Req Articles
4: Articles 5: accept/r acce pt/reject eject
3: Articles
Search:
C ustomer
AIS
D BManager
1: author/idate/title/content author/ida te/title/contents s 2: getArticles 3: Searchin S earching g 4: Article Result Set
5: formatted info
Help:
C ustomer
AIS
D BManager
1: req help topic 2: req help info 3: search
5: formatted help
4: help inf i nfo o
Collaboration Diagram: Login:
2: validate validate code cod e 6: validate user Customer 1: Enter Subcode and pwd
3: ill i llegal egal Format 7: invalid user 8: Re-direct to home
AIS 4: getUserInfo getUserInfo
5: UserInfo
DBManager
Register:
2: verify all info
1: Submit S ubmit All A ll Info Info Customer
AIS AIS 4: store 3: invalid info 6: display status 5: success
DBManager
Review:
5: accept/rej acce pt/reject ect DBManager 2: Req Articles 1: Requested Articles Reviewer AIS AIS
3: Articles
4: Articles
Search: AIS 1: author/idate/title/contents
3: Searching 2: getArticles getArticles
Customer 5: formatted i nfo nfo 4: Article Result Set DBManager
Help: Customer
1: req help topic AIS AIS
5: formatted help
3: search 2: req help help info
4: help info DBManager
Activity Diagram:
Customer
AIS
DBManager
invalid code & pwd
Login
verify user
Verify code
invalid code
valid user retrieve articles
display articles
get articles
articles
result set format articles article
send article
verify
send for publish
store
author/idate/keys/title search
get articles
search
result set show articles
formatting articles
finding articles
Component Diagram:
Crawler
AIS
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"); throw nfe; } 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" 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" 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
1
2
3
Test case ID
+/-
Short Description
Steps to follow
Expected results
Obtained result
+
Check link from index page to login page
Click LOGIN
Forwarded to login page
Forwarded to login page
+
Check link from index page to Register page
Click REGISTER
Registration form should be displayed
Registration form should be displayed
Reviewer page should display
Reviewer page is displayed
Search page should be displayed
Search page is displayed
Useraccount page should be displayed
Useraccount page is displayed
TC1.1
TC1.2
TC1.3
+
Check link from index page to Reviewer page
Check link from home page to search page 4
5
TC1.4
TC1.5
Click Search
Click Search
+
+
Check link from home page to useraccount page
Click 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","");
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", 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\"},disp_tag:\"[html_edi t] subcode\"": "STND.GVF" 4 14 1 { Compare: "AT" %"As Text" $STND.GVF, *1408, }0 "{class: \"edit\", MSW_class: \"html_edit\", html_name: \"pwd\", t ag: \"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\"},disp_tag:\"[html_pus h_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.