Software Requirements

Specification
For
Project Governance Tool
Version 1.0 approved
Auroras Technological and Research Institute

Software Requirements Specification for Project Governance Tool Page ii

Table of Contents
Table of Contents .......................................................................................................................... ii
Revision History ............................................................................................................................ ii
1. Introduction ..............................................................................................................................1
1.1 Purpose ............................................................................................................................................. 1
1.2 Document Conventions .................................................................................................................... 1
1.3 Intended Audience and Reading Suggestions .................................................................................. 1
1.4 Product Scope .................................................................................................................................. 2
1.5 References ........................................................................................................................................ 2
2. Overall Description ..................................................................................................................3
2.1 Product Perspective .......................................................................................................................... 3
2.2 Product Functions ............................................................................................................................ 3
2.3 User Classes and Characteristics...................................................................................................... 3
2.4 Operating Environment .................................................................................................................... 4
2.5 Design and Implementation Constraints .......................................................................................... 4
2.6 User Documentation ........................................................................................................................ 4
2.7 Assumptions and Dependencies....................................................................................................... 4
3. External Interface Requirements ...........................................................................................5
3.1 User Interfaces ................................................................................................................................. 5
3.2 Hardware Interfaces ......................................................................................................................... 5
3.3 Software Interfaces .......................................................................................................................... 5
3.4 Communications Interfaces ............................................................................................................. 5
4. System Features .......................................................................................................................6
4.1 Planning Tasks ................................................................................Error! Bookmark not defined.
4.2 Setting Milestones ...........................................................................Error! Bookmark not defined.
4.3 Discussion Forum 6
4.4 Remote Desktop Viewing 6
4.5 Timely Notification 6
4.6 Uploading Project Updated Versions 6
4.7 Modules 7
5. Other Nonfunctional Requirements .......................................................................................8
5.1 Performance Requirements .............................................................................................................. 8
5.2 Safety Requirements .......................................................................Error! Bookmark not defined.
5.3 Security Requirements ..................................................................................................................... 8
5.4 Software Quality Attributes ............................................................................................................. 8
6. Analysis Models ........................................................................................................................8


Revision History
Name Date Reason For Changes Version




Software Requirements Specification for Project Governance Tool Page 1

1. Introduction
1.1 Purpose
Project Governance Tool specifies the simple, organized and easy way to handle the software
development life cycle process.
The main purpose of this software is to bring the project team under a single roof and allow
interaction without having to meet in-person hence saving time and resources. This tool is the
outcome of the productive usage of software technology to manage the projects in a well planned
method. This tool enhances the efficiency of software development and management processes.

1.2 Document Conventions
Font Style Size
Headings Times Bold 18
Sub-Headings Times Bold 14
Others Arial Italic 12
Words in Bold are important terms, and have been formatted to grab the attention of the
reader.
1.3 Intended Audience and Reading Suggestions
This document is meant for users, developers, project managers, testers. The SRS document aims to
explain in an easy manner, the basic idea behind the Project Governance Tool. It also aims to
introduce to the users the main features of the Project Governance Tool and what makes it different
from other conventional project management tools.


Software Requirements Specification for Project Governance Tool Page 2

1.4 Product Scope
Project management software has the capacity to help plan, organize, and manage resources..
Depending on the sophistication of the software, it can manage estimation and
planning, scheduling budget management, resource allocation, collaboration
software, communication, decision-making, quality management and documentation. .
This web based tool is not confined only to the minor (college) projects but also to major
(Company/ Industry) projects.

This tool provides the users with easy and quick access to their projects and coordinating
between the team.
Keeps team members informed of alerts and notifications.
Clean, intuitive design and layout.
The tool provides the track of due-dates and start-dates of the tasks of the project.
The tool also provides the facility to set task priority and percentage complete .
This tool helps to keep projects on-track by easily tracking Milestones.
This tool provides a histogram representation for scheduling, managing and visualizing the
projects.
This tool also provides the remote desktop sharing to verify and confirm the progress as
indicated by the team.

1.5 References
Web Addresses:

www.google.com
www.wikipedia.com
www.cs.york.ac.uk/projects/howtodo.html
Software Requirements Specification for Project Governance Tool Page 3

2. Overall Description
2.1 Product Perspective
The Project Governance Tool is a package to be used by the project teams to improve the efficiency
of the project management. This tool greatly benefits the members of the project team.The system
provides simplified approach to coordinate between the team and make the process of project
development unsophisticated. The project team can always communicate with the project Lead and
notify him about the progress of the project along with the updated versions of the software being
developed.
2.2 Product Functions
The Project Governance tools provides online real time project management capabilities and the
information about the project team . The Product functions are more or less the same as described in
the product perspective. The functions of the system include the system providing different type of
services based on the type of users [ Team Member/Team Lead ].

Details, tasks, time and communications in one place.
Collaborate on Projects with team.
Ease in assigning tasks to the project team.
Onscreen and e-mail alerts to keep track of the project progress.
Upload and share files with anyone on the project.
Visualize the projects with histogram representation.
2.3 User Classes and Characteristics
The major user classes that are expected to use this product are as follows:


2.3.1 Developers / Team Member

The developer is expected to be the main user class of this tool. These users are expected to
communicate with the project Team and update the progress of the project on to the system then to
be verified by the Lead of the respective project. These users also upload the files of the project to be
validated by the team.





Software Requirements Specification for Project Governance Tool Page 4

2.3.2 Team Lead

This class of users are expected to supervise the ongoing project. They can set the task preferences
and milestones. They can also check the progress and revert the remarks. They give guidance to
team members and follow through on action assignments


2.3.3 Administrator

This class of users are expected to assist the Team Lead to maintain the project development
process systematically. They examine the final project outcome.

2.4 Operating Environment

Operating System

Windows,Mac,Linux

Database

MySQL

Language

PHP 5.0


Web Server Apache
2.5 Design and Implementation Constraints
The users can access the Tool from any computer that has internet connection and browsing
capabilities. The users must have their usernames and passwords to use the system.

2.6 User Documentation
Online help is provided for each of the feature available in the tool. This online-help system guides
the user in operating the components of the tool.


2.7 Assumptions and Dependencies
The users have sufficient knowledge of computers and the computers have internet connection and
browsing capabilities. The users know English language as the Interface will be provided in English.
Software Requirements Specification for Project Governance Tool Page 5

3. External Interface Requirements
3.1 User Interfaces
The system will provide the ability for Team Lead and the Team members to access the Project
Governance Tool via the Internet. There will be three different user interfaces that will accompany this
website: one for the team member, the Team Lead, and the administrators.

Team Member will be having the ability to communicate with Team Lead and other team
members of the project. The other transactions of the team member includes uploading the
files of the project updated version and He will be notified about the tasks to be performed
and the milestones to be met and he will be given a remark on every updated version of the
project.
Team Lead needs to be logged in to the system all the time to supervise the project
development progress. The Team Lead has the ability to assign the tasks to the team
members, setting the milestones of the project, preparing the schedule .He/She is responsible
to verify the project progress based on the updated version and give a remark.
Administrator is the person who is authoritative to approve the project and to validate the
product as per the standards and requirements specified.

3.2 Hardware Interfaces
The System must run over the internet, all the hardware components that need to connect to the
internet will be hardware interface for the system. As for e.g. Modem, WAN LAN, Ethernet Cross-
Cable.
3.3 Software Interfaces
The system is on server so it requires any scripting language like PHP, VBScript etc.The system require
Database also for the storing any transactions of the system like MySQL etc. system also requires DNS
(domain name space) for naming on the internet. At last user needs a web browser to interact with the system.
3.4 Communications Interfaces
The tool shall send an e-mail to the user on registration into the system.
The tool shall send an email to the team / team member notifying about the project updates.
Software Requirements Specification for Project Governance Tool Page 6

4. System Features
4.1 Planning Tasks
4.1.1 Description
The Project Team can handle the tasks given on schedule with an effective task handler. The
tasks can be assigned in seconds. The tool streamlines the process of adding and assigning
tasks and sub-tasks, allows you to assign tasks to several people instead of just one.
4.2 Setting Milestones
4.2.1 Description
The Project Team Lead can utilize the feature of setting the Milestones to accomplish the tasks
previously assigned. The project team member checks the milestones data and works
accordingly to complete the task.
4.3 Discussion Forum
4.3.1 Description
The users of the Project Governance Tool are provided with a discussion forum to interact with
the other project teams on the site. This enables the project teams to communicate and
coordinate effectively.
4.4 Remote Desktop Viewing
4.4.1 Description
The Team Member updates the latest project versions on to the Tool to be verified by the Team
Lead or any other superior authority via a Remote Desktop viewing application. This application
is a Third Party Software which is just being provided as an option to the Team Lead so that he
can check and validate the progress of the project closely.

4.5 Timely Notification
4.5.1 Description
This system is built in such a way that whenever there is important alert to be notified to the
members of the team on the project , it is immediately done and email notifications are also
delivered.
Software Requirements Specification for Project Governance Tool Page 7

4.6 Uploading Project Updated Versions
4.6.1 Description

The Team Member has the ability to always upload the files of the updated versions of the
project being done. This can be verified by the Project Team Lead and revert with respective
remarks and modifications.


4.7 Modules

The system provides three different user modules so that each users activity is distinguished
The modules are:

1. Team Member Module
This Module will be having the ability to communicate with Team Lead and other team
members of the project. The other transactions of the team member includes uploading the
files of the project updated version and He will be notified about the tasks to be performed
and the milestones to be met and he will be given a remark on every updated version of the
project.
2. Team Lead Module
This module provides the Team Lead the ability to supervise the project development
progress. The Team Lead has the ability to assign the tasks to the team members, setting the
milestones of the project, preparing the schedule .She/he is responsible to verify the project
progress based on the updated version and give a remark and at the end submitting the final
version of the project to the Administrator and get remarks.
3. Administrator Module
This module provides the Administrator unique ability to oversee the activities of the project
teams and instruct the Project Team Lead. The Administrator can approve/disapprove the
projects ,give remarks to the completed projects and ensure that the project development life
cycle is being carried on according to the standards and rules.


Software Requirements Specification for Project Governance Tool Page 8

5. Other Nonfunctional Requirements
5.1 Performance Requirements
There is no performance requirement in this system because the server request and response
is depended on the end user internet connection.
5.2 Security Requirements
1. The systems back-end servers shall only be accessible to authenticated administrators.
2. Sensitive data will be encrypted before being sent over insecure connections like the internet.
3. A project team cannot view or learn about any other project including the project details and
progress.
4. The system shall permit the team members to view only the tasks assigned to them and not
others.

5.3 Software Quality Attributes
Availability:

The Project Governance Tool shall be available to users on the Internet to the users 99.9% of
the time.

Reliability:

The Project Governance Tool shall be reliable in most of the operations performed by the users.

Maintainability:

Maintainability is considered of crucial importance in the Project Governance Tool and is
established as one of the most important issues.

6. Analysis Models




Software Requirements Specification for Project Governance Tool Page 9