Database Project: Spy Management System Design and Implementation

This project outlines the design and implementation of a spy management system database. It begins with an overview of the system's goals, which include efficient data access, management of spy information, task assignment, and role-based access for spies, handlers, and management. The project details the end-user requirements, emphasizing functionalities like adding, removing, and searching spies, as well as viewing skill and operation details. An ER diagram illustrates the database's entities and relationships, including spies, handlers, identities, tasks, operations, and skills. The document then presents the functional dependencies within the logical schema, ensuring that all non-primary key attributes are fully dependent on the primary keys. A schema, listing tables with primary and foreign keys, is also provided. Finally, the project includes a description of the GUI, showcasing windows for spy operations, management functions (adding, removing, assigning operations), searching, skill management, and operation views.

Spy Database
PROJECT DESCRIPTION
Overview
The spy management system is implemented to achieve the long term and short term goals of
the spy organization by efficiently accessing and managing the spy data. The system along with
helping in easy and fast retrieval of spy data, also helps in efficiently adding and removing the
spy information, get all spy details, get all operations. This system can also be used to assign
different tasks to various spies. A spy handler can also use the system to check spy’s details.
A spy in this system can easily view his details, and different operations. He can also ask for
operation to be assigned. The management can view the operation and spy, assign operation to
spy. In this manner, the operations given to any spy can be managed. The list of all spies in the
system can be retrieved, so that total spy can be counted. This system helps the internal
functionality of the organization go in smooth manner.
There are various skills, such as language skills, weapon skills, and different skills groups.
Language also contains language groups, because a spy can know many languages, so spy can
be given a language group which spy know. Spy can be judged according to the skills he have
and the level of the spy can be decided.
Spy live with fake identity, and real identity should not be revealed. To make its surety, the
system have fake identity information for all the spy, and contains the information about the
identity they live in. To outside contact these fake identity can be used.
Requirement specification
There are various end user requirements that the system is desired to implement. These
requirements include viewing all the spy details, adding or removing a spy into or from the
database. The system should also help in assigning tasks to spy by its spy handler. The spy
handlers must be able to view spy details. Management must be able to assign tasks to a spy or
remove or add a spy to the database. The system must be able to view skill details. The system
must also ease the task of viewing language skills. The main objective of the system should be
to implement insert, update or search a spy.
There are three different end-user roles, namely, management group, spy handler and spy. Spy
must be able to view his details on the system. The management group will use the system to
add a spy to the database or remove a spy from the database. The spy handler may use the
system to assign operation to a spy. The system can be used by handler or upper management

to search a spy. The system must also provide a button from where we can see detailed view of
spy information. There must be a separate window from where the management may view and
assign all the existing operations to the spy. The management can add or remove skill from a
spy’s skill set.
ER DIAGRAM
The following is the ER diagram for the spy database scenario –
All the entities and relations that exist in the database are shown in the above diagram. There
are total fifteen entities in the database, namely -
spy, spy handler, spy identity, task, operation, upper management group, payment,
communication channel, language group, language, weapon skill, skill group, skill, course, spy
learner. All the cardinalities and relationships in the database are –
 Spy and spy handler –one to one relation
 Spy handler and communication channel – one to one relation

 Spy and communication channel – one to one relation
 Spy and spy identity – one to many relation
 Spy identity and task – one to many relation
 Task and operation – one to many relation
 Operation and upper management group – many to one relation
 Spy and payment – one to many relation
 Spy and Skill group – one to many relation
 Skill group and skill – one to many relation
 Spy and spy learner – one to many relation
 Spy learner and course – one to many relation
 Spy and weapon skill – one to many relation
 Spy and language group – one to many relation
 Language group and language – one to many relation
List of functional dependencies in logical schema
The schema is designed in such a way that all the non-primary key attributes depends on the
primary key attribute of the table. The non-primary key attributes of all the tables are fully
functionally dependent on the primary key attribute of same table. For spy table, all the non-
primary key attributes will be fully functionally dependent on the primary key spy id of the
table. For spy identity, spy handler, weapon skill, language group, language, skill group, skill, spy
learner, courses, task, operation, upper management group, communication channel and
payment, all the non-primary key attributes depend functionally on the respective primary keys
I.e. identity id, handler id, weapon id, language group id, language id, skill group id, skill id,
learner id, course id, task id, operation id, management group id, communication channel id
and payment id.
Schema
The following is the schema of the database implements it lists all the table with their primary
key and foreign key attributes.

For table spy identity, spy handler, weapon, language group, language, skill group, skill, spy
learner, course, task, operation, upper management group, communication channel and
payment table, their primary keys are identity id, handler id, weapon id, language group id,
language id, skill group id, skill id, learner id, course id, task id, operation id, management group
id, communication channel id and payment id respectively.
All the tables implemented are in third normal form.
This project reflects the application related to spy data. The organization contains the spy over
all the different location, with different skills. Spy can have multiple skills such as languages,
weapons, and other related skills. The skills determine the levels of different spy among the
organization. Task distribution among the organization is very systematic, as every spy have a
spy handler. The spy handler decides the task allocation for the spy.
Description of GUI

Different GUI for the organization which have been implemented is shown below.
Spy Operation Window-
The view below is the spy view showing the information of the spy., This will view show the list
of all spy.
After the spy, main entity in the organization is management. The management window is
shown below. Management can assign the operation (Assign Operation Button),
Management Can Add Spy (Add Spy)
Management Can Remove Spy (Remove Spy)
There are various other operations such as checking skills, checking weapons, and checking
operation than can be performed using this management window.

View elaboration more information about management window is shown below.
If we need to search any spy, different view is available for that. The search view is shown
below. Along with search view , insert view is also shown to add spy.

Spy are assigned different skills, They can be added or removed easily. Skills has different view
to be added, remove or search. The view is shown below.

The operation view will look something as shown below. The different operation will contains
the Location, Goals Task Ids, Member names, and how to contact them. This window will be
used to assing the task to spy. The window can be accessed by management for checking the
operation and assigning the task.

Conclusion-
In all above view we found that, adding removing spy was easily handled by management
group. Main functionality of the organization is to add operation to spy. Which was comfortably
achieved by management through add operation functionality.