Software Requirements Specifcation

Software Requirements
Specification
Intra Mailing System
Arpit Pathak
Nidhi Deshmukh
Rutuja Ghate
Sanket Gupta
M.I.T.S
Page 1 of 17
Software Requirements Specifcation
Table of Contents
Table of Contents...........................................................................................................................2
1. Introduction..............................................................................................................................3
1.1 Purpose....................................................................................................................................... 3
1.2 Document Conventions..............................................................................................................3
1.3 Intended Audience and Reading Suggestions.............................................................................3
2. Project Scope............................................................................................................................4
3. Overall Description..................................................................................................................5
3.1 Product Perspective....................................................................................................................5
3.2 Product Features......................................................................................................................... 6
3.3 User Classes and Characteristics................................................................................................6
3.4 Operating Environment..............................................................................................................6
3.5 Design and Implementation Constraints.....................................................................................6
3.6 Assumptions and Dependencies.................................................................................................7
4. System Designing.....................................................................................................................8
4.1 Authentication............................................................................................................................ 8
4.1.1 Description and priority.........................................................................................................8
4.1.2 Functional Requirements........................................................................................................8
5. External Interface Requirements...........................................................................................9
5.1 User Interfaces............................................................................................................................ 9
5.2 Hardware Interfaces...................................................................................................................9
5.3 Software Interfaces..................................................................................................................... 9
6. Other Nonfunctional Requirements.....................................................................................10
6.1 Performance Requirements.......................................................................................................10
6.2 Security Requirements..............................................................................................................11
6.3 Software Quality Attributes......................................................................................................11
7. Other Requirements..............................................................................................................11
Appendix A: Glossary..................................................................................................................11
Appendix B: Analysis Models.....................................................................................................12
Appendix C: Issues List...............................................................................................................13
M.I.T.S
Page 2 of 17
Software Requirements Specifcation
1. Introduction
1.1 Purpose
This document is intended for understanding the definition of requirements that are necessary for the
development of the intra mailing system.
This document act as basis for:
Common understanding between the two audiences regarding Specifications of the intra
mailing system project.
Needs to be satisfied in the architectural and detailed design of the intra mailing system
Project.
Needs to be satisfied in the verification validation and acceptance testing for the intra mailing
project.
1.2 Document Conventions
The format of this SRS is simple. bold face and indentation is used on general topics and specific
points of interest. The remainder of document will be written using the standard font, New Times
Roman.
1.3 Intended Audience and Reading Suggestions
This document is intended to be read by the developer team, project managers HCL group
Members, user SBIT.This is technical document and terms should be understood by the customer.
This SRS is designed for the persons present in this whole project so that they come to know about
project and what to change in the project in future if want, such as
Developers: As different modules of a project are developed by different members of a
team. So to have knowledge of other modules of the project SRS are designed. So that an
individual member of a team come to know about the whole modules of the project.
Project Managers: Members who are going to manage this project must know about the
project thats why this SRS is designed. So that the members can manage the project
according to its design.
M.I.T.S
Page 3 of 17
Software Requirements Specifcation
Marketing Staff: What the developed software/project can do, what was its need, how it
can be helpful to the users all this informations are provided to the marketing staff through
this SRS. Through that a good marketing can be provided to the project and its marketing
price will be good.
Users: Through this SRS the user come to know about the benefits of the project and how
to gain full performance from the project.
Testers: The different tests through which the software/project must undergo are described
in SRS.
Documentation writers: Different modules are designed by different members, so the
different logics are gathered together to develop a software/project. In that case entry of a
new member in the project will make him confused so through documentation one can
understand the logic behind that. So this document is intended for the documentation
writers also.
2. Project Scope
This document outlines the required functions that intra mailing system software is required to
perform. This document presents the detailed specification of each requirement and these
requirements are categori!ed by users and identified after careful analysis and requirements gathering
from the client. This document will not describe design decisions unless e"plicitly stated by the client.
This document will only describe what functionalities the system is required to provide.
3. Overall Description
This section gives overview of current systems available in the mar#et and the
product perspective of our intra mailing system when released into mar#et.
3.1 Product Perspective:
This product is aimed at employees students and every type of users. $henever there is limited
space allowed on mail server user can download mails on to hard dis# and they will be deleted from
the mail server which removes burden on %ail server. The project&s purpose is to classify the mails
into different clusters according to user&s criteria. 't the end of the project the system will have its
codes and functionalities reviewed its mail management system and user interface improved.
M.I.T.S
Page 4 of 17
Software Requirements Specifcation
Product Features
This system allows you to send (mail messages $or# )rder documents Credit Slips
*eceivable Statements and Purchase )rders + directly from within the software + to any
contact with an email address. )r you may simply type in an email address if one is not
recorded on a contact card.
The intra mailing system allows you to attach any number of computer files to an email
message just as you can with most other email programs.
The most common use of this in the software will be to email e"ported reports. ,The software
limits the total si!e of attached files to - %../
)ne can use the software0s unique Preview tool to see how your message will loo# when the
recipient opens it in his email program.
The software errors and support requests may be sent directly to Customer Support via
email.
The software allows all wor#stations in one business 1ocation to share one email account.
3.2 User Classes and Characteristics
This APPLICATION can be used by any user. There is no need of installation and one can use it on the basis
of WORLD WIDE WEB (WWW)..
3.3 Operating Environment
Hardware Platform: PROCESSOR: Intel Pentium IV
RAM: 256MB
HARDDISK: 40GB
LAN: Hi! S"ee# u" t$ %0 m&"'
.
Software Components: PLA()ORM : *in#$+'
(HE OPERA(ING S,S(EM : *in#$+' -P P.$/e''i$n0l
)RAME*ORK : ).0me+$.1 235
)RON(4END (OOL : 5AVA NE( BEANS
BACK4END (OOL : S6L SERVER
Design and Implementation Constraints
The items or options that will limit the options available to the developers are as follows:
M.I.T.S
Page 5 of 17
Software Requirements Specifcation
This software product supports user level security to access mails. There are two levels of
'uthentication used in 2NT*' %'212N3 S4ST(% software.
't the first level of authentication user has to give his5her login and password so that he5she
will be able to access his5her set of mails on the hard dis# as it provides services to multiple
users.
't the second level of authentication user has to give authentication details about the mail
account5accounts so that intra mailing system software access and downloads the mails from
the server using these authentication to#ens.
This second level of authentication needs to be given for the first time whenever user has
logged in as a new user or when ever new mail account is created on different %ail servers.
$here as first level of authentication needs to be given every time user uses 2NT*'
%'212N3 S4ST(% product as it provides services to multiple users at the same time.
Design constraints on some of the files of the application are:
Algorithm constraint
The number of parameters used in the algorithm for classification is fi"ed. 'fter clear
understanding of mail system Neptune&s have come up with four such parameters. Namely
'. Subject
.. From
C. To
6. Cc.
3.4 Assumptions and Dependencies
This project assumes that all the users have at least one valid email account.
This project assumes that the 7sers will enter valid authentication details to access mails.
This project assumes that the system is connected to networ#.
4. System Designing
The designing of the project is done with the text based graphics which causes creation of
curses windows. User simply use mouse to control the basic functioning of project up to his/her
convenience.
M.I.T.S
Page 6 of 17
Software Requirements Specifcation
4.1 Authentication
4.1.1 Description and priority
This feature will give the user a secure and simple login making use of USER and PASS
commands. This will ensure whether the intend user can perform the task of file transfer or not.
4.1.2 Functional Requirements
The database must be in a workable state.
There should be secure password provided to each user or client
It should be easy for the no-vice user.
There should be proper interconnectivity between the files to allow communication.
Different commands for different functions will ensure reliability.
The most important thing is that the username for the administrator is fixed and the password
could be changed in future and must b of at least 6 character.
5. External Interface Requirements
5.1 User Interfaces
The intra mailing system has a simple 7ser 2nterface which has the following components :+
1. User sign-in panel
8or the user to login to access his5her set of mails on the hard dis# as the intra mailing system
provides services to multiple users.
2. New user Sign-up panel
To add a new user to the system.
3. Main panel
The main panel provides access point to the following services
Classifying the inbo" mails
*eply the received mails
8orward the received mails.
6elete the mails.
M.I.T.S
Page 7 of 17
Software Requirements Specifcation
To read Ne"t mail.
To read the Previous mail.
4. Composing mail panel.
Composing mail panel helps user to compose mails and send the mails .
5.2 Hardware Interfaces
In the hardware interface there is description of mouse implementation and keypad
implementation:
Mouse Implementation: When the user selects the SIGN_UP or SIGN_IN selection he/she has to
perform all the selection through the mouse. In this the concept of mouse is introduced.
Keypad Implementation: When the user selects the any of the option he/she has to perform all
the operation through pressing key described in it present on the keyboard.
These are the hardware interfaces which the user must know while performing the request.
5.3 Software Interfaces
Database: In this the record is stored in Mysql database. There are basically 1database and
that one database is containing the record of all users..
Operating System: This project will work on WINDOWS XP/7/VISTA.
Header Files Used: The header files used are described below:
All these are included in the software interface.
import java.sql.*; //FOR DATABASE
import java.sql.Connection;
import java.sql.ResultSet;
import java.sql.Statement;
import java.sql.PreparedStatement;
6. Other Nonfunctional Requirements
M.I.T.S
Page 8 of 17
Software Requirements Specifcation
6.1 Performance Requirements
The intra mailing system should be able to support multiple users at a time.
6.2 Security Requirements
The intra mailing system does not allow users to view other user&s details for privacy and
security reason.
6.3 Software Quality Attributes
This application can be used in all sectors where the file transfer is an important task to be
performed.some of its quality attribute includes:-
9. Checing:+ 'uthentication Chec#ing: $ith this chec#ing the system will not allow
7nauthori!ed user to perform functionalities that he5she does not allowed to do.
:. !orta"ility: + The intra mailing system must be portable between %icrosoft $indows and
1inu". .oth intranet and internet version of the intra mailing system should be portable.
;. Maintaina"ility:+ The intra mailing system should be modular. Specifically file contents
should be easy to maintain as the contents of the database change often.
<. !er#ormance:+ The intra mailing system should be able to support multiple users at a time.
7. Other Requirements
The other requirement related to this SRS is not needed. The different appendixes are given. In case of
more knowledge related to this SRS one can concern with these Appendixes.
Appendix A: Glossary
The definition of the words that are frequently used in this SRS is as follows:
Client one who uses the project
Database- In which data is stored
DFD- Data Flow Diagram
M.I.T.S
Page 9 of 17
Software Requirements Specifcation
Mysql- A basic database already present in many s/w.
Hardware- That can be touch
Interface- through which client send request
Server- that serves request
Software- That can be seen not touch
Appendix B: Analysis Models
a$ Use Case I% & 1
Use Case Name & 6ownload emails
1. %'SC(I!)I*N
This use case describes the process of downloading the emails from the server.
2. AC)*(S
2.1 !rimary Actor - 7ser.
2.2 Secon+ary Actors - 7ser&s mail server.
3. US' CAS' %IA,(AM
M.I.T.S
Page 10 of 17
Software Requirements Specifcation
4. S)'!S
4.1 7ser provides username and password to download mails from server.
4.2 2f username or password wrong system reports error.
4.3 7ser gives Chec# %ail command
4.4 System copies %ails from server to user&s hard dis#.
4.- System deletes mails from server.
"$ Use Case I% & 2
Use Case Name & Sending emails
1. %'SC(I!)I*N
This use case describes the process of sending emails.
2. AC)*(S
2.1 !rimary Actors - 7ser.
2.2 Secon+ary Actors - *ecipient&s mail server.
3. US' CAS' %IA,(AM
M.I.T.S
Page 11 of 17
Software Requirements Specifcation
4. S)'!S
4.1 2f user gives Compose mail command.
4.1.1 7ser gives compose command
4.1.2 Types subject.
4.1.3 Types contents.
4.1.4 Specifies recipients.
4.1.- 3ives send command.
4.1.. 2f ,*ecipient&s %ail Server receives mail successfully/
mail sent else report problem
4.2 2f user gives reply command
4.2.1 (dits subject.
4.2.2 (dits contents.
4.2.3 'dds recipients.
4.2.4 3ive send command.
4.2.- 2f ,*ecipient&s %ail Server receives mail successfully /
mail sent
else report problem
4.3 2f user gives forward command
4.3.1 (dits subject.
4.3.2 (dits contents.
4.3.3 Specifies recipients.
4.3.4 3ive send command.
4.3.- 2f,*ecipient&s %ail Server receives mail successfully /
mail sent
else report problem
c$ Use Case I% & 3
Use Case Name & 'ttachments
M.I.T.S
Page 12 of 17
Software Requirements Specifcation
1. %'SC(I!)I*N
This use case describes the process of sending and receiving the attachments from an
email.
2. AC)*(S
a. !rimary Actors - 7ser.
". Secon+ary Actors - N'.
3. US' CAS' %IA,(AM
4. S)'!S
4.1. Sending 'ttachments.
4.1.1 System must allow user to search the file to attach.
4.1.2 2ntra mailing system should display the list of files on user&s machine.
4.1.3 System must allow user select the file to attach.
4.1.4 'ttached file also sent with the mail.
4.2 6ownloading 'ttachments.
4.2.1 System must allow user to download attachment to his machine.
4.2.2 2ntra mailing system must allow user to save attachment to desired path in his machine.
+$ Use Case I% & 4
Use Case Name& %ail Classification System
M.I.T.S
Page 13 of 17
Software Requirements Specifcation
1. %'SC(I!)I*N&
Classify emails based on similarities. Store similar mails in a separate folder. %ails not belonging to
any group are left in common folder inbo".
2. AC)*(S&
a. !rimary Actor& 7ser
". Secon+ary Actor& N'
3. US' CAS' %IA,(AM&
4. S)'!S&
9. 7ser gives classify command
:. Classification algorithm applied to all mails.
;. 3roups suggested to users.
<. Similar mails moved to a common folder.
-. %ails not falling in any group left in common folder called inbo".
e$ Use Case I% & -
Use Case Name & Sign 2n
1. %'SC(I!)I*N
This use case describes how a registered user can sign in to the system.
2. AC)*(S
2.1 !rimary Actors - 7ser.
2.2 Secon+ary Actors - N5'
3. US' CAS' %IA,(AM
M.I.T.S
Page 14 of 17
Software Requirements Specifcation
4. S)'!S
4.1 System must as# username and password of a user.
4.2 System must verify the right combination of username and password.
4.3 System should report Sign+2n problem if verification fails.
4.4 )n successful Sign+2n system should allow user access to his 5 her mails.

#$ Use Case I% & .
Use Case Name & Sign 7p
1. %'SC(I!)I*N
This use case describes the how an unregistered user can sign up to the system.
2. AC)*(S
2.1. !rimary Actors - 7ser.
2.2. Secon+ary Actors - N5'

3. US' CAS' %IA,(AM
4. S)'!S
M.I.T.S
Page 15 of 17
Software Requirements Specifcation
4.1 The system must as# the username and password ,in duplicate/ from a new user.
4.2 The system must save the combination of username and password of the new user.
4.3 System should Sign+2n the new user.
g$ Use Case I% & /
Use Case Name & 6isplay (mails
1. %'SC(I!)I*N
This use case describes the process of displaying the mails of an user when he signs in .
2. AC)*(S
2.1. !rimary Actors - 7ser.
2.2. Secon+ary Actors-N5'
3. US' CAS' %IA,(AM
4. S)'!S
4.1 System must display the mails of a particular folder selected by the user.
h$ Use Case I% & 0
Use Case Name & Store (mails
1. %'SC(I!)I*N
This use case describes the process of storing the mails of user in a directory specific
to the user.
2. AC)*(S
2.1 !rimary Actors - 7ser.
2.2. Secon+ary Actors - *ecipient&s mail server.
M.I.T.S
Page 16 of 17
Software Requirements Specifcation
3. US' CAS' %IA,(AM
4. S)'!S
4.1 System must store the mails of each user separately .
4.2 System must store mails part of a group in the folder corresponding to the group.
Appendix C: Issues List
The issue on which the work is remaining is as follows:
Security concept
Add the keypad functioning also in the user interface
Performance should be increased.
These three are main and there are some more concepts on which work is pending not described
here.
M.I.T.S
Page 17 of 17