Functional Specifications Document

RBL SBL
Functional Specifications
Document
<Version No. 1.0>
April 2015
Functional Specifications Document

Functional Name
Project Name: RBL SBL
Project Reference #:
Functional Ref. #:
Soft Copy Name:

Version No.:
Date: 24-Apr-15
Version Control
Version
Published
(softcopy)
Date
1.0
Author(s)
Sections
Description of Changes
Changed
Aman Garg
New Document
Information contained herein is for internal use and may be used only for business purposes authorized by Max Life Insurance Co. Ltd.
TM-FSD-01 Ver. 3.0
11
Business Private (when filled), Business Confidential (when not filled) Page 2 of
Approvals
Approving Authority
Name
Author
Aman Garg
Signature
Date
Sr. Business Systems

Analyst
Business Unit Head
User
Information Security Head
TM-FSD-01 Ver. 3.0
11
Table of Contents
Version Control________________________________________________________________________________2
Approvals____________________________________________________________________________________3
Table of Contents______________________________________________________________________________3
1.
Background_______________________________________________________________________________3
1.1.
2.
Business Requirement and Objectives_____________________________________________________3
System/Module Overview____________________________________________________________________3
2.1.
Features In-scope______________________________________________________________________3
2.2.
Out of Scope__________________________________________________________________________3
2.3.
Assumptions__________________________________________________________________________3
2.4.
Hardware and Software Platform________________________________________________________3
2.5.
Proposed Workflow____________________________________________________________________3
3.
SPECIFIC FUNCTION DESCRIPTIONS______________________________________________________3

3.1.
<Function Name>______________________________________________________________________3
3.1.1.
Description________________________________________________________________________3
3.1.2.
Inputs____________________________________________________________________________3
3.1.3.
Processing________________________________________________________________________3
3.1.4.
Outputs___________________________________________________________________________3
3.1.5.
Technical Change___________________________________________________________________3
3.1.6.
Cross Functional Impact_____________________________________________________________3
3.1.7.
Interface Considerations_____________________________________________________________3
4.
Migration Requirements_____________________________________________________________________3
5.
Performance Requirements__________________________________________________________________3
6.
SIC Considerations_________________________________________________________________________3
7.
System Requirements_______________________________________________________________________3
8.
Security Requirements______________________________________________________________________3
8.1.
Password Policy Requirement__________________________________________________________3
8.2.
Unique user ID_____________________________________________________________________3
8.3.
User Management Audit Trails_________________________________________________________3
8.4.
User Transactional Audit Trails_________________________________________________________3
8.5.
Role Based Authorization_____________________________________________________________3
8.6.
Principal of Least privileges___________________________________________________________3
8.7.
Session Management_________________________________________________________________3
8.8.
Input/Output validations______________________________________________________________3
8.9.
Buffer overflow validations___________________________________________________________3
8.10.
Disabling Directory browsing__________________________________________________________3
8.11.
Separate business logic, database and web layers physically and logically_____________________3
8.12.
Error handling mechanism to prevent system from throwing default error messages_______________3
8.13.
NDA, contract and AMC signed with the business partner___________________________________3
8.14.
Baseline, Installation and Recovery documentation________________________________________3
8.15.
Separate Testing, Development and Production Environment________________________________3
TM-FSD-01 Ver. 3.0
11
8.16.
9.
Operating System Hardening__________________________________________________________3
Testing Considerations______________________________________________________________________3
9.1.
System Testing Scope___________________________________________________________________3
9.2.
Testing Scenarios______________________________________________________________________3
10.
Traceability matrix_______________________________________________________________________3
11.
Reference Documents_____________________________________________________________________3
12.
Open Items_____________________________________________________________________________3
13.
Glossary________________________________________________________________________________3
14.
Appendix_______________________________________________________________________________3
TM-FSD-01 Ver. 3.0
11
1. Background
1.1. Business Requirement and Objectives
Describes briefly why the system/module is being developed, and lists the most important
features and capabilities. This should be directly imported from the business requirement
document and expanded upon if necessary. Please revise the objective if the original
requirement was unclear or has been altered by the approach taken.
TM-FSD-01 Ver. 3.0
11
2. System/Module Overview
2.1. Features In-scope
Provide list of the functions that the system/module will be required to perform. Where a
feature comprises several functional capabilities, a table may be developed to illustrate
these relationships.
2.2. Out of Scope

This section describes the exclusions from the scope of this functionality
2.3. Assumptions
Lists any assumptions that were made in specifying the functional requirements
2.4. Hardware and Software Platform

(List the hardware and software platform proposed for the system.)
2.5. Proposed Workflow

(Show a helicopter view of the proposed system/module)
TM-FSD-01 Ver. 3.0
11
3. SPECIFIC FUNCTION DESCRIPTIONS

(Make a laundry list of all the functions with brief description not more than a sentence or
two. This will help ensure that all the functions have been captured in the document and
considered for the next stage System Design.
Some examples of functions are:
calculations, sorting or sequencing, other operations relating inputs to outputs, validity
checks on inputs, error handling and recovery)
S
No.
Function Name
Brief Description
3.1.
3.2.
3.3.
3.4.
3.5.
3.6.
3.7.
The following section should be repeated for each function of the system/module. That is,
create a subsection for each function name
3.1. <Function Name>

3.1.1. Description
Describes the function and its role in the system/module. The detail information for each of
the changes will be included in the Appendix in sub documents, but each component should
also be described here in general with a description of how they fit together to meet the
business requirements. Sub-sections can also be created to separate changes into client
changes and server changes if that makes it more understandable. For ease of reading/flow,
include any screen designs in the Appendix.
3.1.2. Inputs
Describe the inputs to the function. Examples include
New screens and input documents or continued use of existing screens and input
documents - Where user interface (UI) elements are present, these should be described.
Examples of UI elements are check boxes, buttons, hyperlinks, dropdown lists, and
alphanumeric fields. This is usually best done via simulated, non-functioning screen
shots (such as PowerPoint slides), and may take the form of a separate document,
attached as appendix. The navigation flow of the windows, menus, and options is
described, along with the expected content of each window.
Information and storage
Field types (e.g. character (string), number (integer, decimal), memo, data, time)
Keyboard shortcuts
TM-FSD-01 Ver. 3.0
11
Error and alert situations and user responses to correct the situation. Give details about
the validations, as appropriate.
The type of popup box to be displayed.

The wording of the error messages. E.g. You havent saved the new data. Do you really want to log out?
Consistency of messages.
Relevance to the current screen.
Display all messages on one popup or each one separately
Parameters (e.g. screen resolutions, field colors, font size and colors)
3.1.3. Processing
Describe what is done by the function. Examples include Input verification, Reconciliation,
Balancing, Exception reporting, Manual controls, Output validation. Where algorithms,
equations, or other logic are used, they should be described here. If calculations are
required, formulas should be mentioned. Database definitions should be also included where
relevant. Whether the process should occur on-line or automatically in batch, or both should
be specified.
3.1.4. Outputs
Describes the outputs of the function. Where a user interface description is relevant, it is
included. Reports generated are also defined.
3.1.5. Technical Change

This section describes the technical changes to be made in the functionality. This is usually
developed with inputs from the Technical Team.
3.1.6. Cross Functional Impact

If the implementation of this function is dependent upon the implementation of any other
function, simply mention the reference number here. A very brief rationale may be given to
explain the reason they are related (if it is not immediately apparent). If no related
functions, state No related functions
3.1.7. Interface Considerations

Describe or list the interfaces to/from other systems that impact this function, or that this
function impacts. Description of the information flow via the interfaces will be outlined in
the Processing section. If no interface considerations, state No interface considerations.
TM-FSD-01 Ver. 3.0
11
4. Migration Requirements
Describes migration requirements (data fixes) required for the function.
5. Performance Requirements
Discuss items such as response times, throughput requirements, data volume requirements,
maximum data file size or problem complexity, maximum number of concurrent uses, and
peak load requirements (for web-based applications). Include expected response times for
entering information, querying data files and databases, performing calculations of various
complexities, and importing/exporting data.
6. SIC Considerations
Describes SIC considerations required for the function.
7. System Requirements
This section should contain details about system access and capacity, including:
desired hours of operation - Describe requirements items such as days or weeks of

continuous operation,
security requirements - Describe any password-protected access levels such as data
center operator, developer, configuration manager, database administrator and which
functionality will be accessible to each access level and to whom.
backup frequency
disaster recovery
8. Testing Considerations
List the functional acceptance criteria or attach the functional test plan
9.1.
System Testing Scope
Define the system testing scope for this functionality
TM-FSD-01 Ver. 3.0
11
9.2.
Testing Scenarios
Describe unique testing constraints or situations, e.g., the functionality is only tested as part
of the period batch cycle testing process; or ensure that the premium calculations are
tested. Ensure all testing scenarios are identified and captured.
9. Reference Documents
Including list of documents linked with this document
10. Open Items

List the open points pending for closure
S.No
.
Description
Pending With
Target Closure
Date
11. Glossary
List and explain the various acronyms and abbreviations used in the document.
12. Appendix
Including sub documents created for User Interface Designs, Report Formats, and Document
Formats
TM-FSD-01 Ver. 3.0
11

Functional Specifications Document

Uploaded by

Document Information

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

Functional Specifications Document

Uploaded by

Copyright:

Available Formats

RBL SBL