TRAINER DATABASE PLAN When creating a database first it best that we understand why we need the database in the first place. The reason being, I am working as a corporate trainer for a large organization. In the organization there are several other trainers, with each trainer there are many training topics. Our company has grown quickly and scheduling has become difficult. The current method for our scheduling involves writing trainer names and courses on a dry-erase board. This has led to many issues with our trainers changing the assignments in their favor and accidental erasure of some course assignments. So in order to resolve the many issues that we are having, I have decided to build a database for the training schedule process. In my previous organization, we created a database for organizing our documents and the process each packet goes through day-by-day. To do this we used, Microsoft Access which gave each user privileges by the administrator. To design a database in Access or with any software, it is required that those involved understand why that database is need, those functions that will be required by the company and the knowledge of the database features in accordance to the needs of the company or organization . To begin, as a designer we know that it is best to, create a plan that will be used as a reference when the database is being implemented and also to be used as a operative specification for the database as well after it has been implemented. Also, before creating this database it good to have an understanding of the functions in which the database is suppose to perform. Knowing the databases complexity is also very important because it helps determine the exact size of the database, as well as formulating user population. Upon knowing the functions need within the database there are other things that are important. Replacing the information system (manually or instructional), remember that the system that first system (existing) will give you all the information needed. Information gathering is very important, this will help you to get familiar with the user to understand their needs and how that use the system, this is very important as well for the database. This will help you to identify what each user expects from the new system and the database. Gathering information will help with problem solving and also the process of elimination . The next step for towards building the database is, creating the database. This involves the project leader, he or she will schedule meeting to with the database administrator. In meeting they will discuss the requirements, the data schema and any other information that involves the database. After the plans have been agreed upon. The database administrator will work toward creating the physical database and once complete, the developer will gain access. The developer will take the physical plan and develop the database according to the instructions given per the information that was taken in from the meeting. The developer then goes back to meet with the database administrator to review the plan and finalize the database design. Lastly, the database administrator then gives his or her approval for the plan and it is accurate and finished, the database is then lock, and no new changes will be made by anyone but the database administrator. The administrator will give user privileges per individual need or based upon user's title in the company or job. After this has been established, moving the information over from the normal hand written dry erase board is the next step. The advantages with moving the information over are, the trainer will have access to the database and can view the schedule, nothing can be changed unless done so by the administrator and none of the training information can or will be erased like mentioned . One great disadvantage is, how the information is input into the database (user names, schedules, dates, time, etc).