SRS Sample Students

<Project Name> Version: <1.
0>
System Requirement Specification.
<Team Name>
<Team Name>
< Project Name >

Software Requirements Specification
Version < X.0>
Project Guide:( Faculty Guide’s Name )
Members:(Team members name)
College Name:
Department:
Page 1
<Project Name> Version: <1.0>
<Team Name>
Table of Contents
1. Introduction 3
1.1 Purpose 3
1.2 Scope 3
1.3 Definitions, Acronyms and Abbreviations 3
1.4 References .
1.5 Technologies to be used .
1.6 Overview .
2. Overall Description .
2.1 Use-Case Model Survey .

2.2 WEB Architecture diagram .
2.3 ER Diagram .
2.4 Architecture diagram .
2.5 Data Dictionary .
2.6 Assumptions and Dependencies .
3. Specific Requirements .
3.1 Use-Case Reports .

3.2 Class Diagram .
3.2 Supplementary Requirements .
Page 2
<Team Name>
1. Introduction
1.1 Purpose
To develop a fully functional and user interactive online tool which can enhance
and help various project management users to manage and compile their work
efficiently and productively
1.2 Scope
 Create different users with varied roles and scopes.
 Confirm each member by providing activation codes.
 Manage all project details like tasks, deadlines, team members and
resources.
 Assign different tasks to different members.
 Provide documentation to the members about the tasks being added
 Update all members about new proceedings in the project.
 Bind all the information provided by the team members at one place
and show it to all others.
 Maintain start date and end date of each task
 Maintain the overall timeline of the project.
1.3 Definitions, Acronyms and Abbreviation
OPM – Online Project Management.

Admin – Administrator.
PM – Project Manager.
HTML – Hyper Text Markup Language.
XHTML – extensible Hypertext Markup Language.
HTTP – Hypertext Transfer Protocol.
JSP – Java Server Pages.
Page 3
<Team Name>
EJB - Enterprise Java Beans.

WAS – Websphere Application Server.
J2EE – Java 2 Enterprise Edition.
DB2 - DB2 Database Management System.
Msg – Messag.
Doc – document.
1.4 References
IEEE SRS Format.
TGMC-2008 Sample Synopsis Format.
Problem Definition Provided By TGMC-2008
1.5 Technologies to be used
Application Architecture - J2EE
Database Application - DB2
Development tool - Rational System Developer.
Web Deployment Server - WAS.
Designing tool - Rational
1.6 Overview
This project is a tool to help in managing projects. It is more useful in
current market situation where an organization is not close to a door or a
city or a nation. In this case sharing document & data related to project
from one corner of the world to another by using internet makes our work
for easy. But still it is unmanaged to manage this work we are making this
tool Online Project Management System (OPM).
Page 4
<Team Name>
2. Overall Description
2.1 Use-Case Model Survey
Start New
Projects
Invite Project
Administrato
Managers
r
Update
Task Assign Project
Status View Manager
All Decide
Details Deadline
Team
s
Member
Invite New
s
Members
Project
Manager
Create
Message Update
s Project Creat
Status e
New
Task
Provide
Documentation Create
Message
Generate s
Reports
Page 5
<Team Name>
1. Administrator: - is responsible for registering with the tool and creating a profile
with the company name.
a. Start New Project: - Admin logs into the OPM and create a profile with his
company name and initiates a project.
b. Invite Project Manager:- After starting a project the Admin Invites a

Project Manager.
c. Assign Project Manager: - When the invited Project Manager agrees to the
Admin he/she is being allotted the project initiated.
2. Project Manager: - is responsible for dealing with all the proceedings of the
project.
a. Invite New Team Member: - After the Project is being allotted a Manager,
the PM invites various team members to work on the project as well and
sends them invites.
b. Create New Task: - The PM create new tasks and assigns them to the
desired members.
c. Create Message: - The PM can create Message for the other team
members notifying them about project updates etc.
d. Provide Documentation: - The PM gives documentation for the various

tasks.
e. Generate Report: - The PM can generate reports for the various task and
project.
f. Decide Deadline: - The PM can decide the time needed for the task to be
completed.
g. Update Project Status: - The PM can update the completion status of the
project on time-to-time basis.
Page 6
<Team Name>
3. Team Members: -
a. Update Task Status: - the members working on the particular task can
update the task completion status.
b. Create Message: - the members can also create messages to make aware
other members about the task proceedings.
2.2 Web Architecture Diagram
HTML
CLIENT HTTP/HTTPS
(Customer)
DB
WAS
SERVER
Client
Software
TCP/IP
(System Users)
Client Side Application Side DB Server Side

It uses three tier architecture dig where client side application side and DB server are
three diff components that improve security in system.
Page 7
<Team Name>
2.3 ER Diagram
Page 8
<Team Name>
2.4 Architecture Diagram
Page 9
<Team Name>
2.5 Data Dictionary
All tables used in project
3. OPM_ADMIN
4. OPM _ PROJECT_MANAGER
Page 10
<Team Name>
1. OPM_TEAM_MEMBER
2. OPM_PROJECT
Page 11
<Team Name>
3. OPM_TASK
4. OPM_DOCUMENTS
5. OPM_MESSAGE_BOX
Page 12
<Team Name>
6. OPM_MESSAGE_INBOX
7. OPM_MESSAGE_OUTBOX
8. OPM_REPORTS
4.1 Assumptions and Dependencies

Page 13
<Team Name>
 The Project Manager from same company is not being assigned to

two projects.
 Administrator can also be a project manager for a project.
Page 14
<Team Name>
5. Specific Requirements
5.1 Use-Case Reports
1. Administrator- is responsible for registering the company and initiating a

project, sending invitation mails to the project manager.
 Start New Project- the admin starts the project which needs to be
managed and supervised by the project manager. The Admin provides
with the relevant information to the system and initiates a new project.
 Invite Project Manager- the Admin sends an invitation email to the
desired project manager who will be responsible for managing the
project so created.
 Assign Project Manager- the Admin assigns the project manager a

particular project on which he/she needs to work.
Name of Use Case - Start New Project.
Description – a new project will be created for the company.
Pre Condition –The Admin should be logged in the system.
Normal Flow of Events –
 A form will open, necessary information will be entered
 A query will be fired to the database.
 An invitation email will be sent to the desired project manager
 Relevant output will be given to the user.
USE CASE DIAGRAM
Page 15
<Team Name>
New Project Details Filled In
Email to Admin for

activation
Work Flow Diagram
A new Project
details filled in.
An Email is sent to
Admin for activation
Name of Use Case – Invite Project Manager.
Description – an invitation email will be sent to project manager for

confirmation.
Pre Condition The Admin should be logged in the system.
 An invitation email will be sent to Project Manager
 Project Manager will confirm the request.
Page 16
<Team Name>
 Project information will be completed and status will be

updated to ready.
USE CASE DIAGRAM
An invitation mail is
send to PM
Project
Manager
Request confirmation &
PM registration
WORK FLOW DIAGRAM
An Invitation Mail
is send to PM
PM confirms the Invitation

& register to the system
2. Project Manager – is responsible for managing the overall project, it’s tasks,
messages, reports, related deadlines and documents
 Invite New Member – the PM is authorized to invite new members

for the project and he/she do so by sending them invitation.
 Create New Task – The PM is responsible for creating a new task

and assign members to it
Page 17
<Team Name>
 Create Messages – PM can add messages to the project and these

messages will be displayed to all the users.
 Provide Documentation - The PM is responsible for providing

documentation for the various tasks involved.
 Generate Reports – The PM can generate various types of reports

whenever he feels a requirement.
 Update Project Status – The PM can update the project completion

status by analyzing the various task completion statuses.
 Decide Deadlines – The PM is responsible for setting project and

task deadlines i.e. the start date and the end date.
Name of Use Case – Invite Team Member.
Description – an invitation email will be sent to team member for confirmation.
Pre Condition –
 The Project Manager should be logged in the system.
 An invitation email will be sent to Team Member.
 Team Member will confirm the request.
 Project information will be completed and status will be

updated to ready.
USE CASE DIAGRAM
Page 18
<Team Name>
Dispatch an Email to invite

Team Members
Request confirmation and Team

Registration by Team Member
Member
Project Information will be

completed.
WORK FLOW DIAGRAM
Dispatch an
Email to invite
Team Members
Request confirmation
and Registration by
Team Member
Project Information will

be completed
Name of Use Case – Create New Task
Description – PM starts new task and assign team members to it.
Pre Condition –
 The PM should be logged in the system.
 A task will be added to the project and timelines will be

displayed.
Page 19
<Team Name>
 Team Members will update the task status.
 The Project completion status will also be updated.
USE CASE DIAGRAM

A Task will be added to
project
Team Member Update Team

task status Member
Project Completion status

updated
WORK FLOW DIAGRAM
Task Is Added to the

Project
Team Member updates

task status
Project Completion
status updated
Name of Use Case – Create New Message.
Description – a new message will be created which will be displayed to all the
users.
Pre Condition –
Page 20
<Team Name>
 A Msg will be created by filling in details of the msg.
 This msg will be displayed to all the active users of the project.
USE CASE DIAGRAM
A MSG will be created

Team
Member
Displaying MSG to active user
WORK FLOW DIAGRAM
A MSG will be
created
Displaying MSG to
active user
Name of Use Case – Provide documentation.
Description – a task or project related document will be given to the team

members for their guidance
Pre Condition –
Page 21
<Team Name>
 A document will be uploaded to the system.
 Other team members can read the doc.
USE CASE DIAGRAM
Uploading of DOC to system
Team
Accessibility of DOC to other Member
members
WORK FLOW DIAGRAM
Uploading of
DOC to system
Accessibility of
DOC to other
members
Page 22
<Team Name>
Name of Use Case – Generate Reports.
Description – a report can be generated by the PM at any instance of time to

view the project completion status
Pre Condition –
 A project report will be generated
 A database entry would be made.
USE CASE DIAGRAM
Generation of project
report
Enter information to
database
WORK FLOW DIAGRAM
Generation of
project report
Enter
information to
database
Name of Use Case – Update Project Status.
Description – a PM can update the project status by looking at the task
Page 23
<Team Name>
completion status.
Pre Condition –
 Analyze project tasks.
 Update project completion status.
USE CASE DIAGRAM
Analyze Project task
Update project completion

status
WORK FLOW DIAGRAM
Analyze
Project task
Update project
completion
status
Name of Use Case – decide deadlines.
Description – a time line i.e. a start date and an end date would be set for every
Page 24
<Team Name>
task.
Pre Condition –
 Set a start date and an end date.
USE CASE DIAGRAM
Set a start date and an end

date
WORK FLOW DIAGRAM
Set an start date

and an end date
3. Team Member – is responsible for updating task status and completing the
task so that the project may not get delayed.
Page 25
<Team Name>
 Update Task Status – the team member is responsible for

updating the completion status of the project.
 Create/ update MSG – the team member can create and update
the msgs.
Name of Use Case – update task status.
Description – completion status of the task could be updated.
Pre Condition –
 The Team Member should be logged in the system.
 Sets the percentage completion status.
USE CASE DIAGRAM
Set the percentage

completion status
WORK FLOW DIAGRAM
Set the percentage

completion status
Name of Use Case – create/ update MSG.
Description – a new MSG will be created or an already existing MSG will be
Page 26
<Team Name>
updated.
Pre Condition –
 The Team Member should be logged in the system.
 Create a new msg
 Edit an already existing msg.
USE CASE DIAGRAM
Create a new MSG
Edit an already existing Msg
WORK FLOW DIAGRAM
Create a new
Msg
Edit an already
existing MSG
Page 27
<Team Name>
5.2 Class Diagram
Page 28
<Team Name>
Page 29
<Team Name>
5.3 Supplementary Requirements
 Since this a tool which can be used from anywhere and anytime in
the world, so the server should be well managed for such kind of
requirement.
 The users using this and importing the reports from this tool should
have supporting software to run them.
 To use the application in the best possible way please read the tips
displayed while using the tool.
Page 30

SRS Sample Students

Uploaded by

Copyright:

Available Formats

SRS Sample Students

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SRS Sample Students

Uploaded by

Copyright:

Available Formats

<Project Name> Version: <1.

< Project Name >

Project Guide:( Faculty Guide’s Name )

Members:(Team members name)

2.1 Use-Case Model Survey .

3.1 Use-Case Reports .

1.3 Definitions, Acronyms and Abbreviation

OPM – Online Project Management.

EJB - Enterprise Java Beans.

2.1 Use-Case Model Survey

b. Invite Project Manager:- After starting a project the Admin Invites a

d. Provide Documentation: - The PM gives documentation for the various

2.2 Web Architecture Diagram

Client Side Application Side DB Server Side

2.4 Architecture Diagram

2.5 Data Dictionary

All tables used in project

4.1 Assumptions and Dependencies

 The Project Manager from same company is not being assigned to

 Administrator can also be a project manager for a project.

5.1 Use-Case Reports

1. Administrator- is responsible for registering the company and initiating a

 Assign Project Manager- the Admin assigns the project manager a

Name of Use Case - Start New Project.

Description – a new project will be created for the company.

Pre Condition –The Admin should be logged in the system.

Normal Flow of Events –

 A form will open, necessary information will be entered

 A query will be fired to the database.

 An invitation email will be sent to the desired project manager

 Relevant output will be given to the user.

USE CASE DIAGRAM

New Project Details Filled In

Email to Admin for

Work Flow Diagram

Name of Use Case – Invite Project Manager.

Description – an invitation email will be sent to project manager for

Pre Condition The Admin should be logged in the system.

Normal Flow of Events –

 An invitation email will be sent to Project Manager

 Project Manager will confirm the request.

 Project information will be completed and status will be

USE CASE DIAGRAM

WORK FLOW DIAGRAM

PM confirms the Invitation

 Invite New Member – the PM is authorized to invite new members

 Create New Task – The PM is responsible for creating a new task

 Create Messages – PM can add messages to the project and these

 Provide Documentation - The PM is responsible for providing

 Generate Reports – The PM can generate various types of reports

 Update Project Status – The PM can update the project completion

 Decide Deadlines – The PM is responsible for setting project and

Name of Use Case – Invite Team Member.

Description – an invitation email will be sent to team member for confirmation.

 The Project Manager should be logged in the system.

Normal Flow of Events –

 An invitation email will be sent to Team Member.

 Team Member will confirm the request.