Overview Is 362: A Project For Developing Work
Overviewis 362 Incorporates A Project Of Developing A Working Database
Overview IS 362 incorporates a project of developing a working database that is PC based. That is, during the term, the students will systematically work their way through the concept formation, logical design including normalization, and physical design and implementation including building forms and reports using an instructor approved database management system (DBMS). In each unit a new set of activities in this development will be assigned to evolve the final working database. Getting Started This is to be designed and developed on a database that the students have access to, so if you do not have access to a database such as MS Access (inside or separate from the MS Office suite), then they can obtain a copy bundled with MS Office Pro Plus for a few dollars from the Park affiliated JourneyEd software site ( (Links to an external site.) ) This site is used for sale and distribution of software to Park University faculty, staff, and students.
Of course there are many DBMSs that are acceptable including FileMaker Pro, PC-DBMS, OpenOffice's Base, and MySQL, many are free downloadable or have a free trial period. But whichever DBMS is submitted by the student and approved by the instructor, it is the student's responsibility to become proficient in the DBMS on their own (we don't have time to teach a class in any DBMS during this term). For students without previous DBMS experience, it is recommended that they utilize a DBMS which operates on a PC, has wizards and a GUI interface for the user, and has tutorials available online either free or at low cost (like MS Access). Project Requirements The only requirements are that you must use a DBMS system (no spreadsheets like MS Excel), that there are at least three real tables (after modeling in 3rd normal form), and at least 10 attributes.
Of course more attributes and tables are OK, but this is the minimum allowed. And this must be a database developed from scratch, not an implementation of an already designed or implemented database. Directions For the Unit 1 activity, the student is required to consider what the theme or application they want to develop a database in. It should be something that is useful, or needed, either at home or at their job. Previous courses have had almost every application imaginable from an inventory system for household possessions (this comes in handy when moving or if you experience a loss (theft or fire), to a system to organize videos/DVDs/and music, to a system for keeping track of business/travel expenses, to various personnel tracking/locating systems, to almost countless database applications specific to work, etc.
Submit Activity Submit a description of your proposed database application, some examples of potential attributes, your proposed DBMS, and a description of your DBMS experience/proficiency (novice, some experience, expert). Send all this to me in one file.
Paper For Above instruction
Developing a functional and effective database requires careful planning, detailed understanding of the application domain, and proficiency with a chosen database management system (DBMS). For this assignment, I will propose a personal library management system aimed at organizing books, DVDs, and music collections at home. This type of database addresses a common need for cataloging multimedia items, ensuring easy access and management, especially when collections grow large or require regular updates.
Proposed Database Application: Personal Media Collection Management System
This system will allow users to track and organize their personal collection of books, DVDs, and music albums. The system will include detailed attributes for each item, such as title, creator/author/artist, genre, year of release/publication, location within the home, and lending status. This application is relevant at a personal level and offers practical utility for individuals needing to manage their media collection efficiently.
Potential Attributes and Tables
Based on the application, I plan to develop at least three normalized tables:
1. Items Table
- ItemID (Primary Key)
- Title
- Creator (Author/Artist/Composer)
- Type (Book, DVD, Music)
- Genre
- Year of Release/Publication
- Location (e.g., Shelf number, Room)
- Lending Status (Available, Lent Out)
- Borrower (if lent)
- Purchase Date
2. Persons Table
- PersonID (Primary Key)
- Name
- Contact Information
- Relationship to User (Family Member, Friend, Borrower)
3. Transactions Table
- TransactionID (Primary Key)
- ItemID (Foreign Key)
- PersonID (Foreign Key, if lent out)
- Date Borrowed
- Date Returned
- Transaction Type (Lend, Return)
These tables are designed to normalize data, minimize redundancy, and ensure data integrity in third normal form (3NF). Additional attributes and tables, such as a table for item ratings or user notes, can be added with increased complexity.
Proposed DBMS and Experience
For this project, I propose to use Microsoft Access, as I have some experience with it and it provides user-friendly wizards and a GUI interface suitable for beginners and intermediate users. My familiarity with Access is at the “some experience” level; I am able to create tables, relationships, forms, and reports with guidance from tutorials available online. I am committed to improving my proficiency during this project through hands-on practice and online resources.
Conclusion
This project aligns well with my personal needs and provides an opportunity to improve my database development skills. It emphasizes logical database design, normalization, and practical implementation, fulfilling the course objectives. Developing this database from scratch will enhance my understanding of core database concepts, and using Access will give me familiarity with a widely-used DBMS suited for small to medium-sized databases.
References
- Harrington, J. L. (2016). Relational Database Design and Implementation. Morgan Kaufmann.
- Rob, P., & Coronel, C. (2009). Database Systems: Design, Implementation, & Management. Cengage Learning.
- Simons, A., & Hoffer, J. (2014). Modern Database Management. Pearson.
- McFadden, F., & Earl, M. (2010). Access 2010: The Official Guide. Microsoft Press.
- Kroenke, D. M., & Ampanakakis, K. (2014). Analyzing Data with Power BI. Microsoft Press.
- Elmasri, R., & Navathe, S. B. (2015). Fundamentals of Database Systems. Pearson.
- Larson, P.-A. (2013). The Data Warehouse Toolkit. Wiley.
- Chapple, M., & Curtis, S. (2009). Microsoft Access 2007 Programming by Example. Pearson.
- Coronel, C., & Morris, S. (2015). Database Systems: Design, Implementation, & Management. Cengage Learning.
- IBM Knowledge Center. (2023). Introduction to relational databases. IBM.