My Final Project (EDMS) Presentation

(EDMS)

Presented By : Riaz Ali Jamro Supervisor: Ms Bushra Almas

Electronic Document Management System

Introduction

Background (Existing System and Proposed System)

Scope

Requirement Analysis

System Diagrams

System Implementation

System Testing

User Interface

References

Contents

Introduction

The EDMS is a software system for organizing and storing different kinds of documents.

An Electronic Document Management System is designed to manage, store, distribute and archive documents.

Also Known as Content Management System.

It enables storage, retrieval, sharing, revision and distribution of documents and hence information and data they contain.

Existing System

The existing system is a file base system. Some drawbacks in existing system are given below:

Costly retention of duplicate information.

Costly waste of space to store files.

Lack of workflow for electronic documents.

Difficulty in locating documents.

Proposed System

The proposed system is web based system, have complete database on server.

Advantages of proposed system:

To prevent lost records. To save storage space. To make information safeTo manage records easily. To find document quickly.To makes document centrally available.

Scope• Electronic document management solutions are designed to organize business

files and records digitally.

• Document management solutions exist first and foremost to organize, store, and retrieve files accurately and efficiently.

• History of document creation and modification.

• Central to the document management advantage is access to information.

Requirement Analysis

Functional Requirements

Functional requirements capture the intended behavior of the system.

• Login • View/Add/Update/Delete Organization Level Chart• Add/Update/Delete/Assign Functionality Group and User Management.• Add/Update/Delete/View Folder.• Add/Update/Delete/View/Upload/Download/Compress/Email File• Search on Organization Hierarchy Chart.• Logout

Non-Functional Requirements

• Usability:

The system should be understandable for the ease of user.

• Speed

All the queries, commands and other data operations should be

complete within seconds

• Security

How roles and rights between administrator and a user are managed.

Use Case Diagram

erer

System Diagrams

Activity Diagram Entity Relationship Diagram Class Diagram

Activity Diagram: Login

Activity Diagram:

erer

Class Diagram

ER Diagram : User Level Relationship

ER Diagram: Folder and File

Implementation

Implementation

Developed in ASP.NET by using C#.

HTML , JavaScript and CSS is used for to design interface.

Database is maintained in SQL Server that stores the records.

Architecture Diagram

1. Presentation Layer

2. Business Logic Layer

3. Data Access Layer

System Testing

Test Cases:A test case is a document that describes the procedure to test the system.

•Add/Delete Level•Assign Level Rights

System Testing

Testing is to:

• Verify that it behaves as “specified”

• Detect Errors.

Test Case :Add/Delete LevelTest Case ID TC003

Tester Riaz Ali

Test Type Manual Black Box

Test Case Name Add/Delete Level

Description This test checks whether level is added/deleted to the database in or not.

Procedure Login

Mouse over Admin, Select Level. Only Admin can Add and Delete the level of

the organization hierarchy. For adding level click on “Add Level”, for deleting

click on “Delete Level”.

Test Data Scenario 1: Scenario 2:

Select Add Level: Delete Level.

Expected Result The level is added/deleted in the database.

Actual Result Level is Successfully Added and Deleted.

Status Success

Test Case :Assign Level RightsTest Case ID TC005

Tester Riaz Ali

Test Type Manual Black Box

Test Case Name Assign Level Rights

Description Check whether level rights are assign to user or not.

Procedure Login

Click on Admin, Select User Management. Only admin can assign level right to

the user. For Assign Level Rights Click on “Assign Level Rights”.

Expected Result Level Rights are Assigned Successfully

Actual Result Level Rights Assigned Successfully.

Status Success

User Interface: HOME page

Organization Level Chart

Search

References:1. Roger S. Pressman Software Engineering: A practitioner’s Approach. 2. Software Engineering (8th edition) Ian Somerville. 3. SAMS teach yourself ASP.NET. 4. Dhirendran Pandey, U.Suman, A.K Ramani (2010).An Effective Engineering Process Model for Software Development and Requirements Management.

1. http://www.uml-diagrams.org/ 2. http://www.w3schools.com/aspnet/default.asp 3. http://www.slideshare.net/ 4. http://www.codeproject.com/Articles/11128/3-tier-architecture-in-C 5. http://www.wikipedia.org