To: AFRIXAM BANK

Policy Management
SharePoint Module
Customer Requirement Specifications

Linked Gates
 Policy
Customer Requirement Ver.
Management 2.0
Specification No
SharePoint Module

Ver Date Author Summary of changes Reviewed Approved

by(Date) by(Date)
1.0 12-Sep-18 Michael Initialize the document Ahmed

Benyamine Mahmoud

(20-Sep-18)

2.0 20-Sep-18 Michael Do Ahmed Comments Omneia

Benyamine Shawky

(21-Sep-18)

1
 Policy
Customer Requirement Ver.
Management 2.0
Specification No
SharePoint Module

Table of Contents
1. Introduction ............................................................................................................................. 3
1.1. Document Overview ........................................................................................................ 3
1.2. Scope of software ............................................................................................................. 3
1.3. Definitions, Acronyms and Abbreviations ....................................................................... 4
1.4. References ........................................................................................................................ 4
1.5. Outstanding Issue ............................................................................................................. 4
.2 Overall Description ................................................................................................................. 4
2.1 Product Perspective and interfaces ................................................................................... 5
2.2 Product functions: ............................................................................................................ 5
2.3 User Characteristics.......................................................................................................... 6
2.4 Target Environment.......................................................................................................... 6
2.5 General Constraints .......................................................................................................... 7
2.6 Assumptions and Dependencies: ...................................................................................... 7
3. Specific Requirements ............................................................................................................ 7
3.1. Functional Requirements.................................................................................................. 7
3.1.1. Policy Manager ......................................................................................................... 7
3.1.2. Reading Policies........................................................................................................ 9
3.1.3. Reading Statists:.................................................................................................... 12
3.1.4. Policy Departments/Categories: .......................................................................... 14
3.1.5. Reports: .................................................................................................................. 14
3.1 None Functional Requirements ...................................................................................... 15
3.1.1 Operability .............................................................................................................. 15
3.1.2 Transferability ......................................................................................................... 15
3.1.3 Security Requirements ............................................................................................ 15
3.1.4 Maintainability Requirements ................................................................................. 15
3.1.5 Supporting Information ........................................................................................... 15

2
 Policy
Customer Requirement Ver.
Management 2.0
Specification No
SharePoint Module

1. Introduction
This CRS document captures African export-import bank’s requirements for new
SharePoint APP/Module to Track bank policies reading, The SP module Manage policy
and control it’s readings by employees in the bank.

1.1.Document Overview

 The objectives of this document are to

o Captures all needed requirements related to add new features at policy
management Module.
o Analyze the requirements and explain what has to be done.
 Following are the interested audience for this document:
o IT Department Team at African export-import bank.
o Operational Risk Manager .

1.2.Scope of software

 This module aims to manage policies and enable employees to read them after it is
uploaded by the admin. And the admin can track their tries to read with details. The
Module consist of three main parts:

 Policy Manager:

Is a control panel where admin can upload new document, mange it or delete it .

 Policy Reading:

A page where employees can pick a policy to read. The reading will be using an
embed PDF viewer.

 Policy Statistics:

Where admin can view some reports like what is document read and not read by a
specific employee and the hist reading details for each policy document like how
much he spent in each page in the current document .

3
 Policy
Customer Requirement Ver.
Management 2.0
Specification No
SharePoint Module

1.3.Definitions, Acronyms and Abbreviations

Term/Abbreviation Description
SP SharePoint
DB Database
* Mandatory
^ Calculated by the system
Table 1. Definition/Acronym/Abbreviation List

1.4.References

SN Reference name Document location

1.5.Outstanding Issue
 What if the policy admin updated the content of a policy, so how he can tell the employees
that this document shall be read again.
2. Overall Description

4
 Policy
Customer Requirement Ver.
Management 2.0
Specification No
SharePoint Module

Policy Management Module Upload New Policies

Update/Delete Existing Policy

Admin
Start

Monitor Reading Statistics &

Reports
Update Reading Statistics

Select Policy To read Navigate in Document pages

Start
Employee

2.1 Product Perspective and interfaces

 Policy Management Module shall contain three main screens first one is to upload
and manage policy document, second is to read the policy pdf document by the
employee and the third is to query reading statistics .

2.2 Product functions:

 Upload / Update / Delete policy documents and assign name, tag for each one.
 See change history for policy documents.
 Enable employee to read the policy inside SharePoint with custom PDF viewer.
 Enable admin to query policy reading details by more than filter :
o Filter documents not read by a specific employee.
o Filter documents that read by a specific employee and can see his reading
details for each read document.

5
 Policy
Customer Requirement Ver.
Management 2.0
Specification No
SharePoint Module

o Filter users that didn’t read a specific document

o Filter users that read a specific document and can see it is reading details
by each employee .

2.3 User Characteristics

SP Module shall provide the following user types:

User type User capabilities
Operates over all module page
Policy Admin Able to manage policies
Able to query reading statistics
Employee Able to read a policy document
Able to give permission of any user to see any of
SP Admin
the module pages

2.4 Target Environment

 Client Environment is:

 Browser: shall be compatible with internet explorer, and
Google chrome.
 Device: PC, tablet or mobile.
 Deployment Environment
o Hosting environment:
 Online SharePoint account that belongs to the bank.

6
 Policy
Customer Requirement Ver.
Management 2.0
Specification No
SharePoint Module

2.5 General Constraints

 All policy documents expected to be in PDF format only .

2.6 Assumptions and Dependencies:

 Employee supposed to be an any SP user.

 Reading Reports consider an employee read a policy if he tried to read at least one
page of the it’s document.
 Reading Reports consider an employee didn’t read a policy when he didn’t read
any pages of the it’s document

3. Specific Requirements

3.1.Functional Requirements

3.1.1. Policy Manager

3.1.1.1. Use Case

Upload Policy
Documents

Policy-Admin Update/Delete Existing

Policies

3.1.1.2. Description

7
 Policy
Customer Requirement Ver.
Management 2.0
Specification No
SharePoint Module

This screen is to allow Policy Admin to manage Policy Documents .

ID Policy-Manager Priority High

Name Manage Policy documents.
Description:  This page should allow the admin to upload policy
documents and update or delete it.
 Each uploaded policy shall have the following
information:
o Policy Title *: Subject or domain of the policy
o File Name ^: Name of the document
o Tags: Labels attached to each policy to facilitate
search later.
o Category *: What this policy belongs to. Used
to classify documents.
o Uploaded by ^: User that uploaded the
document
o Uploaded ^: Date when document uploaded.
o Modified By ^: User that modified the document
o Modified ^: Date of last modification
 The page shall list all existing policy documents grouped
by Category.
 The page shall enable filtering by all columns .

Page Main Functions:

1. Display list of all policy documents.
2. Upload new policy document.
3. Update / Delete properties of existing policy
document.

8
 Policy
Customer Requirement Ver.
Management 2.0
Specification No
SharePoint Module

Reference 

3.1.1.3. Mockup

3.1.2. Reading Policies

3.1.2.1. Use Case

9
 Policy
Customer Requirement Ver.
Management 2.0
Specification No
SharePoint Module

Search Policies

Update Statistics
<<include>>
Employee
Read Policy

3.1.2.2. Description
This screen is to allow employees list and read the Policy Documents .

ID Policy-Reader Priority Medium

Name Reading Policies
Description:  This page shall view list of all available policies for reading to
current employee.
 The list will be grouped by categories and has ability to
filter/search with all columns.
 Policy list shall contain the following columns:
o Policy Title
o Modified: Date of last modification
o My Last Read: (Date time can be null)
o Read :(Link to start reading)
 Employee can select to read any policy from the list.
 After hitting read link ,the page shall redirect to a page where the
PDF document will be explored it’s. Employee can navigate
through the using previous and next buttons.

10
 Policy
Customer Requirement Ver.
Management 2.0
Specification No
SharePoint Module

 In background the page shall record time spent in reading current

page and send it to update the reading statistics.
 That reading data that shall be sent is the following:
o Current User
o Current Document
o Current Page
o Time Spent
 User shall be able to exit and return back to the policy list and select
another policy to read .

Reference 
3.1.2.3.Mockups

11
 Policy
Customer Requirement Ver.
Management 2.0
Specification No
SharePoint Module

3.1.3. Reading Statists:

3.1.3.1. Description
Reading statistics for policy documents that read by employees.

ID Reading-Statistics Priority Medium

Name Reading Statistics

12
 Policy
Customer Requirement Ver.
Management 2.0
Specification No
SharePoint Module

Description:  This page shall allow admin to list all readings operations that don
for any policy by any employee.
 Each reading row shall contain the following:
o Employee Name
o Policy Title
o Total Spent Time
o Total Read Pages
o Last Reading (Date Time of last reading)
o Start Reading (Date Time of first read for this document)

 If admin press on total read pages, then he can shall view reading
details in another page / popup.
 Reading details shall contain the following:
o Page No
o Spent Time (spending time for reading this page in this
trail)
o Date (Date Time when start read this page in this trial)
 Page shall enable filter/Search by Policy Name , Policy Tags ,
Employee Name , Date From , Date To .

Reference 
Mockups :

13
 Policy
Customer Requirement Ver.
Management 2.0
Specification No
SharePoint Module

3.1.4. Policy Departments/Categories:

ID Policy-Categories Priority Medium
Name Manage Policy Categories
Description:  This page shall allow admin to manage Policy categories is a
lookup entity used in the policy manager screen .
 Each Policy Category row shall contain the following:
o Policy Category
Reference 

3.1.5. Reports:
ID Reading-Reports Priority Medium
Name Policy Reading Reporting
Description:  The module shall provide the following reports.
o Policies that have been read by specific employee.
o Policies that haven’t been read by specific employee.

14
 Policy
Customer Requirement Ver.
Management 2.0
Specification No
SharePoint Module

o Employees that read specific Policy.

o Employees that didn’t read a specific Policy yet.
Reference 

3.2. None Functional Requirements

3.2.1. Operability
o Usability :
Providing auto complete while search about employee or policy document.
o No. of languages:
Only English.
o Configuration values and ability for change:
N/A.

3.2.2. Transferability
 Portability :
o The module will be a set of web parts that can be installed and uninstalled easily.
o Internet Browser: IE and Chrome
3.2.3. Security Requirements
 API’s shall be secure and encrypted.
 Pages of Policy Manager and reading statistics shall be allowed only to the policy
admin.

3.2.4. Maintainability Requirements

N/A
3.2.5. Supporting Information
N/A

Approved By Position Signature

15