OPPapers.com Essay Index >> Technology >> Training Database
We have many free term papers and essays on Training Database. We also have a wide variety of research papers and book reports available to you for free. You can browse our collection of term papers or use our search engine.
training database. ... Having a proven program would reduce some of the testing but it
would still require and extensive trials with our training database. ...
... Therefore, it is vital to individual database personnel to make sure they are receiving
the proper training to prepare them for our rapidly changing technology ...
... for an order, supplier relations program, research and development of new programs,
food marketing trends studies and design a training database for new ...
... in the ELECTRICITY DELIVERY FIELD SERVICES DEPARTMENT within ESKOM on quality training. ...
June 2008 Field research: Set up database of employees and email ...
... Development of a system that uses the current customer demographic database to generate ...
Top Service Request SR-kf-003 Employee Training Organization: Kudler ...
Submitted by loid on May 3, 2007
Category: Technology
Words: 791 | Pages: 4
Views: 176
Popularity Rank: 69,402
Average Member Grade: N/A (Add a Comment / Grade this Paper)
During the design phase of the development, the IT department decided they would use a Microsoft Access platform to create the training database. The decision to apply this platform was base on the extensive knowledge that the technicians already had and the established success of the Access. Having a proven program would reduce some of the testing but it would still require and extensive trials with our training database. This was especially necessary, in the functions that interfaced with the internet and other Air Force databases.
When developing the system, the IT department took a few different approaches to testing. The initial approach was unit testing. Unit testing is defined as the testing of individual code modules or methods before they are integrated with other modules (Satzinger, 2004). This is exactly how the IT department explained their testing to me. As each module of the database was created, it was then tested for functionality and error.
Upon successful unit testing, the individual modules were then tested for compatibility and continuity with other modules. This is what the text refers to as integration testing. Although the modules tested okay separately, they did not always test properly with the other modules. Once interfaced with other functions, the possibility for error is dramatically increased. Some of the errors could include but are not limited to interface incompatibility, invalid parameter values, runtime errors or unexpected state interactions (Satzinger, 2004). Once this portion of the testing was completed the designers could then move on to testing the system as a whole.
Since the size of the project was relatively small and it would operate mostly in-house, the IT department decided to skip further testing and release a Beta version of the database. At the time the database was not mission critical and system failure or crashing would not affect the unit's day-to-day...
You must Login to view the entire paper.
If you are not a member yet, Sign Up for free!