Scribd
Upload
1K views

SRS On ADDRESS BOOK

This document provides a software requirements specification for an offline address book application. It describes the purpose, intended users, and scope of the project. The document outlines key product features such as storing unlimited contact entries with various fields, categorizing contacts, and printing contacts. It also provides use cases for creating, updating and deleting contacts. Finally, it specifies the required hardware, software, programming language and describes some design and implementation constraints.

Uploaded by

Rahul Dwivedi
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as RTF, PDF, TXT or read online on Scribd
1K views

SRS On ADDRESS BOOK

This document provides a software requirements specification for an offline address book application. It describes the purpose, intended users, and scope of the project. The document outlines key product features such as storing unlimited contact entries with various fields, categorizing contacts, and printing contacts. It also provides use cases for creating, updating and deleting contacts. Finally, it specifies the required hardware, software, programming language and describes some design and implementation constraints.

Uploaded by

Rahul Dwivedi
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as RTF, PDF, TXT or read online on Scribd
You are on page 1/ 17

Software requirement specification

On

Address book
(offline mode)

MINI PROJECT ON ADDRESS BOOK


(OFFLINE MODE)

SOFTWARE REQUIRMENT SPECIFICATION


Submitted by
ANSHIKA DIXIT
ANUJ MISHRA
ANURAAG MISHRA
ASHISH MISHRA
in partial fulfillment for the award of the degree

of

BACHELOR OF ENGINEERING
IN

INFORMATION TECHNOLOGY

PRANVEER SINGH INSTITUTE OF TECHNOLOGY


KANPUR

BONAFIDE CERTIFICATE
Certified that this project report “ADDRESS BOOK (OFFLINE

MODE)” is the bonafide work of“ ANSHIKADIXIT(0716413014),

ANUJ MISHRA(0716413015) , ANURAAG MISHRA(0716413016),

ASHISH MISHRA(0716413017)”, who carried out the project work under

my supervision.

SIGNATURE

MR.RAM JEE MISHRA


Lecturer
I.T. Department
P.S.I.T. Kanpur

INTERNAL EXAMINER
Table of Contents

Table of Contents......................................................................................ii
Table of Figures........................................................................................iii
1.0.Introduction..........................................................................................1
1.1. Purpose...............................................................................................1
1.2. Intended audience.................................................................................1
1.3. Project Scope........................................................................................1
1.4. References............................................................................................2
1.5. Document overview.............................................................................2
2.0. Overall description............................................................................4
2.1. Product Prospective..............................................................................4
2.2.Product Features....................................................................................4
2.3.Operating Environment.......................................................................11
2.4. Use cases..............................................................................................5
2.4.1. Use Case: Create New Entry..........................................................8
2.4.2. Use Case: Update an Entry.............................................................9
2.4.3. Use Case:Delete an Entry.............................................................10
2.5.Design and Implementation Constraints....Error: Reference source not
found
2.6.Assumptions and Depndencies.........Error: Reference source not found
2.7.Operating Environment....................Error: Reference source not found
TABLE OF FIGURES

PAGE NO.
FIGURE TITLE
NO.

1 ZERO LEVEL DFD 20

2.3.a ONE LEVEL DFD 24


26
2.3.b ER DIAGRAM

INTRODUCTION:

Purpose
The purpose of this software requirements specification (SRS) is to establish the
major requirements necessary to develop san address book in offline mode
which can assist the storage, retrieval , updation , deletion of contact details in a
user friendly manner

Intended Audience
the different types of reader that the document is intended for:
developers,
users,
testers,
documentation writers.
The sequence for reading the document, beginning with the content table along
with a look on the table of figures.

Project Scope
short description:
Address Book is easy to use, yet powerful software that makes keeping
track of your contacts .  The user interface is designed to minimize
keystrokes or mouse movements necessary to get your information
quickly

Relevant benefits:

 Handy Address Book offers complete storage of contacts details added


to memorandums, reminders
 Simple and attractive GUI
 Lessr keystrokes required for working
 Print your addresses in a tabular list format, booklet, or as detailed
records
Objectives:
To provide easy working, user friendly interface and strong working based
address book .

References
 http://www.beiley.com/habook/help/documentation.htm
 http://www.wikipedia.com/addressbook.htm
Document Overview

This document is prepared for the requirement specification of address book.


This software is for users who are interested in storing, accessing updating,
deleting , printing the contact details. It will accomplish this by posting contact
details. The view of contact details can be customized as list ,grid, icons.

OVERALL DESCRIPTION:
Product Perspective
An address book or a name and address book (NAB) is a book or a database
used for storing entries called contacts. Each contact entry usually consists of a
few standard fields (for example: first name, last name, company name,
address, telephone number, e-mail address, fax number, mobile phone
number). Most such systems store the details in alphabetical order of people's
names, although in paper-based address books entries can easily end up out of
order as the owner inserts details of more individuals or as people move. Many
address books use small ring binders that allow adding, removing and shuffling
of pages to make room

Product Features
 Handy Address Book offers complete storage of contacts details added
to memorandums, reminders

 Simple and attractive GUI

 Lessr keystrokes required for working

 Print your addresses in a tabular list format, booklet, or as detailed


records

 Multiple Address Books


You can create as many address books as you'd like.  You may want to
organize your addresses into different address books.  Each person in
your family could have their own address book, or you could have a
separate address book for your company or club.

 Unlimited Addresses
Each address book can contain an unlimited number of addresses.

 Categorize Your Addresses


Organize your addresses by assigning them to categories.  For
example, you may want to have a "Holiday Card" category, where
everyone in this category will get sent a card.   You can create as many
different categories as you'd like, and addresses can belong to multiple
categories.
 Printing
Print your addresses in a list or table format.  Print them in a detailed report
format.  You can also print mailing addresses out on envelopes and labels. 
Printing is very customizable, so you can make your printouts appear just as
you want.

 Print Preview
Preview your print job before printing to make sure it appears just as you
want.

Operating Environment

The required technical specification for the project are listed as follows:

Hardware:

 R.A.M.(1 G.B.)
 PROCESSOR (intel P IV,2.4 GHz)
 Hard disk space(10 GB)

Software:

 VB.Net
 MS SQL(database)

Language Used:

 C#(for scripting)

USE CASES:
Create New Entry

Update an Entry

Delete an Entry

Design and Implementation Constraints


<Describe any items or issues that will limit the options available to the developers.
These might include: corporate or regulatory policies; hardware limitations (timing
requirements, memory requirements); interfaces to other applications; specific
technologies, tools, and databases to be used; parallel operations; language
requirements; communications protocols; security considerations; design conventions
or programming standards (for example, if the customer’s organization will be
responsible for maintaining the delivered software).>

Assumptions and Dependencies


<List any assumed factors (as opposed to known facts) that could affect the
requirements stated in the SRS. These could include third-party or commercial
components that you plan to use, issues around the development or operating
environment, or constraints. The project could be affected if these assumptions are
incorrect, are not shared, or change. Also identify any dependencies the project has on
external factors, such as software components that you intend to reuse from another
project, unless they are already documented elsewhere (for example, in the vision and
scope document or the project plan).>

You might also like