Software Requirements

Specification
For

E-Tutorial for Engineering

Students of IPU

Version 1.0

M-tech (CSE)

USIT, GGSIPU, Delhi-110006

 Software Requirements Specification for <Project>

Table of Contents
1 Introduction.................................................................................................................................1
1.1 Purpose ............................................................................................................................................... 1
Almost every activity in the world today is controlled by online systems.............................................. 1
1.2 Document Conventions....................................................................................................................... 1
1.3 Intended Audience and Reading Suggestions..................................................................................... 2
1.4 Project Scope....................................................................................................................................... 2
1.5 References .......................................................................................................................................... 2
Appendix for the E-Tutorial for Engineering Students of IPU................................................ 2
Software Engineering book by “K.K. Aggarwal”......................................................................2
Internet and many online e- book on online tutorial................................................................. 2
2.0 Overall Description..................................................................................................................2
2.1 Project Perspective.............................................................................................................................. 3
2.2 User Characteristics............................................................................................................................ 3
2.3 Operating Environment....................................................................................................................... 3
2.4 Design and Implementation Constraints............................................................................................. 3
2.5 User Documentation........................................................................................................................... 4
2.6 Assumptions and Dependencies......................................................................................................... 4
3.0 System Features....................................................................................................................... 4
3.1 System Feature 1................................................................................................................................ 4
3.2 System Feature 2 (and so on)............................................................................................................. 5
4 External Interface Requirements.............................................................................................. 5
4.1 User Interfaces.................................................................................................................................... 5
4.2Hardware Interfaces............................................................................................................................ 5
4.3 Software Interfaces............................................................................................................................ 5
4.5 Communications Interfaces................................................................................................................ 6
5 Other Nonfunctional Requirements..........................................................................................6
5.1 Performance Requirements................................................................................................................ 6
5.2 Safety Requirements.......................................................................................................................... 6
5.3 Security Requirements....................................................................................................................... 6
5.4 Software Quality Attributes............................................................................................................... 6

Revision History
Name Date Reason For Changes Version
Software Requirements Specification for <E-Tutorial for Engineering Students of IPU>

1 Introduction
The following subsections of the Software Requirements Specifications (SRS) document provide an
overview of the entire SRS.
The Software Requirements Specification (SRS) will provide a detailed description
of the requirements for the E-Tutorial for Engineering Students of IPU .This SRS will allow for a
complete understanding of what is to be expected of the Website to be constructed. The clear
understanding of this website and its’ functionality will allow for the Learning, Downloading study
material, Expertise of subject, students Queries, class videos etc. for the end user. This SRS will
provide the foundation for the project. From this SRS, the E-Tutorial for Engineering Students of
IPU can be designed, constructed, and finally tested.

This SRS will be used by the software engineers constructing the E-Tutorial for Engineering
Website and the University end users. The software engineers will use the SRS to fully understand
the expectations of this Website to construct the appropriate system. The University end users will
be able to use this SRS as a “test” to see if the software engineers will be constructing the system to
their expectations. If it is not to their expectations the end users can specify how it is not to their
liking and the software engineers will change the SRS to fit the end users needs.

1.1 Purpose

Almost every activity in the world today is controlled by online systems.

According to the above facts, managing and maintaining a Tutorials and Study material could
also be controlled by efficient websites. This project focuses attention on designing
efficient and reliable website which provides study materials and resolve problems of students
related with their subjects.
In real world, it tends to associate with website as they provide many
benefits than doing the same thing in searching the specific material for the subjects. As above
mentioned, here we have introduced a website which can be used to maintain notes,
presentations, E-books, Expertise, video etc...In briefly, the manual searching process is very
slow. But automation will reduce the time taken in the whole process.

1.2 Document Conventions

Font-Times New Roman

Font Size-12
High level Priorities- Bold and underlined text
 Software Requirements Specification for <E-Tutorial for Engineering Students of IPU>

1.3 Intended Audience and Reading Suggestions

University Lectures, University Proffesors, University Students, Developers, Testers.

1.4 Project Scope

The name of the project is E-Tutorial for Engineering Students of IPU

The software provides both the Students and the Professors an Account which is
Unique.
The software provides the following facilities to the Students:
 Facilitates with online notes, presentations, E-books, Expertise, video etc.any where and

with no
Cost.
 Provides information about Engineering subjects and Syllabus.
 Can avail the facility of providing tutors who are the senior students of university or
expertise of the specific
Subject.
 Students are provided with up to date information on the stuff related to all the subjects
of engineering.

 Provides email facility for future correspondence

 Facilitates easy searching of intended data online any where with free of cost.

 Can avail the facility of purchasing and selling second hand books.

1.5 References

• Appendix for the E-Tutorial for Engineering Students of IPU.

• Software Engineering book by “K.K. Aggarwal”.

• http://www.scribd.com/doc/23362865/Srs-of-E-Book-Shopping .

• Internet and many online e- book on online tutorial.

2.0 Overall Description

The following subsections provide the complete overview of the specifications
Software Requirements Specification for <E-Tutorial for Engineering Students of IPU>

Requirements documentation for the E-Tutorial for Engineering Students of IPU.

In this module we define the overall description of the -Tutorial for Engineering Students of IPU.
Like the importance of the website, what are the student and professor characteristics, what are the
general constraints and assumptions and dependencies?

2.1 Project Perspective

This project is a web-based application which can connect the people of the University.
This website is totally self contained and works relatively as efficient as other
websites related to the subjects. It provides simple database rather than complex ones
for high requirements and it provides good and easy graphical user interface to both
new, naive as well as experienced users of the computers.

2.2 User Characteristics

 No pre knowledge of html

 No pre knowledge of database management

 Should be familiar with internet

 Should know English

 Should be able to use and do according to the graphical user interface

 The user should have a basic computer literacy to work

with computer.
 The user of this software should be well trained and should given the relevant
user documentation, reference material and instruction.
 The user should be able to follow simple instruction given by the system.

2.3 Operating Environment

Internet connection, web browser, minimum RAM capacity 128MB, minimum screen resolution
600×800.

2.4 Design and Implementation Constraints

The Website is designed in such a way that it would be:

• User-friendly
• Interactive
• Easy Maintainable
Software Requirements Specification for <E-Tutorial for Engineering Students of IPU>

• Easy to Handle etc.

My project is following everything listed above in the designed constraint.

2.5 User Documentation

We are providing site map in the web site, it will help the students and teachers while accessing the
web application.

2.6 Assumptions and Dependencies

The web site assumes that the users …………………………………………………….

Cannot support multiple user interfaces.

2.7 General Constraints

 The browser should support java.

 The browser should be at least Netscape navigator v 4.0 or internet explorer.

 Data encoding scheme: ASCII character.

 Total available memory for programming, logic, tables etc as specified in this
document should not be exceeded.

3.0 System Features

<This template illustrates organizing the functional requirements for the product by system
features, the major services provided by the product. You may prefer to organize this section by
use case, mode of operation, user class, object class, functional hierarchy, or combinations of
these, whatever makes the most logical sense for your product.>

3.1 System Feature 1

<Don’t really say “System Feature 1.” State the feature name in just a few words.>
3.1.1 Description and Priority
<Provide a short description of the feature and indicate whether it is of High,
Medium, or Low priority. You could also include specific priority component ratings,
such as benefit, penalty, cost, and risk (each rated on a relative scale from a low of
1 to a high of 9).>
3.1.2 Stimulus/Response Sequences
Software Requirements Specification for <E-Tutorial for Engineering Students of IPU>

<List the sequences of user actions and system responses that stimulate the
behavior defined for this feature. These will correspond to the dialog elements
associated with use cases.>
3.1.3 Functional Requirements
<Itemize the detailed functional requirements associated with this feature. These
are the software capabilities that must be present in order for the user to carry out
the services provided by the feature, or to execute the use case. Include how the
product should respond to anticipated error conditions or invalid inputs.
Requirements should be concise, complete, unambiguous, verifiable, and
necessary. Use “TBD” as a placeholder to indicate when necessary information is
not yet available.>

<Each requirement should be uniquely identified with a sequence number or a

meaningful tag of some kind.>

REQ-1:
REQ-2:

3.2 System Feature 2 (and so on)

4 External Interface Requirements

4.1User Interfaces

The website provides good graphical interface for the front end of the database and a
good informative interface for the rear end.

4.2Hardware Interfaces

The system should have these hardware requirements:

• The processor should be at least Pentium 3 or above
• The processor speed should be greater than 400Mhz
• The video device should support graphics
• Ram should be or greater than 128 MB.

4.3 Software Interfaces

The software requires the support of the following softwares for the database and other
requirements
• C#,ASP.NET and html editor for web interface
• SQL 2005 for database
• Server (windows 2000,apache or…)
Software Requirements Specification for <E-Tutorial for Engineering Students of IPU>

4.5 Communications Interfaces

Local intranet and internet protocols.

Supports all HTTPS, SMTPS and POP3 services

5 Other Nonfunctional Requirements

5.1 Performance Requirements

Performance requirements are:

• good working pc with all the requirements as stated in the hardware interfaces
• works for medium size information databases
• should not be overloaded

5.2 Safety Requirements

All the data stored in the database should be handled by the person which are the part of the
organization and have the knowledge about the database, and these operators should have
authenticated ID’s.

5.3 Security Requirements

<Specify any requirements regarding security or privacy issues surrounding use of the product or
protection of the data used or created by the product. Define any user identity authentication
requirements. Refer to any external policies or regulations containing security issues that affect
the product. Define any security or privacy certifications that must be satisfied.>

5.4 Software Quality Attributes

All private data like passwords must be stored in encrypted form.

6 Other requirements:-

 Future aspects of the projects

 Changes in upcoming technologies

 Requirements needed in the expansion of the system

Software Requirements Specification for <E-Tutorial for Engineering Students of IPU>

Appendix A: Glossary
<Define all the terms necessary to properly interpret the SRS, including acronyms and
abbreviations. You may wish to build a separate glossary that spans multiple projects or the
entire organization, and just include terms specific to a single project in each SRS.>

Appendix B: Analysis Models

<Optionally, include any pertinent analysis models, such as data flow diagrams, class diagrams,
state-transition diagrams, or entity-relationship diagrams.>

Appendix C: Issues List

< This is a dynamic list of the open requirements issues that remain to be resolved, including
TBDs, pending decisions, information that is needed, conflicts awaiting resolution, and the like.>