Spy Database. PROJECT DESCRIPTION. Overview. The spy ma
Added on - 21 Sep 2019
Spy DatabasePROJECT DESCRIPTIONOverviewThe spy management system is implemented to achieve the long term and short term goals ofthe spy organization by efficiently accessing and managing the spy data. The system along withhelping in easy and fast retrieval of spy data, also helps in efficiently adding and removing thespy information, get all spy details, get all operations. This system can also be used to assigndifferent 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 foroperation to be assigned. The management can view the operation and spy, assign operation tospy. In this manner, the operations given to any spy can be managed. The list of all spies in thesystem can be retrieved, so that total spy can be counted. This system helps the internalfunctionality 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 canbe given a language group which spy know. Spy can be judged according to the skills he haveand the level of the spy can be decided.Spy live with fake identity, and real identity should not be revealed. To make its surety, thesystem have fake identity information for all the spy, and contains the information about theidentity they live in. To outside contact these fake identity can be used.Requirement specificationThere are various end user requirements that the system is desired to implement. Theserequirements include viewing all the spy details, adding or removing a spy into or from thedatabase. The system should also help in assigning tasks to spy by its spy handler. The spyhandlers must be able to view spy details. Management must be able to assign tasks to a spy orremove or add a spy to the database. The system must be able to view skill details. The systemmust also ease the task of viewing language skills. The main objective of the system should beto implement insert, update or search a spy.There are three different end-user roles, namely, management group, spy handler and spy. Spymust be able to view his details on the system. The management group will use the system toadd a spy to the database or remove a spy from the database. The spy handler may use thesystem 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 ofspy information. There must be a separate window from where the management may view andassign all the existing operations to the spy. The management can add or remove skill from aspy’s skill set.ER DIAGRAMThe 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. Thereare 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, spylearner. All the cardinalities and relationships in the database are –Spy and spy handler –one to one relationSpy handler and communication channel – one to one relation
Spy and communication channel – one to one relationSpy and spy identity – one to many relationSpy identity and task – one to many relationTask and operation – one to many relationOperation and upper management group – many to one relationSpy and payment – one to many relationSpy and Skill group – one to many relationSkill group and skill – one to many relationSpy and spy learner – one to many relationSpy learner and course – one to many relationSpy and weapon skill – one to many relationSpy and language group – one to many relationLanguage group and language – one to many relationList of functional dependencies in logical schemaThe schema is designed in such a way that all the non-primary key attributes depends on theprimary key attribute of the table. The non-primary key attributes of all the tables are fullyfunctionally 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 thetable. For spy identity, spy handler, weapon skill, language group, language, skill group, skill, spylearner, courses, task, operation, upper management group, communication channel andpayment, all the non-primary key attributes depend functionally on the respective primary keysI.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 idand payment id.SchemaThe following is the schema of the database implements it lists all the table with their primarykey and foreign key attributes.