opm srs

8/3/2019 opm srs

1/18

Software Requirement Specification

Online Project Management

Project Guide Team MembersMr. T.N.Sharma

Index & Tables

1) Introduction1.1) Purpose...

1.2) Scope..

1.3) Abbreviations.

1.4) Reference...

1.5) Technologies.

2) Overall Description

2.1) Product Perspective2.2) Software Interface...

2.3) Hardware Interface.

2.4) Communication Interface

2.5) Product Function.

2.6) User Characteristics

2.7) Constraints..2.8) Use Case Model Survey.

2.9) DFD Design (Context Diagram)

2.10) ER Diagram...

2.11) Database Design...

3)Specific Requirement 3.1) Supplementary Requirement

1

8/3/2019 opm srs

2/18

1) Introduction:

1.1. Purpose:

The need for managing the projects using international standards &monitoring through the web from across the worldwide

organization branches are directing towards having an online

project management tool.

The basic project monitoring should have the clear personalized

dashboard views provide at-a-glance summary of your status

across all project. Allocation of resources and view resources load

across all project activities, all the information you need at your

fingertips project status and plans, related documents, notes and

discussions, project status and related data is securely shared in

real time, based on each users role and permissions.

More over the system need to be available for access over the web

anytime, anywhere.

1.2. Scope: Any IT company can be added all its project details

and update any time. Here we can maintain all employee details like

name, address, and role in project, skills, and working status.

Admin can be checked all project status any time

from anywhere across the world.

Here Admin, Project manager, Team members can

be share ideas from anywhere.

Track all employee and contact details.

Allocations of resources (tools, technologies etc.),

view resources load across all projects and activities. All the information at our fingertips project status,

related documents, notes and discussion.

Project status and related data is securely shared in

real time, based on each users role and permissions.

From the entire project details we can be planned

project.

2

8/3/2019 opm srs

3/18

Project Dashboard updates automatically to

provide us with an up-to-date data of the current health of our

projects, while its happening.

Every project involves creating document. User can

easily upload and download these documents into the central

location.

Take a look to the project management software

already available.

1.3. Abbreviations: HTML: Hypertext Markup language, used to make

static page.

ASPX: Active Sever Page, used for make dynamic

page.

CS: C# Files

SQL Server 2005: SQL Server 2005 is database

management system that delivers a flexible and cost effective

database platform to build robust on demand business application.

IIS: Internet Information Service ,a web Server

HTTP: Hypertext Transfer Protocol is a transaction

oriented client/server protocol between web browser & a Web

Server.

1.4. Reference:

IEEE SRS Format

1.5. Technologies: Dot Net: Application Architecture

Sql Server 2005: Database

WSAD: Development Tool

IIS: Web Server

Visual Studio: Design Tool

3

8/3/2019 opm srs

4/18

2) Overview: SRS will include two sections: Overall Description will describe major components

of the system, interconnection and external interfaces.

Specific Requirements will describe the functions of

actors, their role in the system and constraints.

OverallDescription:

Describe the general factor that effect product and its requirement.

2.1. Product Perspective:

Client Side Application Database

Server Server

The web pages (ASPX/HTML) are present to provide the user interface on

customer client side. Communication between customer and server is providedthrough HTTP/HTTPS Protocol.

The Client Software is to provide the user interface on system user client side

and for this TCP/IP protocols are used.

2.2. Software Interface:

Client on Internet: Web Browser, Operating System (any)

4

HTML

CLIENTHTTP/HTTPS

IISSql server

8/3/2019 opm srs

5/18

Client on Intranet: Web Browser and Operating System.

Web Server: IIS, Operating System (any Microsoft OS).

Data Base Server: SQL Server 2005, Operating System (any Microsoft OS).

Development End: Visual Studio 2005 (Dot Net 2.0, C#, ASPX, HTML),

Sql Server 2005, OS (Windows), IIS.

2.3. Hardware Interface:

Client Side

Processor RAM Disk Space

Pentium II at 500 MHz 64 MB 1 GB

Server Side

Pentium III at 1 GHz 512 MB 2 GB

2.4. Communication Interface:

Client on Internet will be using HTTP/HTTPS protocol.Client on Intranet will be using TCP/IP protocol.

2.5. Product Function:

Track Project Level Data: In this module, all project are maintained bythe admin.

There are multiple project that are mange every day.

There are facilities for message board where users can be shared ideas.

There is multiple tasks that are may or may not be associated with a

project.

The entire information client need at him fingertips project status and

related documents.

By project reporting, you can show your client that the project is ontrack and has been managed.

Online Storage Every project involves creating documentation.

2.6. User Characteristics: Every user should be comfortable of working with computer and net

Browsing. He must have basic knowledge of English too.

5

8/3/2019 opm srs

6/18

2.7. Constraints: GUI is only in English.

Login and password is used for identification of user and there is no

facility for guest.

This system is working for single server.

There is no maintainability of back up so availability will get effected.

Limited to HTTP/HTTPS.

2.8. Use Case Model Survey:

Use Case Diagram

1) Administrator: Responsible for manage all activity of project and its

functionality.

6

Actor Actor

View

All

Details

Edit

All

Details

Manage Project in case

Project ManagerManage all users

Manage Project Team in case

Project Manager

Software Eng Admin Manage All project

& Assign to Project

Manager

Manage Document

&

Send Msg and View

Manage Document

&

Send Msg And View

Create task and assign in case

Project Manager

8/3/2019 opm srs

7/18

Manage All Users: Admin can be modified all details of users. He

can give the role to users within any project.

Manage project: Admin can be managed all details of Project ,can

assign project to Project Manager.

Maintaining all records and share ideas to users for further

improvement.

Admin can be edit and view all details.

Admin Can Upload Any Document in any Project And View,

Download.

Admin can send message to every Team Member.

2) Software Engineer: Here software eng has different role like Project

Manager, team leader and team member.

Manage all projects in which he is project manager.

Create Team, Add Team Member Assign Rolls them.

Manage team and give tasks to team member in case of team

Members.

He can view all details of project in which he is involve.

Software Engineer Can Upload Any Document in his related

Project And View, Download.

Software Engineer can send message to every Team Member.

2.9. DFD Design (Context Diagram):

7

System

Administrator Software Engineer Request for add,

edit, view

details ofvarious project

and all

employees

View ,edit

Details of

Projects, addteam member

assign task and

Update task

status

Response

Response

8/3/2019 opm srs

8/18

User

ManagementProject

Management

Administrator

Add, Edit,

View, Delete

users detail, Set

accessauthorization to

users and also

disable users

Software EngineerAdd New

Project,

Modules,

Tasks; Assign

project teamRe

sp

on

se

View allocated

project, create

module and

task, and assigntask to team

member

Add team .

Response

Response

Edit, View, own

details and use

message board toshare ideas

DFD Level 1

Response

8

8/3/2019 opm srs

9/18

1) Administrator: Responsible for manage all activity of project and

its functionality.

Add New Employee: Here Admin can be add new Employee in the

system and can update Employee details anytime

Add New Project: Here Admin can be add new project in the

system and can update project details anytime.

Add Module: Here Admin can be add module in the project and

can update Module details anytime.

Add New Task: Here Admin can be add new Task in the Project

Module and can update Task details anytime

Upload and Download any Document in the any Project

Share his Idea using Message Board.

2) Software Engineer: Here software eng has different role like

Project Manager, team leader and team member.

View, Update Project: Software Engineer can be view and Update

all details of allocated project. Add Module: Here Project Manager can be add module in the

project and can update Module details anytime.

Add New Task: Here Project Manager can be add new Task in the

Project Module and can update Task details anytime

Assign Task :- Here Project Manager can be Assign Task in the

Project Module to any Team Member and can update Task details anytime

All software Eng submits and updates tasks status.

Upload and Download any Document Related with Project

Share Their Idea using Message Board.

9

8/3/2019 opm srs

10/18

Send

Message

EmployeeWorks

on

Have

For

Assigned

Have

Project Team

Tasks

Modules

Project

Project_Type

task_end_time

task_daily_status

task_start_time

M

N

MM

M

M

N1

1

1

1

1

Project_id

Project comment

Project_NameEmp_idDesignation

User_type

Module_title

Admin_comment

Approx_duration

S. No.

Team name

Member Role

Task_id

Taskpriority

Task name

First Name

DOB

module_id

2.10 Entity Relationship Diagram

M

10

8/3/2019 opm srs

11/18

2.11 Database Design :

1. technologies_master

field name data type size constraints descriptiontechnology_name Varchar 50 Java, PHP, .Net, XML, AJAX,

J2ME, EJB, J2EE

Id bigInt PK

PlatformId BigInt FK

Description varchar 250

2. tools_master

field name data type Size constraints description

Id bigInt PK

tool_name varchar 100 Eclipse, Tomcattool_description varchar 500 Use of tool

tool_category varchar 50 Web Server, Editor, RDBMS,

Reporting Tool, etc.

3. emp_details

Field_name Type Size Constraint Description

Id bigInt PK Atuo Generated

first_name varchar 30

last_name varchar 30

Dob dateTime

Qualification varchar 50 mca, m-tech, bca,BE/Btech

Gender varchar 6 Male/Female

Designation Int FK

Address varchar 200

City varchar 50

State varchar 50

Country varchar 50

Zip varchar 6

Phone varchar 15

Mobile varchar 15 9950442821Fax varchar 15

Email varchar 100 [email protected]

Experience integer 4 In month

salary integer 5 1000/hr and monthly salary for

general employee

working_status varchar 20 Task Assigned / Free.

status Bit Enabled/Disabled

11

8/3/2019 opm srs

12/18

CreateDate DateTime System Date

4. employee_expertise

field name data type size constraints description

Id bigInt PK

emp_id Bigint FK contain Employee id

Platform Bigint FK

Technology Bigint FK

Skill Bigint Fk

Experience Float work experience time on skill

5. project_details

field name type size constraints description

project_id BIGINT PK Auto incremented numeric

value

project_name varchar 200 - i.e. online project management

Alias Varchar 50

Description varchar 200 -

project_type varchar 20 Web Project/Standalone

Priority varchar 20 Urgent/ Normal/ Low/ High

Client varchar 500 - only for admin use

scheduled_start_date date - 11 Jan 2009

scheduled_end_date date - 15 jun 2009

Actual_start_date date

Actual_end_date date

approx_duration integer - Duration in days

Platform Bigint FK


Completion Int

CreateDate dateTime System Date

project_status varchar 10

New/ Planned/ Running/Completed/ Paused/ Updation.

Updated by OnlyAdmin/Project Manager.

12

8/3/2019 opm srs

13/18

6. project_documentsField name data type Size constraints description

Id Bigint PK

project_id Bigint FK name varchar 100 File name

CreateDate Datetime

uploaded_by Bigint FK Employee Id

Description Varchar 500

url Varchar 500

Type Varchar 100

Date Datetime

Active Bit

Mail Ref description Varchar 500

7. project_module

field data type size constraints Description

module_id Bigint PK

project_id Bigint FK

module_title varchar 50

approx_duration integer duration will be in days

module_description varchar 2000

Status bit 20Completion Int

CreateDate Datetime

8. project_team


Id Bigint PK Auto incremented numeric

valueteam_name varchar 50

project_id Bigint FK

EmpId Bigint FK ProjectManager Id

start_date Datetime

Deadline Datetime

CreateDate Datetime System date

Size Int Size of team

13

8/3/2019 opm srs

14/18

14

8/3/2019 opm srs

15/18

9. Taskfield name data type size constraints description

Id integer 9 PK auto-increment id

Title varchar 100 store all over msg

Description Varchar 1000moduleId Bigint FK

Createdate DateTime

Duration Int

ProjectId Bigint FK

10. messages

field name data type size constraints descriptionmsg_id Bigint PK auto-increment id

message varchar 5000 store all over msg

projected Bigint FK

subject Varchar 100

SenderID BIGINT Fk

11. Login


Username Varchar 100 PK Email id

Password Varchar 30 Case

Sensitive

User type Varchar Admin/project manager/ team

member

Active Bit

empId BIGINT Fk

15

8/3/2019 opm srs

16/18

12.Task Assign


Id Bigint PK

ProjectId Bigint FK PmID Bigint Fk

EmpId Bigint FK

moduleId Bigint FK

TaskId Bigint FK

Duration Int

AssignDate Datetime

Deadline Datetime

Status Varchar 10

Completion Int

Active Bit

Submit BitSubmitdate Datetime

Ischecked Bit

Priority Varchar 50

EndDate Datetime

CreateDate Datetime

Remark Varchar 500

13 . Designation


Id Bigint PK

Designation Varchar 50

User type Varchar Admin/project manager/ team

member

Description Varchar 500

14. Skill


Id Bigint PK

Name Varchar 100

Platform Bigint FK


Description

16

8/3/2019 opm srs

17/18

15. Platform


ID Bigint PK

Platform Varchar 100Description Varchar 100

16. Team Member


TeamID Bigint FK

EmpId Bigint Fk

Roll Varchar 100

17

8/3/2019 opm srs

18/18

3) Specific Requirement:

Supplementary Requirements:

Have hours of operation that are 24 x 7: - Because system can be an automatedProcess, so it can stay open for 24 hours a day. If the base is now the entire world,

Staying open 24 hours a day becomes critical. System is required to be available24X7 so UPS support must be on server site for at least 8 hours in case of power

failure. System will remain inaccessible to users at 2:00 to 4:00 am for backup and

maintenance purpose.

Make the existing Web site more dynamic in nature: - Many early Web

Implementations consisted of static HTML pages. This becomes very difficult tomanage if the number of pages gets too large. An effective system should be

largely dynamic Taking advantage of technology that automates this process ratherthan relying on manual Processes. Application should serve dynamic user based

customized web pages to its Clients from server.

Tie the existing Web site into existing enterprise systems: Any existing Web site

that relies on the manual duplication of data from another system is one that can be

Improved. Most of the business data in the world today exists in enterprise serversthat can be connected to the Web servers to make this process far more effective.

Provide good performance and the ability to scale the server: - The WebApplication Server should provide good performance and the ability to manage

Performance with techniques, such as support for caching, clustering, and load

Balancing.

Providing session management capability: - Web application developers should not

spend valuable time worrying about how to maintain sessions within the application.The Web Application Server should provide these services.

18

opm srs

Documents

Transcript of opm srs