Sunteți pe pagina 1din 16

1

Database Development for a Legal firm to Organize the pending and On Going Cases and Case
Allocation to the Individual Associates Randomly.
Lakkineni,Shashidhar.
Wilmington University.

1. Table of Contents2
2. Analysis .3
a. Business Requirements ..3
b. Technical Requirements..3
c. Security Requirements3
d. Operational..3
e. Functional and Non-functional Requirements4
f. Reporting Requirements.5
g. User Requirements..6
3. Modeling.6
a. Decision Table AND Decision
Tree.6
b. Must contain: .8
i. A Functional Decomposition Diagram ..8
ii. Data Flow Diagram ....9
iii. Context diagram....11
4. Design.
a. List of all Inputs.11
b. List of all Outputs...12
c. Data Dictionary...12
d. Designs....12
i. Input Design ...13
ii. Output Design. ...13
iii. Data Design13
iv. Integration Design ......14
v. Security ..14
5. References...15

Analysis:
a. Business Requirements:

In the present situation of the developed information system additional features like
adding a database to the company can give the best user impact in the competitive market.
To develop this project data collection is required in the form of soft copies so that they
can uploaded to the database and give access to the associates. On another factor allocation of
cases to the associates can be initiated by the logical programing depending on the span of the
cases and the difficulty in the issue.
Developing a database can give the scope of reducing the commercial space which is
allocated to the hardcopies of the cases. Moreover, the participation of group meeting and team
activities will be furnished in the organization with this program initiation.
Client interaction will be very much easy and the access of cases from the remote
location can give the extent to organizations growth in the field of legal aid and make the
company as a role model for the upcoming startups in the legal era.
b. Technical Requirements:
Developing a database requires a selection of the platform where it gives the flexibility
for the developers to update the files which are converted to the soft copies from the hard copies.
Creating a logical program for the case allocation to the individual associates in the random
order for the equal distribution of the work among the employees.
c. Security Requirements:
The criteria of security is major aspect in any database development and here it is matter
of conspiracy because in a leading organization there is a requirement of the high security on the
case files and the strategies they are using for the cases.
Updating the files give a free hand option to the cyber thefts and the covert employees
outside and inside the organization. So, developing a database with the employee logins for their
access to the cases and make sure that who is searching for the certain cases which are kept
under the observation, and cases allocated to associate has to look for the day to day observation
for minimizing the threats from every point of view.
d. Operational:
Monitoring activities as, when as employee is logged in for the access and when the
employee is loge out from the session. This is a part of an operational activity of the because it
shows the login details with the employee details as well as the information he accessd for the
client beneficiary.
On another factor of the backing up the details of the safeguard of the information which
is present in the database, hence if there is any kind of spam or a virus attacks the database this
backup can plays a vital role in the data recovery. More the availability of the data operations

should be 24/7 because in the field of legal organization time is crucial part hence completion of
case in the give time for the client will repute the organization
e. Functional and Non-functional Requirements:
In the functional requirements of organization, creating a profiles for the database
identification such as attaching the basic details as employee name, employee id, employee age,
role of the employee. Adding this details will generate the unique logins and passwords to the
individual employees, so whenever there is a requirement of the access to the case files they will
be using their logins to access the data of the cases.
Case remunerations are also part of the functional requirements they have to maintained
in the secure manner and go for the genuine transactions from the clients, so that it doesnt make
any mess in the future dealing with the clients or client organization.
Old case files have to be secured for the future reference in the database so that any case
similar to the one which exist can be replicated or used as a reference format to minimize the
time required for the case proceedings and hearings.
Looking in to the non-functional requirements developed logins will be monitored by the
database handlers for the operation done through the individual logins and coming to the case
remunerations are handled through the secure transaction method of the bank to commercial
organizations accounts.
Segregation of the case files into required categorize can give the search optimization to
the efficient way so these methods come under the non-functional operations. Usage of the
database heat map also the part of the operations because when the employees are on the work
they are authorized to the handling the case sheets whereas when there is a requirement for the
remote operations then the heat mapping of the website can give the access location and the
usage time of the associates login.
f. Reporting Requirements:
Dates of the previous cases and processing cases have to be noticed for the reporting
requirements, employee information for the database update is the part of the reporting
requirements and the heat signature of the employee as well as the finger prints for the biometric
access as well as the retinal scan will be the part of the major reporting requirements, for this
there is a requirement of the additional attachments such as the scanners for the biometrics and
the heat accessors.
g. User Requirements:
A database or software which is developed for the organization should give the best user
interface for the best out come in the runtime. Hence the user requirements in other case is there

should be maximum flexibility of the database to update with the latest updates and the
completed cases. Whenever a employee try to get the details of the case, database should give
such interface with the flexibility of extracting the case sheets from the initial stage who was
chandelling the case and what are the judgments of the previous hearings. In the logical
operation of random procuring the case has to a lottery system such that it shows equal approach
on every employee.
Modeling:
a. Decision Table:
Decision table for the login access of the employee
F

Password

Expected result

Error: Please Error: please


entre email
enter email

Actions

Conditions

Login Id

Conditions

Case number
Case type

Actions

Expected result

T
F

Error: please
entre
password

F
T

T
F

Error: Invalid case Error: Invalid case Error: not valid


type
number

Decision table for the case number identification and case type:

Decision Tree:

Login
processed

T
Case file
processed

Decision tree for the employee access to the login and the access to the cases

Random allocation of case to every employee

a. Must contain:
i. A Functional Decomposition Diagram

i. Data Flow Diagram:

Random allocation of cases through the logical flow diagram

10

Context diagram:

Design:
a. List of all Inputs:
1. Data files with the segregation into the span of the cases will the major input to the system.
2. Login id identification for the secure access on the unknown persons.
3. Biometric scanners for the operations of the retinal and finger print scanning in the database
access.
4. Dates for the old case proceeding in the database for the call sheets at the judiciary
5. Notification implementation on the database to intimate the upcoming forecasts on the case
proceedings.
6. Shuffling system for the random case allocation on the cases depending on the case span.
7. Backup and update of information every day will give the potential to face the worst case
scenarios

11

8. Authentication on every day information for the access to the associates through the chief
executive officer.
b. List of all Outputs
1. Optimization of the commercial space in the organization as the hard copies are transferred
into the soft copies.
2. This gives the scope for the team building activity in the organization.
3. Access of the database through the secure login gives the protection to the personal and
confidential data.
4. Information authorization will be the part of the output as well as the monitoring of the data
access will give the mapping of, who is accessing which kind of data for the proficiently usage.
5. Login time and the login position of the employee will be the useful tracking information for
the organization record.
6. Notification on the upcoming case schedules will be addressed with required case files and the
proceedings on the case in the judiciary.
c. Data Dictionary

12

Designs
i. Input Design:
Step 1:

Name
First
name
Last
name

Date of
birth
Given
DOB
DOB

Identificati
on
Finger
print id
Retinal
id

13

Step 2:

Address

Street, state

Primary
contact

Login id

Zip code

Contact info

Secondary
contact

Employee id

Password

Enter text
OK

:____________

Finger print id :_____________


Retinal id :_____________
Id
:_____________
Password :_____________

iii. Data Design:

Sign in

Identificati
on

Login

ii. Output Design:


14

15

iv. Integration Design:

16

v. Security Design:

References
Software Protection and Licensing. (n.d.). Retrieved February 23, 2016, from http://www.umldiagrams.org/examples/software-license-use-case-diagram-example.html?context=uc-examples
Identify Reporting Requirements. (n.d.). Retrieved February 23, 2016, from
http://betterevaluation.org/plan/reportandsupportuse/identify_reporting_requirements

S-ar putea să vă placă și