Académique Documents
Professionnel Documents
Culture Documents
ADDRESS BOOK
SOFTWARE REQUIREMNT SPECIFICATION
VERSION 1.0
2. PRIYANKA NEMA
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
1.0 INTRODUCTION
1.1 PURPOSE
1.2 SCOPE
Web Address
(a). www.google.com
A firewall will be used with the server to prevent unauthorized access to the system.
Database -: DB2
Language -:JAVA
The existing Local Area Network (LAN) will be used for collecting data from the
users.
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].
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.)
• 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
1.2 The Sequence Diagram for the Save Address Book As ... Use Case is left
as an exercise to the student
Performance Requirements
Security 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