Software Requirements

Specification
For

Online Project Tracking

Portal
Version 1.0 approved

Prepared by:
Amol Samel (14030141072)
Harish Kumar (14030141058)
Kartik Sharma (14030141085)

SICSR,Pune

10/12/2014

Permissionisgrantedtouse,modify,anddistributethisdocument.

SoftwareRequirementsSpecificationforOnlineProjectTrackingPortal
Pageii

Table of Contents
Contents
1. Introduction.......................................................................................................................1
1.1
1.2
1.3
1.4
1.5

Purpose....................................................................................................................................1
Document Conventions......................................................................................................1
Intended Audience and Reading Suggestions............................................................1
Project Scope.........................................................................................................................1
References..............................................................................................................................1

2. Overall Description........................................................................................................2
2.1
2.2
2.3
2.4
2.5
2.6
2.7

Project Perspective..............................................................................................................2
Project Features....................................................................................................................2
User Classes and Characteristics...................................................................................2
Operating Environment......................................................................................................2
Design and Implementation Constraints.....................................................................2
User Documentation...........................................................................................................2
Assumptions and Dependencies.....................................................................................3

3. External Interface Requirements..........................................................................3

3.1
3.2
3.3
3.4

User Interfaces:....................................................................................................................3
Hardware Interfaces............................................................................................................3
Software Interfaces.............................................................................................................3
Communications Interfaces..............................................................................................3

4. System Features..............................................................................................................3
4.1
4.2

System Feature 1.................................................................................................................3

System Feature 2:................................................................................................................4

5.1
5.2
5.3
5.4

Performance Requirements..............................................................................................5
Safety Requirements:.........................................................................................................5
Security Requirements.......................................................................................................5
Software Quality Attributes..............................................................................................5

5. NonfunctionalRequirements..................................................................................................5

6. OtherRequirements................................................................................................................5

Revision History
Name

Date

Reason For Changes

Version

SoftwareRequirementsSpecificationforOnlineProjectTrackingPortal
Page1

1. Introduction
1.1 Purpose
Online Project Tracking Portal will help to track all the past and ongoing
projects of a university or an institution. The main purpose of this portal is to
help students and faculties to be aware of all the ongoing and past projects
throughout the organization.

1.2 Document Conventions

The format of this SRS is simple. Bold face and indentation is used on general
topics and or specific points of interest. The remainder of the document will
be written using the standard font, Calibri. The IEEE standards for writing SRS
document has been followed when writing this SRS.

1.3 Intended Audience and Reading Suggestions

ThisdocumentisintendedtobereadbySICSRadministrationandstudentsonly.Thisisatechnical
documentandthetermsshouldbeunderstoodbytheorganization.

1.4

Project Scope

The scope of the web portal is to provide a user friendly set of web pages that are easy to
navigate and at the same time provides sufficient depth and information about all the projects
carried out in the organization.

The scope includes a database for managing projects documentations. This

web portal will help students and faculties to find documentations related to all
the ongoing as well as past projects throughout the organization.
The system will also contain a relational database for maintaining list of valid
and registered users who can use this application by signing into their
accounts. The web portal will be accessible to the users belonging to the
organization only.
The goal of the website is to provide a platform for sharing knowledge in the
organization.

1.5 References
None.

SoftwareRequirementsSpecificationforOnlineProjectTrackingPortal
Page2

2. Overall Description
2.1

Project Perspective

The Web portal is aimed toward students and faculties of the organization and
looking for documentations related to the projects carried by other students or
faculties of the organization.
Web portal should be user-friendly.

2.2

Project Features

Major features of the web portal include the following pages/subsections:

Downloads
o Documents in .pdf or .doc format.
o Presentation files.

News and events

o Any latest document uploaded.
o Announcement or information organization wants to provide.

About Us/Mission
o It specifies the aim of Web portal

2.3 User Classes and Characteristics

There are mainly two types of user:
1. Faculty and teachers looking for project documentations for reference.
2. Students that are in the college and are seeking for some information
about all the ongoing as well as past projects.

2.4 Operating Environment

The Web portal will run on a College server.

2.5 Design and Implementation Constraints

There are no Design and Implementation Constraints.

2.6 User Documentation

There are no user documents.

SoftwareRequirementsSpecificationforOnlineProjectTrackingPortal
Page3

2.7 Assumptions and Dependencies

There are no development assumptions or dependencies.

3. External Interface Requirements

3.1 User Interfaces:
Uploaded once the static web page is done.

3.2 Hardware Interfaces

There are no special hardware requirements.

3.3 Software Interfaces

ThesystemwillinteractwithMysql5.6.1softwaretomaintainthedatabase.

3.4 Communications Interfaces

The system will use hypertext transfer protocol to interact with the server and internet
protocol ipv6 model to work on desktop. The system uses W.A.P protocol to work on
mobile PDAs.

4. System Features
Thesearethefollowingfeatureswhicharebeingavailbythesystem:

4.1 System Feature 1

The system will allow tracking all the past and ongoing project of an university.
4.1.1

Description and Priority

The system will allow all registered user to track the currently running
project and the entire project done in the past. The system will use the
searching algorithm to compare the user required project with the entire
current project in the database.
The risk will be decided upon the various parameters as:
1. Low-Risk: The required project does not exist in the database.
2. Medium-Risk: Some kind of similar project exists in the database.
3. High-Risk: A same project of similar project exists in the database.

SoftwareRequirementsSpecificationforOnlineProjectTrackingPortal
Page4

4.1.2

Stimulus/Response Sequences
A user enters the project name in the search bar and then presses submit.
A system connect to database and after searching using specific searching
Algorithm displays the result.

4.1.3

Functional Requirements:
REQ-1: A database system.
REQ-2: An efficient searching algorithm.

4.2 System Feature 2:

Thesystemwillallowregistereduserstoshareinformationandtheirviewsabouttheprojects.
4.2.1 Description and Priority
The system will allow all registered user to share information and their
views about the currently running and the projects done in the past. The
system will give same priority to all the registered users.
4.2.2Stimulus/Response Sequences
A user enters the project name in the search bar and then presses share
views and information button. A system displays the views window in
which previous views are displayed. On clicking the submit button, the
system connect to database and upload the view.
4.2.3 Functional Requirements
REQ-1 A database system.
REQ-2: An efficient searching algorithm.
REQ-3: Connectivity with the database.

4.3 System Feature 3:

The system will allow students and faculties to submit their research paper and
documentation.
4.3.1

Description:
The system will allow all registered user to submit their research paper
and documentation. The system keeps record of all research paper with
inserted date and time.

4.3.2

Stimulus/Response Sequences:
A user presses submit research paper button. A system displays a w
window on a user upload their respective research paper. On clicking the
submit button, the system connect to database and upload the research
paper.

4.3.3

Functional Requirements:

SoftwareRequirementsSpecificationforOnlineProjectTrackingPortal
Page5

REQ-1: A database system.

REQ-2: An efficient searching and sorting algorithm.
REQ-3: Database connectivity.

5.

NonfunctionalRequirements

5.1 Performance Requirements

Accessible from different websites.

Capacity and scalability- current and future web hosting web services.
Internal and external human resource.
Efficient page load and calculations.

5.2 Safety Requirements:

System and data backup-business and data recovery.

Identification and rectification of fault.

5.3 Security Requirements

Maintainability configuration and content management.

Online asset needs to be maintained.
It must ensure ISO-27001 ( IT security ) standard.
Password must contain alphanumeric characters.

5.4 Software Quality Attributes

6.

Object oriented approach every module must be tested.

Useable Easy to use by the target.
Must assure ISO 9001-2008 standard.

OtherRequirements

AppendixA:Glossary
HTML: Hypertext Markup Language
SRS: Software Requirements and Specifications
WAP: Wireless Application Protocol
TCP/IP: Transmission Control Protocol/Internet Protocol
IPv4: Internet Protocol version 4