BEST2

ADDRESS BOOK
SOFTWARE REQUIREMNT SPECIFICATION

VERSION 1.0

TEAM GUIDE: MR.KAPIL SISODIA

MEMBERS: 1. RUHITA CHOUHAN

2. PRIYANKA NEMA

COLLEGE NAME : GYAN GANGA INSTITUE OF TECHNOLOGY & SCIENCES

DEPARTMENT: COMPUTER SCIENCE

STATE : MADHYA PRADESH

 Table of Contents

1.0 INTRODUCTION

1.1 PURPOSE
1.2 SCOPE
1.3 DEFINITION, ACRONYM&ABBREVIATION
1.4 REFERNCES
1.5 TECHNOLOGY TO BE USED
1.6 OVERVIEW

2.0 OVERALL DESRCIPTION

2.1 PERSPECTIVE DESCRIPTION
2.2 SOFTWARE INTERFACE
2.3 HARDWARE INTERFACE
2.4 PRODUCT FUNCTION
2.5 USER CHARACTERISTICS
2.6 CONSTRAINTS
2.7 ARCHTECTURAL DESIGN
2.8 USE CASE MODEL DESCRIPTION
2.9 CLASS DIAGRAM
SEQUENCE DIAGRAMS
2.10 DATABASE DESIGN
2.11.1 ER DIAGRAM
2.11.2 SCHEMA

2.12 ASSUMPTION AD DEPENDENCIES

3.0 SPECIFIC REQUIREMENTS

3.1 USE CASE REPORTS

3.2 SUPPLEMENTARY REQUIREMENTS

SOFTWARE REQUIREMENT
SPECIFICATION

1.0 INTRODUCTION
1.1 PURPOSE

The purpose of Software Requirements Specification (SRS) document is to describe the

external behavior of the Web based address Book system. Requirements Specification
defines and describes the operations, interfaces, performance, and quality assurance
requirements of the Web based address Book system. The document also describes the
nonfunctional requirements such as the user interfaces. It also describes the design
constraints that are to be considered when the system is to be designed, and other factors
necessary to provide a complete and comprehensive description of the requirements for the
software. The Software Requirements Specification (SRS) captures the complete software
requirements for the system.

1.2 SCOPE

The Software Requirements Specification captures all the requirements in a single

document. The Web based address Book system that is to be developed provides
convenience to manage their contacts. The Web based address Book system is supposed to
have the following features.

1. User can access his/her account.

2. He/She can insert, delete, update contacts.
3. Data of user must remain secure from unauthorized use.
 The features that are described in this document are used in the future phases of the
software development cycle. The features described here meet the needs of all the users.
The success criteria for the system is based in the level up to which the features described
in this document are implemented in the system.

1.3 DEFINITION , ABBREVIATION & ACRONYMS

• HTML(HYPER TEXT MARK UP LANGUAGE)

• JSP(JAVA SERVER PAGES)
• J2EE(JAVA 2 ENTERPRISE EDITION)
• WASCE(WEB SPHERE APPLICATION SEVER COMMUNTIY EDITION)
• WSAD (WEB SPHERE STUDIO APPLICATION DEVELOPER)
• DB2(IBM DATABASE 2)
• HTTP(HYPER TEXT TRANSFER PROTOCOL)
•
1.4 REFERENCES

Web Address

(a). www.google.com

1.5 TECHNOLOGIES TO BE USED

• J2EE
• DB2
• JAVA
• XML
• RAD 7.0
1.6 OVERVIEW
THIS INCLUDES 2 SECTIONS
1. OVERALL DESCRIPTION-SECTION WILL DESCRIBE MAJOR COMPONENTS OF THE
SYSTEM,INTERCONNECTION AND EXTERNAL INTERFACES.
2. SPECIFIC REQUIREMENTS-SECTION DESCRIBES FUNCTION OF ACTORS,THEIR ROLES IN
THE SYSTEM AND THE CONSTRAINTS FACED BY THE SYSTEM.
 2.0 OVERALL DESCRIPTION
2.1 PRODUCT PERSPECTIVE
The Web based address Book system is a package to be used by users to
manage their contacts.The system provides insert , edit ,delete , search facilities. The user
is provided a login id and password so his information can be secure
2.2 SOFTWARE INTERFACES

A firewall will be used with the server to prevent unauthorized access to the system.

Operating System -: Window XP

Database -: DB2

Language -:JAVA

Web Server -: WASCE

2.3 HARDWARE INTERFACE

The existing Local Area Network (LAN) will be used for collecting data from the
users.

512 MB RAM, Pentium P3/P4, 20/40 GB Hard disk

2.4 PRODUCT FUNCTIONS

The Web based address Book system is management of information about the contacts
given by user. The Product functions are more or less the same as described in the
product perspective. The functions of the system include the system providing different
type of services based on the type of users[DBA/USER].

The users have sufficient knowledge of computers. The institute

computer should have Internet connection and Internet server capabilities. The users
know the English language, as the user interface will be provided in English.
2.5 USER CHARACTERISTICS
The users of the system are users and DBA who maintain the system.
m. The users are assumed to
have basic knowledge of the computers and Internet browsing.The
The proper user interface, users
manual, help of system must be sufficient to educate th
thee users on how to use the system without
any problems.

2.6 CONSTRAINTS
The information of all the users must be stored in a database that is accessible by
the Web based address Book system. The Web based address Book system is
running all 24 hours a day. The uusers
sers access the Web based address Book system
from any computer that has Internet browsing capabilities and an Internet
connection. The users must have their correct usernames and passwords to enter
into the system
2.7 ARCHITECTURE DESIGN
Use case diagram

Class diagram
The diagram includes the classes discovered during analysis, plus some additional
classes discovered during design. (In a more significant system, the total number of
classes may be about five times as great as the number of classes uncovered during
analysis.)

• AddressBookApplication - main class for the application; responsible for

creating the FileSystem and GUI objects and starting up the application.
• MultiInputPane - a utility class for reading multiple values at a single time.
(Design not further documented, but javadoc is included.)
• Person.CompareByName - Comparator for comparing two Person objects by
name (used for sorting by name).
• Person.CompareByZip - Comparator for comparing two Person objects by zip
(used for sorting by name).

The following relationships hold between the objects:

• The main application object is responsible for creating a single file system
object and a single controller object.
• The file system object is responsible for saving and re-loading address books
• The controller object is responsible for creating a single GUI object.
• The controller object is responsible for initially creating an address book
object, but the GUI is henceforth responsible for keeping track of its current
address book - of which it only has one at any time.
• The GUI object and the address object are related by an observer-observable
relationship, so that changes to the address book content lead to
corresponding changes in the display
• The address book object is responsible for creating and keeping track of
person objects, of which there can be many in any given address book.
• A MultiInputPane object is used by the controller to allow the user to enter
multiple items of data about a person.
• A comparator object of the appropriate kind is used by the address book
object when sorting itself.
 1.1.1.1 Click on a class icon for links to further information about it

2.11 sequence diagrams

1.1.2 Add a Person Use Case Sequence Diagram

1.1.3 Edit a Person Use Case Sequence Diagram

1.1.4 Delete a Person Use Case Sequence Diagram

1.1.5 Sort Entries By Name Use Case Sequence Diagram

1.1.6 Sort Entries By Zip Use Case Sequence Diagram

 1.1.7 Print Entries Use Case Sequence Diagram

1.1.8 Create New Address Book Use Case Sequence Diagram

1.1.9 Open Existing Address Book Use Case Sequence Diagram
 1.1.10 Save Address Book Use Case Sequence Diagram

1.1.11 Save Address Book As ... Use Case Sequence Diagram

1.2 The Sequence Diagram for the Save Address Book As ... Use Case is left
as an exercise to the student

1.2.1 Offer To Save Changes Extension Use Case

2.10.1 DATABASE DESIGN
3.0 SPECIFIC REQUIREMENTS
SUPPLEMENTARY REQUIREMENTS

Performance Requirements

• The performance of the functions and every module must be well.

• For individual function the performance will be well.
• For login to the software password and user name will be matched
ed to the password and name
saved in the database and thus only authenticated users are allowed to the login.
• Theree will be various formats of retrieving data
data.
• The overall performance of the software will reliable and enable the users to work efficiently.

Security Requirements

• There will be proper security regarding to the accessing of data.

• The external security can be provided by given the login authentication.
• The data that are stored in the database must be private.
• There is also required a user authentication.
• Capcha security is also provided.
• The whole software is secure from the outside accessing.
 BEST2/G.G.I.T.S

External Interface Requirements

User Interfaces

• The design or layout of every form will be very clear and very interactive to the user.
• When the user open the software the welcome window will appear.
• In the login window the user can easily entered the desired password and login name.
• Then it will give the successfully login message.
• From each and every window the user can easily go to any desired window that is there is will be
a absolute and relative linking.
• There will be a proper collection of GUI interface, which will provide better look and feel.
• In the screen layout the background color is very light and the graphics and font style will be in
proper manner and well organized.
• In each and every window there will be alert, confirm etc message box for displaying message.
• The user will be able to search any data from the record by using proper guideline shown in the
window & Linux.
• User can easily save its data in to the database and update as their need.
• This software will be easily understandable and operable by the user.
BEST2/G.G.I.T.S