Software Requirements

Specification

for

Petroleum Refinary Monitoring

System
Version 1.1

Prepared by

Ajit F. Jha
[Roll No.:-74(IMS)]
Project Guide: Ms. Gayatri Jain

Course: MCA

Date: 2-02-2011

Date: 30-3-11
Content

1 INTRODUCTION
1.1 DOCUMENT PURPOSE.................................................................................................................................1
1.2 PRODUCT SCOPE........................................................................................................................................1
1.3 INTENDED AUDIENCE AND DOCUMENT OVERVIEW....................................................................................1
1.4 DOCUMENT CONVENTIONS.........................................................................................................................1
1.5 REFERENCES AND ACKNOWLEDGMENTS...................................................................................................2
2 OVERALL DESCRIPTION...............................................................................................................................3
2.1 PRODUCT PERSPECTIVE.............................................................................................................................3
2.2 PRODUCT FUNCTIONALITY..........................................................................................................................3
2.3 USERS AND CHARACTERISTICS..................................................................................................................3
2.4 OPERATING ENVIRONMENT.........................................................................................................................3
2.5 DESIGN AND IMPLEMENTATION CONSTRAINTS..........................................................................................4
2.6 USER DOCUMENTATION..............................................................................................................................4
2.7 ASSUMPTIONS AND DEPENDENCIES...........................................................................................................4
3 SPECIFIC REQUIREMENTS...........................................................................................................................5
3.1 EXTERNAL INTERFACE REQUIREMENTS.....................................................................................................5
3.2 FUNCTIONAL REQUIREMENTS.....................................................................................................................6
3.3 BEHAVIOUR REQUIREMENTS......................................................................................................................6
4 OTHER NON-FUNCTIONAL REQUIREMENTS..........................................................................................7
4.1 PERFORMANCE REQUIREMENTS................................................................................................................7
4.2 SAFETY AND SECURITY REQUIREMENTS...................................................................................................7
4.3 SOFTWARE QUALITY ATTRIBUTES..............................................................................................................7
5 OTHER REQUIREMENTS................................................................................................................................8
APPENDIX A – DATA DICTIONARY.......................................................................................................................9
 1 Introduction
1.1 Document Purpose
This document provides the srs(software reuirement specification) for a development of web
based portal of the online petroleum plant monitoring system. This document will be very useful
for the developer in building a system. This document also will be very useful for a customer to
understand if they have provided all the required information regarding the project,& all the
information’s are correct.

It also provides the necessary information regarding what kind of funcationalities has been
included in the system. From where to where the control flaws in the project. What are the
features of the new system.

1.2 Product Scope

Here we have been specifying the srs for the project petroleum plant monitoring system. It
specifies that what is the functionalities has been provided by this system. It also specifies that
how this kind of this is very useful for better functioning of the system. It also specifies that what
are the new features has been used in this system. It also specifies that how this project helps in
providing more securities in the plant than it currently exists. Here it also specifies that how all
the problems regarding the plant problems& etc. has been solved without any difficulty.It also
specifies that how the problems regarding the plant has been solved without wasting the time.

1.3 Intended Audience and Document Overview

The intended audience for this document will be a project co-ordinatior, project guide &
developer.
In this SRS ,you will find all the regarding details about the project ,it also contains lists of
functionalities performed by the system.It also contains numbers of use cases for the
system,which specifies all the necessary functionalities & the persons who uses this project as
per their conventions.For better understanding of the project i would like to suggest first
understand what is the system,who are the intended user who will get the benefit regarding the
new system. After that please read the table & usecases for understanding the what kind of
functionalities has been performed by the each user of a system.

1.4 Document Conventions

In general this document follows the IEEE formatting requirements. Use Times New Roman font
size 11, or 12 throughout the document for text. Use italics for comments. Document text should
be single spaced and maintain the 1” margins found in this template. For Section and Subsection
titles please follow the template.

TO DO: Describe any standards or typographical conventions that were followed when writing
this SRS, such as fonts or highlighting that have special significance. Sometimes, it is useful to
divide this section to several sections, e.g., Formatting Conventions, Naming Conventions, etc.>
1.5 References and Acknowledgments
<List any other documents or Web addresses to which this SRS refers. These may include user
interface style guides, contracts, standards, system requirements specifications, use case
documents, or a vision and scope document.

TO DO: Use the standard IEEE citation guide for this section. An example citation guide is
posted for you on the website.>

2 Overall Description
2.1 Product Perspective
This product is used in the replacement of the existing system. Existing system is offline
system,which is only available throughout the limited area. Here I would like to develop a sytem
which will be available online & which has a global coverage area.
2.2 Product Functionality
There are various functionalities which should have been performed by the several users ,they
are as under:
 Monitor the System Online
 Apply for a leave
 Allow the distributor to allow the status of their application
 Issue a new tendors.
 Allow the new candidates to apply online for their career prosepective.
 Allow the employee to view & update their personal informations
 Here administrator should have a complete control over all the data of the system.

2.3 Users and Characteristics

There are certain levels through which we will specify the user of the system. Here we are
classifying the types of users based on their privillage to access the data. Description is as under:
 Privillage user:- Administrator
 Medieum privillage user:- Manager, Engineer
 Least privillage user:- Employee,Distributor,
 Naive user:- public, student etc.

2.4 Operating Environment

Software Requirements
 Operating system:- Windows XP & above.
 Browser:- Internet Explorer,Mozila etc.(Google chrome not supported)
 Software needed :-Adobe flash player
Hardware Requirements

 Processor:- Pentium-4 & above

 Ram:- 1 gb & above
 Graphic interface:- required

2.5 Design and Implementation Constraints

There is a some issues which will limit the options available to the users ,that are as under:
Hardware limitations:
i) it will need atleast 160GB harddisk to run the program
ii) Ram should by atlaeast 512 MB
iii) it should include graphics card.
iv) Hardware should be responded well to any kind of circumstances.

Software limitation
i) The developers should use visual studio 2005 & lateron
ii) Oracle should be version 9.0 or more.
2.6 User Documentation
Here for the user better using of the system,i would like to provide several features which will be
helpful for the user for better understanding of the system. Lists of the documents are as under:
 Manuals (In the pdf format)
 On-line help
 Tutorials for download( for high & medium privillage user)

2.7 Assumptions and Dependencies

There are some assumptions has been made while developing this system. The assumptions are
as under:
 All the employees knows the internal working of the system.
 Here the system(plant ) is using PLC automation system.
 Plant’s all data should be connected to the web server.
 3 Specific Requirements
3.1 External Interface Requirements
3.1.1 User Interfaces

Characteristics of each interface between the software product and the users is as under:
 Transitions time between live & online data should be very less.
 User should have a easy understanding of the system.
 All the standard conventions & symbols has been used while developing a system.

Here for the user the first page available to the user is a home page,in which there will be a
option for the login ,see the notifications ,list of tenders & career prospective. It also includes
news & several other options. Here when the user will be logged in based on the privillage of the
user several list of options to be displayed in front of the user based on their functionalities.

i) if the user is high privillage user then he has a right to view & do the modifications of the data
& features of the system.
ii) if the user has medium privillage user then he has a right to view & alter his own & his
department’s data & view the system’s current status but he can’t modify all the data without any
prior permission.

3.1.2 Hardware Interfaces

Hardware Recommended System Requirements

CPU - Speed <700 MHz>
RAM <256 MB>
Hard-disk Space <16 GB>
Network <Client Server Application>
Configuration

3.1.3 Software Interfaces

Front End <Visual Studio.Net 2005>

Back End <MS SQL Server 2005>
Operating System <Windows 2000+>
Third Party SDK
Tools/Libraries
Programming C#.net 2.0
Language
Project Technology ASP.net 2.0
Browser IE, Netscape, Mozilla, and Opera
Compatibility

3.1.4 Communications Interfaces

Here for the communication purpose we are including several mediums.They are as under:
 E-mail
 Sms
 Web browser
 Here all the data which has been sent ,is sended in the encrypted form.

3.2 Functional Requirements

Here there are several functionalities which should have performed by the system. They are as
under:
 Monitor the live status of the system
 View & modify the data
 Identify employee’s future in the organization
 Solve any problem regarding to the system.

3.3 Behaviour Requirements

3.3.1 Use Case View

i) For administrator login

ii) For admin

ii) For Manager

iii) For Engineer

iv) For general Employee

v) Customer
 4 Other Non-functional Requirements
4.1 Performance Requirements
There are various performace requirements which should have been followed.They are as under:

i) Time interval between online data & actual data will not be more than 10 seconds
ii) Message should have been delivered within 10 seconds.
iii) Message should have been sent in the encrypted form.
4.2 Safety and Security Requirements
Here for the safety prosepectus we have to follow some guidelines ,they are as under:
i) Message should have been delivered in the encrypted form.
ii) Some encrypted system should be followed while developing any system.
iii)Warning should be displayed if any person is doing any work above his privillage.
iv) set a time out period for a system for a specified privillage user.

4.3 Software Quality Attributes

There are some quality attributes which should have been followed while developing a system.
They are as under:
i) It should follow IEEE standard.
ii) It should be available globally.
iii) It should support all types of the data.
iv) it should be checking itself for updates at frequent time interval.
v) it should have a support to fight against a malicious attack.

DATA DICTIONARY

Types of Crude oil

Description
Data Description
Type_crude It represents the the type of crude oil based on
the amount of sulphur,iti is sweet,sour &
medium
 Location It shows the location from where the crude oil
has been imported
Cost\bareel It shows the standard price of crude oil (based
on the data from OPEC).It is in the $

It shows the description that which types of crude oil has been passed in which plant
Type Field Name Data Type Constraints

FK Crude_type Varchar2(10) Not Null

Plant1 Varchar2(20) Not Null
Date Date Not Null
Time in Time Not Null
Products Varchar2(20) Not Null
Time out Time Not Null

Data Description

Crude_type It shows the type of crude oil .

Plant1 It shows the plant name in which crude oil is first entered
Date It shows the date on which crude oil has been passed in the plant for
distillation
Time in It shows the the time at which crude oil has been entered into the
system
Products IT shows the outputs at different level
Time out It show the output time of different products

Products Information
Type Field Name Data Type Constraints

Products Varchar2(15) Not Null

Temparature Number Not Null
Viscocity Number Not Null
Density Number Not Null
Amount _Sulphur Number Not Null

Data Description
Data Description
Products It shows the list of components which is
distillated from the crude oil
Temparature IT is represented in degree Celsius
Viscocity
 Density
Amount _Sulphur It is the amount of sulphur presented in crude
oil

Ouput Delivered to plant for further refinements

Type Field Name Data Type Constraints
H1 Varchar2(10) Not Null
P2 Varchar2(10) Not Null
Delivered Time Time Not Null

Data Description
Data Description

H1 It shows the the name of heat exchanger

P2 It shows the plant name
Delivered Time It shows the time at which crude oil has been
entered into the plant

Employee information

Type Field Name Data Type Constraints

 Type Field Name Data Type Constraints
PK emp_id Int Not Null

emp_name Varchar2(10) Not Null

emp_dept Varchar2(10) Not Null

emp_designation Varchar2(10) Not Null

emp_address Varchar2(30) Not Null

Plant_name Varchar2(10) Not Null

Data Description
emp_id This field stores the identification number for
the specific employee. It acts as a primary key
for the table.
emp_name This field stores the name of the particular
employee in the company.
emp_dept This field stores the related department of the
particular employee in the company.
emp_designation This field stores the related designation of the
particular employee in the company.
emp_address This field stores the address of the employee in
the company.
plant_name This field stores the name of the plant, on
which it is working currently.

Log table
Type Field Name Datatype Constraints

Fk Employee_id Int Not Null

system_id Int Not Null
Mac_address Int Not Null
Session_id Int Not Null
Log_in_time Datetime Not Null
Log_out_time Datetime Not Null
Log_date Datetime Not Null
Data Description

System_id It contains the system’id through which user

has been logged in
Mac_address It contains the mac address of the system
through which user has been logged in
Session_id It is a id for a particular session for which user
has been logged in
Login_time It is a time when user enters into the system
Logout_time It is a time when the user logged out of the
system
Log_date It is a date about which the previous data has
been stored.