What This Document Is
This is a project assignment guide for CSCI 585: Database Systems at the University of Southern California. Specifically, it details a set of testing procedures designed to validate the implementation of a “V” storage manager. It outlines a series of tests focused on core storage management functionalities, requiring students to build and execute these tests themselves as part of a larger term project. The document serves as a blueprint for verifying the correctness and efficiency of a storage management system.
Why This Document Matters
This assignment is crucial for students enrolled in advanced database systems courses. It’s intended for those actively building a storage manager and needing a structured approach to debugging and performance analysis. Students will benefit from this guide during the implementation and testing phases of their project, ensuring their storage manager meets specified functional requirements. It’s particularly valuable for understanding how to systematically evaluate data zone creation, record insertion, deletion processes, and caching mechanisms. This assignment bridges theoretical knowledge with practical application.
Common Limitations or Challenges
This document provides a framework for testing, but it does *not* offer pre-built test code or solutions. Students are expected to independently implement all test routines. It also assumes a foundational understanding of database storage concepts and programming skills. The guide focuses on the *what* to test, not the *how* – the specific implementation details are left to the student. It also doesn’t cover all possible error conditions or edge cases; students are encouraged to consider these during implementation.
What This Document Provides
* A clear outline of six distinct test suites.
* Defined objectives for each test, focusing on key storage manager functionalities.
* Guidance on initial setup and configuration requirements for each test.
* A description of expected behaviors and verification points within each test.
* Deliverable specifications, including submission requirements and due dates.
* Information regarding memory allocation and data zone initialization parameters.
