This Assignment Is A Tfour Part Project Building Off The Fir

This Assignment Is A Tfour Part Project Building Off The First Week This assignment is a four-part project building off the first week. Imagine there were four assignments.

Question 1 is for Week 1. Question 2 is for Week 2. Question 3 is for Week 3. You MUST submit the answers as labeled Week 1, Week 2, and Week 3.

Question 1 (Week 1): You are about to create an application to manage your CDs/DVDs collection. The application to keep track of the inventory (in/out), who borrowed what and when it is due back (no money transactions please). The system should be able to produce at least 3 reports such as inventory list, items due, most active user, and most borrowed item. What are the steps you are going to take to complete the development process? Include a detailed requirements document (5 pages max) with suggested design and ER diagram. Use MS Word for the diagram. You MUST include the structure of the tables in the database, not the data, and there needs to be first and last names.

Question 2 (Week 2): Create the database you defined in Question 1 (Week 1). Use simple SQL inserts to append records to each table you created. There need to be 3 records per table. Save these SQL statements in a text file and submit it along with the database.

Question 3 (Week 3): Create an appropriate form for each table with add/edit/delete functionality. Forms MUST include 1.) frmBorrower (add, edit, delete, list borrowers), 2.) frmMedia (add, edit, delete, list media), 3.) frmQuickSearchMedia (lookup media, show status of media such as in house, out, and who checked it out), 4.) frmQuickSearchBorrower. Do NOT send an automatic reply without having read the assignment. I will pass you over. Send me an IM stating you have read the assignment. Do this correctly, and there will be 8 more weeks of assignments coming your way.

Paper For Above instruction The first step in developing an application to manage a CD/DVD collection is to thoroughly understand the requirements and design an effective database schema. This process involves requirements gathering, designing an ER diagram, and planning out the system architecture. The primary goal is to facilitate inventory management, borrowing transactions, and report generation for the collection without involving financial transactions.

Requirements Gathering and System Planning From the assignment, the essential features include maintaining a detailed inventory of media items,

tracking borrowings and returns, monitoring due dates, and generating specific reports. The system needs to manage media details, borrower details, and transaction records, which necessitates designing multiple interconnected tables. Additionally, reports such as inventory listing, most active users, and most borrowed items help in analyzing the collection's usage and status.

Designing the Database Schema The core tables for the database involve Media, Borrowers, and Transactions. The Media table includes fields such as MediaID, Title, MediaType, Status, and LastBorrowedDate. Borrowers will have BorrowerID, FirstName, LastName, ContactInfo, and possibly other demographic details. The Transactions table records each borrowing event, linking MediaID and BorrowerID, along with BorrowDate, DueDate, and ReturnDate.

The Entity-Relationship (ER) diagram visually represents relationships: one borrower can borrow many media items, and each media item can be borrowed multiple times, indicating a many-to-many relationship managed through the Transactions table. The ER diagram can be constructed in MS Word, illustrating entities, attributes, and relationships accordingly.

Development Steps Requirement analysis and documentation, including designing detailed use cases.

Creating the ER diagram to define the database structure and relationships.

Implementing the database schema in SQL, defining table structures, primary and foreign keys, and constraints.

Populating tables with sample data via SQL INSERT statements as per the assignment instructions.

Developing user interface forms for managing media, borrowers, and searching functionalities using a database front-end tool such as MS Access.

Implementing add/edit/delete features within the forms to allow CRUD operations.

Creating reports for inventory, active users, and most borrowed items, using built-in report tools or SQL queries.

Testing the complete system, ensuring data consistency, functional correctness, and usability.

Documenting the development process and system design clearly for future reference and maintenance.

Conclusion This systematic approach ensures a well-structured, functional, and user-friendly media collection management system. Effective planning, designing, implementing, and testing are crucial steps to deliver a robust application that meets all specified requirements, including comprehensive reporting, reliable data storage, and intuitive data management interfaces.

References Elmasri, R., & Navathe, S. B. (2015). Database Systems: Concepts, Design, and Applications (6th ed.).

Pearson.