group 3 address book srs

7
PROBLEM STATEMENT The software to be designed is a program that can be used to maintain an address book. An address book holds a collection of entries, each recording a person's first and last names, address, city, state, zip, and phone number. It must be possible to add a new person to an address book, to edit existing information about a person (except the person's name), and to delete a person. It must be possible to sort the entries in the address book alphabetically by last name (with ties broken by first name if necessary), or by ZIP code (with ties broken by name if necessary). It must be possible to print out all the entries in the address book in "mailing label" format. The program will keep track of whether any changes have been made to an address book since it was last saved, and will offer the user the opportunity to save changes when an address book is closed either explicitly or as a result of choosing to create/open another or to quit the program.

Upload: swagata-rana

Post on 09-Nov-2015

4 views

Category:

Documents


1 download

DESCRIPTION

SRS for ADRRESS BOOK GUI

TRANSCRIPT

PROBLEM STATEMENT

The software to be designed is a program that can be used to maintain an address book. An address book holds a collection of entries, each recording a person's first and last names, address, city, state, zip, and phone number. It must be possible to add a new person to an address book, to edit existing information about a person (except the person's name), and to delete a person. It must be possible to sort the entries in the address book alphabetically by last name (with ties broken by first name if necessary), or by ZIP code (with ties broken by name if necessary). It must be possible to print out all the entries in the address book in "mailing label" format. The program will keep track of whether any changes have been made to an address book since it was last saved, and will offer the user the opportunity to save changes when an address book is closed either explicitly or as a result of choosing to create/open another or to quit the program.

INTRODUCTION

In this project we are going to build a software model for A SIMPLE ADDRESS BOOK.

Our main aim of this project is to store the address data of N number of persons and arrange them by using their names and other formats like sort by zip, state, name. By this Address Book Application we are going to store the details of people. It mainly contains the following detailsCreate a address book, Add a person, Edit a person, Delete a person, Sorting the entries, Open existing address book .

We are going to implement using the methods and sources of Objective Oriented Analysis & Design and Principles of Software Engineering.REQUIREMENTSUSER REQUIREMENTS

It must be possible to add a new person to an address book, to edit existing information about a person (except the person's name), and to delete a person.

It must be possible to sort the entries in the address book alphabetically by last name (with ties broken by first name if necessary), or by ZIP code (with ties broken by name if necessary).

It must be possible to print out all the entries in the address book in "mailing label" format.

The initial requirements call for the program to only be able to work with a single address book at a time.FUNCTIONAL REQUIREMENTS If the user chooses the New or Open menu option, any current address book will be closed before creating/opening a new one.

A later extension might allow for multiple address books to be open, each with its own window which can be closed separately, with closing the last open window resulting in terminating the program.

In this case, New and Open will result in creating a new window, without affecting the current window.

The program will keep track of whether any changes have been made to an address book since it was last saved, and will offer the user the opportunity to save changes when an address book is closed either explicitly or as a result of choosing to create/open another or to quit the program.

The program will provide the features like sort by name or zip.

NON-FUNCTIONAL REQUIREMENTS Proper design of the system and its architecture.

Accessing the system is very fast.

Good performance and efficiency.PERFORMANCE AND USABILITY PERFORMANCE The software should response to user requests at a speed equal to or better tha competing applications, in any event not to exceed 500 ms.Reliability The system should enter and retrieve or exchange address book data without loss or error.

Consistency

It should be possible to edit the name any time while keeping the associated dataGraphical User Interface

The system shall provide use of icons and toolbars.

The overall aim of the design aspect is to have a GUI that is

convenient and provides ease of usability to the customer.

Interfaces: There are many types of interfaces : User Interface, Software Interface and Hardware Interface.User Interfaces

The user interface for the software will be compatible to any OS that support java based GUI such as windows7, windows8, Linux.The user interface shall be implemented using any tool or software package like Java Swing.Hardware Interfaces512 MB RAM, Pentium P3/P4, 20/40 GB Hard diskSoftware Interfaces

Operating system: Windows7, Linux

Database: MySQLDESIGN CONSTRAINTS:The information of all the users must be stored in a database that is accessible by the Web based address Book systemAssumptions and Dependencies:

The users have sufficient knowledge of computers. The users know the English language, as the user interface will be provided in English. CONCLUSION

This is a brief description of the preliminary version of a address book system. This documentation may be improved and revised.