Document Management System Report
Document Management System Report
A MINI-PROJECT REPORT
ON
Submitted by
CERTIFICATE
Certified that the project work entitled “DOCUMENT MANAGEMENT SYSTEM”
carried out by AMALE VEDIKA RAVINDRA [1SG18IS006], GOUTHAMI V
KULKARNI [1SG18IS038] bonafide students of 6th semester, department of Information
Science & Engineering carried out at our college Sapthagiri College of Engineering,
Bengaluru in partial fulfillment for the 6th Semester BE, FILE STRUCTURES Mini-Project-
18ISL67/17ISL68 by Visvesvaraya Technological University, Belagavi during the year
2020-21. It is certified that all corrections/suggestions indicated for Internal Assessment have
been incorporated in the Report deposited in the departmental library. The project report has
been approved as it satisfies the academic requirements in respect of Project work prescribed
for the said Degree.
External Viva
Name of the Examiners Signature of the Examiners with date
1. …....…........................ 1. …........................................
2. …....…........................ 2. …........................................
ABSTRACT
Document management is the process of handling documents in such a way that information
can be created, shared, organized, and stored efficiently and appropriately. This is a simple
project called Document Management System.
This web application is developed using PHP/MySQLi. The main purpose of this project is to
store and manage the file documents of a certain company or organization. The system stores
the documents in the database as BLOB type. Talking about storing the documents in the
database, the system also stores another file information such as the file type and file size.
The files that’ve been stored in the database will be shown in the File List Tab of the system.
Each file shown in the list has 2 actions that can be done by the user which are the delete and
download. The system has 2 types of users which are the Administrator and the Normal user.
The admin is only the one who can register a new user.
The system is developed using PHP/MySQLi, MySQL Database, HTML, CSS, and JavaScript
(Ajax and jQuery). The code was originally developed using PHP/MySQL and recently
updated to PHP/MySQLi, so this can prevent any errors due to some deprecated PHP functions.
i
ACKNOWLEDGEMENT
Any achievement doesn’t depend solely on the individual efforts but on the guidance,
encouragement and co-operation of intellectuals, elders and friends. A number of personalities
have helped us. We would like to take this opportunity to thank them all.
We would like to express our heart-felt gratitude to Dr. H. Ramakrishna, Principal, Sapthagiri
College of Engineering, Bengaluru, for his help and inspiration during the tenure of the course.
It is great privilege to extend our deep sense of gratitude to Dr. H R Ranganatha, Head of
the Department, Information Science and Engineering, Sapthagiri College of Engineering,
Bengaluru, who patronized throughout our career, for his constant support and encouragement
and for the facilities provided to carry out this work successfully.
We wish to express our sincere thanks to our guide Prof. Chaithra B M, Assistant Professor,
Department of Information Science and Engineering, Sapthagiri College of Engineering,
Bengaluru for helping us throughout and guiding us from time to time. We also extend our
sense of gratitude and sincere thanks to non-teaching staff members of Information Science
and Engineering, Sapthagiri College of Engineering, Bengaluru for their views and
encouraging ideas.
Finally, we also thank our family and friends for their co-operation and motivation.
ii
TABLE OF CONTENTS
1 INTRODUCTION 1
1.1 INTRODUCTION TO FILE STRUCTURES 1
2 SYSTEM ANALYSIS 6
2.1 ANALYSIS OF APPLICATION 6
2.2 STRUCTURE USED TO STORE FIELDS AND 6
DIRECORDS
2.3 OPERATIONS PERFORMED ON A FILE 7
2.4 COMPRESSION USED 8
2.5 ENCRYPTION/DECRYPTION USED 8
3 SYSTEM DESIGN 10
3.1 DESIGN OF THE FIELDS AND RECORDS 10
3.2 USER INTERFACE 11
4 IMPLEMENTATION 16
4.1 JAVASCRIPT, HTML AND CSS 16
4.2 PSEUDO CODE 17
4.3 TESTING 19
4.4 DISCUSSION OF RESULTS 21
REFERENCES 27
iii
LIST OF FIGURES
iv
DOCUMENT MANAGEMENT SYSTEM
CHAPTER 1
INTRODUCTION
The goal of File Structure is to get the information we need with one access to the disk. If
it is not possible, then get the information with as few accesses as possible. Group information so
that we are likely to get everything we need with only one trip of the disk. It is relatively easy to
come up with File Structure designs that meet the general goals when the files never change.
When files grow or shrink when information is added and deleted, it is much more difficult.
Goal of this course is with reference to time and space is to first minimize number of trips
to the disk in order to get desired information. Ideally get what we need in one disk access or get
it with as few disk accesses as possible. Secondly grouping related information so that we are
likely to get everything we need with only one trip to the disk for example name, address, phone
number, account balance.
1.1.1 HISTORY
➢ History of File Structure design, in the beginning the file access was sequential, and the cost of
access grew in direct proportional to the size of the file. So, indexes were added to files.
➢ Indexes made it possible to keep a list of keys and pointers in a smaller file that could be
searched more quickly
➢ Simple indexes become difficult to manage for dynamic files in which the set of keys changes.
Hence Tree Structures were introduced.
➢ Trees grew unevenly as records were added and deleted, resulting in long searches requiring
multiple disk accesses to find a record. Hence an elegant, self-adjusting binary tree structure
called an AVL Tree was developed for data in memory.
➢ Even with a balanced binary tree, dozens of accesses were required to find a record in
moderate sized files.
➢ A method was needed to keep a tree balanced when each node of the tree was not a single
record as in a binary tree, but a file block containing hundreds of records. Hence B-trees were
introduced.
➢ AVL trees grow from top down as records are added, B-trees grow from the bottom up.
➢ B-trees provided excellent access performance but, a file could not be accessed sequentially
with efficiency.
➢ The above problem was solved using B+ tree which is a combination of a B-tree and a
sequential linked list added at the bottom level of the B-tree.
➢ To further reduce the number of disk accesses, Hashing was introduced for files that do not
change size greatly overtime.
For example, to create a text file we use text editor, to create an image file we use an image
editor, and to create a document we use a word processor.
Files are not made for just reading the contents; we can also perform some operations on the
Files.
➢ Read operation: Meant to read the information which is stored into the files.
➢ Write operation: For inserting some new contents into a file.
➢ Rename or change the Name of the file.
➢ Copy the file from one location to the other.
➢ Sorting or arrange the contents of the file.
➢ Move or cut the file from one place to another.
➢ Delete a file.
➢ Execute Means to Run means File Display Output.
We can also link a file with any other File. These are also called Symbolic Links; in the symbolic
links all the files are linked by using some text Alias.
Record Structures:
A record can be defined as a set of fields that belong together when the file is viewed in terms of
a higher-level organization. Five most common methods follow:
Method 1: Make the records be a predictable number of bytes in length.
Method 2: Make the record be a predictable number of fields in length.
Method 3: Begin each record with a length indicator consisting of a count of the number of bytes
that the record contains.
Method 4: Use a second file to keep track of the beginning byte address for each record. Method
5: Place a delimiter at the end of each record to separate it from the next record.
File manager:
File Manager is blandly named, but it’s actually quite good. It’s a newer file manager app
that gives you one of the best sets of features without adding too much bloat. You’ll get basic file
management features along with cloud storage features, NAS support, and more.
MK explorer:
MK Explorer is another newer file manager option. It’s a simple option that doesn’t have
a whole lot of flair. That is extremely preferable if you really just want something simple. It
features a Material Design interface, the basic file management features (copy, paste, delete, SD
Card support for Lollipop), and root access. There are also support for 20 languages and it has a
built-in text editor, gallery, and music player. It doesn’t have anything like cloud storage or
network storage support, but that’s not really what it’s for. It’s a good, cheap option.
CHAPTER 2
SYSTEM ANALYSIS
The admin can sign-in to the dashboard and can manage the documents stored in the
record structure. The landing page shows a doc system where the admin can add new users and
files to the record, admin can view all the users and files in the record in a structured format.
There is a registration option where one can register themselves and logout. The user
registration form consists of the users details like name, phone number, email. The admin can
change their password in case they forgot the password or want to change. The user, after
accessing their file can delete their file and download it and view the storage space required by
the file. While adding a new file, the user can browse for the file and upload it.
The admin can edit and delete the user's details. The new user can view all the files stored,
related to the organization and can add files which others can view. This application provides the
user to save any document related to their purpose which is protected and taken care of by the
admin.
• A field is an item of stored data. A field could be a name, an address, a description, etc.
• A record is the collection of fields that are related to a single entity.
We take inputs from the user with their respective datatypes. The user details are stored in a
location and can be viewed.
First name, Last name, Phone number, Email Address, User Type
When the user uploads a file, it gets stored in the documents. The actions performed on stored
files are editing and deleting.
#, First name, Last name, Phone number, Email Address, User Type, Action (Delete, edit)
The name of the file in String along with its id in integer and size is displayed.
CHAPTER 3
SYSTEM DESIGN
3. Dashboard consists:
1. Add New File: User can upload their new files here.
2. View File: The user can download and edit their uploaded files.
3. Add User: Register new user.
4. View User: View registered users and edit their details.
4. Logout:
A logout feature for the admin.
• The user interface (UI), in the industrial design field of human-computer interaction, is the
space where interactions between humans and machines occur.
• The goal of this interaction is to allow effective operation and control of the machine from the
human end, whilst the machine simultaneously feeds back information that aids the operators'
decision-making process.
• Examples of this broad concept of user interfaces include the interactive aspects of computer
operating systems, hand tools, machinery operator controls, and process controls. The design
considerations applicable when creating user interfaces are related to or involve such disciplines
as ergonomics and psychology.
• The junction between a user and a computer program. An interface is a set of commands or
menus through which a user communicates with a program.
• A graphical user interface is the one which helps a user graphically to accomplish the
operations of the application. Document Management System works in a GUI environment built
on phpMyAdmin.
CHAPTER 4
IMPLEMENTATION
4.3 TESTING
4.3.1 UNIT TESTING
Unit testing is a software testing method by which individual units of source code, sets of one or
more computer program modules together with associated control data, usage procedures, and
operating procedures, are tested to determine whether they are fit for use.
We first take the unit testing by testing the component of user sign-up.
When a user creates a new account, it should reflect in the ViewUser.txt file.
➢ If the admin logs in to the dashboard, the following welcome screen is shown.
4.4.2 ADDITION
➢ The admin can add a new user.
4.4.3 DELETION
➢ The admin can delete a user.
4.4.4 MODIFICATION
➢ The admin can modify the user details.
4.4.5 VIEW
➢ The admin can view a list of users.
This project is developed to help users preserve all their documents and files in one place
with a privacy. The main purpose of this project is to store and manage the file documents of a
certain company or organization. The system stores the documents in the database as BLOB type.
Talking about storing the documents in the database, the system also stores another file
information such as the file type and file size. Allowing features of adding, deleting and
modifying files, makes it easier for the users to utilize the website.
sufficient for the future of work. Enterprises who undertake a digital transformation towards
powerful API-enabled content platforms combined with edge technology integrations will be the
victorious enterprises in the 21st Century. To remain competitive and to gain market share,
companies are now rethinking their digital strategies to drive a new and more robust view of the
value of ‘content’ within their organizations. Key themes for innovation powering these new
Increasing Regulatory, Security and Compliance mandates (e.g., HIPAA, GDRP, etc.)
Workflow enablement.
Improved Search.
With these new innovation mandates, companies are highly aware to remain competitive, now is
the time to begin investing in the new generation of cloud and hybrid-based platforms to fuel the
REFERENCES
• www.google.com
• www.youtube.com
• www.stackoverflow.com
• www.wikipedia.org
• www.sourcecodester.com
• File Structures –An Object-Oriented Approach with C++ by Michael J.Folk, Bill Zoellick,
Greg Riccardi
• Support.office.com
• www.geeksforgeeks.org
• www.thebalancesmb.com
• www.quora.com