Term Project: Employee In-Service Training DatabaseMychaela CammackINFO 321: Information Database Management SystemsAmerican Military UniversityMarch 29, 2020
Name of the ProjectEmployee In-Service Training DatabaseAbstractThe purpose of this paper is to introduce a database management system and the reason for its development. During this report, key topics will be the purpose of the database, design methodology, entities used and their significance, the use of the administrator and the end user, In addition, the relationship of entities will be described and how the rows will relate between each table, and identifying different normal functions throughout. The main query function will be to be able to pull information from the Employee table and the Training table together thus creating a training record to identify which training each employee has completed. There will be a series of other queries to generate other reports as well such as completed and not completed rosters as well as reports by training requirement rather than individual employee.
Database PurposeThe proposed database for Employee In-Service Training Database could have potential to be very effective in daily functions and operations. Unfortunately, businesses conduct a multitude of trainings annually, but lose track of records and who attended which training. This results in having to reconduct training and spending more money on the costs of the specific training, but without a central database to track these trainings, they have an uncontrolled way of reporting and storing data to include analyzing events. With this new database, the idea is to centralize and track trainings with each employee per department in which they work in. Each employee's information will be stored with a Subdatasheet displaying each of their completed trainings, and not yet completed training. User IdentificationThe end goal of this database management system is for the database to be used by all staff members who conduct a training. As the instructor conducts a training, they will be able to access the database and enter in the key data via a form, then use the merge records function to add the completed class to each individual employee, as well as indicate whether the training wasrequired or not with a remarks section in the event additional data will need to be stored. The general staff will only be able to see the auto-populated form to prevent data manipulation by other users. Once placed, the administrator, typically the Unit Training Manager, will be the key primary administrator, this individual would ideally be able to operate or change queries, edit forms and reports, delete employees, add employees and so forth. This individual will also have to be familiar with access to be successful. Once built, it should be designed to not have to be
updated by the architect. The secondary administrators will be the chosen departmental training officers, or the Non-Commissioned Officer in Charge. They will then be the individuals manipulating data or generating each report. The end user would be the handlers as the general