In This Project Deliverable You Should Develop The 10 Functi
In This Project Deliverable You Should Develop The 10 Functionalities
In this project deliverable, you should develop the 10 functionalities proposed in deliverable 2 in MS Access, and turn in the following files: 1) The updated project proposal ( Word document ) which has the same five sections as before. Copy my comments from the deliverable 2 and highlight any changes you made from the previous version by turning track changes on in MS Word (or using a different text color). 2) A MS Visio file that contains the updated ERD (even if you didn't make any changes from the previous version). 3) An Access database should have all the tables shown in the ERD with at least 6 to 7 records in each table and all the PK/FKs/relationships/data types properly enforced. The referential integrity option should be checked when setting up the relationship in MS Access. The Access file should also include the 10 queries used to accomplish the 10 functionalities outlined in the proposal. Name the 10 queries based on the order of functionalities listed in the Word document. Please name the above file as Project_3_Lastname.docx / .vsdx / .mdb, respectively). All group members need to submit these three project files. The final project deliverable is due on November 30 at 11:59 PM. This is a firm deadline and no extension will be given. You are strongly encouraged to submit your project files earlier to avoid any technical issues.
Paper For Above instruction
The objective of this project is to develop a comprehensive MS Access database that embodies ten distinct functionalities outlined in the previous deliverable. This undertaking involves creating an integrated system that supports the core operations of a given business process, ensuring all components—from the conceptual design to the implementation—are thoroughly executed and documented.
Initially, the project requires revising and updating the original project proposal document. This document must be formatted strictly using Microsoft Word, containing the same five sections as the original. It should incorporate all feedback and comments provided in deliverable 2, with modifications clearly highlighted. To accomplish this, the track changes feature in MS Word should be utilized, allowing evaluators to easily identify amendments. This meticulous revision process ensures clarity, precision, and traceability of the project’s evolution.
Simultaneously, a comprehensive Entity-Relationship Diagram (ERD) must be developed and maintained in Microsoft Visio. Whether or not there are modifications from the previous ERD, the updated diagram should be included in the submission. The ERD serves as the foundation for the database structure, illustrating entities, attributes, relationships, and cardinalities. Maintaining accuracy in this diagram is crucial, as it ensures the logical integrity of the database schema and facilitates future troubleshooting or enhancements.
The core deliverable involves constructing a functional MS Access database that embodies the ERD’s specifications. This database must include all tables depicted in the ERD, with each table containing a minimum of six to seven records. Proper enforcement of data integrity constraints, such as primary keys (PK), foreign keys (FK), and data types, is essential. Additionally, referential integrity constraints should be properly enabled to prevent orphaned records and maintain consistent relationships across tables. This setup guarantees data consistency and supports reliable query processing.
Beyond mere table creation, the project mandates developing ten queries within MS Access. These queries should correspond to the functionalities outlined in the initial proposal. For example, if a functionality involves retrieving customer data, the associated query should be named accordingly and optimized for accuracy and efficiency. The naming convention for these queries should reflect the order of functionalities as listed in the Word document, establishing a clear linkage between requirements and implementation. These queries serve as operational tools, enabling users to perform essential database functions seamlessly.
All files associated with the project must adhere to strict naming conventions for easy identification. The Word proposal should be named using the format Project_3_Lastname.docx; the Visio ERD should be named Project_3_Lastname.vsdx; and the Access database file should be named Project_3_Lastname.mdb. These files represent the final deliverables and must be submitted collectively by all group members, emphasizing teamwork and shared responsibility.
The submission deadline is set for November 30 at 11:59 PM. This deadline is non-negotiable, and no extensions will be granted under any circumstances. To mitigate potential technical issues, students are strongly encouraged to submit their work ahead of schedule. Early submission ensures ample time to address unforeseen difficulties, thereby safeguarding against last-minute complications.
In essence, this project integrates database design, development, documentation, and validation. It demands careful adherence to technical specifications and deadlines while demonstrating proficiency in MS Access, Visio, and Word. Completing this project successfully will showcase the ability to translate conceptual requirements into a fully operational database system, fulfilling academic and practical standards in database management.