SRS

SYSTEM REQUIREMENTS SPECIFICATION
FOR
<NAME OF THE SYSTEM>

<NAME OF THE COMPNAY>
Prepared By: <Who created this document>

Date Created: <date started>
Last Update: <Last updated>
Version: <Versions of creation>
Reviewed By:
<Personnel you have interviewed>
Recommending Approval:
Members
Members
Members
Members
Members
Approved By:
Thom Christian Makiling

<Course/s of each member>
<Subject Description> Reference No: <Project Number>
Input Logo of the Revision No: 01
company System Requirements Specification
Date Created
<Name of the System> Date Updated:
Page 2 of xx
DOCUMENT CONTROL
Change Record
DATE AUTHOR DOCUMENT CHANGE REFERENCE

VERSION
Member 2.1 <Identify all the changes>

Member 2.2
Member 2.3
Member 2.4
Member 2.5
Distribution
Copy No. Name Location
1
2
3
4
Filename: Name of this Document --COMPANY CONFIDENTIAL --

ICCT Colleges Foundation Inc.
Date Created
Page 3 of xx
DOCUMENT CONTROL..................................................................................................................... 2
CHANGE RECORD...........................................................................................................................................2
DISTRIBUTION............................................................................................................................................2
1. SYSTEM HISTORY....................................................................................................................... 4
2. SYSTEM DEFINITION................................................................................................................. 4
3. OBJECTIVES.................................................................................................................................. 4
4. SCOPE AND SYSTEM CONTROLS.............................................................................................. 4
5. INTENDED USERS....................................................................................................................... 4
6. GENERAL ASSUMPTIONS AND POLICIES..............................................................................4
7. CURRENT PROCESS FLOW....................................................................................................... 5
7.1 <NAME OF THE PROCESS FLOW>.........................................................................................................5
8. TO-BE PROCESS FLOW............................................................................................................... 5

8.1 <NAME OF THE PROCESS>..................................................................................................................5
9. NARRATIVE OF PROCEDURES.................................................................................................. 5
10. <SYSTEM> FRONT-END.......................................................................................................... 6
10.1 LOGIN SCREEN...................................................................................................................................6
10.2 USER MAIN SCREEN.............................................................................................................................7
10.XX SYSTEM MAINTENANCE: MANAGE USER ACCOUNTS...................................................................................10
11. <SYSTEM> REPORT GENERATION.....................................................................................12
11.1 <NAME OF MODULE/REPORT> REPORT...........................................................................................12
13. NON-FUNCTIONAL REQUIREMENTS..................................................................................13
13.1 ENVIRONMENT.................................................................................................................................13
13.2 AVAILABILITY...................................................................................................................................13
13.3 MAINTENANCE..................................................................................................................................13
13.4 SECURITY AND ACCESS CONTROL.....................................................................................................14
13.5 SERVICE CONTINUITY.......................................................................................................................14
14. SYSTEM-GENERATED ID/CODE CONVENTIONS..............................................................15
15. TERMINOLOGIES.................................................................................................................... 15

Date Created
Page 4 of xx
1. SYSTEM HISTORY
System Name:
Version Number: 1.0
Target Date:
Date Started: June 16, 2010
Steering Committee:
 Mr. Sean Oliver G. Meclat
Functional Team Members:

 Members
Technical Team Members:

 Members
2. SYSTEM DEFINITION
3. OBJECTIVES
4. SCOPE AND SYSTEM CONTROLS
5. INTENDED USERS
6. GENERAL ASSUMPTIONS AND POLICIES

Date Created
Page 5 of xx
7. CURRENT PROCESS FLOW
7.1 <Name of the process flow>
Fig. 7.1 – <Process Flowchart>
8. TO-BE PROCESS FLOW
8.1 <Name of the Process>
Fig. 8.1a <Image of the Process flow>
9. NARRATIVE OF PROCEDURES

Date Created
Page 6 of xx
10. <SYSTEM> FRONT-END
10.1 Login Screen
Primary Function(s):
This screen will serve as the User’s main entry point to the system. The user should fill in the required
Username and Password.
Upon user login, the ff. will be retrieved based on their user accounts:
 As an employee
 Already added in the user’s maintenance
The entry screen will include the ff.:

 Username
 Password
Contributing Function(s):
o Provide descriptive warning and error messages when exceptions occur.
General Validation(s):
o Username and password should exist in the database (employees).

o User must have access rights to the system.
o User’s access rights should not be expired.
Output:
Allow access to various modules of the system based on the user privileges and/or permission/s granted
to the user.

Date Created
Page 7 of xx
<Put image of the login screen>

Fig. 10.1 Login Screen
Source
Input Data Description Validation
Type
 Required value
Username based on the  Valid username
User Name existing record in User Manual entry  User Account
maintenance  System User Account and
Privileges
 Required value
Password as defined in user
 Valid username
Account
Password Manual entry  User Account
 System User Account and
Privileges
Validates the User Name and
Password inputted.
Returns the User Accounts list
 Valid User Name
of values in the dropdown list Button
 Valid Password
provided.
Gains access for the user’s list
of account.
Clears previously inputted
values in the User Name and Button
Password fields.
 Enabled only, when there
is more than one User
Account
Button
 Should have selected one
account to be able to
proceed.
Output Description Output Report

Data
Access to the  User’s Access/Privileges N/A
system
10.2 User Main Screen
The User Main Screen is the initial screen that will be shown upon login to the System.

Date Created
Page 8 of xx
It serves as a display, retrieval and monitoring of transactions.

For each type of user, the tabular display and records retrieved varies per access.
It also contains a search tool which is accessible by all types of user.
The User Main screen will vary depending on the logged-in User Type identified as follows:
 <Identify the user types and its specific responsibility>
The User Main Menu, which will also vary depending on the logged-in User Type and corresponding access
type, are as follows:
 <identify the menu’s>
Menu User 1 User 2 User 3 User 4 User 5 User 6
Home      
Transaction 1    
Transaction 2   
Transaction 6  
Transaction 7  
Transaction 9 
Log-off      
The User Main Screen Functions and access for modules will vary depending on the logged-in User Type
and access:
 User Main Screen/Home Page

 Transactional Screens
MODULES User 1 User 2 User 3 User 4 User 5
Module 1     
Module 2     
Module 3   

Date Created
Page 9 of xx
The User Main Screen Tab and functionality will vary depending on the logged-in User Type and access:
 User 1
 <Identify what type of user>
USER MAIN SCREEN MENU FUNCTIONS REQUEST TYPE
 User 2
 <Identify what type of user>
USER MAIN SCREEN MENU FUNCTIONS REQUEST TYPE
o Display and retrieval of all Requests in a data grid showing transactions filtered based on the currently
logged in user.
o Depending on the menu function -
o User’s Search Functionality –
o View Transaction History –
o Provide descriptive warning messages for all exceptions that may occur.
o Provide confirmation messages when deleting, canceling and saving.
o Access rights on system modules classified per User Type

o Menu display identified per User Type
o User’s access rights per module should not be expired.
Output:

Date Created
Page 10 of xx
List of Requests filtered based on the current user, current tab, and/or the search criteria given in the
search fields.
Fig. 10.2a User Main Screen <Provide all screenshots per usertype>
Input Data Description Source Type Validation

Tab function as retrieval and
displaying of  See definition matrix in
User Main Tab Menu tab
requisitions/transactions given Primary Functions section
the User Type and Access.

10.xx System Maintenance: Manage User Accounts
This screen will serve as the maintenance of user account privileges used by the system as reference or
look-up for the User Account values and modules access.
o Data Grid listing all user accounts with privileges records.

o Add record – complete required field entry.
o Edit record – edits the selected record
o Provide descriptive warning messages for all exceptions that may occur.
o Provide confirmation messages when saving.
o Only the system admin account can access this module and will be hidden from all other users.
o Maintain referential integrity. Do not allow deletion if User Account if is used/saved in any
transactional table – current and historical that uses it.
Output:
User Access and System Privileges as referential look-up for modules access/rights per User Account
Fig. 10.13a System Maintenance – User Privileges Screen <provide a screenshot>

Date Created
Page 11 of xx

 Required field
<table and
 Values derived from User
User Name Lists all User Names database
Names from employees record
name>
to users Accounts
Add selected User Name and
Account to the User Accounts Button
List
Disregard any changes made and
Button
closes the entry for update
User ID Assigned User ID Display
User Name User Name or Profile Name Display
User Account User Account Display
Account Type User Account Type Display
Opens input fields for updating. Link/Button

Date Created
Page 12 of xx
11. <SYSTEM> REPORT GENERATION
11.1 <Name of Module/Report> Report
Fig. 11.1a <name of module> Report Input Parameter Screen

 
 


Report Specifications:
 <specify all the reports needed>

Date Created
Page 13 of xx
13. NON-FUNCTIONAL REQUIREMENTS
13.1 Environment
Server Requirements
Hardware Requirements:
 <Identify the hardware needed (harddisk, memory, processor, etc)>
Software Requirements:
 <Identify the software needed (operating system, crystal reports, etc.)>
Speed of network access:
Type of network access:
13.2 Availability
Application availability requirement:
Service availability :
Service Level Commitment :
13.3 Maintenance
Data back-up
 On-site/Offsite back-up
Data/files needed to be back-up

 Database (ORS)
Frequency of back-up
 Full Backup (Every Sunday)
 Differential Backup (Every night)
 Transactional Backup (Every 2 hours)

Date Created
Page 14 of xx
13.4 Security and Access Control
Position/ User Type Modules Access Type

Function
System Administrator Identify the modules Full
Administrator Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Granting of access
 <Identify on how a user can be given an access>
Changing, canceling of access
 <Identify on how to cancel a user’s access>
13.5 Service Continuity
How long business can operate without the system?

 <Identify>
Estimated lead time to set up system (based on latest back-up)?

 <Identify>
Who will be involved in the recovery procedures (process owners)?

 <Identify>
Where the system can/will operate upon recovery?

 <Identify on how the system will work on the company>

Date Created
Page 15 of xx
14. SYSTEM-GENERATED ID/CODE CONVENTIONS
CODE DESCRIPTION FORMAT SAMPLE VALUE(S)

EMPNO Employee number The first 4 digit is the year and 19973621
the remaining digit is the auto
generated number assigned to
an employee
15. TERMINOLOGIES
ACRONYMS/TERMS DESCRIPTION


SRS

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

SRS

Enviado por

Direitos autorais:

Formatos disponíveis

SYSTEM REQUIREMENTS SPECIFICATION

<NAME OF THE SYSTEM>

Prepared By: <Who created this document>

Thom Christian Makiling

DATE AUTHOR DOCUMENT CHANGE REFERENCE

Member 2.1 <Identify all the changes>

Copy No. Name Location

Filename: Name of this Document --COMPANY CONFIDENTIAL --

8. TO-BE PROCESS FLOW............................................................................................................... 5

Filename: Name of this Document --COMPANY CONFIDENTIAL --

Functional Team Members:

Technical Team Members:

4. SCOPE AND SYSTEM CONTROLS

6. GENERAL ASSUMPTIONS AND POLICIES

Filename: Name of this Document --COMPANY CONFIDENTIAL --

7. CURRENT PROCESS FLOW

7.1 <Name of the process flow>

Fig. 7.1 – <Process Flowchart>

8. TO-BE PROCESS FLOW

8.1 <Name of the Process>

Fig. 8.1a <Image of the Process flow>

Filename: Name of this Document --COMPANY CONFIDENTIAL --

10. <SYSTEM> FRONT-END

10.1 Login Screen

The entry screen will include the ff.:

o Provide descriptive warning and error messages when exceptions occur.

o Username and password should exist in the database (employees).

Filename: Name of this Document --COMPANY CONFIDENTIAL --

<Put image of the login screen>

Output Description Output Report

10.2 User Main Screen

Filename: Name of this Document --COMPANY CONFIDENTIAL --

It serves as a display, retrieval and monitoring of transactions.

 <identify the menu’s>

Menu User 1 User 2 User 3 User 4 User 5 User 6

 User Main Screen/Home Page

MODULES User 1 User 2 User 3 User 4 User 5

Filename: Name of this Document --COMPANY CONFIDENTIAL --

USER MAIN SCREEN MENU FUNCTIONS REQUEST TYPE

USER MAIN SCREEN MENU FUNCTIONS REQUEST TYPE

o Access rights on system modules classified per User Type

Filename: Name of this Document --COMPANY CONFIDENTIAL --

Input Data Description Source Type Validation

10.xx System Maintenance: Manage User Accounts

o Data Grid listing all user accounts with privileges records.

Fig. 10.13a System Maintenance – User Privileges Screen <provide a screenshot>

Filename: Name of this Document --COMPANY CONFIDENTIAL --

Input Data Description Source Type Validation

Filename: Name of this Document --COMPANY CONFIDENTIAL --

11. <SYSTEM> REPORT GENERATION

11.1 <Name of Module/Report> Report

Fig. 11.1a <name of module> Report Input Parameter Screen

Input Data Description Source Type Validation

Filename: Name of this Document --COMPANY CONFIDENTIAL --

13. NON-FUNCTIONAL REQUIREMENTS

Speed of network access:

Type of network access:

Application availability requirement:

Service Level Commitment :

Data/files needed to be back-up

Filename: Name of this Document --COMPANY CONFIDENTIAL --

13.4 Security and Access Control

Position/ User Type Modules Access Type