Document Management System Report
-
Upload
ashish-thakrar -
Category
Documents
-
view
213 -
download
0
Transcript of Document Management System Report
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 1/99
DDU, Faculty of Technology, Department of Computer Engineering
[i]
Document Management System (Web based)
by
Nehal Pankajkumar Bhagat (ID No. 102013)Meghal Maheshkumar Gandhi (ID No. 102037)
A Project Submitted
In
Partial fulfilment of the requirements
For the degree of
BACHELOR OF TECHNOLOGY
In
COMPUTER ENGINEERING
Faculty of Technology
Department of Computer Engineering
Dharmsinh Desai University
Nadiad-387001
External Guide Mr. Hemant Joshi
Scientist SE
Institute For Plasma Research
Internal Guide Prof. Malay S. Bhatt
Associate Professor
Dept. of Comp. Engg. DDU
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 2/99
DDU, Faculty of Technology, Department of Computer Engineering
[ii]
CERTIFICATE
This is to certify that the project work titled
Document Management System
is a bonafide work of
Nehal Pankajkumar Bhagat (ID No. 102013)
Meghal Maheshkumar Gandhi (ID No. 102037)
carried out in the partial fulfilment of the degree of Bachelor of Technology in Computer
Engineering at Dharmsinh Desai University in the academic session December 2013 to April2014.
Prof. Malay S. Bhatt Prof. C.K.Bhensdadia
Associate Professor, Head of Dept.,
Dept. of Computer Engg. Dept. of Computer Engg.
Faculty of Technology
Department of Computer Engineering
Dharmsinh Desai University
Nadiad-387001
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 3/99
DDU, Faculty of Technology, Department of Computer Engineering
[iii]
Acknowledgement
Every Project big or small is successful largely due to the effort of a number of people who
have always given their valuable advice or lent a helping hand. We sincerely appreciate theinspiration; support and guidance of all those people who have been instrumental in making
this project a success.
We are extremely grateful to “Institute for Plasma Research” for the confidence bestowed in
us. We would like to express our sincere thanks to Mr.Hemant Joshi for helping us
throughout the development of this project; introducing us to ASP.NET technology and for
always answering any doubts we ever had. We could not have achieved this without the
resources he made available and his valuable insights.
We’d also like to take this opportunity to express our gratitude to Mr.Amit Srivastava for hissupport and encouragement.
We would also like to thank our project guide, Prof. Malay Bhatt for his constant guidance
and inputs that helped us improve.
Regards,
Nehal Pankajkumar Bhagat
Meghal Maheshkumar Gandhi
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 4/99
DDU, Faculty of Technology, Department of Computer Engineering
[iv]
Abstract
Document Management System helps providing user friendly platform to
upload, view and download documents based on their requirements. Prior to this system,
employees should have to meet respective persons personally for any document related work.
Lots of paper work is involved in it and storage problems of hard copy of documents is also
an issue. For the approval of Abstract & Abstract form, Authorities must had to schedule
meetings for discussion. One should have to wait for his document’s final status until it gone
through the hierarchies of admin. It is a tedious task for all. This system is made to reduce
this type of tedious work by using software interface.
First, Admin creates users and assigns different roles to them. User can uploadhis document in particular folder and can see any uploaded document details. In document
category module, user can upload category and sub-category wise document and can see only
his uploaded document. User cannot see other users’ documents so that document security
can be maintained.
Abstract document upload module provides users to upload their document
for particular conference for higher authority’s approval. When new document is uploaded,
notification mail will be sent to abstract head and abstract admin. Abstract Admin and head
gives their decision (approve, regret, comment) for particular document and they can also see
the decisions made by other authorities. Only abstract head’s decision will be reflected inuser view. Abstract admin and head can give their decision only once for particular
document. When final decision is made by abstract head, decision mail will be sent to
particular user.
Project Management Cell (PMC) module facilitates user to upload his project
related documents separately. All the users are provided folder’s name as their project’s name
beforehand.
Document Management System gives helpful environment to manage all the
documents effectively.
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 5/99
DDU, Faculty of Technology, Department of Computer Engineering
[v]
Table of Contents
Title Page
Certificate .......................................................................................................... ii
Acknowledgement ............................................................................................... iii
Abstract ................................................................................................................ iv
List of Figures ..................................................................................................... vii
List of Tables ....................................................................................................... ix
Chapter 1: About the System .............................................................................. 01
Chapter 1: About the System .............................................................................. 01
Chapter 1: About the System ........................................................................... 01
Chapter 2: Software Requirements Specification ............................................. 02
2.1 Introduction .......................................................................................... 02
2.2 General Description ................................................................................. 03
2.3 Overall Description .................................................................................. 05
2.4 Functional Requirements ........................................................................... 06
2.5 Non Functional Requirements ..................................................................... 12
Chapter 3: Analysis .......................................................................................... 14
3.1 Use Case Diagram ................................................................................. 14
3.2 Sequence Diagram ................................................................................ 15
3.3 Class Diagram ....................................................................................... 17
3.4 Activity Diagram ................................................................................... 18
3.5 State Chart Diagram .............................................................................. 19
3.6 Structure Chart Diagram ......................................................................... 20
3.7 Entity Relationship Diagram .................................................................... 21
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 6/99
DDU, Faculty of Technology, Department of Computer Engineering
[vi]
3.8 Table Relationship Diagram .................................................................... 22
3.9 Gantt Chart .......................................................................................... 24
3.10 Pert Chart .......................................................................................... 25
Chapter 4: Data Dictionary ............................................................................... 26
Chapter 5: Implementation .............................................................................. 38
5.1 Methods & their Description: Module wise ................................................ 38
5.2 Methods & their Description: Predefined .................................................. 41
5.3 Naming Convention ............................................................................... 47
5.4 Error Handling ...................................................................................... 48
Chapter 6: Testing ............................................................................................ 53
6.1 Introduction ......................................................................................... 53
6.2 Test Plan ............................................................................................. 53
6.3 Test Strategy ........................................................................................ 54
6.4 Testing Method .................................................................................... 54
6.5 Test Cases ........................................................................................... 55
6.6 Screenshots ......................................................................................... 58
Chapter 7: Conclusion & Future Extension ....................................................... 78
Appendix A: Initial Learning ............................................................................. 79
Appendix B: Data Flow Diagrams ..................................................................... 87
Bibliography ..................................................................................................... 90
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 7/99
DDU, Faculty of Technology, Department of Computer Engineering
[vii]
List of Figures
Chapter 3: Analysis
Figure 3.1 Use Case Diagram .................................................................................................. 14
Figure 3.2 Sequence Diagram for Simple Document Upload ................................................. 15
Figure 3.3 Sequence Diagram for Abstract Upload ................................................................. 16
Figure 3.4 Class Diagram ........................................................................................................ 17
Figure 3.5 Activity Diagram .................................................................................................... 18
Figure 3.6 State Chart .............................................................................................................. 19
Figure 3.7 Structure Chart........................................................................................................ 20
Figure 3.8 Entity Relationship Diagram .................................................................................. 21
Figure 3.9 Table Relationship Diagram ................................................................................... 22Figure 3.10 Gantt Chart ........................................................................................................... 24
Figure 3.11 Pert Chart .............................................................................................................. 25
Chapter 6: Testing
6.6: Screenshots
Figure 6.1 Login Page .............................................................................................................. 58
Figure 6.2 Home Page.............................................................................................................. 58
Figure 6.3 Page to create user by Admin ................................................................................. 59
Figure 6.4 Page to change password by user ........................................................................... 59
Figure 6.5 Page to upload document in selected folder ........................................................... 60
Figure 6.6 Acknowledgement of successful document upload ............................................... 60
Figure 6.7 Validations on document upload ............................................................................ 61
Figure 6.8 View of document upload ...................................................................................... 61
Figure 6.9 Filtered view based on from-to dates. .................................................................... 62
Figure 6.10 View based on selected folder. ............................................................................. 62
Figure 6.11 Validations ............................................................................................................ 63
Figure 6.12 Selection of categories .......................................................................................... 63
Figure 6.13 Acknowledgement of successful document upload ............................................. 64
Figure 6.14 Admin view of all uploaded files regardless of any user ................................... 64
Figure 6.15 User view of uploaded files (particular user files) ............................................... 65
Figure 6.16 Filtered view ......................................................................................................... 65
Figure 6.17 Add categories (Only admin can add) ................................................................. 66
Figure 6.18 Validations on Abstract document ....................................................................... 66
Figure 6.19 Normal User uploads document .......................................................................... 67
Figure 6.20 Acknowledgement of successful document upload ............................................. 67
Figure 6.21 Admin view of uploaded files (documents having last submission date within aweek and still “In Process” is displayed in red) ..................................................................... 68
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 8/99
DDU, Faculty of Technology, Department of Computer Engineering
[viii]
Figure 6.22 User view of Abstract ........................................................................................... 68
Figure 6.23 Filtered view ......................................................................................................... 69
Figure 6.24 User view for uploaded file when click on “Select” ............................................ 69
Figure 6.25 Abstract admin view for approving document ..................................................... 70
Figure 6.26 Abstract head approves document ........................................................................ 70Figure 6.27 Abstract head’s status is reflected ....................................................................... 71
Figure 6.28 Admin can add conference ................................................................................... 71
Figure 6.29 Successfully added new conference ..................................................................... 72
Figure 6.30 List of conferences and editing can be done ........................................................ 72
Figure 6.31 Validations ............................................................................................................ 73
Figure 6.32 Role wise file is stored in particular folder ......................................................... 73
Figure 6.33 Acknowledgement of successful upload ............................................................. 74
Figure 6.34 View of uploaded documents with employee’s name ......................................... 74
Figure 6.35 Filtered view of uploaded document by department name ................................. 75
Figure 6.36 Identifies user and path from database and displays the folder and also it is
physically existed ..................................................................................................................... 75
Figure 6.37 Shows the stored files in the user folder(if subfolders are there then manual
entry of that path should be done in database ......................................................................... 76
Figure 6.38 User selects the project name from dropdown. Dropdown shows only particular
user’s projects’ names. ............................................................................................................ 76
Figure 6.39 Acknowledgement of successful upload ............................................................. 77
Figure 6.40 User can view the list of all the uploaded documents of his projects ................. 77
Appendix A: Initial Learning
Figure 1 Master Page .............................................................Error! Bookmark not defined.0
Figure 2 Publish Profile ........................................................................................................... 84
Figure 3: Connection Tab ........................................................................................................ 85
Figure 4: Settings Tab .............................................................................................................. 85
Figure 5: Preview ..................................................................................................................... 86
Appendix B: Data Flow Diagrams
Figure 1 Data Flow Diagram Level-0 ...................................................................................... 87
Figure 2 Data Flow Diagram Level-1 ...................................................................................... 88
Figure 3 Data Flow Diagram Level-2 ...................................................................................... 89
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 9/99
DDU, Faculty of Technology, Department of Computer Engineering
[ix]
List of Tables
Chapter 4: Data Dictionary
Table 4.1 document .................................................................................................................. 26
Table 4.2 documentcategory .................................................................................................... 27
Table 4.3 ChssCard .................................................................................................................. 27
Table 4.4 employee .................................................................................................................. 28
Table 4.5 membercomment ..................................................................................................... 29
Table 4.6 userfolder ................................................................................................................. 30
Table 4.7 usergroup ................................................................................................................. 30
Table 4.8 administration .......................................................................................................... 31
Table 4.9 abstract ..................................................................................................................... 31
Table 4.10 groups..................................................................................................................... 32
Table 4.11 payband .................................................................................................................. 32
Table 4.12 aspnet_Membership ............................................................................................... 33
Table 4.13 aspnet_Roles .......................................................................................................... 34
Table 4.14 aspnet_Users .......................................................................................................... 35
Table 4.15 UsersinRoles .......................................................................................................... 36
Table 4.16 pmc......................................................................................................................... 36
Table 4.17 pmcuser .................................................................................................................. 37
Table 4.18 conference .............................................................................................................. 37
Chapter 5: Implementation
Table 5.1 Methods and their description: Module wise ........................................................... 38
Table 5.2 Methods and their description: Predefined .............................................................. 41
Table 5.3 Naming Conventions ............................................................................................... 48
Chapter 6: Testing
Table 6.1 Test Cases ................................................................................................................ 55
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 10/99
1
DDU, Faculty of Technology, Department of Computer Engineering
Chapter 1
About the System
Document Management System at IPR has reduced lot of paperwork and has also stored
document details in the database safely. It has reduced the time of employee to get document
approved and has also eliminated number of meetings for it.
It facilitates the Admin to create user and to assign roles them. Admin gives username and
password to all the employees.
User who wants to upload documents can login with their username and password. User can
only see his uploaded documents except Admin. User can also use filters. In addition to this,Admin view is enhanced by the advanced filters for the management purpose. It efficiently
maintains security.
User can also get the approval decision for uploaded Abstract document. At first, Request
mail is sent to authorities as notification to review the document. After final decision, User
also receives the decision email. This saves time of both authorities and employees.
DMS provides document upload facility to Administration, PMC etc sectors. In most of them,
documents are stored in particular username folder. User can download any of his documents
any time. It makes the maintenance task of documents easier than before.
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 11/99
2
DDU, Faculty of Technology, Department of Computer Engineering
Chapter 2
Software Requirement Specification
2.1 Introduction:
Document management system (DMS) is used to upload, Store and
view/retrieve documents. It also helps to track the document at different levels. It also
notifies authorities when new document is uploaded for approval and replies back
when final decision is made.
2.1.1 Purpose:
Document management Process begins with the conversion of paper
documents and record to electronic files. Conversion eliminates many of the obstacles
created by paper: labor-intensive duplication procedures, slow distribution, misplaced
originals and the inconvenience of retrieving files from off-site storage. Because
paper files are also costly to process, duplicate, distribute and store, digitizing paper
archives ultimately reduces operating expenses and overhead.
2.1.2 Scope:
This is a web application that can be accessed from anywhere in the institute
and it shares the same database due to which users from different departments can use
it at different locations simultaneously.
In Scope:
Simple document upload.
Simple upload with different categories and sub categories.
List of uploaded documents based on logged in other.
Approving document process.
List of uploaded documents based on role of user.
Review and give appropriate comments.
Accordingly give approval/regret decision.
Not in Scope:
Document size, No files except .doc/docx, ppt, pptx and .pdf
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 12/99
3
DDU, Faculty of Technology, Department of Computer Engineering
2.1.3 Technology & Tools Used
Microsoft Asp.net Framework
Microsoft Visual Studio 2012
SQL Server Manager 2012
2.1.4 Software Development Model
Iterative Waterfall Model
2.1.5 Acronyms and Abbreviations:
DMS: Document Management System.
IPR: Institute for Plasma Research
PMC: Project Management Cell
MS: Microsoft
SQL: Structured Query Language
VS: Visual Studio
LINQ: Language-Integrated Query
SRS: Software Requirement Specification
CSS: Cascading Style Sheets
2.2 General Description
2.2.1 Hardware Interfaces
Memory minimum of 1GB RAM
Hard disk of 40 GB
Monitor
Mouse
Keyboard
Printer
2.2.2 Software Interfaces
Operating System: Windows XP / Vista / 7 / 8
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 13/99
4
DDU, Faculty of Technology, Department of Computer Engineering
Front End: ASP.Net
Back End: C#
Designing: CSS
2.2.3 Communication Interfaces
This system is a Web Application and the communication between the user and the system
takes place through a Web Browser.
2.2.4 Software Functions
User authentication and login Simple document upload
Review of document and store decision
Send request and decision email
Management of Roles (creation of roles and their assignment)
2.2.5 Performance Requirements
The overall system should be fast, reliable and error free. It should have built in error checking facilities.
The system should be able to handle large amount of data comfortably.
2.2.6 Attributes
Reliability
In order to ensure the reliability of this system, we have developed it using MS Visual
Studio 2012 which is stable and easy to use. Availability
This system is designed to run as and when the user wishes to use it.
Security
The access to the system is given only to the users having a valid username and
password. Without proper credentials, the system can’t be accessed and the data
remains safe. Also added security is provided by Visual Studio when passwords are
stored in the database in encrypted format.
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 14/99
5
DDU, Faculty of Technology, Department of Computer Engineering
2.3 Overall Description
2.3.1 Product Perspective
This software is developed specifically to cater to the IPR employees’ document
management, is totally self-contained and works efficiently. It provides a robust database and
it provides good and easy graphical user interface to both new as well as experienced user of
the computer.
2.3.2 User Characteristics
2.3.2.1 End Users
End user should have basic idea about internet surfing and filling of online application
forms, uploading and downloading documents and photographs.
2.3.2.1 Administrator
Administrator must be having good knowledge of database management system.
Administrator must be capable to manage user rights.
If the network connection does not work properly then our system should not work as
intended.
Also that is assumed that the product is installed properly on the web server.
This system will not take care of any virus problem, which might occur either on the
client or the server system. Avoiding the use of pirated software and ensure thatfloppies and other removable media are scanned for viruses before use.
Recovery of data after a system crash will be possible only if backups are taken at
regular intervals
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 15/99
6
DDU, Faculty of Technology, Department of Computer Engineering
2.3.3 Assumptions and Dependencies
Assumptions
We assume that the client machine must have the environment required for thisapplication to run.
The client machine should be running 64-bit or 32-bit versions of Windows 7/8
The operating system requirements for the server is 64-bit versions of
Windows Server 2008 R2 with SP1.
Dependencies
All necessary hardware and software are available for implementation and useof the tool.
The client machine should have a printer.
2.4 Functional Requirements:
R1 Create user
Input : User provides user name, password, confirm password, email and
clicks on the create user button.
Output : System gives an acknowledgement of the success.
Processing : System inserts the data in the database.
R2 Login
R2.1 Verify username and password
Input : User provides user name and password.
Output : System allows user to proceed.
Processing : System authenticates user name and password.
R2.2 Check user type and rights given to users
Input : User provides user name and password.
Output : System allows access of the system if user is authenticated.
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 16/99
7
DDU, Faculty of Technology, Department of Computer Engineering
Processing : System verifies authorization and allows access.
R2.3 Change password
Input : User provides old password, new password, confirm password and
clicks on the change password button.
Output : System gives an acknowledgement of success.
Processing : System inserts the data in the database.
R2.4 Logout
Input : User clicks on the logout link.
Output : System logs out the user and redirects to login page.
Processing : System ends session.
R3 Simple Document Upload
R3.1 Upload document
Input : User selects the appropriate directory, fills up the details and chooses
the file to upload.
Output : System gives the acknowledgement of success.
Processing : System stores the document in selected Directory and reflects
document details in database.
R3.2 View document
Input : User clicks the view button and selects the appropriate directory to
view its contents and selects the file to view.
Output : System opens the file.
Processing : System selects proper document from appropriate directory.
R4 Simple upload with different categories
Description : Categories of the document to be uploaded will be changed according
to user roles and authentication and based on it sub-categories will be
shown.
R4.1 Add categories and subcategories
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 17/99
8
DDU, Faculty of Technology, Department of Computer Engineering
Input : Admin inserts the categories and subcategories.
Output : System gives an acknowledgement of success.
Processing : System reflects the details in the database.
R4.2 Select categories
Input : User selects the category and sub-category and selects the appropriate
file to upload.
Output : System gives the acknowledgement of success. .
Processing : System identifies the role of the user when he logs in and based on
that displays the categories and sub-categories and stores file in
particular directory.
R4.3 Role wise view
R4.3.1 Admin view
Input : User clicks on the view button.
Output : System displays the directories of all the users and contents of
uploaded documents.
Processing : System retrieves the files from the directories.
R4.3.2 User view
Input : User clicks on the view button.
Output : System displays the directories of that user and contents of
uploaded files.
Processing : System retrieves the files from the directories.
R5 Document approval for Abstract documents
Description : Approval/Regret/Comment decision for uploaded Abstract and
Abstract form documents is made only once by approving authority.
Final decision for document is made only by Abstract admin.
R5.1 Add conference
Input : Admin enters the conference short and long name, location and
conference start date and clicks submit button.
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 18/99
9
DDU, Faculty of Technology, Department of Computer Engineering
Output : System gives an acknowledgement of success.
Processing : System reflects the data in the database.
R5.2 Document review
Input : User enters the details of document, conference name, conference
start date, location and submits document for approval.
Output : System displays approval status.
Processing : System stores data in Database and document on file system path.
R5.3 Document approve/comment/regret
Input : Approval/Comment from approving authority.
Output : System displays updated approval/regret status.
Processing : System updates data in Database.
R5.4 Role wise approval
R5.4.1 Abstract admin approval
Input : User gives the appropriate decision and comments if any.
Output : System displays the temporary decision and also shows the
previously made comments.
Processing : System stores the decision temporarily but does not reflect it
into database.
R5.4.2 Abstract head approval
Input : User gives the appropriate decision and comments if any.
Output : System displays the final decision and also shows the
previously made comments.
Processing : System stores the final decision and reflect it into database.
R5.5 Role wise view
R5.5.1 Abstract Admin/head view
Input : User clicks on the view button and then selects the document
to view the details.
Output : System displays the details of the uploaded files and if the
decision is not made previously by logged in user then promptsthe decision options.
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 19/99
10
DDU, Faculty of Technology, Department of Computer Engineering
Processing : System identifies the role of the logged in user and displays
the previously stored decisions and restricts the user if the
decision is already made once by him. If new decision is made
by Abstract head then reflects it into database.
R5.5.2 User view
Input : User clicks on the view button and then selects the document
to view the details.
Output : System displays the details of the uploaded files.
Processing : System identifies the role of the logged in user and displays
the previously stored decisions
R6 View filtering
Input : User enters the Document id and/or User-id and/or group and/or title
and/or dates for filtering purpose and clicks on the view button.
Output : System displays the required data in grid view.
Processing : System fetches appropriate results from the database.
R7 Role Management
R7.1 Creation of New Roles
Input : User enters the new role to be created.
Output : New role gets added to the database.
Processing : Checks for valid role name (eg. No commas) are carried out. Also the
role shouldn’t already exist.
R7.2 Assigning Users to Roles
Input : User selects the user that needs to be assigned role(s).
Output : The user is assigned to the particular role(s).
Processing : The user may be assigned more than one role.
R7.3 Assigning Roles to Users
Input : User selects a role to which users need to be assigned.
Output : New user(s) is assigned to that particular role.
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 20/99
11
DDU, Faculty of Technology, Department of Computer Engineering
Processing : More than one user maybe assigned that role.
R8 Admin-group wise document upload
R8.1 Upload document
Input : User enters the document title and selects the appropriate files to be
uploaded.
Output : System gives the acknowledgement of success.
Processing : System selects the appropriate folder according to the role of admin
to save the uploaded files, stores the uploaded files there and updates data in database.
R8.2 View document
Input : User selects appropriate options to filter and clicks on the view button
Output : System displays filtered results of the uploaded files of any admin.
Processing : System fetches appropriate results from the database.
R9 Email notification
R9.1 Send request email
Input : User uploads the Abstract & Abstract form document and clicks on
submit button.
Output : System gives an acknowledgement of success.
Processing : System sends email to Abstract head and Abstract admin.
R9.2 Send decision email
Input : Abstract head gives the decision.
Output : System reflects the decision.
Processing : System sends email to specific user.
R10 Project Management Cell (PMC) document
R10.1 PMC document upload
Input : User selects the project name from his project list and file to upload.
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 21/99
12
DDU, Faculty of Technology, Department of Computer Engineering
Output : System gives an acknowledgement of success.
Processing : System stores the document in particular user project folder and
reflects the document details the database.
R10.2 PMC document view
Input : User clicks on the view button.
Output : System displays the list of his uploaded file.
Processing : System fetches appropriate results from the database .
2.5 Non Functional Requirements
R1. Usability
R1.1 Ease of Use
The application created by us is user-friendly, so any non-technical user will find it
easy to use.
The application has a very interactive user interface. The nesting level of menu is not
more than 2 which facilitates easy navigation.
The menu titles have clarity and are meaningful.
Tool tip is also provided in menus
R2. Reliability
R2.1 Error Handling
The application should not crash
The application should not have memory leak
If any error occurs during runtime, it should notify the user about it.
R2.2 Ease of Recovery
If the application crashes or any error occurs, the information and configuration data
about the work done should be restored.
R3. Performance
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 22/99
13
DDU, Faculty of Technology, Department of Computer Engineering
R3.1 Response Time
The application will be able to save the data which is submitted by user during
session.
R3.2 Resource Usage
The memory requirement of the application should be as minimum as possible. Also,
the memory occupied by the application should not affect the performance of other
applications in the PC.
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 23/99
14
DDU, Faculty of Technology, Department of Computer Engineering
Chapter 3
Analysis
3.1 Use Case Diagram
Document Management System
Admin
Create User
Create Roles
Login
<<includes>>
Simple User
For Admin Only
Manage Roles
Add Conference
Add Categories and
Sub categories
View and Download
Document
By Group By Category &
SubCategory By TitleBy From date & To
date
Change Password
<<includes>>
<<includes>>
Upload Document
Upload Abstract
Document
Send Request Email
<<includes>>
Abstract Head
Abstract Admin
View Abstract
Document
Abstract Document
Decision
Regret Document
Approve Document
Do Comment
«extends»
«extends»
«extends» G i v e s t e m p o r a r y d e c i s i o n
G i v e s f i n
a l d e c i s i o
n
Send Email of
Decision
<<includes>>
For Abstract Head Only
«extends»
Use Case Diagram
< < e x t e
n d s >
>
< < e x t e n d s > >
< < e x t e n d s > >
For Admin only
Figure 3.1: Use Case Diagram for DMS
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 24/99
15
DDU, Faculty of Technology, Department of Computer Engineering
3.2 Sequence Diagram
3.2.1 Sequence Diagram for Simple Document Upload
Admin User DMS
createUserAssignRole()
provideUsernamePassword()
doAuthentication()
[valid] diaplay home page
selectUploadType()
prompts selected page
provideDocumentDetails
AndUpload()
doProcessing()
displays success
message or failure
message
selectViewOption()
displays uploaded documents details
selectDownload()
selectLogout()
doProcessing()
displays login page
Sequence Diagram For Simple Document Upload
Figure 3.2: Sequence Diagram for Simple Document Upload
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 25/99
16
DDU, Faculty of Technology, Department of Computer Engineering
3.2.2 Sequence Diagram for Abstract Upload
Abstract Admin/ Abstract
HeadDMS
chooseUploaddocumentOption()
User
prompts abstract upload page
provideDocumentdetailsandUpload()
sendRequestEmail()
logs in and selects view option
IsAlreadygivenDe
cisionByAbstractA
dmin/Head()[not given] displays
decisions of other
authorities and prompts the
decision options
Selects proper option to give
decision or give commentcheckRoles()
[abstract head] reflects the final
decision in a document detail
view
[abstract Admin] displays
temporary decisions
sendDecisionEmail()
Sequence Diagram For Abstract Document Upload
Figure 3.3: Sequence Diagram for Abstract Document Upload
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 26/99
17
DDU, Faculty of Technology, Department of Computer Engineering
3.3 Class Diagram
+fileUploading() : void
+changePassword() : void
-username : string
-password : string
-emailid : string
-role : string
User
+roleExists() : bool
+isUserInRole() : bool
+getUserInRole() : string
+findUserInRole() : string
+getAllRoles() : string
+getRolesForUsers() : string
+rolename : string
+rights : string
Roles
+sendRequestEmail()
Simple User
+ceateUser() : void
+createRoles() : void
+manageRoles() : void
+manageUsers() : void
Admin
+finalApproval()
+sendApprovalEmail()
Abstract head
+tempApproval()
Abstract Admin
-group_code : string
-group_name : string
Group
+paging()
+chooseFile()
+downloadFile()
+doc_View()
+doc_Upload()
-doc_id : int
-filename : string
-uploadDate
Document
+choosePath()
-user_id : string
-owner : string
-title : string
Simple Document
+addCategory()
+addSuncategory()
-newCategory : string
-newSubcategory : string
Category
+checkRole()
+roleviseView()
-category : string
-sub-category : string
-title : string
-empname : string
-userGroup : string
-userType : string
Document Category
+checkRole()
+roleviseView()
-projectName : string
-category : string
-discription : string
-uploadedBy : string
PMC
+selectDepartment()
+ckeckRole()
+groupviseView()
-uploadedBy : string
-title : string
-filename : string
Administration
+selectFolder()
+checkRole()
+assignUserfolder()
User Folder
+ckeckRole()
+roleviseView()
+updateStatus()
+statusApproval()
-category : string
-sub-category : string
-conference : string
-fromdate
-location : string
-title : string
-abstractUpload
-abstractFormUpload
Abstract Document
+addConference()
-shortname : string
-longname : string
-fromdate
-todate
-submissiondate
-location : string
Conference
*
*
*
1
Manages
*
1
manages
*
*uploads
*
1
*1
Class Diagram for Document
Management System
Class Diagram for Document
Management System
has
Belongs to
Figure 3.4: Class Diagram for APMS
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 27/99
18
DDU, Faculty of Technology, Department of Computer Engineering
3.4 Activity Diagram
Get username and password
Authenticate user Check role
Review Abstract document
Take decision
Reflect final decision
Document upload
[Abstracthead/
Abstractadmin][Users]
[Valid]
Login failure
[Invalid]
Send Request email
Display previous decision
[decision not give
yet]
[decision once
given]
Send decision email
Close
Activity Diagram for Document
Management System
Figure 3.5: Activity Diagram for DMS
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 28/99
19
DDU, Faculty of Technology, Department of Computer Engineering
3.5 State Diagram
Waiting for authorize
Get username &
password[Invalid]
Start
waiting for option selection
[Valid]/
Redirect to
home page
Get document details Get Abstract document details
Receive acknowledgement
Uploading
document
Uploading
Abstract
document
Waiting for the decision
[Abstract document]/
Send request email
Selection of AbstractSelection of documents
Get decision
Selection of proper
option
Role checkingDisplay document
Selection of view button
Store final decision Get decision temporary
[Role==Abstract Admin]/
receive final decision
[Role==Abstract Head]/
receive temporary
decision
[option locked]/ Send
decision email
[option locked]
State diagram for Document
Management Syatem
Figure 3.6: State Chart for DMS
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 29/99
20
DDU, Faculty of Technology, Department of Computer Engineering
3.6 Structural Chart
Main
Upload
document
Display status of
Abstract document Create user
Get document
details
D o c u m
e n t d
e t a
i l s
Get status of
Abstract document
Review Abstract
Document
Upload Abstract
document
Check roles
S t a t u
s d e t a
i l s
A b s t r a c t d o c u m e n t
s t a t u s
S t a t u s
d e t a i l s
Receive status
Of Abstract
Get user roles Get user details
R o l e
d e t a i l
sU s e r d
e t a i l s
R o l e
d e t a l s
A b s t r
a c t d
e t a i l
s
R o l e d e t a l s
S t a t u s d e t a i l s
Read user data
U s e
r d e
t a i l s
Validate user data
U s e r d
e
t a i l s
D o c u
m e n t
u p l o a
dU s e r c r e a t i o n
U s e r d e t a i l s
Structural chart for Document
Management System
Figure 3.7: Structure Chart for DMS
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 30/99
21
DDU, Faculty of Technology, Department of Computer Engineering
3.7 Entity-Relationship Diagram
User username
password
role
has
roles
rolename
roleid
Upload
Upload
Categorizwd
document
Document id
filename
upload datefetch
Categories
Admin
add
Abstract
document
category sub category
filename1
filename2
document id
conference
name
Simple
documentDocument id
userid
filename
identify
identify Conference
location
conference
nameconference
id
short name
fetch
from date
to date
last
submission
date
Abstract
head
Abstract
admin
give temp
status
give finalstatus
PMC
document
project
name
upoad date
group name
Administration
document
department
name
document id
document id
Entity Relationship Diagram for
Document Management System
1
*
*
1
*1
1
1
*
*
1
*
1*
*
1*
1
*
1
*
*
*
Figure 3.8 Entity Relationship Diagram for DMS
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 31/99
22
DDU, Faculty of Technology, Department of Computer Engineering
3.8 Table Relationship Diagram
Figure 3.9a Table Relationship Diagram for DMS
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 32/99
23
DDU, Faculty of Technology, Department of Computer Engineering
Figure 3.9b Table Relationship Diagram for DMS
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 33/99
24
DDU, Faculty of Technology, Department of Computer Engineering
3.9 Gantt Chart
Week 1,2
Feasibility Study
RequirementGathering
Week 9,10 Week 7,8 Week 5,6 Week 3,4 Week 13,14Week 11,12 Week 15,16
Testing
Coding
Designing
Gantt Chart for Document Management System
Figure 3.10 Gantt Chart for DMS
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 34/99
25
DDU, Faculty of Technology, Department of Computer Engineering
3.10 Pert Chart
9/12/2013 2 week
20/12/
2013
Feasibility study
6/3/2014 3 week28/3/2014
Testing
26/1/2014
5 week 5/3/2014
Coding
9/1/2014 3 week 24/1/
2014
Designing
23/12/
2013 3 week 8/1/2014
Requirement Gathering
Pert Chart for Document Management System
Figure 3.11 Pert Chart for DMS
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 35/99
26
DDU, Faculty of Technology, Department of Computer Engineering
Chapter 4
Data Dictionary
This section contains detailed information of all the tables that have been used and also the
.aspx pages in which these tables have been used.
1.
Dbo.document:
This table is used in Document.aspx and DocumentView.aspx.
Table 4.1 document
COLUMN
NAME
DATATYPE
NUMERIC
SCALE
NUMERIC
PRECISION
ISNULLABLE
CHARACTER
MAXIMUM
LENGTH
CONSTRAINT
NAME
CONSTRAINT
TYPE
cur_date datetime NULL NULL YES NULL
docid numeric 0 18 NO NULL PK_documen
t
PRIMARY KEY
userid numeric 0 18 NO NULL
title varchar NULL NULL NO 50
owner varchar NULL NULL YES 50
fpath varchar NULL NULL YES 50
fname varchar NULL NULL YES 100
2.
Dbo.documentcategory:
This table is used in the following pages:
AddCategory.aspx
DocumentCategory.aspx
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 36/99
27
DDU, Faculty of Technology, Department of Computer Engineering
Table 4.2 documentcategory
COL
UMN
NA
ME
DATA
TYPE
NUM
ERIC
SC
ALE
NUM
ERIC
PREC
ISION
ISNUL
LABLE
CHAR
ACTER
MAX
IMUM
LEN
GTH
CONSTRAINT
NA
ME
CONSTRAINT
TY
PE
category varchar NULL NULL YES 50
subcategory varchar NULL NULL YES 50
3.
Dbo.ChssCard:
This table is used in ChssCard.aspx page.
Table 4.3 ChssCard
COLUMN
NAME
DATATYPE
NUMERIC
SCALE
NUMERIC
PRECISION
ISNULLABLE
CHARACTER
MAXIMUM
LENGTH
CONSTRAINT
NAME
CONSTRAINT
TYPE
Payrollno numeric 0 20 NO NULLPK_Chss
Card
PRIMAR Y
KEY
Spouse
Namevarchar NULL NULL YES 50
Spouse
Dobdate NULL NULL YES NULL
ch1name varchar NULL NULL YES 50
ch1dob date NULL NULL YES NULL
ch2name varchar NULL NULL YES 50
ch2dob date NULL NULL YES NULL
Fname varchar NULL NULL YES 50
Mname varchar NULL NULL YES 50
ch3name varchar NULL NULL YES 50
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 37/99
28
DDU, Faculty of Technology, Department of Computer Engineering
COLUMN
NAME
DATATYPE
N
UMERIC
SCALE
N
UMERIC
PRECISION
ISNULLABLE
CH
ARACTER
M
AXIMUM
LENGTH
CO
NSTRAINT
NAME
CO
NSTRAINT
TYPE
ch3dob date NULL NULL YES NULL
Eimg varchar NULL NULL YES 50
Spouse
Imgvarchar NULL NULL YES 50
ch1img varchar NULL NULL YES 50
ch2img varchar NULL NULL YES 50
Fimg varchar NULL NULL YES 50
Mimg varchar NULL NULL YES 50
ch3img varchar NULL NULL YES 50
4.
Dbo.employee:
This table is used in Employee.aspx page.
Table 4.4 employee
C
OLUMN
NAME
DA
TATYPE
NUMERIC
SCALE
NUMERIC
PR
ECISION
ISN
ULLABLE
CHARACTER
MAXIMUM
L
ENGTH
CONSTRAINT
NAME
CONSTRAINT
TYPE
Payno numeric 0 6 NO NULLPK_em ployee
PRIMAR Y KEY
empname varchar NULL NULL YES 30
Doj date NULL NULL YES NULL
Dob date NULL NULL YES NULL
pay_inband numeric 0 6 YES NULL
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 38/99
29
DDU, Faculty of Technology, Department of Computer Engineering
payband_id numeric 0 10 NO NULL
desig_code numeric 0 6 NO NULL
group_code numeric 0 18 NO NULL
empstatus varchar NULL NULL YES 20
emailipr varchar NULL NULL YES 20
emailalt varchar NULL NULL YES 20
extno varchar NULL NULL YES 20
roomlab varchar NULL NULL YES 25
contact1 varchar NULL NULL YES 25
contact2 varchar NULL NULL YES 25
Dor date NULL NULL YES NULL
extdate date NULL NULL YES NULL
Dol date NULL NULL YES NULL
Doi date NULL NULL YES NULL
UserName nvarchar NULL NULL YES 256
5.
dbo.membercomment:
This table is used in AbstractView.aspx page.
Table 4.5 memebercomment
COLUMN
NAME
DATATYPE
NUMERIC
SCALE
NUMERIC
PRECISION
ISNULLABLE
CHARACTER
MAXIMUM
LENGTH
CONSTRAINT
NAME
CONSTRAINT
TYPE
docid numeric 0 18 NO NULL
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 39/99
30
DDU, Faculty of Technology, Department of Computer Engineering
username varchar NULL NULL YES 50
tempstatus varchar NULL NULL YES 50
commentdate datetime NULL NULL YES NULL
6. dbo.userfolder:
This table is used in UserFolder.aspx
Table 4.6 userfolder
COLUMN
NAME
DATATYPE
NUMERI
C
SCALE
NUMERI
C
PRECISIO
N
ISNULLAB
LE
CHARACT
ER
MAXIMU
M
LENGTH
CONSTRAINT
NAME
CONSTRAINT
TYPE
userid nchar NULL NULL NO 10 PK_us
erfolde
r
PRIMA
RY KEY
path nchar NULL NULL YES 50
7.
dbo.usergroup
This table is used in DocumentCategory.aspx and DocumentCategory.aspx
Table 4.7 usergroup
CO
LUMN
N
AME
DAT
ATYPE
NUMERIC
SC
ALE
NUMERIC
PRE
CISION
ISNULLABLE
CHARACTER
MAXIMUM
LE
NGTH
CONS
TRAINT
N
AME
CONS
TRAINT
T
YPE
docid numeric 0 18 NO NULL PK_use
rgroup
PRIMA
RY KEYempname varchar NULL NULL YES 50
username varchar NULL NULL NO 50usergroup varchar NULL NULL YES 50
usertype varchar NULL NULL YES 50
category varchar NULL NULL YES 50
subcategory varchar NULL NULL YES 50
title varchar NULL NULL YES 50
filename varchar NULL NULL YES 50
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 40/99
31
DDU, Faculty of Technology, Department of Computer Engineering
foldername varchar NULL NULL YES 50
cur_date date NULL NULL YES NULL
8.
dbo.administration
This table used in FileUpload.aspx
Table 4.8 administration
COLUMN
NAME
DATATYPE
NUMERIC
SCALE
NUMERIC
PRECISION
ISNULLABLE
C
HARACTER
MAXIMUM
LENGTH
C
ONSTRAINT
NAME
C
ONSTRAINT
TYPE
username varchar NULL NULL YES 50
title varchar NULL NULL YES 50
filename varchar NULL NULL YES 50
filepath varchar NULL NULL YES 50
uploaddate date NULL NULL YES NULL
role varchar NULL NULL YES 50empname varchar NULL NULL YES 50
9.
dbo.abstract:
This table is used in Abstract.aspx and AbstractView.aspx
Table 4.9 abstract
COLUMN
NAME
D
ATATYPE
N
UMERIC
SCALE
N
UMERIC
P
RECISION
ISNULLABLE
CH
ARACTER
M
AXIMUM
LENGTH
CO
NSTRAINT
NAME
CO
NSTRAINT
TYPE
docid numeric 0 18 NO NULL PK_abstract
PRIMAR Y KEY
username varchar NULL NULL YES 50
empname varchar NULL NULL YES 50
user_group varchar NULL NULL YES 50
usertype varchar NULL NULL YES 50
category varchar NULL NULL YES 50
subcategory varchar NULL NULL YES 50
conferenceful
lname
varchar NULL NULL YES 50
title varchar NULL NULL YES 50
filename1 varchar NULL NULL YES 50
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 41/99
32
DDU, Faculty of Technology, Department of Computer Engineering
filename2 varchar NULL NULL YES 50
foldername varchar NULL NULL YES 50
cur_date date NULL NULL YES NULL
status varchar NULL NULL YES 50
comment varchar NULL NULL YES 8000
10. Dbo.groups:
This table is used in following pages:
Employee.aspx
Table 4.10 groups
COLUMN
NAME
DATATYPE
NUMERIC
SCALE
NUMERIC
PRECISION
ISNULLABL
E
CHARACTER
MAXIMUM
LENGTH
CONSTRAIN
T
NAME
CONSTRAIN
T
TYPE
group_code numeric 0 18 NO NULL PK_GroupPRIMARY
KEY
group_name varchar NULL NULL NO 25
11. Dbo.payband:
This table is used in following pages.
ManagePayband.aspx
Employee.aspx
Table 4.11 payband
COLUMN
NAME
DATATYPE
NUMERIC
SCALE
NUMERIC
PRECISION
ISNULLABLE
CHARACTER
MAXIMUM
LENGTH
CONSTRAINT
NAME
CONSTRAINT
TYPE
payband_id numeric 0 10 NO NULL PK_paybandPRIMAR
Y KEY
Payband varchar NULL NULL YES 50
grade_pay numeric 0 18 NO NULL
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 42/99
33
DDU, Faculty of Technology, Department of Computer Engineering
12. Dbo.aspnet_Membership:
This table is used in following pages:
Login1.aspx
CreateUserwiz.aspx
ChangePassword.aspx
Table 4.12 aspnet_Membership
COLUMN
NAME
DATATYPE
NUMERIC
SCALE
NUMERIC
PRECISION
ISNULLABLE
CHARACTER
MAXIMUM
LENGTH
CONSTRAINT
NAME
CONSTRAINT
TYPE
Application
Id
Unique
identifier NULL NULL NO NULL
FK_aspnet_
Me_Appli
FOREIG
N KEY
UserIdUnique
identifier NULL NULL NO NULL
PK_aspnet_
M
PRIMAR
Y KEY
Password nvarchar NULL NULL NO 128
Password
FormatInt 0 10 NO NULL
Password
Saltnvarchar NULL NULL NO 128
MobilePIN
nvarchar NULL NULL YES 16
Email nvarchar NULL NULL YES 256
Lowered
Emailnvarchar NULL NULL YES 256
Password
Questionnvarchar NULL NULL YES 256
Password
Answernvarchar NULL NULL YES 128
IsApproved Bit NULL NULL NO NULL
IsLocked
OutBit NULL NULL NO NULL
CreateDate datetime NULL NULL NO NULL
LastLogin
Datedatetime NULL NULL NO NULL
Last
Password
Changed
Date
datetime NULL NULL NO NULL
LastLockoutDate
datetime NULL NULL NO NULL
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 43/99
34
DDU, Faculty of Technology, Department of Computer Engineering
C
OLUMN
NAME
DATATYPE
N
UMERIC
SCALE
N
UMERIC
PRECISION
ISNULLABLE
CH
ARACTER
M
AXIMUM
LENGTH
CO
NSTRAINT
NAME
CO
NSTRAINT
TYPE
Failed
Password
Attempt
Count
Int 0 10 NO NULL
Failed
Password
Attempt
WindowStart
datetime NULL NULL NO NULL
FailedPassword
Answer
Attempt
Count
Int 0 10 NO NULL
Failed
Password
Answer
Attempt
WindowStart
datetime NULL NULL NO NULL
Comment ntext NULL NULL YES 1073741823
13. Dbo.aspnet_Roles:
This table is used in RoleMgmt.aspx page.
Table 4.13 aspnet_Roles
COLUMNNAME
DATATYPE
NUMERIC
SCALE
NUMERIC
PRECISION
ISNULLABLE
CHARACTER
MAXIMUM
LENGTH
CONSTRAINT
NAME
CONSTRAINT
TYPE
Application
Id
Unique
identifier NULL NULL NO NULL
FK_aspne
_Ro_Appli
FOREIG
N KEY
RoleId
Unique
identifier NULL NULL NO NULL
PK
_aspnet_R
PRIMAR
Y KEY
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 44/99
35
DDU, Faculty of Technology, Department of Computer Engineering
RoleName nvarchar NULL NULL NO 256
Lowered
Role
Name
nvarchar NULL NULL NO 256
Description nvarchar NULL NULL YES 256
14. Dbo.aspnet_Users:
This table is used in following pages:
Login1.aspx
RoleMgmt.aspx
Table 4.14 aspnet_Users
COLUMN
NAME
DATATYPE
NUMERIC
SCALE
NUMERIC
PRECISION
ISNULLABLE
CHARACTER
MAXIMUM
LENGTH
CONSTRAINT
NAME
CONSTRAINT
TYPE
Application
Id
Unique
identifier NULL NULL NO NULL
FK_aspnet
_Us_Appli
FOREIG
N KEY
UserIdUnique
identifier NULL NULL NO NULL
PK_aspnet_
U_
PRIMAR
Y KEY
UserName nvarchar NULL NULL NO 256
Lowered
UserNamenvarchar NULL NULL NO 256
Mobile
Aliasnvarchar NULL NULL YES 16
Is
AnonymousBit NULL NULL NO NULL
Last
Activity
Date
datetime NULL NULL NO NULL
15. Dbo.aspnet_UsersInRoles:
This table is used in RoleMgmt.aspx page.
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 45/99
36
DDU, Faculty of Technology, Department of Computer Engineering
Table 4.15 aspnet_UserInRoles
COLUMN
NAME
DATATYPE
NUM
ERIC
SC
ALE
NUM
ERIC
PRECISION
ISNULLABLE
CHAR
ACTER
MAX
IMUM
LENGTH
CONS
TRAINT
NAME
CONS
TRAINT
T
YPE
User
Id
Unique
identifier NULL NULL NO NULL
PK_aspnet
_U
FK_aspnet _Us_UserI
FK_aspnet _Us_UserI
PRIMAR
Y KEY
FOREIGN
KEY
Role
Id
Unique
identifier NULL NULL NO NULL
PK__aspnet_U
FK_aspnet
_Us_RoleI
FK_aspnet
_Us_RoleI
PRIMAR
Y KEY
FOREIGN
KEY
16. dbo.pmc
This table is used in PMCView.aspx.
Table 4.16 pmc
CO
LUMN
N
AME
DAT
ATYPE
NUMERIC
SCALE
NUMERIC
PRE
CISION
ISNU
LLABLE
CHARACTER
MAXIMUM
LE
NGTH
CONSTRAINT
N
AME
CONSTRAINT
T
YPE
Docid numeric 0 18 NO NULLPK_pmc
PRIMAR Y KEY
category varchar NULL NULL YES 50
projectname varchar NULL NULL YES 50
description varchar NULL NULL YES 500
username varchar NULL NULL YES 50
empname varchar NULL NULL YES 50
filename1 varchar NULL NULL YES 50Fpath varchar NULL NULL YES 100
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 46/99
37
DDU, Faculty of Technology, Department of Computer Engineering
cur_date date NULL NULL YES NULL
17. dbo.pmcuser
This table is used in PMCView.aspx.
Table 4.17 pmcuser
COLUM
N
NAME
DATATY
PE
NUMERIC
SCALE
NUMERIC
PRECISION
ISNULLA
BLE
CHARACTER
MAXIMU
M
LENGT
H
CONSTRA
INT
NAME
CONSTRA
INT
TYPE
username varchar NULL NULL YES 50
userfolder varchar NULL NULL YES 100
Fpath varchar NULL NULL YES 500
18. dbo.conference
This table is used in AddConference.aspx.
Table 4.18 conference
C
OLUMN
NAME
DA
TATYPE
N
UMERIC
SCALE
N
UMERIC
PR
ECISION
ISN
ULLABLE
CH
ARACTER
M
AXIMUM
L
ENGTH
CONSTRAINT
NAME
CONSTRAINT
TYPE
conf_id numeric 0 18 NO NULL PK_conference PRIMARYKEY
empname varchar NULL NULL YES 50
shortname varchar NULL NULL YES 50
conferencename varchar NULL NULL YES 50
Fromdate date NULL NULL YES NULL
Todate date NULL NULL YES NULL
submit_lastdate date NULL NULL YES NULL
Location varchar NULL NULL YES 50
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 47/99
38
DDU, Faculty of Technology, Department of Computer Engineering
Chapter 5
Implementation
5.1 Methods & their Description: Module wise
Table 5.1 Methods & their description: Module wise
1.
Simple Document
NAME
SPACE
CLASS(C# Page) METHOD/PROPERTY DESCRIPTION
IPR -> DocumentUpload-> View
BuildTree() Gets the root directory, createand add the root node to the tree
view
TraverseTree(DirectoryInfocurrentDirectory, TreeNode
currentNode)
Loop through each sub-directory in the current one,
create node and add to the treeview. Recursively call samemethod to go down the next
level of the tree.
clearscreen() Clears all filled up data in theform.
DocumentUpload btnSave_Click(object sender,EventArgs e) Inserts data into database.Throws an exception if any.
TreeView1_SelectedNodeCha
nged(object sender, EventArgse)
Gets the full path of the selected
node and displays the selected path and stores the document in
selected path.
View TreeView1_SelectedNodeChanged(object sender, EventArgs
e)
Fetches data from database based on selected node and
binds it to grid view.
View_btn(object sender,
EventArgs e)
Fetches data from database
based on given inputs and bindsit to grid view.
page_index(object sender,GridViewPageEventArgs e)
Binds the data source to the gridview and handles paging.
DownloadFile(object sender,EventArgs e)
Checks whether the selected filefrom grid view exists or not and
if it does then promptsdownloading pop-up otherwise
displays exception message.
txttodate_TextChanged(objectsender, EventArgs e)
Checks whether ‘from date’ isgiven or not. If not then
displays message.
txtfromdate_TextChanged(object sender, EventArgs e)
Checks whether ‘to date’ isgiven or not. If not then
displays message.
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 48/99
39
DDU, Faculty of Technology, Department of Computer Engineering
2.
Document Category
NAME
SPACE
CLASS(C# Page) METHOD/PROPERTY DESCRIPTION
IPR AddCategory Add(object sender, EventArgs
e)
Inserts data related to category
and subcategory to the database.Throws exception if any.
-> DocumentCategory-
>DocumentCategoryView
txtCategory_SelectedIndexChanged(object sender, EventArgs
e)
Based on selected category, populates the subcategory from
database and binds it to thedropdown control.
DocumentCategory btnSave_Click(object sender,EventArgs e)
Inserts data into database.Throws an exception if any.
DocumentCategoryView View_btn(object sender,EventArgs e)
Fetches data from database based on given inputs and binds
it to grid view.
GridView1_SelectedIndexCha
nging(object sender,GridViewPageEventArgs e)
Binds the data source to the grid
view and handles paging.
DownloadFile(object sender,
EventArgs e)
Checks whether the selected file
from grid view exists or not andif it does then prompts
downloading pop-up otherwisedisplays exception message.
txttodate_TextChanged(objectsender, EventArgs e)
Checks whether ‘from date’ isgiven or not. If not then
displays message.
txtfromdate_TextChanged(obj
ect sender, EventArgs e)
Checks whether ‘to date’ is
given or not. If not thendisplays message.
3. Abstract Document
NAME
SPACE
CLASS(C# Page) METHOD/PROPERTY DESCRIPTION
IPR -> _Abstract
-> Conference
btnSave_Click(object sender,
EventArgs e)
Inserts data into database.
Throws an exception if any.
_Abstract DropDownList2_SelectedIndex
Changed(object sender,EventArgs e)
Fetches values for dropdown
from database based onselected date from date pickerand populates related value for
textbox.
txtconference_DataBound(object sender, EventArgs e)
Binds null values to dropdownto remove previously boundvalues.
AbstractView View_btn(object sender,EventArgs e)
Identifies user roles and basedon that fetches values fromdatabase and binds it to gridview.
DownloadFile(object sender,EventArgs e)
Checks whether the selectedfile from grid view exists ornot and if it does then prompts
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 49/99
40
DDU, Faculty of Technology, Department of Computer Engineering
pop-up for downloadingotherwise displays exceptionmessage.
GridView1_SelectedIndexChanged(object sender, EventArgs e)
Identifies the selected row ofgrid view and checks user role.If the user is a normal userthen data is fetched anddisplayed in text area in readonly mode. If the user is‘Abstract head’ and status isnot assigned previously to theselected file, then dropdownand comment text area isshown.
Button2_Click(object sender,
EventArgs e)
Updates the new given status
in database for selected fileand checks the user role. If it is
‘Abstract head’ then reflectsgiven status in a grid viewotherwise not.
GridView1_SelectedIndexChanging(object sender,GridViewPageEventArgs e)
Binds the data source to thegrid view and handles paging.
GridView1_RowDataBound(ob
ject sender,GridViewRowEventArgs e)
Checks for the documents
having status ‘In Process’ andlast submission date within aweek and displays that row in‘red’ color.
4. User Folder Document
NAME
SPACE
CLASS(C# Page) METHOD/PROPERTY DESCRIPTION
IPR userfolder BuildTree() Identifies the user and sets thefolder of that user as a rootnode.
TreeView1_SelectedNodeChanged(object sender, EventArgs
e)
Gets the full path of the selectednode and displays the selected
path. Fetches the stored
documents in the user folderand binds to the grid view.
DownloadFile(object sender,EventArgs e)
Checks whether the selected filefrom grid view exists or not and
if it does then prompts pop-upfor downloading otherwisedisplays exception message.
5. Admin Document
NAMESPACE CLASS(C# Page) METHOD/PROPERTY DESCRIPTION
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 50/99
41
DDU, Faculty of Technology, Department of Computer Engineering
IPR FileUpload btnSave_Click(object sender,EventArgs e)
Identifies user role and insertsdata for particular user folderin database. It throws anexception if any.
FileUploadView View_btn(object sender,EventArgs e)
Identifies user roles and basedon that fetches values of that particular role from databaseand binds it to grid view.
6. PMC
NAME
SPACE
CLASS(C# Page) METHOD/PROPERTY DESCRIPTION
IPR PMC btnSave_Click(object sender,EventArgs e)
Inserts data into database.Throws an exception if any.
PMCView Page_Load(object sender,
EventArgs e)
Identifies the role and based
on that displays uploadeddocuments. Admin can viewall the uploaded file. Grouphead can see all thedocuments of his particulargroup and normal user can seeonly his uploaded documents.
5.2 Methods & their Description: Predefined
Table 5.2 Methods & their description: Predefined
SR.
NO
NAMESPACE CLASS METHOD/PROPERTY DESCRIPTION
1. System DateTime(Structur
e)
Now Gets a DateTImeobject that is set to thecurrent date and timeon this computer
Convert ToDateTime(string) Converts the specifiedstring representation ofa date and time to anequivalent date andtime value.
Exception Message Gets a message that
describes the currentexception.
2 System.Data.SqlClient SqlCommand SqlCommand() Initializes a newinstance of this class.
ExecuteNonQuery() Executes a Transact-SQL statement against
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 51/99
42
DDU, Faculty of Technology, Department of Computer Engineering
the connection andreturns the number ofrows affected.
ExecuteScalar() Executes the query,and returns the firstcolumn of the first rowin the result setreturned by the query.Additional columns orrows are ignored.
ExecuteReader() Sendsthe CommandText tothe Connection and
buildsa SqlDataReader.
SqlConnection SqlConnection() Initializes a newinstance of this class.
Open() Opens a databaseconnection with the
property settingsspecified bythe ConnectionString.
Close() Closes the connectionto the database.
SqlDataReader Read() Advancesthe SqlDataReader to
the next record.
3. System.Configuration ConfigurationManager
ConnectionStrings Gets theConnectionStringsSect
ion data for thecurrent application’sdefault configuration
4. System.IO DirectoryInfo DirectoryInfo(filepath) Initializes a newinstance ofthe DirectoryInfo classon the specified path.
GetDirectories() Returns thesubdirectories of thecurrent directory.
Path GetFullPath(path) Returns the absolute
path for the specified path string.
5. System.Web.UI.WebControls;
TreeNode TreeNode(rootDir.Name,rootDir.FullName)
Initializes a newinstance of theTreeNode class usingthe specified text and
value.
Button Button()
Initializes a new
instance of the Button
Class.
OnClick()Raises the Click event
of the Button Control.CausesValidation Gets or Sets a value
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 52/99
43
DDU, Faculty of Technology, Department of Computer Engineering
indicating whether
validation is performed
when the button
control is clicked.
ID
Gets or sets the
programmatic
identifier assigned to
the server control.
Text
Gets or sets the text
caption displayed in
the Button Control.
Visible
Gets or Sets a value
that indicates whether
a server control is
rendered as UI on the
page.
ContentPlace
Holder
Defines a region for
content in an
ASP.NET master page.
CreateUser
Wizard
Provides a user
interface for creating
new website user
accounts.
DropDownList DropDownList()
Represents a control
that allows the user to
select a single itemfrom a dropdown list.
DataBind()
Binds a data source to
the invoked server
control and all its child
controls.
ID
Gets or sets the
programmatic
identifier assigned to
the server control.
SelectedValueGets the value of theselected item in the list
control.
OnSelectedIndexChanged()
Raises the
SelectedIndexChanged
event. This allows you
to provide a custom
handler for the event.
GridView GridView()
Displays the values of
a data source in a tablewhere each column
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 53/99
44
DDU, Faculty of Technology, Department of Computer Engineering
represents a field and
each row represents a
record. This Control
enables you to select,
sort and edit this items.
AllowPaging
Gets or Sets a value
indicating whether the
paging feature is
enabled.
AllowSorting
Gets or Sets a value
indicating whether the
sorting feature is
enabled.
AutoGenerate
DeleteButton
AutoGenerate
EditButton
Gets or Sets a value
indicating whether a
CommandField fieldcolumn with a
delete/edit button for
each data row is
automatically added to
a gridview control.
Caption
Gets or Sets the text to
render in an HTML
caption element in a
gridview control.
DataSource
Gets or Sets the objectfrom which the data
bound control retrieves
its list of data items.
FooterRow
Gets a gridview object
that represents the
footer row in a
gridview control.
ID
Gets or sets the
programmatic
identifier assigned tothe server control.
Visible
Gets or sets a value
that indicates whether
a server control is
rendered as UI on the
page.
DataBind()Binds the data source
to the gridview control.
ImageButton
A control that displays
an image and respondsto mouse clicks on the
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 54/99
45
DDU, Faculty of Technology, Department of Computer Engineering
image.
LabelRepresents a labelcontrol, which displaystext on a web page.
LinkButton
Displays a hyperlink
style button control onweb page.
Login
Provides UI elements
for login into awebsite.
MenuDisplays a menu in anASP.NET web page.
Regular
ExpressionValidator
Validates whether thevalue of an associated
input control matchesthe pattern specified bya regular expression.
RequiredFieldValidator
Makes the associatedinput control arequired field.
SiteMapData
Source
Provides a data sourcecontrol that webservercontrols and other
controls can use to bind to hierarchicalsite map data.
SqlDataSourceRepresents a SQLdatabase to data-bound
controls.
TableDisplays a table on aweb page.
TextBox TextBox()Displays a texbox
control for user input.
ID
Gets or sets the
programmatic
identifier assigned to
the server control.
AutoPostBack
Gets or Sets a value
that indicates whetheran automatic postbackto the server occurswhen the textboxcontrol loses focus.
CausesValidation
Gets or Sets a value
indicating whether
validation is performed
when the button
control is clicked.
ReadOnly
Gets or Sets a valueindicating whether the
contents of the textboxcontrol can be
changed.
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 55/99
46
DDU, Faculty of Technology, Department of Computer Engineering
OnTextChange ()
Raises theTextChanged event.This allows you tohandle the event
directly.
6. System.Web.UI
This namespace
provides classes and
interfaces that enable
you to create
ASP.NET server
controls and ASP.NET
Web pages for the user
interface of your
ASP.NET Web
applications.
HtmlControls
The
System.Web.UI.HtmlC
ontrols
namespace contains
classes that allow you
to create HTML server
controls on a Web
Forms page.
7.
System.Web.Security Roles
Manages usermembership in rolesfor authorisation
checking in anASP.NET application.
AddUsersToRole()Adds the specifiedusers to the specified
role.
AddUserToRoles()Adds the specified userto the specified roles.
AddUserToRole()Adds the specified userto the specified role.
CreateRole()Adds a new role to thedatasource.
FindUsersInRole()
Gets a list of users in a
specified role whetheruser name contains thespecified user name tomatch.
GetAllRoles()Gets a list of all theroles for theapplication.
GetRolesForUsers(String)Gets a list of the rolesthat a user is in.
GetUsersInRole()Gets a list of users inthe specified role.
IsUserInRole(String,String) Gets a value indicatingwhether the specified
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 56/99
47
DDU, Faculty of Technology, Department of Computer Engineering
user is in the specifiedrole.
RemoveUserFromRole()Removes the specifieduser from the specifiedrole.
RoleExists()
Gets a value indicatingwhether the specifiedrole name already
exists in the roledatasource.
SqlMembershipProvider
Manages storage ofmembershipinformation for anASP.NET applicationin a SqlServerdatabase.
SqlRoleProvider
Manages storage of
Role membershipinformation for an
ASP.NET applicationin a SqlServerdatabase.
8.System.Linq
Provides classes andinterfaces that supportqueries that use LINQ.
9.
System.Collections
Contains interfaces and
classes that definevarious collections of
objects, such as lists,
queues, etc.10.
IPR Date_FileClass Date_FileClass()Creates an instance ofthis class.
ExtractDate(TextBox)
Returns date enteredin the textbox in(“yyyy/MM/dd”)format.
FileUp(FileUpload,TextBox,TextB
ox)
Renames the uploadedfile name.
5.3 Naming Conventions
We have followed the naming convention stated below while coding. We followed this at the
time of giving ID names of various Microsoft Visual Studio 2012 controls like Textbox,
TreeView etc.
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 57/99
48
DDU, Faculty of Technology, Department of Computer Engineering
Table 5.3 Naming Conventions
Sr. No. Control Name Convention followed
1. Textbox txtName
2. Label lblName
3. Dropdown List txtddName
4. TreeView TreeView1
5. Button btnButtonName
6. GridView GridView1
7. SqlDataSource SqlDataSource1
8. RequiredFieldValidator RequiredFieldValidator1
5.4 Error Handling
Err or 1: Error on passing NULL values.
Solution: In parameterized insert query, If you want to pass null value then write “ ”
in Parameters.AddWithValue’s argument instead of null.
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 58/99
49
DDU, Faculty of Technology, Department of Computer Engineering
Err or 2: Could not find resources:AjaxControlToolkit at compile time.
Solution: To use Ajax toolkit, drag ToolkitScriptManager from AjaxToolKit from
toolbox.
Err or 3: Could not load :AjaxControlToolkit
Solution: To solve it, drag and drop the .dll file of the ajax toolkit from the bin folder
of Ajax toolkit.
Err or 4: “Http:404 file not found”
When you write “localhost” in browser, it gives “Http:404 file not found” error.
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 59/99
50
DDU, Faculty of Technology, Department of Computer Engineering
Solution: In inet manager, change the port of IIS in binding section.
Err or 5: Logon failure because of unknown usename or bad password
Solution: Check your “Data Source” property of connectionstring in web.config file,
it must be your computer’s MSSQL 2012’s server name (we are using MSSQL 2012
for database) or you have to start MSSQL service manually if it is not started.
Err or 6: Could not find stored procedure 'dbo.aspnet_CheckSchemaVersion'.
Server Error in '/' Application.
--------------------------------------------------------------------------
Could not find stored procedure 'dbo.aspnet_CheckSchemaVersion'.
Solution: When we execute sql script of whole database then we have to run the
command given below.
Go to this path from command line :
“C:\Windows\Microsoft.NET\Framework\v4.0.30319”
Run the bellowed command:
aspnet_regsql.exe -S DBServerName -U DBLogin -P DBPassword -A all -
d DBName
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 60/99
51
DDU, Faculty of Technology, Department of Computer Engineering
Err or 7: Converting data type nvarchar to numeric.
Solution: Close and restart the sql server manager.
Err or 8: Calender is not displayed error.
Solution: Tags to be added at .aspx page are:
<%@ Register Assembly="AjaxControlToolkit" Namespace="AjaxControlToolkit"
TagPrefix="Ajax" %>
<Ajax:ToolkitScriptManager ID="ToolkitScriptManager1"
runat="server"></Ajax:ToolkitScriptManager>
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 61/99
52
DDU, Faculty of Technology, Department of Computer Engineering
Err or 9: Menu is hiding behind the report viewer:
Solution: Put a z-index property in the site.css class under
div.menu ul:
{
zindex:1;
}
And for report
.report
{
z-index:0;
}
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 62/99
53
DDU, Faculty of Technology, Department of Computer Engineering
Chapter 6
Testing
6.1. INTRODUCTION
Testing is the process carried out on software to detect the differences between its behaviour
and the desired behaviour as stipulated by the requirements specifications.
Testing is advantageous in several ways:
Firstly, testing gives an idea as to how reliable the software is.
Secondly, over time, the record of defects found reveals the most common kinds of defects,which can be used for developing appropriate preventive measures such as training, proper
design and reviewing.
6.2. TEST PLAN:
The testing sub-process includes the following activities in a phase dependent manner:
a) Create Test Plans.
b) Create Test Specifications.
c) Review Test Plans and Test Specifications.
d) Conduct tests according to the Test Specifications, and log the defects.
e) Fix defects, if any.
f) When defects are fixed continue from activity.
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 63/99
54
DDU, Faculty of Technology, Department of Computer Engineering
6.3. TEST STRATEGY:
A test strategy is an outline that describes the testing approach of the software development
life cycle. It is created to inform project managers, testers, and developers about some key
issues of the testing process. This includes the testing objective, methods of testing new
functions, total time and resources required for the project, and the testing environment.
Test strategies describe how the product risks of the stakeholders are mitigated at the test-
level, which types of test are to be performed, and which entry and exit criteria apply. They
are created based on development design documents. System design documents are primarily
used and occasionally, conceptual design documents may be referred to. Design documents
describe the functionality of the software to be enabled in the upcoming release.
6.4. TESTING METHODS:
6.4.1 Unit Testing:
Objective:
The primary goal of unit testing is to take the smallest piece of testable software in theapplication, isolate it from the remainder of the code, and determine whether it behaves
exactly as you expect. Each unit is tested separately before integrating them into modules to
test the interfaces between modules. Unit testing has proven its value in that a large
percentage of defects are identified during its use.
Testing Process:
Checking for availability of Code Walk-through reports which have documented
the existence of and conformance to coding standards.
Review of Unit Test Specifications.
Verify the Unit Test Specifications confirm to the program specifications.
Verify that all boundary and null data conditions are included.
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 64/99
55
DDU, Faculty of Technology, Department of Computer Engineering
6.5. Test Cases
Table 6.1 Test Cases
Sr.No.
Test Case Name Test CaseProcedure
Precondition ExpectedResult
Output
1. Login Enter the valid
username and password and
click on thelogin button.
Start the
browser andenter the valid
URL and usershould have
been created.
User should be
directed to thehome page
Success
Enter incorrectusername and password and
click on thelogin button
Start the browser andenter the valid
URL.
Message“Incorrect
username or password ”
should bedisplayed.
Success
2. Check User type andrights
Applicationmenus should
be visibledepending on
the type of
logged in user
Successfullogin.
Menus arevisible/invisibledepending on therole of the user
Success
3. Passwordchange
User clicks onthe change password
URL.
Successful login User enters thecurrent
password, new
password andconfirmation ofthe new
password.
Success
4. Logout User clicks onthe logout
link.
Successful login User should bedirected to theLogin page.
Success
5. User creation Enter the username,
password,
confirm password and
email.
Start the browser andenter the valid
URL.
Message “Usersuccessfully
created ” should
be displayed.
Success
Enter the password withthe length less
than 6.
Start the browser andenter the valid
URL.
Message“Password atleast
of length 6”should be
displayed.
Success
6. Simple documentupload
Specify the path where fileto be uploaded
and basicdetails of file.
Successfullogin.
Message “Fileuploaded
Successfully ”
should bedisplayed.
Success
Specify basicdetails of files
without
Successful login Message “Pleaseselect the path ”
should be
Success
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 65/99
56
DDU, Faculty of Technology, Department of Computer Engineering
choosing the path
displayed.
7. View simple document User clicks onthe view
button andmay or maynot apply
filters to viewresults.
Successful login Uploaded Filesof selecteddirectory should be displayed todownload.
Success
8. Categorized documentupload
User selectsthe appropriatecategory and
file.
Admin musthave addedcategories-subcategories.
Message “FileUploadedSuccessfully ”should be
displayed.
Success
9. Categorized documentview
User clicks onthe view
button and
may or maynot apply
filters to viewresults.
Successful loginand rolechecking.
Uploaded Filesshould bedisplayed to
download.
Success
10. Approval of
document
Abstract
head/Abstract
admin selects
the
appropriate
decision first
time.
Successful
login and role
checking.
Abstract
admin’s status
reflects on the
view page
,disable the
decision
selection and
send decisionmail to user
Success
After
decision
given once,
Abstract
head/Abstract
admin clicks
on the select
link.
Successful
login and role
checking.
Previous
decision is
shown in read
only mode.
Success
11. Administration
document upload
User inserts
the details ofdocument to
be uploaded
and upload it.
Successful
login and rolechecking.
Message “File
UploadedSuccessfully ”
should be
displayed and
file stored in
particular
Admin’s folder.
Success
View Administration
document
User clicks
on the view
button and
may or may
not apply
filters to
Successful
login and role
checking.
Uploaded Files
should be
displayed to
download
according to
role.
Success
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 66/99
57
DDU, Faculty of Technology, Department of Computer Engineering
view results.
12. PMC document
upload
User inserts
the details of
document to
be uploaded
and upload it.
Successful
login and role
checking.
Uploaded Files
should be
displayed to
download
according torole.
Success
View PMC
document
User clicks
on the view
button and
may or may
not apply
filters to
view results.
Successful
login and role
checking.
Uploaded Files
should be
displayed to
download
according to
role.
Success
13. User folderwise
document view
User clicks
on the view
button/folder.
Successful
login and that
user’s folder
must becreated before.
Uploaded Files
should be
displayed to
downloadaccording to
username.
Success
14. Creation of Roles
Enter the
name of the
new role to
be created
User must be
logged in as
Admin and the
role entered
should not
already exist
The role is
successfully
created
Success
15.
Assigning/
Removing Roles
from a User
Select a
Username
and assign
new roles or
remove
existing roles
of that user.
User should be
logged in as
Admin.
Role(s)
successfully
assigned/
removed from a
user
Success
16. Assigning/RemovingUsers from a Role
Select a
Rolename
and add ordelete Users
of that role.
User should be
logged in asAdmin.
User(s)
successfullyadded/removed
from that role.
Success
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 67/99
58
DDU, Faculty of Technology, Department of Computer Engineering
6.6 ScreenShots
Figure 6.1 Login Page
Figure 6.2 Home Page
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 68/99
59
DDU, Faculty of Technology, Department of Computer Engineering
6.6.1 Create User
Figure 6.3 Page to create new user by Admin
6.6.2 Change Password
Figure 6.4 Page to change password by user
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 69/99
60
DDU, Faculty of Technology, Department of Computer Engineering
6.6.3. Upload Document (Table: document)
Figure 6.5 Page to upload document in selected folder
Figure 6.6 Acknowledge of successful document upload
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 70/99
61
DDU, Faculty of Technology, Department of Computer Engineering
Figure 6.7 Validations on document upload
Figure 6.8 View of document upload
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 71/99
62
DDU, Faculty of Technology, Department of Computer Engineering
Figure 6.9: Filtered view based on from-to dates.
User selects From date and To date to see results.
Figure 6.10: View based on selected folder.
User selects particular folder to see results.
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 72/99
63
DDU, Faculty of Technology, Department of Computer Engineering
6.6.4. Document Category (Table: usergroup)
Figure 6.11: Validations.
Figure 6.12: Selection of categories.
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 73/99
64
DDU, Faculty of Technology, Department of Computer Engineering
Figure 6.13 Acknowledge of successful document upload
Figure 6.14 Admin view of all uploaded files regardless of any user
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 74/99
65
DDU, Faculty of Technology, Department of Computer Engineering
Figure 6.15 User view of uploaded files (particular user files)
Figure 6.16 Filtered View
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 75/99
66
DDU, Faculty of Technology, Department of Computer Engineering
6.6.5
Add Categories
Figure 6.17 Add categories (Only admin can add)
6.6.6. Abstract Document (Table: abstract)
Figure 6.18 Validations on Abstract document
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 76/99
67
DDU, Faculty of Technology, Department of Computer Engineering
Figure 6.19 Normal User uploads document
Figure 6.20 Acknowledge of successful document upload
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 77/99
68
DDU, Faculty of Technology, Department of Computer Engineering
Figure 6.21 Admin view of uploaded files (documents having last submission
date within a week and still “In Process” is displayed in red)
Figure 6.22 User view of Abstract
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 78/99
69
DDU, Faculty of Technology, Department of Computer Engineering
Figure 6.23 Filtered view
Figure 6.24 user view for uploaded file when click on “Select”
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 79/99
70
DDU, Faculty of Technology, Department of Computer Engineering
Figure 6.25 Abstract admin view for approving document
Figure 6.26 Abstract head approves the document
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 80/99
71
DDU, Faculty of Technology, Department of Computer Engineering
Figure 6.27 Abstract head’s status is reflected
6.6.7 Add Conference
Figure 6.28 Admin can add new conferences
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 81/99
72
DDU, Faculty of Technology, Department of Computer Engineering
Figure 6.29 Successfully added new conference
Figure 6.30 List of conferences and editing can be done
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 82/99
73
DDU, Faculty of Technology, Department of Computer Engineering
6.6.8 Admin Document (Table: administration)
Figure 6.31 Validations
Figure 6.32 Role wise file is stored in particular folder
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 83/99
74
DDU, Faculty of Technology, Department of Computer Engineering
Figure 6.33 Acknowledge of successful upload
Figure 6.34 View of uploaded documents with employee’s name
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 84/99
75
DDU, Faculty of Technology, Department of Computer Engineering
Figure 6.35 Filtered view of uploaded document by department name
6.6.9. User Folder (Table: userfolder)
Figure 6.36 Identifies user and path from database and displays the folder and
also it is physically existed.
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 85/99
76
DDU, Faculty of Technology, Department of Computer Engineering
Figure 6.37 Shows the stored files in the user folder (if subfolders are there then
manual entry of that path should be done in database)
6.6.10. Project Management Cell (PMC)
Figure 6.38 User selects the project name from dropdown. Dropdown shows
only particular user’s projects’ names.
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 86/99
77
DDU, Faculty of Technology, Department of Computer Engineering
Figure 6.39 Acknowledge of successful upload
Figure 6.40 User can view the list of all the uploaded
documents of his projects
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 87/99
78
DDU, Faculty of Technology, Department of Computer Engineering
Chapter 7
Conclusion & Future Extensions
Our main goal while developing this Document Management System was to fulfil the main
functional requirements that the IPR had. We had to make sure that our system was easy to
navigate through and we developed its interface keeping in mind the ease of use for the user
and also that the user may/may not belong from a technical background. DMS provides the
functionality like document upload, document download, document approve/regret/comment
decision.
Possible future extensions to this “Document Management System” are listed as follows:
In future, Abstract document module will be enhanced for each department and if
there is no abstract head or admin for particular department to give the decision,
external admin will be added to the system for that department related documents and
he will handle the documents.
Another possible future extension could be constraints on documents like size
restriction, file types i.e. only .pdf files can be uploaded or no .jpg files should be
uploaded.
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 88/99
79
DDU, Faculty of Technology, Department of Computer Engineering
Appendix A
Initial Learning
Installation and Environment Setup:
We have created this system using Microsoft Visual Studio and Microsoft SQL Server
(For our database needs). We decided to use Microsoft Visual Studio and Microsoft SQL
Server as our development platform because IPR wanted an application that could be
created easily.
Visual Studio offers a comprehensive development environment for building standards-
based web applications and services. It improves productivity by allowing users to rapidly
develop, test and deploy web solutions. Microsoft SQL Server is a very stable and fast
database engine. There is a tremendous amount of support and resources available on the
web. It is tightly integrated with the Windows Server security settings. This allows for a
quick installation on your existing server.
Installation Specification:
Windows OS 7, 64 bit & Service Pack 1
Microsoft SQL Server 2012, 64 bit
.net Framework 4.0 & IIS 7 or higher
Microsoft Visual Studio 2012
In order to get familiar with MS Visual Studio and MS SQL database, we developed two
modules:
CHSS card
Employee
These helped us to understand the following concepts.
1.
Master page and Site Map:
Master Pages provide the mechanism for creating consisting web pages and give the
developer a centralised way of changing the UI elements that need to be changed
across all the pages of the web application.
Following is the master page which we had developed.
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 89/99
80
DDU, Faculty of Technology, Department of Computer Engineering
Figure 1: Master Page
Maintaining the menu of a large web application is difficult and time consuming. In
ASP.NET, the site navigation system uses an XML file that contains the site
hierarchy.
This sitemap file must be located in the application root directory, though it can
reference other sitemap providers or other sitemap files in other directories as long as
those files are in the same application.
2. WSAT(Web Site Administration Tool ):
This tool is a utility provided along with MS Visual Studio which assists in
configuration and administration of a web site/application. The security tab is used to
create users and roles, group users under different roles and assign access rules either
at the role-level or user-level. The database that stores ASP.NET membership-related
information, by default, is called ASPNETDB . The security tab simplifies and
optimizes user authentication and authorization. Major drawback of this tool is that
access rules could be defined only at the folder-level and not at the page level.
3. Ajax Control Toolkit:
The ASP.NET Ajax control kit is an open source project built on top of Microsoft
ASP.NET Ajax Framework. It provides a powerful infrastructure to write reusable,
customizable and extensible ASP.NET Ajax extenders and controls, as well as a rich
array of controls that can be used out of the box create an interactive web experience.
The first step is to download the Ajax Control Toolkit. The next step is to add it to the
Visual Studio Toolbox. Follow these steps:
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 90/99
81
DDU, Faculty of Technology, Department of Computer Engineering
Create a new Tool Box tab by right clicking the toolbox and selecting “Add Tab”.
Name the new tab “Ajax”.
Right click beneath the new tab and select the menu option “Choose Items”.
Click the Browse button and browse to the folder where you extracted the Ajax
Control Toolkit. Pick the AjaxControlToolkit.dll and click the “ok” button to close the “Choose
Toolbox Items” dialog .
From this toolkit , we have majorly used “CalendarExtender ” control.
4.
Validations:
In the modules that we created, we had to ensure that the data entered through our
forms was validated that is we had to make sure that the user did not provide any
incorrect data. So to fulfil this requirement we used the “Validation control” provide d
in the Microsoft visual studio tool box.
We learnt about various types of validators:
Required Field Validator:
This ensures that the field on which this validator is applied is not left blank.
Regular Expression Validator:
This ensures that the field on which this validator is applied only accepts that data
which matches the specified regular expression.
Custom validator:
This ensures that the field on which this validator is applied only accepts that datawhich matches the conditions specified in the custom defined method.
5. File Uploading:
The “file upload” control enables you to provide user with a way to send a file from
their computer to the server at a specific location. You can also limit the size of the
file and examine the properties of the uploaded file before storing.
We used this control to upload a file to the server. In addition to this, we also created
a class “Date_FileClass.cs” which renamed the uploaded file as per IPR’s
requirement. Also to limit the size of the uploaded file to 1 MB, we used a custom
validator.
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 91/99
82
DDU, Faculty of Technology, Department of Computer Engineering
6. Data Migration:
After installing the Microsoft SQL Server Management Studio and creating the
desired tables, the next important task was to populate these tables with the available
data.
We achieved this task in 2 ways:
From text format (.csv file)
Initially, our data was in MS Excel and needed to be transferred to the respective
tables. We did this as follows:
I. We first separated all the columns by placing a delimiter (comma, space)
between them.
II. This delimited file was saved in .csv format.
III.
The data from this .csv file was copied to a .txt file (in Notepad).IV. Open SQL Server Management Studio, then right click on your database
and select “Import Data”.
V. In the “Import & Export Wizard”, follow the steps as below:
(1) Choose the “Data Source” as “Flat File Source”.
(2) Select the delimiter as “Comma” (,).
(3) And change the data types and lengths of the columns as defined in the tables.
From SQL Scripts
This method was useful when we wanted to transfer selected tables (schema and
data) from one laptop to another and also between different versions of MS SQL
Server Management Studio.
I. In SQL Server Management Studio, right click on the database name &
select “Task” then “Generate Scripts”.
II. Then follow the steps in the Wizard and select the tables you wish to
generate the scripts for.
III.
In “Advanced Scripting Options”, choose “Schema & Data” for “Types of
data to Script” property.
IV. Save the generated script at the desired location.
V. Now execute this script on the computer where you want to transfer the
data.
7. User & Role Creation in SQL Server Manager:
This enabled us to create different database users having different roles. Its advantage
is that it provides added security as we can give table/column-level access permissions to the user.
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 92/99
83
DDU, Faculty of Technology, Department of Computer Engineering
Order of creation: Login -> Role -> User
LOGIN:
Allows you to enter into the SQL Server. Many USERS may be mapped to the
same login BUT each of these users should be linked with a different database.Steps to follow:
I. Security -> new login -> untick "enforce password expiration"
II.
Select "default database" as your database name.
III.
In the "user mapping" tab, the username is automatically generated, may
change the schema (ex. to "dbo")
IV.
Tick your database name as the database.
V.
For "database role membership" option, select public or if a role is created
then may select that.
VI. Rest need not be changed.
ROLES:
Steps to follow:
I. Rt. click on your database -> new database role
II. Role name: Give a role name.
III.
"owner" and "schemas owned by this role" may be left blank
IV.
Role Members: can add a user to this role from the browse option.
V.
"Securable" section: Choose "All objects of the type" - then may select
database/tables etc. depending on the requirement.
VI.
If we choose tables, then select the table you want to give permissionsfrom the “grant/deny/don’t grant” columns.
8. Encryption and Decryption:
Protected Configuration helps improve the security of an application by enabling you
to encrypt sensitive information that is stored in a configuration file. The .NET
framework automatically decrypts the configuration file when the configuration file is
processed, and decryption does not require any additional code.
Steps:
Create a custom RSA Key container. The following command will create the
“MyKeys” Key container.
aspnet_regiis –pc “MyKeys” – exp
Granting read access to an RSA Encryption Key. Before ASP.NET can decrypt
encrypted information that is in the web.config file, the identity of your application
must have read access to the encryption key that is used to encrypt and decrypt the
encrypted sections.
aspnet_regiis –pa “MyKeys” “NT AUTHORITY\ NETWORK SERVICE”
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 93/99
84
DDU, Faculty of Technology, Department of Computer Engineering
Next specify an instance of a Protected Configuration provider in the web.config file.
The following command encrypts the < connectionStrings> element of the web.config
file.
aspnet_regiis –pe “connectionStrings” –app “/MyApplication” –prov “MyProvider”
To access the decrypted configuration settings give the following command.
aspnet_regiis –pd “connectionStrings” –app “/MyApplication” –prov “MyProvider”
9. Publishing our Web Application:
For publishing a Web Application, right click on the root folder and then click on
Publish carry out the following steps.
I.
Publish Web Wizard:You can choose or create a profile for your web application. A publish profile
specifies the server you are deploying to, the credentials needed to log on to
the server, the databases to deploy, and other deployment options.
Figure 2: Publish Profile
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 94/99
85
DDU, Faculty of Technology, Department of Computer Engineering
II. Configuring the Connection Tab:
Select a value from the “Publish method” list. The “File System” publish
method publishes the web application to a folder that you specify.
Figure 3: Connection Tab
III.
Configuring the Settings Tab:
Figure 4: Settings Tab
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 95/99
86
DDU, Faculty of Technology, Department of Computer Engineering
IV. Previewing Changes & Publishing the Project:
Figure 5: Preview
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 96/99
87
DDU, Faculty of Technology, Department of Computer Engineering
Appendix B
Data Flow Diagrams
Data Flow Diagram Level-0
Document
Management
System
0
Admin
Simple
User
Abstract
Head
Abstract
admin
Manage roles and
users
Manage
conference
Add categories and
sub-categories
Gives final regret/
approve/comment
decision
Gives temporary
regret/approve/
comment decision
Upload
document
List of uploaded
documents
Data Flow Diagram Level 0
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 97/99
88
DDU, Faculty of Technology, Department of Computer Engineering
Data Flow Diagram Level-1
Upload
Abstract
Document
0.6
Manage
Users and
Roles
0.1
View
documents
0.3
Login user
0.2
Manage
categories and
sub-categories
0.5
Manage
conference
0.4
Username and
passwordDisplay home
page
Add
conference
Display
conference
Add category
and sub-
category
Upload abstract
document
Display status
Upload document
Display document
details
Abstract
document
details
Document
details
User
details
Roles
details
Conference
details
Categories and
sub-categories
details
Add roles and
users
Data Flow Diagram Level 1
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 98/99
89
DDU, Faculty of Technology, Department of Computer Engineering
Data Flow Diagram Level-2
Upload
abstract
document
0.6.1
Give
decision
0.6.2
Displaydecision
0.6.3
View
abstract
document
0.6.4
User
details
Abstract
document details
Pending
status details
Temporary
status details
Final status
details
Roles
details
Username
and password
Send decision
Send request
Data Flow Diagram Level 2
8/18/2019 Document Management System Report
http://slidepdf.com/reader/full/document-management-system-report 99/99
90
Bibliography
The following resources and websites have been of immense help in understanding .NETtechnology.
msdn.microsoft.com
www.asp.net/webforms
www.stackoverflow.com
www.codeproject.com
weblogs.asp.net
www.youtube.com
The large number of videos available on the Microsoft site helped us to get our basics
right.