Documentation

13SOECE11041 Introduction
13SOEIT11024
TABLE OF CONTENTS
1. INTRODUCTION........................................................................................................... 2
1.1. Existing System ................................................................................................................. 3
1.2. Need for the New System .................................................................................................. 4
1.3. Objective of the New System ............................................................................................ 5
1.4. Problem Definition ............................................................................................................ 6
1.5. Core Components .............................................................................................................. 7
1.6. Project Profile .................................................................................................................... 8
1.7. Assumptions and Constraints............................................................................................. 9
1.8. Advantages and Limitations of the Proposed System...................................................... 10
1.9. Proposed Time Line Chart ............................................................................................... 11
2. REQUIREMENT DETERMINATION & ANALYSIS ............................ 12

2.1. Requirement Determination ............................................................................................. 12
2.2. Targeted Users ................................................................................................................. 12
2.3. Feasibility Analysis ......................................................................................................... 13
2.4. Requirement Specification............................................................................................... 14
3. SYSTEM DESIGN........................................................................................................ 15
3.1. Use Case Diagram ........................................................................................................... 15
3.2. Class Diagram .................................................................................................................. 18
3.3. Interaction Diagram ......................................................................................................... 23
3.4. Activity Diagram ............................................................................................................ 32
3.5. Data Dictionary ................................................................................................................ 48
3.6. User Interface Design ...................................................................................................... 60
3.7. Report Design ................................................................................................................ 118
4. DEVELOPMENT........................................................................................................ 119
4.1. Coding Standards ........................................................................................................... 119
5. TESTING......................................................................................................................... 120
5.1. Test Plan & Testing Method .......................................................................................... 120
5.2. Test Cases ...................................................................................................................... 122
6. IMPLEMENTATION ............................................................................................... 130

7. PROPOSED ENHANCEMENTS ....................................................................... 130
8. CONCLUSION ............................................................................................................. 132
9. BIBLIOGRAPHY ....................................................................................................... 133
CE-IT 1|Page
13SOEIT11024
1. INTRODUCTION
In document managing system, the process of manual work that has been carried out
across almost all Law forms.
Its very difficult to search documents based on meta data such as document owner,
created date which is a difficult task.
It becomes more difficult when there are multiple users exist in system for searching
same document, user can access all documents and may miss use any document.
Today, we need not maintain all documents on all machine. For this reason, the
development of this application is come into existence using web platform.
CE-IT 2|Page
13SOEIT11024
1. EXISTING SYSTEM
The Existing system in the Law farm involves maintenance of all documents related to
cases.
When the user wants to search specific file (s)he need to find via windows explorer.
For quick access user need to store path to same file in somewhere.
Print out
Take HDD of
document for
client
proof
Existing
eZArchiving
System
Search for any

Store its path
document
CE-IT 3|Page
13SOEIT11024
2. NEED FOR THE NEW SYSTEM
Following are the reasons for need of new system
Risk: All the operations are performing on clients data! It is very risky.
Data on single place: All data are store on single place we cannot copy it to other disk
storage; it may lose Meta data of documents.
Report: At the various reports are tabulated manually they are not such attractive and
require more time. In exist system there is very difficult to generate reports manually.
Multiple user: If multiple user wants to access/search file then it is impossible because
all documents are stored on single disk.
Permissions: All users can access to all data; any user may misuse those data or
delete.
Easy retrieve: If user want to store document for then (s)he can easily store its path.
To overcome the entire above problem and to lessen the overburden following system
comes into existence.
CE-IT 4|Page
13SOEIT11024
3. OBJECTIVE OF THE NEW SYSTEM
Lessen the overburden: Due to the manual system, overburden for mentor becomes
high. Due to new system, the allocation of the work can be made easy.
Centralized system: Centralized system plays the vital role. With the help of
centralized system, the data can be viewed from anywhere and at any time.
Generate Reports: As the system made centralized and store at the one place
generation of the reports becomes easy, fast and accurate result can be provided.
Reducing the human errors: Manual works would consist of various human error,
which is difficult to modify, but computerized system can solve these problem.
User-friendly System: The main objective of the new system is to have user-friendly
system so that it become easy to understand by the nonprofessional.
CE-IT 5|Page
13SOEIT11024
4. PROBLEM DEFINITION
In Law firm, it is very difficult to manage all of the documents by single user. For
providing online efficient document managing system for all stack holders such as Admin
and User, and provide different type of permissions to all users such that users can search
and preview/download document with permissions.
CE-IT 6|Page
13SOEIT11024
5. CORE COMPONENTS
Component Description
Users Users can access all documents with permissions, search documents
based on meta data, and make comments on those documents as well
as store assign tags to documents and view/download those
documents.
Admin Admin can import case folders & archive those cases, add users,
manage roles & permissions for users, view reports based on users
operations, as well as all of the operations performed by user.
CE-IT 7|Page
13SOEIT11024
6. PROJECT PROFILE
Project Title eZArchival
Developed at Capital Novus (Logical Software Solutions) Pvt. Ltd.
Type of Application Web Application
Front End Tool ASP.NET, C# and Extjs-5.1.1(JavaScript Framework)
Back End Tool SQL SERVER 2014
IDE Used Visual Studio 2015
Browsers Mozilla Firefox, Google Chrome, Microsoft Edge
Project Duration 19th Dec 2016 to 24th Mar 2017
Internal Guide
External Guide Mr. Mayur Manvar
Submitted By
Submitted To
Team Members
CE-IT 8|Page
13SOEIT11024
7. ASSUMPTIONS AND CONSTRAINTS
1.7.1 Assumption
All files Meta data are not altered.
Import operation perform only from computer where service was installed,
however it can access from anywhere.
1.7.2 Constraint
Only text/image documents can be preview online.
User cannot download their tag/comment data however, admin can see audit.
CE-IT 9|Page
13SOEIT11024
8. ADVANTAGES AND LIMITATIONS OF THE PROPOSED

SYSTEM
1.8. 1 Advantage of Proposed System
Maintain document access based on roles & permissions.

Multiple users can work together from different place.
User can place comment/tag, which will be visible to all users.
Archive and restore any folder.
Easily generate reports on certain parameters.
Centralized system for all users.
1.8.2 Disadvantage of Proposed System

Because of large amount of data, it is little bit difficult for admin to audit any user
operation however, admin can perform audit.
CE-IT 10 | P a g e
13SOEIT11024
9. PROPOSED TIME LINE CHART
CE-IT 11 | P a g e
13SOECE11041 Requirement Determination & Analysis
13SOEIT11024
2. REQUIREMENT DETERMINATION & ANALYSIS
1. REQUIREMENT DETERMINATION
2.1.1 Observation:
By Observing the Process carried out by the law firm we able to know about the overburden
and complexity of the work.
Its very time consuming process.

Taught to search any document based on Meta data.
Lake of permission & roles.
Very difficult to audit by admin.
Difficult to manage users data.
2. TARGETED USERS
There are two types of Targeted Users including Students.
Admin
User
CE-IT 12 | P a g e
13SOEIT11024
3. FEASIBILITY ANALYSIS
2.3.1. Economic Feasibility
Proposed system requires larger Database and disk storage.
As it was developed in an MNC it become much costlier.
However, our client can afford those for proposed system therefor this system is
economic feasible.
2.3.2. Technical Feasibility

Main requirement of this system is store data in centralized place and provide
search & report generating facility which can possible with current technology so
this system is practical.
So, this system is technical feasible
2.3.3. Operational Feasibility

This system requires following software to work:
o Computer system with Internet connection or connected to network where
these systems get install.
o Client System with the browser like Google Chrome, Mozilla Firefox, Safari,
Opera, etc.
o Our windows service installer & HDD for importing case folders.
Microsoft Office Excel or Notepad.
o Therefore, this system is operationally feasible because all of this software is
available for work.
CE-IT 13 | P a g e
13SOEIT11024
4. REQUIREMENT SPECIFICATION
2.4.1. Functional Requirements
Documents Meta data must be correct.

Admin would able to upload case folder at any time.
User able to search any documents, and place comments/tags on those.
User can archive entire case folder.
Admin is able to manage users, permissions, roles, tags, comment headers.
2.4.2. Non-Functional Requirements
These systems would have following characteristics:
Performance
Capacity
Availability
Reliability
Maintainability
CE-IT 14 | P a g e
13SOECE11041 System Design
13SOEIT11024
3. SYSTEM DESIGN
1. USE CASE DIAGRAM
Basic Use Case Diagram Symbols and Notation:
System
Draw your system's boundaries using a rectangle that contains use cases. Place actors
outside the system's boundaries.
Use Case
Draw use cases using ovals. Label the ovals with verbs that represent the system's
functions.
Actors
Actors are the users of a system. When one system is the actor of another system, label the
actor system with the actor stereotype.
Relationships
Illustrate relationships between an actor and a use case with a simple line. For
relationships among use cases, use arrows labeled either "uses" or "extends." A "uses"
relationship indicates that one use case is needed by another in order to perform a task. An
"extends" relationship indicates alternative options under a certain use case.
Use case: For User

CE-IT 15 | P a g e
13SOEIT11024
CE-IT 16 | P a g e
13SOEIT11024
Use case: For Admin
CE-IT 17 | P a g e
13SOEIT11024
2. CLASS DIAGRAM
Class Diagram Symbols and Notation:
Classes
Classes represent an abstraction of entities with common characteristics. Associations
represent the relationships between classes.
Illustrate classes with rectangles divided into compartments. Place the name of the class in
the first partition (centered, bolded, and capitalized), list the attributes in the second
partition (left-aligned, not bolded, and lowercase), and write operations into the third.
Active Classes
Active classes initiate and control the flow of activity, while passive classes store data and
serve other classes. Illustrate active classes with a thicker border.
Visibility
Use visibility markers to signify who can access the information contained within a class.
Private visibility, denoted with a - sign, hides information from anything outside the class
partition. Public visibility, denoted with a + sign, allows all other classes to view the
marked information. Protected visibility, denoted with a # sign, allows child classes to
access information they inherited from a parent class.
CE-IT 18 | P a g e
13SOEIT11024
Associations
Associations represent static relationships between classes. Place association names above,
on, or below the association line. Use a filled arrow to indicate the direction of the
relationship. Place roles near the end of an association. Roles represent the way the two
classes see each other.
Multiplicity (Cardinality)
Place multiplicity notations near the ends of an association. These symbols indicate the
number of instances of one class linked to one instance of the other class. For example,
one company will have one or more employees, but each employee works for just one
company.
CE-IT 19 | P a g e
13SOEIT11024
Constraint
Place constraints inside curly braces {}.
Composition and Aggregation

Composition is a special type of aggregation that denotes a strong ownership between
Class A, the whole, and Class B, its part. Illustrate composition with a filled diamond. Use
a hollow diamond to represent a simple aggregation relationship, in which the "whole"
class plays a more important role than the "part" class, but the two classes are not
dependent on each other. The diamond ends in both composition and aggregation
relationships point toward the "whole" class (i.e., the aggregation).
CE-IT 20 | P a g e
13SOEIT11024
Generalization
Generalization is another name for inheritance or an "is a" relationship. It refers to a
relationship between two classes where one class is a specialized version of another. For
example, Honda is a type of car. So the class Honda would have a generalization
relationship with the class car.
CE-IT 21 | P a g e
13SOEIT11024
Class Diagram
CE-IT 22 | P a g e
13SOEIT11024
3. INTERACTION DIAGRAM
Sequence Diagram Symbols and Notation
Class Roles or Participants

Class roles describe the way an object will behave in context. Use the UML object symbol
to illustrate class roles, but don't list object attributes.
Activation or Execution Occurrence

Activation boxes represent the time an object needs to complete a task. When an object is
busy executing a process or waiting for a reply message, use a thin gray rectangle placed
vertically on its lifeline.
Messages
Messages are arrows that represent communication between objects. Use half-arrowed
lines to represent asynchronous messages. Asynchronous messages are sent from an object
that will not wait for a response from the receiver before continuing its tasks. For message
types, see below.
CE-IT 23 | P a g e
13SOEIT11024
Lifelines
Lifelines are vertical dashed lines that indicate the object's presence over time.
Types of Message in Sequence Diagram
Synchronous Message
A synchronous message requires a response before the interaction can continue. It's
usually drawn using a line with a solid arrowhead pointing from one object to another.
Asynchronous Message
Asynchronous messages don't need a reply for interaction to continue. Like synchronous
messages, they are drawn with an arrow connecting two lifelines; however, the arrowhead
is usually open and there's no return message depicted.
Reply or Return Message

A reply message is drawn with a dotted line and an open arrowhead pointing back to the
original lifeline.
Self Message
A message an object sends to itself, usually shown as a U shaped arrow pointing back to
itself.
CE-IT 24 | P a g e
13SOEIT11024
Create Message
This is a message that creates a new object. Similar to a return message, it's depicted with
a dashed line and an open arrowhead that points to the rectangle representing the object
created.
Delete Message
This is a message that destroys an object. It can be shown by an arrow with an x at the
end.
Found Message
A message sent from an unknown recipient, shown by an arrow from an endpoint to a
lifeline.
Lost Message
A message sent to an unknown recipient. It's shown by an arrow going from a lifeline to
an endpoint, a filled circle or an x.
CE-IT 25 | P a g e
13SOEIT11024
Sequence: Login
CE-IT 26 | P a g e
13SOEIT11024
Sequence: Forget Password
CE-IT 27 | P a g e
13SOEIT11024
Sequence: Add Comment Header
CE-IT 28 | P a g e
13SOEIT11024
Sequence: Edit Profile
CE-IT 29 | P a g e
13SOEIT11024
Sequence: Generate Reports
CE-IT 30 | P a g e
13SOEIT11024
Sequence: Import Case
CE-IT 31 | P a g e
13SOEIT11024
Sequence: Archive Case
CE-IT 32 | P a g e
13SOEIT11024
Sequence: Assign Tag
CE-IT 33 | P a g e
13SOEIT11024
Sequence: Manage Permissions
CE-IT 34 | P a g e
13SOEIT11024
Sequence: Assign Role to User
CE-IT 35 | P a g e
13SOEIT11024
4. ACTIVITY DIAGRAM
Activity Diagram Symbols and Notation:
Initial State or Start Point

A small filled circle followed by an arrow represents the initial action state or the start
point for any activity diagram. For activity diagram using swimlanes, make sure the start
point is placed in the top left corner of the first column.
Activity or Action State

An action state represents the non-interruptible action of objects. You can draw an action
state in Smart Draw using a rectangle with rounded corners.
Action Flow
Action flows, also called edges and paths, illustrate the transitions from one action state to
another. They are usually drawn with an arrowed line.
Decisions and Branching

A diamond represents a decision with alternate paths. When an activity requires a decision
prior to moving on to the next activity, add a diamond between the two activities. The
outgoing alternates should be labeled with a condition or guard expression. You can also
label one of the paths "else."
CE-IT 36 | P a g e
13SOEIT11024
Guards
In UML, guards are a statement written next to a decision diamond that must be true
before moving next to the next activity. These are not essential, but are useful when a
specific answer, such as "Yes, three labels are printed," is needed before moving forward.
Final State or End Point

An arrow pointing to a filled circle nested inside another circle represents the final action
state.
CE-IT 37 | P a g e
13SOEIT11024
Activity Diagram: User login process
CE-IT 38 | P a g e
13SOEIT11024
Activity Diagram: Forget Password
CE-IT 39 | P a g e
13SOEIT11024
Activity Diagram: Add Comment Header
CE-IT 40 | P a g e
13SOEIT11024
Activity Diagram: Edit Profile
CE-IT 41 | P a g e
13SOEIT11024
Activity Diagram: Generate Report
CE-IT 42 | P a g e
13SOEIT11024
Activity Diagram: Import Case Folder
CE-IT 43 | P a g e
13SOEIT11024
Activity Diagram: Archive Case Folder
CE-IT 44 | P a g e
13SOEIT11024
Activity Diagram: Assign Tag
CE-IT 45 | P a g e
13SOEIT11024
Activity Diagram: Manage Permissions
CE-IT 46 | P a g e
13SOEIT11024
Activity Diagram: Assign Role to user
CE-IT 47 | P a g e
13SOEIT11024
5. DATA DICTIONARY
Sr Table Name Description
1 user_master Contains basic user details for all types of users including User
type
2 reset_password Contains details for resetting password.
3 login_time_details Contains timestamp for login & logout time for all users.
4 case_folder Contains all details about folder/case imported by admin.
5 archive_folder Contains details about folder which was archived by admin.
6 user_folder_master Contains all details for folder created by specific user.
7 user_folder_document Contains all document list added in user folders.

s
8 Document Contains details about all document with in any folder.
9 document_meta_data Contains all meta data details for all documents.(i.e. Owner,
size)
10 process_status Contains fixed status for folders (i.e.
Archived/Copying/Finished).
11 saved_search Contains search criteria for saved search by user.
12 tag_master Contains all tags added by user
13 document_tags Contains details about all documents with assigned tags.
14 comment_master Contains all comment type (i.e. Numeric, Text, Date)
15 comment_header Contains all comment headers added by admin. (i.e. Notes)
16 comment_description Contains comment details added by user on documents.
17 permission_master Contains different types of permissions. (i.e. Read, Write,

Deny).
18 permission_on_case_f Bind permission with case folder & users.
older
CE-IT 48 | P a g e
13SOEIT11024
19 permission_on_comm Bind permission with comment/tag & users.

ent_tag
20 role_master Contains different role details added by admin.
21 role_assign Bind use with roles.
22 role_on_case_folder Bind roles with case folders.
23 role_on_comment_tag Bind roles with comments/tag & users.
CE-IT 49 | P a g e
13SOEIT11024
Table 1
Table Name: users_master
Table Description: Contains basic user details for all types of users including User
type.
Field Name Data Type Constraint Sample Data

User_id Smallint Primary Key + 3
Auto Increment
First_name nvarchar(20) Nilay
Last_name nvarchar(20) Mehta
User_mail nvarchar(31) fake@mail.com
User_password varchar(128) 94afaf25ac17fe7bc39fda
(128 C)
Is_admin Bit True
Is_active Bit True
Failed_attempt Tinyint 2
Failed_timestamp Smalldatetime 2017/02/11 19:23:01
Created_by Smatint user_master 1
(user_id)
Created_date_time Smalldatetime 2017/02/11 19:23:01
Last_updated_by Smallint user_master 1
(user_id)
Last_updated_date smalldatetime 2017/02/11 19:23:01
_time
CE-IT 50 | P a g e
13SOEIT11024
Table 2
Table Name: reset_password
Table Description: Contains details for resetting password.

Reset_id Smallint Primary Key + 1
Auto Increment
User_id Smallint User_master 3
(User_id)
Reset_token varchar(50) af25ac17fe7bc39f
Reset_time Smalldatetime 2017/02/11 19:23:01
Table 3
Table Name: login_time_details
Table Description: Contains timestamp for login & logout time for all users.

Login_id Smallint Primary Key + 1
Auto Increment
User_id Smallint user_master 3
(user_id)
Login_timestamp Smalldatetime 2017/02/11 19:20:30
Logout_timestamp Smalldatetime 2017/02/11 19:23:01
CE-IT 51 | P a g e
13SOEIT11024
Table 4
Table Name: case_folder
Table Description: Contains all details about folder/case imported by admin.

Case_folder_ id Smallint Primary Key + 25
Auto Increment
Case_folder_parent Smallint Case_folder 24
_ id (case_folder_id)
Hierarchy Varchar(max) 1C2C5C24C25

Folder_name nVarchar(255) MyDocs
Created_by smallint user_master 3
(user_id)
Created_date_time smalldatetime 2017/02/11 19:23:01

Has_document bit False
Total_document int 25
Process_status tinyint Process_status 1
(status_id)
Table 5
Table Name: archive_folder
Table Description: Contains details about folder, which was archived by admin.

Archive_folder_ id Smallint Primary Key + 1
Auto Increment
Case_folder_ id Smallint Case_folder 24
(case_folder_id)
Created_by Smallint user_master 3
(user_id)
CE-IT 52 | P a g e
13SOEIT11024
Table 6
Table Name: user_folder_master
Table Description: Contains all details for folder created by specific user.

User_folder_ id int Primary Key + 102
Auto Increment
User_folder_name Nvarchar(255) MyData
User_folder_parent int user_folder 100
_id _master
(user_folder_id)
User_id smallint user_master 3
(user_id)
CE-IT 53 | P a g e
13SOEIT11024
Table 7
Table Name: user_folder_documents
Table Description: Contains all document list added in user folders.

User_folder_docu int Primary Key + 302
ment_ id Auto Increment
User_folder_id Nvarchar(255) user_folder 102
_master
(user_folder_id)
Document_id int Document 10
(document_id)
Table 8
Table Name: document
Table Description: Contains details about all document with in any folder.

Document_ id int Primary Key + 302
Auto Increment
Case_folder_id smallint case_folder 10
(case_folder_id)
Document_name Nvarchar(255) My Presentation
Document_extension Varchar(255) ppt
CE-IT 54 | P a g e
13SOEIT11024
Table 9
Table Name: document_meta_data
Table Description: Contains all meta data details for all documents.(i.e. Owner,
size)

Document_ Int Primary Key + 302
meta_id Auto Increment
Document_ id Int case_folder 10
(case_folder_id)
Size_in_kb Int My Presentation
Owner Varchar(26) ppt
Modified_date_tim smalldatetime 2017/02/11 19:23:01
e
Last_access_date_t smalldatetime 2017/02/11 19:23:01
ime
Attribute Varchar(3) ARH
Table 10
Table Name: process_status
Table Description: Contains fixed status for folders (i.e.

Archived/Copying/Finished).

Status_ id Tinyint Primary Key + 1
Auto Increment
Status_desc Varchar(12) Importing
CE-IT 55 | P a g e
13SOEIT11024
Table 11
Table Name: saved_search
Table Description: Contains search criteria for saved search by user.

Search_ id Tinyint Primary Key + 1
Auto Increment
Search_by Smallint user_master 1
(user_id)
Search_query Varchar(Max) {filename:xyz,
minSize:700}
Search_title Varchar(32) XYZ Search
Table 12
Table Name: tag_master
Table Description: Contains all tags added by user

Tag_master_ id Int Primary Key + 10
Auto Increment
Tag_parent_id Varchar(max) Tag_mater 5
(tag_master_id)
Tag_name Varchar(255) Important
(user_id)
(user_id)
_time
CE-IT 56 | P a g e
13SOEIT11024
Table 13
Table Name: document_tags
Table Description: Contains details about all documents with assigned tags

Document_tag_id Int Primary Key + 10
Auto Increment
Document_id Int Document 5
(document_id)
Tag_master_id Int Tag_master 3
(tag_master_id)
Table 14
Table Name: comment_master
Table Description: Contains details about all documents with assigned tags

Comment_master_ Int Primary Key + 10
id Auto Increment
Comment_type Varchar(max) Tag_mater 5
(tag_master_id)
Created_by Varchar(255) Important
(user_id)
_time
CE-IT 57 | P a g e
13SOEIT11024
Table 15
Table Name: comment_header
Table Description: Contains all comment headers added by admin. (i.e. Notes)

Comment_header_ Int Primary Key + 10
id Auto Increment
Comment_type Int Comment_master 2
(comment_master_id)
Comment_header_ Varchar(255) Important Page
name
(user_id)
(user_id)
_time
Table 16
Table Name: comment_description
Table Description: Contains comment details added by user on documents.

Comment_desc_id Int Primary Key + 10
Auto Increment
Comment_header_ Smallint Comment_header 5
id (comment_header_id)
Comment_desc Varchar(max) This doc must be
check
CE-IT 58 | P a g e
13SOEIT11024
Table 17
Table Name: permission_master
Table Description: Contains different types of permissions.
Field Name Data Type Constraint Sample

Data
PermissionMasterID Tinyint Primary Key + 3
Auto Increment
PermissionName Varchar(5) Read
Table 18
Table Name: permission_on_case_folder
Table Description: Bind permission with case folder & users.

Data
Permission_on_case_fold Tinyint Primary Key + 3
er_id Auto Increment
Permission_master_id Varchar(5) Permission_master 3
(permission_master_id)
User_id smallint user_master(user_id) 1

Case_folder_id smallint 10
Created_by smallint user_master(user_id) 1
Created_date_time smalldatetime 2017/02/11
19:23:01
Last_updated_by smallint user_master(user_id)
Last_updated_date_time smalldatetime 2017/02/11
19:23:20
CE-IT 59 | P a g e
13SOEIT11024
Table 19
Table Name: permission_on_comment_tag
Table Description: Bind permission with comment/tag & users.

Permission_on_comm Int Primary Key + 10
ent_tag_id Auto Increment
Permission_master_id Smallint Permission_master 5
User_id Smallint user_master(user_id) 1
Comment_header_id smallint Comment_header 10
(comment_header_id)
Document_tag_id Smallint Document_tag Null
(document_tag_id)
Created_date_time Smalldateti 2017/02/11
me 19:23:01
Last_updated_by Smallint user_master(user_id) 2
Last_updated_date_ti Smalldateti 2017/02/11
me me 19:23:20
Table 20
Table Name: role_master
Table Description: Contains different role details added by admin.

Role_master_id Tinyint Primary Key + 10
Auto Increment
Role_name Varchar(20) Senior
Created_by Smallint user_master(user_id) 1
Created_date_time smalldateti 2017/02/11
me 19:23:01
Last_updated_by Smallint user_master(user_id) Null
Last_updated_date_time smalldateti user_master(user_id) 2017/02/11
me 19:23:01
CE-IT 60 | P a g e
13SOEIT11024
Table 21
Table Name: role_assign
Table Description: Bind users with roles.

Data
Role_assign_id Tinyint Primary Key + 3
Auto Increment
Role_master_id Varchar(20) Role_master 3
(role_master_id)
User_id smallint user_master(user_id) 1
19:23:01
Last_updated_by smallint user_master(user_id)
Last_updated_date_time smalldatetime 2017/02/11
19:23:20
Table 22
Table Name: role_on_case_folder
Table Description: Bind roles with case folders.

Data
Role_on_case_folder_id Tinyint Primary Key + 3
Auto Increment
Permission_master_id Varchar(5) Permission_master 3

Role_id smallint role_master 1
(role_id)
Case_folder_id smallint 10
19:23:01
Last_updated_by Smallint user_master(user_id)
Last_updated_date_time Smalldatetime 2017/02/11
19:23:20
CE-IT 61 | P a g e
13SOEIT11024
Table 23
Table Name: role_on_comment_tag
Table Description: Bind roles with comments/tag & users

Role_on_comment_ta Int Primary Key + 10
g_id Auto Increment
Permission_master_id Smallint Permission_master 5
Role_master_id Smallint role_master 1
(role_master_id)
Comment_header_id Smallint Comment_header 10
(comment_header_id)
Document_tag_id Smallint Document_tag Null
(document_tag_id)
Created_by Smallint user_master(user_id) 1
19:23:01
Last_updated_by Smallint user_master(user_id) 2
Last_updated_date_ti smalldatetime 2017/02/11
me 19:23:20
CE-IT 62 | P a g e
13SOEIT11024
6. USER INTERFACE DESIGN

Screen: Login Page
CE-IT 63 | P a g e
13SOEIT11024
Screen: Login Page - Invalid Mail Id
CE-IT 64 | P a g e
13SOEIT11024
Screen: Login Page - Wrong Password
CE-IT 65 | P a g e
13SOEIT11024
Screen: Login Page - Locked Account
CE-IT 66 | P a g e
13SOEIT11024
Screen: Forgot Password
CE-IT 67 | P a g e
13SOEIT11024
Screen: Forgot Password - Success
CE-IT 68 | P a g e
13SOEIT11024
Screen: Change Password
CE-IT 69 | P a g e
13SOEIT11024
Screen: Change Password - Require Fields
CE-IT 70 | P a g e
13SOEIT11024
Screen: Change Password - Not Match
CE-IT 71 | P a g e
13SOEIT11024
Screen: Home page: Case folder list
CE-IT 72 | P a g e
13SOEIT11024
Screen: Home page: Import case folder
CE-IT 73 | P a g e
13SOEIT11024
Screen: Home page: Import time setting
CE-IT 74 | P a g e
13SOEIT11024
Screen: Home page: set time for import
CE-IT 75 | P a g e
13SOEIT11024
Screen: Home page: Document list
CE-IT 76 | P a g e
13SOEIT11024
Screen: Home page: Doc preview
CE-IT 77 | P a g e
13SOEIT11024
Screen: Home page: Doc Meta data
CE-IT 78 | P a g e
13SOEIT11024
Screen: Home page: Assign tag
CE-IT 79 | P a g e
13SOEIT11024
Screen: Home page: Tag assign success
CE-IT 80 | P a g e
13SOEIT11024
Screen: Home page: Download & Comments
CE-IT 81 | P a g e
13SOEIT11024
Screen: Home page: User folder list
CE-IT 82 | P a g e
13SOEIT11024
Screen: Home page: Create user folder
CE-IT 83 | P a g e
13SOEIT11024
Screen: Search: Form
CE-IT 84 | P a g e
13SOEIT11024
Screen: Search: Result
CE-IT 85 | P a g e
13SOEIT11024
Screen: Search: by type
CE-IT 86 | P a g e
13SOEIT11024
Screen: Search: by owner
CE-IT 87 | P a g e
13SOEIT11024
Screen: Search: by file size
CE-IT 88 | P a g e
13SOEIT11024
Screen: Search: by tag
CE-IT 89 | P a g e
13SOEIT11024
Screen: Search: by comments
CE-IT 90 | P a g e
13SOEIT11024
Screen: Search: Save search result
CE-IT 91 | P a g e
13SOEIT11024
Screen: Search: Save search success
CE-IT 92 | P a g e
13SOEIT11024
Screen: Search: Saved search list
CE-IT 93 | P a g e
13SOEIT11024
Screen: Archive page: List of archived folders
CE-IT 94 | P a g e
13SOEIT11024
Screen: Manage permissions: Assign user on case
CE-IT 95 | P a g e
13SOEIT11024
Screen: Manage permissions: Assign role on case
CE-IT 96 | P a g e
13SOEIT11024
Screen: Manage permissions: Assign user on comments
CE-IT 97 | P a g e
13SOEIT11024
Screen: Manage permissions: Assign role on comments
CE-IT 98 | P a g e
13SOEIT11024
Screen: Manage permissions: Assign user on tags
CE-IT 99 | P a g e
13SOEIT11024
Screen: Manage permissions: Assign roles on tags
CE-IT 100 | P a g e
13SOEIT11024
Screen: Manage users: Add new user
CE-IT 101 | P a g e
13SOEIT11024
Screen: Manage users: Filter list of users
CE-IT 102 | P a g e
13SOEIT11024
Screen: Filter list of users 2
CE-IT 103 | P a g e
13SOEIT11024
Screen: Manage users: View roles of specific user
CE-IT 104 | P a g e
13SOEIT11024
Screen: Manage users: De-active user
CE-IT 105 | P a g e
13SOEIT11024
Screen: Manage users: Edit user
CE-IT 106 | P a g e
13SOEIT11024
Screen: Manage users: Edit user success
CE-IT 107 | P a g e
13SOEIT11024
Screen: Manage Roles: List of roles
CE-IT 108 | P a g e
13SOEIT11024
Screen: Manage Roles: Edit roles
CE-IT 109 | P a g e
13SOEIT11024
3.1 Report Design
Report: Archive Docs: Graph
CE-IT 110 | P a g e
13SOEIT11024
Report: Archive Docs: Grid
CE-IT 111 | P a g e
13SOEIT11024
Report: Based on tags: Graph
CE-IT 112 | P a g e
13SOEIT11024
Report: Based on tags: Grid
CE-IT 113 | P a g e
13SOEIT11024
Report: Based on comments: Graph
CE-IT 114 | P a g e
13SOEIT11024
Report: Based on comments: Grid
CE-IT 115 | P a g e
13SOEIT11024
Report: Based on comments: CSV
CE-IT 116 | P a g e
13SOEIT11024
Report: Imported Docs: Graph
CE-IT 117 | P a g e
13SOEIT11024
Report: Imported Docs: Grid
CE-IT 118 | P a g e
13SOECE11041 Development
13SOEIT11024
4. DEVELOPMENT
1. CODING STANDARDS
Indenting
o Using 4 spaces for an indention. And give indention at proper level.

Function Calls
o There is no space between function call and its parameters.

Comments
o Provide proper comments for all of the functions so it is easy to understood by

someone else.
o Using C style comments [// & /* */]
o Using documentation comments for documenting. [/** */]
Naming Conventions
o All variable & function names are in lower case letters.

o All constants are defined as uppercase.
o All class names are capitalized and prefixed with .class
o Use underscore (_) as the word separator.
o All file names are in lowercase and use hyphen for separation.
Remove Trailing Spaces
o Removed trailing spaces after every line by using plugins in sublime text.
Classes
o Encapsulate all of the core functionality of app into different classes.
SQL statements
o Use prepared statements for handles escaping, quoting, and int-casting for SQL queries.
o Using mysqli instead of mysql.
o Close connection after completing operation.
Error Control Operator @
o Using error control operator: the at sign (@) for hiding all errors after deploying system.
Control Structures
o There is no space after opening or closing parenthesis.

o Using IFENDIF statement when it is necessary.
CE-IT 119 | P a g e
13SOECE11041 Testing
13SOEIT11024
5. TESTING
1. TEST PLAN & TESTING METHOD
Test planning, the most important activity to ensure that there is initially a list of tasks and
milestones in a baseline plan to track the progress of the project. It also defines the size of
the test effort.
It is the main document often called as master test plan or a project test plan and usually
developed during the early phase of the project.
Test Plan Identifiers:

S.No. Parameter Description
1. Test plan identifier Unique identifying reference.
2. Introduction A brief introduction about the project and to the document.
3. Test items A test item is a software item that is the application under test.
4. Features to be tested A feature that needs to tested on the ytest ware.
5. Features not to be Identify the features and the reasons for not including as part of testing.
tested
6. Approach Details about the overall approach to testing.
7. Item pass/fail criteria Documented whether a software item has passed or failed its test.
8. Test deliverables The deliverables that are delivered as part of the testing process, such as test plans, test
specifications and test summary reports.
9. Testing tasks All tasks for planning and executing the testing.
10. Environmental needs Defining the environmental requirements such as hardware, software, OS, network
configurations, tools required.
11. Responsibilities Lists the roles and responsibilities of the team members.
CE-IT 120 | P a g e
13SOEIT11024
12. Staffing and training Captures the actual staffing requirements and any specific skills and training requirements.
needs
13. Schedule States the important project delivery dates and key milestones.
14. Risks and Mitigation High-level project risks and assumptions and a mitigating plan for each identified risk.
15. Approvals Captures all approvers of the document, their titles and the sign off date.
Test Planning Activities:

To determine the scope and the risks that need to be tested and that are NOT to be tested.
Documenting Test Strategy.
Making sure that the testing activities have been included.
Deciding Entry and Exit criteria.
Evaluating the test estimate.
Planning when and how to test and deciding how the test results will be evaluated, and
defining test exit criterion.
The Test artefacts delivered as part of test execution.
Defining the management information, including the metrics required and defect
resolution and risk issues.
Ensuring that the test documentation generates repeatable test assets.
CE-IT 121 | P a g e
13SOEIT11024
2. TEST CASES
Test Case ID: TC-01 Test Case Name: Managing User
Designed by: Nilay Mehta Design Date: 23/03/2017
Module Name: Managing User Sub Module Name: Creating User
Executed by: Dhaval Sanghani Execution Date: 23/03/1017
Brief Description: Admin can Create New User Test Priority (Low/Medium/High):Medium
Pre-conditions: User has valid Email Address
Dependencies: User Should be Admin
Step Test Steps Test Data Expected Result Actual Result Status (Pass/Fail) Remarks
Give the messge of mandatory Give Validation message to PASS All Validation
1 Click on Add User Blank Fields Field enter mandatory field Message is show
First Name: Vijya Error Massage(This field Should Error Massage(This field Fail
be an Email Address). Should be an Email Address).
Last Name: Chaudhari
Email : vijya@cn
2 All Data would be entered User Type: User
Enter already entered Give Error message Username Already Exists PASS
3 All Data would be entered username
122 | P a g e
13SOEIT11024
Test Case ID: TC-02 Test Case Name: Import Case Folder
Designed by: Shubham Koladiya Design Date:
Module Name: Import Case Folder Sub Module Name: Allocate Mentor
Executed by: Priyank Patel Execution Date:24/3/1017
Brief Description: Mentor Committee and Director allocate mentor Test Priority (Low/Medium/High):Medium
Pre-conditions: User has valid username and password
Dependencies: Mentor Committee or Director should be exist to Allocate mentor and Student should be register to system
Step Test Steps Test Data Expected Result Actual Result Status (Pass/Fail)
1 Right Click on CaseTree Node - Show Context menu Show Context menu PASS
2 Click on Import - Show Import Window Show Import Window PASS
3 Click on Upload Empty Error Message Import Valid Path PASS
4 Click on Upload E:\Jquery2\css Impotrs the folder to case tree Impotrs the folder to case tree PASS
CE-IT 123 | P a g e
13SOEIT11024
Test Case ID: TC-03 Test Case Name: Archive the Folder
Designed by: Priyank Patel Design Date:24/3/2017
Module Name: Archive the Folder Sub Module Name: Archive the Folder now
Executed by: Shubham Kholadiya Execution Date:24/3/2017
Brief Description: User can Archive the folder from Case Folder Test Priority (Low/Medium/High):Medium
Dependencies:
2 Click On Archive - Pop-up Archive Window Pop-up Archive Window PASS
Archives Selected folder Archives Selected PASS

3 Click On Archive Button - folder(Success Message)
CE-IT 124 | P a g e
13SOEIT11024
Test Case ID: TC-04 Test Case Name : Archive the Folder
Designed by : Prakash Makvana Design Date: 24/3/2017
Module Name: Archive the Folder Sub Module Name : Set Schedule to Archive The Folder
Executed by : Nilay Mehta Execution Date: 24/3/2017
Brief Description: Setting the date and time to Archive Folder Test Priority (Low/Medium/High):Medium
Dependencies:
2 Click On Archive - Pop-up Archive Window Pop-up Archive Window PASS
Change the Radio Button to Enable the Date-Time Picker Enable the Date-Time Picker PASS
3 schedule -
Selecting Date-Time and Click Give the Success Message Give the Success Message PASS
4 on Archive 25/3/2017 7:30 pm
CE-IT 125 | P a g e
13SOEIT11024
Test Case ID: TC-05 Test Case Name : Add User Folder
Designed by : Vijya Chaudhari Design Date: 24/3/2017
Module Name: Add User Folder Sub Module Name: Cerate User Folder
Executed by : Shravansingh Rajpurohit Execution Date: 24/3/2017
Brief Description: Add new User folder to userfolder Test Priority (Low/Medium/High):Medium
Dependencies: User should be logged in
Pop-up Add User Folder Pop-up Add User Folder PASS
1 Click on New Folder - Window Window
2 Click on Add User Folder Empty Give Error message Enter the Folder Name PASS
3 Click on Add User Folder Latest Success message Success Message PASS
CE-IT 126 | P a g e
13SOEIT11024
Test Case ID: TC-06 Test Case Name : Search
Designed by : Dhaval Shanghani Design Date: 25/3/2017
Module Name: Search Sub Module Name: Search
Executed by : Vijya Chaudhari Execution Date: 25/3/2017
Brief Description: Search By varies Criteria Test Priority (Low/Medium/High):Medium
Dependencies:
Able to give all the files which Able to give all the files which PASS
1 Click on Search File Name: new starts From new keyword. starts From new keyword.
Gives all the text file in case Gives all the text file in case PASS
2 Click on Search File Type: txt folder. folder.
Gives all the file whos owner is Gives all the file whos owner PASS
3 Click On Search File Owner: Nilay Nilay is Nilay.
CE-IT 127 | P a g e
13SOEIT11024
Gives all the file of important Gives all the file of important PASS
4 Click On Search Tag: Important Tag. Tag.
Gives all the file which has Gives all the file which has
5 Click On Search Comment Header: note Comment Header note. Comment Header note.
Test Case ID: TC-07 Test Case Name: Managing Roles
Designed by: Shravansingh Rajpurohit Design Date: 24/03/2017
Module Name: Managing Roles Sub Module Name: Creating Role
Executed by: Prakash Makvana Execution Date: 24/03/2017
Brief Description: Admin can Create New Role Test Priority (Low/Medium/High):Medium
Pre-conditions:
Dependencies: User Should be Admin
Expected Result Actual Result Status

Step Test Steps Test Data (Pass/Fail)
CE-IT 128 | P a g e
13SOEIT11024
Give the messge of mandatory Give Validation message to enter PASS
1 Click on Add Role Blank Fields Field mandatory field
Role added and selected roles Role should be added and selected PASS
Role name would be entered and assigned users should be assigned this role
2 Click on Add Role users can also be selected
CE-IT 129 | P a g e
13SOEIT11024
6. IMPLEMENTATION
Installation and configuration
Before Importing & Archiving user must have to install out windows service.
Admin Module
In this module admin can create the user and assign types to that user and gives the
permission as well as role to the user for the purpose of accessing the software
Here, Admin user can create and update the comment type, category type and role.
Admin manage the folder and upload the document according to it.
Here, Admin user gets the all kind of updating and creation of permissions by default.
Main Module
Main module contains the following functionality:
Import Documents
Archive Documents
Make Comments/Tags on Document
Search Documents by various criteria.
Preview/Download of documents.
130 | P a g e
13SOECE11041 Proposed Enhancements
13SOEIT11024
7. PROPOSED ENHANCEMENTS
Finally, we conclude with the fact that as perfection is impossible to achieve,
the same way no application can be made with such perfection, which cannot
have any scope of improvement.
Improve search algorithm for quick search.
Provide preview for Native files such as PDF & Docs.
More user-friendly interface.
CE-IT 131 | P a g e
13SOECE11041 Conclusion
13SOEIT11024
8. CONCLUSION
eZArchival has been developed and the system was tested with proper data. The
system result in regular timing preparation of the required output. In comparison
with manual system, the benefit under a computer system considerable into
saving of manpower, working hour, efforts, and provide accurate result.
It can observe that the information required can be obtained with ease and
accuracy in the computerized system. The user with minimum knowledge about
computer can be able to operate the system easily. Informative message has
been provided to help the user to take necessary, correct action while using the
system. Various validation techniques have been used to implement accuracy of
data in all formats of input. The system has produced all required the report by
admin & user.
This software can be used by any law firm as it can be modified easily
additional features can be added without interrupting the normal functioning of
the system.
CE-IT 132 | P a g e
13SOECE11041 Bibliography
13SOEIT11024
9. BIBLIOGRAPHY
Books
Learning ExtJS, Packt Publishing 4th Edition
Professional WCF with .NET 4, Wrox publication
C# 4.0 The Complete Reference, Herbert Schildt
Websites
msdn.microsoft.com
docs.sencha.com/extjs/5..11/
www.Bing.com
www.Google.co.in
www.Wikipedia.org
www.StackOverflow.com
www.FontAwesome.io
www.codeproject.com
CE-IT 133 | P a g e

Documentation

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Documentation

Caricato da

Copyright:

Formati disponibili

13SOECE11041 Introduction

2. REQUIREMENT DETERMINATION & ANALYSIS ............................ 12

6. IMPLEMENTATION ............................................................................................... 130

Search for any

2. NEED FOR THE NEW SYSTEM

Following are the reasons for need of new system

3. OBJECTIVE OF THE NEW SYSTEM

Project Title eZArchival

Developed at Capital Novus (Logical Software Solutions) Pvt. Ltd.

Type of Application Web Application

Front End Tool ASP.NET, C# and Extjs-5.1.1(JavaScript Framework)

Back End Tool SQL SERVER 2014

IDE Used Visual Studio 2015

Browsers Mozilla Firefox, Google Chrome, Microsoft Edge

Project Duration 19th Dec 2016 to 24th Mar 2017

External Guide Mr. Mayur Manvar

7. ASSUMPTIONS AND CONSTRAINTS

All files Meta data are not altered.

Only text/image documents can be preview online.

8. ADVANTAGES AND LIMITATIONS OF THE PROPOSED

1.8. 1 Advantage of Proposed System

Maintain document access based on roles & permissions.

1.8.2 Disadvantage of Proposed System

9. PROPOSED TIME LINE CHART

2. REQUIREMENT DETERMINATION & ANALYSIS

Its very time consuming process.

2.3.2. Technical Feasibility

2.3.3. Operational Feasibility

Documents Meta data must be correct.

2.4.2. Non-Functional Requirements

These systems would have following characteristics:

Basic Use Case Diagram Symbols and Notation:

Use case: For User

Use case: For Admin

Class Diagram Symbols and Notation:

Composition and Aggregation

Sequence Diagram Symbols and Notation

Class Roles or Participants

Activation or Execution Occurrence

Types of Message in Sequence Diagram

Reply or Return Message

Sequence: Forget Password

Sequence: Add Comment Header

Sequence: Edit Profile

Sequence: Generate Reports

Sequence: Import Case

Sequence: Archive Case

Sequence: Assign Tag

Sequence: Manage Permissions

Sequence: Assign Role to User

Activity Diagram Symbols and Notation:

Initial State or Start Point

Activity or Action State

Decisions and Branching

Final State or End Point

Activity Diagram: User login process

Activity Diagram: Forget Password

Activity Diagram: Add Comment Header

Activity Diagram: Edit Profile

Activity Diagram: Generate Report

Activity Diagram: Import Case Folder

Activity Diagram: Archive Case Folder

Activity Diagram: Assign Tag

Activity Diagram: Manage Permissions