Format:1) One MS-ACCESS .mdb file2) One MS-WORD .doc fileMark:25%Due:12 midnight. Sunday. October 31, 2004.Submission Instructions:o Before uploading your assignment, make a back-up copy of your .mdb file, then(from the MS-ACCESS main menu) run ToolsDatabase UtilitiesCompact& Repair Database to reduce and optimize the file size of your MS-Accessdatabase file.o FTP the .mdb and .doc files to the Arst593BUpload FTP space before the duedate.o Please use the following naming convention for the MS-ACCESS file:Assign2_studentLastName_studentFirstName.mdbo Please use the following naming convention for the MS-WORD file:Assign2_student_LastName_studentFirstName.doco Students will lose 2% per day that the assignment is overdueAssignment Description:Using the features learned in the Absolute Beginner s Guide to MS-Access LabTutorials, you will create an MS-ACCESS database application for one of thefollowing functional components commonly found in AMS software:1) Box Management Module2) Accessioning Module3) Archival Description ModuleYou will also provide documentation in an accompanying MS-WORD document thatprovides instructions to the users of your MS-ACCESS database application on howto use your AMS software module.
--------------------------------------------------------------------------------
Page 2
!"# ( %& 'AMS Module Entity-Relationship Diagrams:1. Box Management Module2. Accessioning Module3. Archival Description Module
--------------------------------------------------------------------------------
Page 3
!"# ' %& 'Minimum Requirements:1) Using MS-ACCESS as the DBMS software, create the tables, fields andrelationships for an AMS software module based on one of the Entity-Relationship diagrams on page 2 above.a. It is up to you to determine the data-type and data format to be used foreach field.b. Refer to the Detailed Requirements Catalogue section (pp.11-60) in theAMS Software Requirements document, as well as ISAD(G), ISAAR(CPF)or RAD for more background and context on the possible structure andcontent of the fields listed in the Entity-Relationship diagrams above.2) Create at least one MS-ACCESS form to enter data into your tables.3) Create at least one MS-ACCESS report which outputs data from your tablesa. For the Box Management module, create a box locations reportb. For the Accessioning module, create a Deed of Gift reportc. For the Archival Description module, create an item-level catalogue report(see Appendix B in ISAD(G))4) Provide a minimum of three sample (hypothetical) database records for everytable in your MS-ACCESS databasea. No null values (i.e. provide sample, hypothetical data for every field inevery database record)5) Provide a minimumpage of documentation that provides instructions to theusers of your database application on how to input and output data using yourAMS software module.a. Everyone ! "#!$%&'$"(#! )"** +,-"# )"$. /0&#'. 12-ACCESS and loadthe Assign2_[studentLastName_studentFirstName].mdb database file!b. After that, the instructions will depend on the AMS Module you havechosen to create, which database objects you 3, '%,0$,4 0#4 .() 5(& 3,named them.c. You may assume that your end-users have a basic knowledge of MS-ACCESS itself (i.e. they will know what you mean when you say '*"'6 (#the Forms Shortcut in the MS-ACCESS Database Window!)d. Assume, however, that your end-users have never used your AMSsoftware module.Refer to the AMS Software Requirements document for additional contextand information that may be used to supplement your application data,forms, and reports.Take note of the Forms and Reports configuration options covered inchapters 13 & 14 of Absolute Beginner s Guide to Microsoft Access toimprove the overall usability of your database application
AMS Module Entity-Relationship Diagrams:1. Box Management Module2. Accessioning Module3. Archival Description Module
--------------------------------------------------------------------------------
Page 3
!"# ' %& 'Minimum Requirements:1) Using MS-ACCESS as the DBMS software, create the tables, fields andrelationships for an AMS software module based on one of the Entity-Relationship diagrams on page 2 above.a. It is up to you to determine the data-type and data format to be used foreach field.b. Refer to the Detailed Requirements Catalogue section (pp.11-60) in theAMS Software Requirements document, as well as ISAD(G), ISAAR(CPF)or RAD for more background and context on the possible structure andcontent of the fields listed in the Entity-Relationship diagrams above.2) Create at least one MS-ACCESS form to enter data into your tables.3) Create at least one MS-ACCESS report which outputs data from your tablesa. For the Box Management module, create a box locations reportb. For the Accessioning module, create a Deed of Gift reportc. For the Archival Description module, create an item-level catalogue report(see Appendix B in ISAD(G))4) Provide a minimum of three sample (hypothetical) database records for everytable in your MS-ACCESS databasea. No null values (i.e. provide sample, hypothetical data for every field inevery database record)5) Provide a minimumpage of documentation that provides instructions to theusers of your database application on how to input and output data using yourAMS software module.a. Everyone ! "#!$%&'$"(#! )"** +,-"# )"$. /0&#'. 12-ACCESS and loadthe Assign2_[studentLastName_studentFirstName].mdb database file!b. After that, the instructions will depend on the AMS Module you havechosen to create, which database objects you 3, '%,0$,4 0#4 .() 5(& 3,named them.c. You may assume that your end-users have a basic knowledge of MS-ACCESS itself (i.e. they will know what you mean when you say '*"'6 (#the Forms Shortcut in the MS-ACCESS Database Window!)d. Assume, however, that your end-users have never used your AMSsoftware module.Refer to the AMS Software Requirements document for additional contextand information that may be used to supplement your application data,forms, and reports.Take note of the Forms and Reports configuration options covered inchapters 13 & 14 of Absolute Beginner s Guide to Microsoft Access toimprove the overall usability of your database application