Software Requirements Specification

Software Requirements
Specification
SMS Based Push Mail System

Sep 3, 2010

Group 7

Ankit Kumar (IT/07/405)

Anjali Arora (CSE/07/310)
Ankit Gauri (CSE/07/311)
Dheeraj (IT/07/415)
Madhuri (CSE/07/329)
Sapna (CSE/07/267)

Page i of 15
Software Requirements Specification

Table of Contents
1. Introduction................................................................................................................................1
1.1 Purpose ............................................................................................................................................... 1
1.2 Document Conventions....................................................................................................................... 1
1.3 Intended Audience and Reading Suggestions..................................................................................... 1
1.4 Project Scope....................................................................................................................................... 2
1.5 References........................................................................................................................................... 2
2. Overall Description....................................................................................................................2
2.1 Product Perspective............................................................................................................................. 2
2.2 Product Features.................................................................................................................................. 3
2.3 User Classes and Characteristics........................................................................................................ 3
2.4 Operating Environment....................................................................................................................... 3
2.5 Design and Implementation Constraint.............................................................................................. 3
2.6 Assumptions and Dependencies......................................................................................................... 4
3. System Features......................................................................................................................... 4
3.1 System Feature 1................................................................................................................................. 4
3.2 Logging out........................................................................................................................................ 5
3.3 Sending Mail....................................................................................................................................... 5
3.4 Retrieving Mail................................................................................................................................... 6
3.5 Adding Members in the Contact List.................................................................................................. 6
3.6 Checking Mails of Staff...................................................................................................................... 7
3.7 Chit-Chat............................................................................................................................................. 7
4. External Interface Requirements............................................................................................. 9
4.1 User Interfaces.................................................................................................................................... 9
.................................................................................................................................................................. 9
4.2.1 Hardware Interfaces........................................................................................................................ 9
5. Other Nonfunctional Requirements.......................................................................................10
5.1 Performance Requirements............................................................................................................... 10
5.1.1 Availability................................................................................................................................. 10
5.1.2 Portability................................................................................................................................... 10
Mail system will be designed with in mind to run this application on different platform. SQL
SERVER provides well defined interfaces which are independent of the platform it runs on. It
should be possible to have these running on another platform but it will not be tested.....................10
5.1.3 Flexibility - Effort needed to modify operational program is less............................................. 10
5.1.4 Interoperability - Effort needed to couple one system with another will be less...................... 10
5.2 Safety Requirements......................................................................................................................... 11
5.3 Security Requirements...................................................................................................................... 11
5.4 Software Quality Attributes.............................................................................................................. 11
5.4.1 Maintainability........................................................................................................................... 11
5.4.2 Reliability................................................................................................................................... 11

Page ii of 15
Software Requirements Specification

Revision History
Name Date Reason For Changes Version
SMS Based Push Sep3, Initial Version 2.0
Mail System 2010

Page iii of 15
Software Requirements Specification

1. Introduction

1.1 Purpose

The objective of this system is to define the requirements for Email Systems. In detail this
application will provide description of the System. The main objective is to develop a user-friendly
system which sends, receives and saves the email messages, documents and images by attachments
from one user to another. It also provides the feature of chit-chat i.e. the chat option, so that the
staff members in a organization can talk and chat whenever they feel like, staff members can chat
with the members who are in the contact list, if they want to chat with the other staff member then
they have to first add in contact list and then they can chat. It also provides the specific
requirements and functionality needed for this system.

This application was developed for an intranet project, and would be useful for any small to
medium sized organization who use a Windows NT Server, Windows XP, Windows 7, Windows
Vista etc, or even just a Networked Windows 95 solution running the personal web server, and who
want an e-mail system, but don't want the associated costs. This system could also be used for a
community based website, as to allow members only to send email to other members.

The system uses the Asp.Net for the purpose of front end and SQL Server as a back end in the
development process.

1.2 Document Conventions

Here for describing the functionality we include point like:

1. Description: describes the functions provided to user like make Login etc
2. Priority: describe whether functionality is essential or not.
3. Trigger: which web page is opened when we click on the functionality?
4. Actors: describes the users who can access the respective functionality.
5. Path: describes the complete path.

1.3 Intended Audience and Reading Suggestions

The document is meant for the developers and project managers. It specifies the software
requirements for developing this module.
The rest of this SRS is organized as follows:

Section 2 gives an overall description of the software. It gives what level of proficiency is expected
of the user, some general constraints while making the software and some assumptions and
dependencies that are assumed.

Page 1 of 15
Software Requirements Specification

Section 3 gives specific requirements which the software is expected to deliver. Various
Functional requirements are given. Some performance requirements and design constraints are also
given.

Section 4 gives some interface requirements.

Section 5 gives some non-functional requirements.

Section 6 gives other requirements like database and other legal requirements.

1.4 Project Scope

The purpose of this report is to gather useful context and to provide information concerning the
relationship between the members of the organization at all professional levels and their activities. .
The report also concerns about interactions of the members with in the organization around the
world in all scopes. We describe what features are in the scope of the software

• User authentication.
• Managing records of each user.
• Managing mails of users.
• Managing contact list of the users.
• Sending and receiving the emails over the Intranet
• Chit- chat etc.

1.5 References

• www.wikipedia.com
• www.dotnetspider.com
• Complete Reference of ASP.NET

2. Overall Description

2.1 Product Perspective

This application is basically an Intranet project, and would be useful for any small to medium sized
organization running the personal web server, and who want an e-mail system, but don't want the
associated costs. Mail system should be user-friendly, ‘quick to learn’ and reliable software for the
above purpose.
Mail system is intended to be a stand-alone product and should not depend on the availability of
other software. It should run on both UNIX and Windows based Platform.

Page 2 of 15
Software Requirements Specification

2.2 Product Features

Some of the major functions provided by the module for respective users are mentioned as follows:-
ADMINISTRATOR AUTHORITY:

• Can view the mails of all the staff members of the organization so that the official activities
can be performed through mails.

• All the basic features of the mail system are provided like sending and receiving the emails
etc

• Admin have got the power to create the new accounts of new user and delete the user
accounts of the persons who have left the organization.

STAFF FUNCTIONS:

• All the basic features of the mail system are provided like sending and receiving the emails
etc

• Staff members can maintain a contact list.

• Staff members can search the others users by their id, name, department.

2.3 User Classes and Characteristics

The user interface for this product is built with simple .net pages and coding is done in asp.net. The
screen will be constructed from with text , tables , radio buttons , forms , submit buttons ,text
boxes, pull-down menus and other familiar tools provided by the dot net framework . The users will
need a basic knowledge of the browser/operating system in order to work with this product. The
administrator must have in addition a basic knowledge of SQL Server in order to take backups of
the data used by the product.

2.4 Operating Environment

The product needs some third party products in order to function like a database (SQL Server) and
a web server which is accessible for the users who work with the product. There are no restrictions
on the kind of operating system or browser used. No special hardware is required for the end-user.

2.5 Design and Implementation Constraint

• Security: The files in which the information regarding securities and portfolios should be
secured against malicious deformations

Page 3 of 15
Software Requirements Specification

• Fault Tolerance: Data should not become corrupted in case of system crash or power
failure

2.6 Assumptions and Dependencies

• SQL SERVER must be installed on server

• Application must be implemented on sever with IIS 6 or more.

3. System Features

3.1 System Feature 1

As given above that the system provides functionalities for two kinds of users, the functional
requirements can be given as follows:-

3.1 Logging in
Description
A user must log in to the application to be identified.
Priority
Essential

Trigger
Opening Mail system homepage
Actors
All Users
Path

1. The user fills in the login-form.

2. The user confirms the login-form.

3. The application confirms the user and redirects him to the main page.

Exception
A user can be administrator or a staff member, during logging in it must be possible to
choose an identity.
When invalid login or password is supplied, the user gets informed to retrieve his password
or to contact the administrator.

Page 4 of 15
Software Requirements Specification

3.2 Logging out

Description
A user can log out after working with the application. This protects the user from abuse of
people who use the same computer after he was working on it.
Priority
Essential
Trigger
Log-out button present in every form
Precondition
Must always be possible after correct login
Actors
All Users
Path
1. The user selects 'Log out'.

2. The application notifies the user that he is logged out.

3. The application returns to the login-screen

3.3 Sending Mail

Description
A user can send mail to the members of the organization by clicking on compose mail and a
window will be opened, and he has to fill the required fields
Priority
Essential
Trigger
Compose mail link at the master page
Precondition
Must always be possible after correct login
Actors
All Users
Path

1. The user selects 'Compose Mail link'.

2. A compose mail window will be opened and the required fields must be filled like ‘TO:’.
Some files can also be attached with the mail

3. After clicking on send button, the mail is sent

Page 5 of 15
Software Requirements Specification

3.4 Retrieving Mail

Description
A user can retrieve mails sent by the members of the organization by clicking on Inbox link
a.
Priority
Essential
Trigger
Inbox link at the master page
Precondition
Must always be possible after correct login
Actors
All Users

Path

1. The user selects 'Inbox link'.

2. A list of all the mails which he has in his account will be shown.

3. After clicking on any particular mail, the mail will be opened and he can check that mail

4. Possibly, the attachments would be there with mail. So the person can also download by
clicking on download link.

5. A user can also see the attachments without downloading it by simply clicking on View
link.

3.5 Adding Members in the Contact List

Description
A user can search for another user on the basis of name, or user name and can add to his
contact list.
Priority
Essential
Trigger
Search link at the master page
Precondition
Must always be possible after correct login
Actors
Staff Members

Page 6 of 15
Software Requirements Specification

Path

1. The user selects 'Search link'.

2. A textbox will be opened and thereby enter the name or user name of the person ,who is to
be added on the list

3. Click the SEARCH button, if any name or user is found, the person is notified that the
search is successful.

4. After clicking on ADD button, the person will be added onto the contact list.

3.6 Checking Mails of Staff

Description
A user can check the mails of his staff
Priority
Essential
Trigger
Search link at the master page
Precondition
Must always be possible after correct login
Actors
Administrator

Path

1. The user selects 'Search link'.

2. A dropdown menu will be shown and thereby select the person, whose mails are to be
checked

3. Inbox, outbox will be shown of that particular person.

4. After clicking any of the two links, the list will be opened.

5. After clicking on any of the mail, he can read it out

3.7 Chit-Chat
Description
A user can chat with the staff members of the organization.

Page 7 of 15
Software Requirements Specification

Priority
Essential
Trigger
Search link at the master page
Precondition
Must always be possible after correct login
Actors
Staff members , Administrator

Path

6. The user selects ‘chat ‘ link on the master page.

7. A dropdown menu will be shown and thereby select the person, with whom he/she wants to
chat.

8. A pop up types window will be opened on the right side of the web page.

9. On the pop up window ,we can chat with the other staff members.

10. We can chat by simply writing our messages in the pop up window opened on the right
hand side of the web page.

Page 8 of 15
Software Requirements Specification

4. External Interface Requirements

4.1 User Interfaces

4.2 System interface:-

System interface are logically divided into Hardware interface & Software interface

4.2.1 Hardware Interfaces

Number Description Alternatives (If available)

1 PC with 10 GB hard-disk Not-Applicable
and 512 MB RAM

Page 9 of 15
Software Requirements Specification

4.2.2 Software Interfaces

Name
SQL Server 2005
Description
The product will need the database management system 'SQL SERVER' running in order to save
the information during the use of it. SQL SERVER is freely available. The user of the product
needs only to configure and use SQL SERVER when installing the product, thereafter this
configured SQL SERVER should only be running during the use of the program.

Name
Visual Studio 2005 /2008
Description
In computing, Microsoft Visual Studio is an integrated development environment (IDE) from Microsoft. It
can be used to develop console and graphical user interface applications along with Window
Forms applications, web sites, web applications, and web services in both native code together
with managed code for all platforms supported by Microsoft Windows, Windows Mobile, Windows CE,.NET
Framework.

5. Other Nonfunctional Requirements

5.1 Performance Requirements

5.1.1 Availability

Our system should be available at any time for authorized users.

5.1.2 Portability

Mail system will be designed with in mind to run this application on different platform. SQL
SERVER provides well defined interfaces which are independent of the platform it runs on. It
should be possible to have these running on another platform but it will not be tested.

5.1.3 Flexibility - Effort needed to modify operational program is less

5.1.4 Interoperability - Effort needed to couple one system with another will be less.

Page 10 of 15
Software Requirements Specification

5.2 Safety Requirements

All data should be saved in the database. It is important that the database is consistent at any time
and therefore a good database structure is of a great importance.

5.3 Security Requirements

• It is important that non authorized persons don't have access.

• The id of the user-id will be saved and can be used for further investigation

5.4 Software Quality Attributes

5.4.1 Maintainability

The program will heavily depend on the server(s) which holds the used web server and database. In
a good configured environment with a reliable web server and database, this should imply that no
special maintenance is needed to keep MAIL SERVER running.

5.4.2 Reliability

It is very important that the application is very reliable. In cause of system failure no information
relating to Inbox, Outbox, and Contacts etc. is lost and the user must be able to start again from
where the system went into failure. The application is also dependent of other programs. In case
failure our program must be able to recover after the external program is back operational.

Appendix A: Glossary
Administrator
A person who administrates the product, mostly in the role of Manager or the Chairman of
the Organization.

Staff members
A number of persons that are working an particular Organization who can send and receive
mails within that particular organization

Mails
A method of exchanging digital messages across the computer networks.

SRS:
Software Requirements Specification - specifies customer and detailed requirements

Page 11 of 15