SRS of G7

8/8/2019 SRS of G7

1/14

Software Requirements Specification

Software RequirementsSpecificationSMS 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

8/8/2019 SRS of G7

2/14


Table of Contents

1. Introduction................................................................................................................................11.1 Purpose ............................................................................................................................................... 11.2 Document Conventions....................................................................................................................... 11.3 Intended Audience and Reading Suggestions..................................................................................... 11.4 Project Scope....................................................................................................................................... 21.5 References........................................................................................................................................... 2

2. Overall Description....................................................................................................................22.1 Product Perspective............................................................................................................................. 22.2 Product Features.................................................................................................................................. 32.3 User Classes and Characteristics........................................................................................................ 32.4 Operating Environment....................................................................................................................... 32.5 Design and Implementation Constraint.............................................................................................. 32.6 Assumptions and Dependencies......................................................................................................... 4

3. System Features......................................................................................................................... 43.1 System Feature 1................................................................................................................................. 43.2 Logging out........................................................................................................................................ 53.3 Sending Mail....................................................................................................................................... 53.4 Retrieving Mail................................................................................................................................... 63.5 Adding Members in the Contact List.................................................................................................. 63.6 Checking Mails of Staff...................................................................................................................... 73.7 Chit-Chat............................................................................................................................................. 7

4. External Interface Requirements............................................................................................. 94.1 User Interfaces.................................................................................................................................... 9.................................................................................................................................................................. 94.2.1 Hardware Interfaces........................................................................................................................ 9

5. Other Nonfunctional Requirements.......................................................................................10

5.1 Performance Requirements............................................................................................................... 105.1.1 Availability................................................................................................................................. 105.1.2 Portability................................................................................................................................... 10Mail system will be designed with in mind to run this application on different platform. SQLSERVER provides well defined interfaces which are independent of the platform it runs on. Itshould be possible to have these running on another platform but it will not be tested.....................105.1.3 Flexibility - Effort needed to modify operational program is less............................................. 105.1.4 Interoperability - Effort needed to couple one system with another will be less...................... 10

5.2 Safety Requirements......................................................................................................................... 115.3 Security Requirements...................................................................................................................... 115.4 Software Quality Attributes.............................................................................................................. 11

5.4.1 Maintainability........................................................................................................................... 115.4.2 Reliability................................................................................................................................... 11

Page ii of 15

8/8/2019 SRS of G7

3/14


Revision History

Name Date Reason For Changes Version

SMS Based PushMail System

Sep3,2010

Initial Version 2.0

Page iii of 15

8/8/2019 SRS of G7

4/14


1. Introduction

1.1 Purpose

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

This application was developed for an intranet project, and would be useful for any small tomedium sized organization who use a Windows NT Server, Windows XP, Windows 7, WindowsVista etc, or even just a Networked Windows 95 solution running the personal web server, and whowant an e-mail system, but don't want the associated costs. This system could also be used for acommunity 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 thedevelopment 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 softwarerequirements 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 expectedof the user, some general constraints while making the software and some assumptions anddependencies that are assumed.

Page 1 of 15

8/8/2019 SRS of G7

5/14


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

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 therelationship 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 sizedorganization running the personal web server, and who want an e-mail system, but don't want theassociated costs. Mail system should be user-friendly, quick to learn and reliable software for theabove purpose.Mail system is intended to be a stand-alone product and should not depend on the availability ofother software. It should run on both UNIX and Windows based Platform.

Page 2 of 15
http://www.wikipedia.com/http://www.dotnetspider.com/http://www.wikipedia.com/http://www.dotnetspider.com/

8/8/2019 SRS of G7

6/14


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 activitiescan be performed through mails.

All the basic features of the mail system are provided like sending and receiving the emailsetc

Admin have got the power to create the new accounts of new user and delete the useraccounts 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 emailsetc

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. Thescreen will be constructed from with text , tables , radio buttons , forms , submit buttons ,textboxes, pull-down menus and other familiar tools provided by the dot net framework . The users willneed a basic knowledge of the browser/operating system in order to work with this product. Theadministrator must have in addition a basic knowledge of SQL Server in order to take backups ofthe 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 restrictionson 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 besecured against malicious deformations

Page 3 of 15

8/8/2019 SRS of G7

7/14


Fault Tolerance: Data should not become corrupted in case of system crash or powerfailure

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 functionalrequirements can be given as follows:-

3.1 Logging in

DescriptionA user must log in to the application to be identified.

PriorityEssential

TriggerOpening Mail system homepage

ActorsAll 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.

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

Page 4 of 15

8/8/2019 SRS of G7

8/14


.

3.2 Logging out

Description

A user can log out after working with the application. This protects the user from abuse ofpeople who use the same computer after he was working on it.

PriorityEssential

TriggerLog-out button present in every form

PreconditionMust always be possible after correct login

ActorsAll 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

DescriptionA user can send mail to the members of the organization by clicking on compose mail and awindow will be opened, and he has to fill the required fields

PriorityEssential

TriggerCompose mail link at the master page


ActorsAll 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

8/8/2019 SRS of G7

9/14


3.4 Retrieving Mail

DescriptionA user can retrieve mails sent by the members of the organization by clicking on Inbox linka.

PriorityEssentialTrigger

Inbox link at the master pagePrecondition

Must always be possible after correct loginActors

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 byclicking on download link.

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

3.5 Adding Members in the Contact List

DescriptionA user can search for another user on the basis of name, or user name and can add to hiscontact list.

PriorityEssential

TriggerSearch link at the master pagePrecondition

Must always be possible after correct loginActors

Staff Members

Page 6 of 15

8/8/2019 SRS of G7

10/14


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

DescriptionA user can check the mails of his staff

PriorityEssential

TriggerSearch link at the master page


ActorsAdministrator

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

DescriptionA user can chat with the staff members of the organization.

Page 7 of 15

8/8/2019 SRS of G7

11/14


PriorityEssential

TriggerSearch link at the master page


ActorsStaff 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 tochat.

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 righthand side of the web page.

Page 8 of 15

8/8/2019 SRS of G7

12/14


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-diskand 512 MB RAM

Not-Applicable

Page 9 of 15

8/8/2019 SRS of G7

13/14


4.2.2 Software Interfaces

NameSQL Server 2005

Description

The product will need the database management system 'SQL SERVER' running in order to savethe information during the use of it. SQL SERVER is freely available. The user of the productneeds only to configure and use SQL SERVER when installing the product, thereafter thisconfigured SQL SERVER should only be running during the use of the program.

NameVisual Studio 2005 /2008

DescriptionIn computing, Microsoft Visual Studio is an integrated development environment (IDE) from Microsoft. Itcan be used to develop console and graphical user interface applications along with WindowForms 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,.NETFramework.

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. SQLSERVER provides well defined interfaces which are independent of the platform it runs on. Itshould 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 less5.1.4 Interoperability - Effort needed to couple one system with another will be less.

Page 10 of 15

8/8/2019 SRS of G7

14/14

Documents

SRS of G7