Professional Documents
Culture Documents
Arpit Pathak
Nidhi Desh
Rutuja Ghate
Sanket Gupta
M.I.T.S
Page 2 of 19
Software Requirements Specification
Page 1 of 17
M.I.T.S
Page 3 of 19
Software Requirements Specification
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
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:
M.I.T.S
Page 4 of 19
Software Requirements Specification
• 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.
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.
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
Project Managers: Members who are going to manage this project must know about the
project that’s why this SRS is designed. So that the members can manage the project
according to its design.
Marketing Staff: What the developed software/project can do, what was its need, how it
can be helpful to the users all this information’s 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.
M.I.T.S
Page 5 of 19
Software Requirements Specification
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 categorized by users and identified after careful analysis and requirements
gathering from the client. This document will not describe design decisions unless explicitly 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 market and the
product perspective of our intra mailing system when released into market.
3.1 Product Perspective:
This product is aimed at employees, students and every type of users. Whenever there is limited
space allowed on mail server, user can download mails on to hard disk and they will be deleted
from the mail server, which removes burden on Mail server. The project’s purpose is to classify the
mails into different clusters according to user’s criteria. At the end of the project, the system will
have its codes and functionalities reviewed, its mail management system and user interface
improved.
Product Features
• This system allows you to send Email messages, Work Order documents, Credit Slips,
Receivable Statements, and Purchase Orders - directly from within the software - to any
contact with an email address. Or 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 exported reports. (The
software limits the total size of attached files to 5 MB.)
• One can use the software's unique Preview tool to see how your message will look when the
recipient opens it in his email program.
M.I.T.S
Page 6 of 19
Software Requirements Specification
• The software errors and support requests may be sent directly to Customer Support via
email.
• The software allows all workstations in one business Location to share one email account.
.
Software Components: PLATFORM : Windows
THE OPERATING SYSTEM : Windows XP Professional
The items or options that will limit the options available to the developers are as follows:
• This software product supports user level security to access mails. There are two levels of
Authentication used in INTRA MAILING SYSTEM software.
• At the first level of authentication user has to give his/her login and password so that he/she
will be able to access his/her set of mails on the hard disk, as it provides services to multiple
users.
• At the second level of authentication, user has to give authentication details about the mail
account/accounts so that intra mailing system software access and downloads the mails from
the server using these authentication tokens.
• 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 Mail servers.
Where as first level of authentication needs to be given every time user uses INTRA
MAILING SYSTEM product, as it provides services to multiple users at the same time.
M.I.T.S
Page 7 of 19
Software Requirements Specification
Design constraints on some of the files of the application are:
Algorithm constraint
• The number of parameters used in the algorithm for classification is fixed. After clear
understanding of mail system, Neptune’s have come up with four such parameters. Namely
A. Subject
B. From
C. To D. Cc.
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.
4.1 Authentication
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.
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.
M.I.T.S
Page 8 of 19
Software Requirements Specification
3. Main panel
The main panel provides access point to the following services
• Classifying the inbox mails Reply the received mails
• Forward the received mails.
• Delete the mails.
• To read Next mail.
• To read the Previous mail.
• 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.
M.I.T.S
Page 9 of 19
Software Requirements Specification
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..
• Header Files Used: The header files used are described below:
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.
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:
1. Checking:- Authentication Checking: With this checking, the system will not allow
Unauthorized user to perform functionalities that he/she does not allowed to do.
2. Portability: - The intra mailing system must be portable between Microsoft Windows and
Linux. Both intranet and internet version of the intra mailing system should be portable.
3. Maintainability:- The intra mailing system should be modular. Specifically, file contents
should be easy to maintain as the contents of the database change often.
4. Performance:- The intra mailing system should be able to support multiple users at a time.
M.I.T.S
Page 10 of 19
Software Requirements Specification
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
M.I.T.S
Page 11 of 19
Software Requirements Specification
1. DESCRIPTION
This use case describes the process of downloading the emails from the server.
2. ACTORS
2.1 Primary Actor - User.
2.2 Secondary Actors - User’s mail server.
M.I.T.S
Page 12 of 19
Software Requirements Specification
4. STEPS
4.1 User provides username and password to download mails from server.
4.2 If username or password wrong system reports error.
4.3 User gives Check Mail command
4.4 System copies Mails from server to user’s hard disk.
4.5 System deletes mails from server.
1. DESCRIPTION
This use case describes the process of sending emails.
2. ACTORS
2.1 Primary Actors - User.
2.2 Secondary Actors - Recipient’s
mail server.
4. STEPS
M.I.T.S
Page 13 of 19
Software Requirements Specification
4.1.6 If (Recipient’s Mail Server receives mail successfully) mail sent else
report problem
2. ACTORS
a. Primary Actors - User.
b. Secondary Actors - NA.
M.I.T.S
Page 14 of 19
Software Requirements Specification
4. STEPS
2. ACTORS:
a. Primary Actor: User
b. Secondary Actor: NA
M.I.T.S
Page 15 of 19
Software Requirements Specification
4. STEPS:
1. DESCRIPTION
This use case describes how a registered user can sign in to the system.
2. ACTORS
2.1 Primary Actors - User.
2.2 Secondary Actors - N/A
4. STEPS
M.I.T.S
Page 16 of 19
Software Requirements Specification
1. DESCRIPTION
This use case describes the how an unregistered user can sign up to the system.
2. ACTORS
2.1. Primary Actors - User.
2.2. Secondary Actors - N/A
4. STEPS
4.1. The system must ask 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-In the new user.
1. DESCRIPTION
This use case describes the process of displaying the mails of an user when he signs in .
M.I.T.S
Page 17 of 19
Software Requirements Specification
2. ACTORS
2.1. Primary Actors - User.
2.2. Secondary Actors-N/A
4. STEPS
4.1. System must display the mails of a particular folder selected by the user.
1. DESCRIPTION
This use case describes the process of storing the mails of user in a directory
specific to the user.
2. ACTORS
2.1 Primary Actors - User.
2.2 Secondary Actors - Recipient’s mail server.
3. USE CASE DIAGRAM
4. STEPS
M.I.T.S
Page 18 of 19
Software Requirements Specification
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 19 of 19