Change Request Document: Adding Announcement Feature to the Bank's LMS

Background: As part improvement and enhancement of the bank's Learning Management System
(LMS), there is a requirement to integrate a digital library feature. This feature will allow users to
access various documents related to the bank’s operations and policies seamlessly. The digital library
aims to improve accessibility, searchability, and management of documents within the LMS platform.
Objective: The objective of this change request is to enhance the existing LMS by adding a
announcement feature, enabling users to browse, search and manage documents effectively.

Proposed Features:
For Authors (Content Creator/Administrators):
1. Document Type Management:
Ability to create and manage Document Types as master data for the application.
Document Types will appear as a dropdown menu while creating a document, allowing
authors to categorize documents effectively.
Estimation: 2 Weeks

Comments: This involves creating functionalities to manage document types, including UI

design, backend API development, and database integration.

2. Document Upload:
Capability to upload documents in various formats (text, ppt, pdf, excel, etc.).
Option to attach appropriate metadata such as title, description, department, category,
permissions, and Document Type.

Estimation: 2-3 Weeks

Comments: Developing the functionality to upload documents in various formats with

metadata handling. This includes integrating with the frontend, backend API development,
Database changes, and ensuring proper validation.

3. Document Publishing:
Flexible to publish all access levels (e.g., Regions, Circles, departments-etc.

Estimation: 2 Weeks

Comment: Implementing the feature to publish documents across different access levels
involves creation of frontend screens, backend API creation, Database changes and
integration with the existing permission system.
4. Document Management:
Functionality to archive documents that are no longer relevant or valid.
Option to extend documents' validity period if necessary.
Ability to modify documents.

Estimation: 2-3 Weeks

Comments: Developing the document management capabilities, including archiving,

modifying, and extending document validity. This involves both frontend and backend
changes and DB changes.

5. Metadata Management:
Tools to manage metadata associated with documents, including editing, updating, or
metadata fields.

Estimation: 2-3 Weeks

Comments: Building tools to manage metadata associated with documents. This includes
creation of UI screens, backend API development, and database changes.

6. Download Restriction Flag:

Introduction of a flag during document creation where authors can specify whether the
download of the document should be restricted or enabled.
Authors can set this flag based on the sensitivity or confidentiality of the document.

Estimation: 1-2 Weeks

Comments: Introducing a flag for download restriction involves UI changes, backend API
changes etc.

For End Users:

1. Document Access:
 Seamless access to the digital library from within the LMS interface.
Browsing, viewing, downloading, and printing documents in different formats.

Estimation: 1-2 Weeks

Comments: Implementing seamless access to the digital library from within the LMS
interface involves frontend changes and potentially extending backend APIs to facilitate this
integration. Browsing, viewing, downloading, and printing functionalities will also need to be
developed separately on the frontend and backend.

2. Advanced Search:
Advanced search functionality allowing users to search documents by keywords, titles,
departments, categories, or Document Types.
Filters to refine search results based on relevance, date, or document type.

Estimation: 1-2 Weeks

Comments: Developing an advanced search functionality requires frontend enhancement for

the user interface and backend enhancements for efficient searching. This includes
implementing keyword, title, department, category, and Document Type search options and
others. Additionally, filters for refining search results based on relevance, date, or document
type need to be developed and integrated.

Reporting:
Implementation of a "Mark as Read" button for end users to indicate their interaction with documents.
Estimation: 1 Week

Comments: Implementing the "Mark as Read" button for end users involves frontend
development to create the button within the document interface. Additionally, backend API
enhancements are needed to capture and record user interactions.

Records of end clicking the "Mark as Read" button, will be captured in reports.

Estimation: 1 Week

Comments: Creating reports on end users clicking the "Mark as Read" button requires
backend development to capture and store these interactions on the database. Additionally,
frontend changes may be necessary to display relevant information to administrators or users
with reporting privileges.