EDMS

Nathan Budhu - 1040656 Shafeek Hiraman - 1040961

Akeem Headley- 1039587 Monipha Sagon- 1040135 Adam Singh- 1041493

PRESENTATION

CSE2101

Semester Project

System Testing

System Design

Software Requirements Specification

Project Plan

04

03

02

01

Index

Problem

01

Unseure handling of files

Searching and indexing is difficult

Time consuming manual document handling

GBTI is a commercial bank in Guyana that suffers from high time-consuming document processing procedures. Handling documents manually in a bank can be a very time consuming and an error prone process. It can be difficult to keep track of all the paperwork, as well as to ensure that all documents are properly filed and stored in an organized manner. Additionally, manual document handling can lead to a lack of data security, with sensitive documents being at risk of being lost or stolen.

Problem

01. Problem

Solution

02

The use of an electronic document management system in a bank can solve the problem. It provides a secure and efficient way to store, track and manage documents related to customer accounts, bank operations, and regulatory requirements. This system helps to ensure compliance with laws and regulations, improve customer service, and streamline operations. It also helps to reduce costs associated with storage and retrieval of physical documents, as well as reduce paperwork and manual processes.

Solution

02. Solution

Feasibility and Risk analysis

03

Pros:

• Improved document security, with access control and authentication measures in place
• Increased document organization and accessibility
• Enhanced collaboration among bank departments
• Greater efficiency in document management processes

• Initial setup and training costs
• Potential difficulties in transitioning existing processes to the new system
• Potential compatibility issues with existing systems

Feasibility

03. Feasibility

High Risk:

• Data loss from malicious attacks or hardware failure
• Possible incompatibility with existing systems
• Organizational restructuring
• Code issues
• Quality Risk

• Potential for errors in data entry or document management
• Difficulty in transitioning existing processes to the new system
• Staff illness

Risk Assessment Outcome

03. Risk Assessment Outcome

Low Risk:

• Organizational financial problems

Risk Assessment Outcome

03. Risk Assessment Outcome

Software Requirements Specification

04

1. The system must have user registration and authentication. 2. The system must allow the management of user roles and groups. 3. The system must have secure storage of documents. 4. The system must have the ability to index documents. 5. The system must have the ability to upload documents into the system. 6. The system must have the ability to add, edit, and delete documents. 7. The system must allow a user to save documents. 8. The system must have the ability to create, rename, lock and delete folders. 9. The system must have the ability to search for documents. 10. The system must have the ability to assign document access permissions. 11. The system must have document version control. 12. The system must have the ability to annotate documents. 13. The system must have the ability to integrate with other systems. 14. The system must have the ability to view reports.

Functional Requirements

04.Functional Requirements

Usability: The system shall be easy for users to understand and use. Security: The system shall ensure that user authentication is required to access the system and its data. Reliability: The system shall be reliable and provide consistent performance. Availability: The system shall be available 24 hours a day, 7 days a week with the exception of maintenance. Performance: The system shall allow users to access the system with a response time of less than 5 seconds. Scalability: The system shall be able to handle increased traffic and data load. Auditability: The system shall be able to generate audit reports to ensure compliance with internal policies and external regulations.

Non-Functional Requirements

05.Non-Functional Requirements

System Design

05

05.Context Diagram

Product / Service

05. Use Case Diagram

Product / Service

05. Class Diagram

INFO

A repository architecture for document management system for a bank is an important tool for managing and archiving documents related to the banking industry. This type of architecture allows for the organization, storage, and retrieval of documents in a centralized location. It also enables the bank to quickly and easily access documents when they are needed. Repository architecture also allows the bank to create and maintain a consistent set of standards and procedures for all documents, ensuring that the documents are organized and stored in a secure, consistent, and efficient manner. Additionally, it enables the bank to track and monitor all documents, ensuring that all documents are properly managed and archived.

Repository architecture

05. Repository Architecture

System Testing

06

Functional Reqiurement: The system should be capable of using the ID and password as login authentication. Test case ID: TC_LOGIN_001 Test priority: High Test Title/Name: Verify the login page with a valid ID and password Summary: This test case is used to verify that the user is able to successfully log in to the application using valid credentials. The test will validate that the user is able to successfully enter their ID and password, and that the correct page is loaded after the login is successful. Pre-conditions: Users must be registered. Dependencies: • Simple Mail Transfer Protocol (SMTP) for email alert to administrator. • The test is dependent on the login form being available and the server being able to accept login requests.

Test Case

06.System Testing

06.System Testing

06.System Testing

Questions?