What This Document Is
This document outlines the requirements and guidelines for the implementation phase of a significant software systems project within the CSCI 477a course at the University of Southern California. It serves as a practical application of previously completed design and architecture work, focusing on bringing a theoretical system to life through code. It details expectations for a prototype build, emphasizing the importance of aligning implementation with established design principles.
Why This Document Matters
This guide is essential for students enrolled in CSCI 477a who are tasked with building a functional prototype of a complex system. It’s particularly valuable during the implementation stage of the course project, helping students understand deliverables, grading criteria, and the development environment. Students will benefit from reviewing this before and during coding to ensure their work meets the assignment’s objectives and avoids common pitfalls. It’s crucial for teams to understand these guidelines to maximize their score.
Common Limitations or Challenges
This document does *not* provide pre-written code, specific solutions to implementation problems, or a comprehensive tutorial on the Player Stage software. It assumes a foundational understanding of software development principles and the design choices made in prior assignments. It also doesn’t detail every possible scenario or edge case; students are expected to exercise independent problem-solving skills. It focuses on *what* needs to be done, not *how* to do it.
What This Document Provides
* A clear description of the project’s implementation scope and expectations.
* Guidance on the available programming environment (nunki.usc.edu) and initial setup.
* Details regarding required deliverables, including design documentation, source code, and a readme file.
* Information on grading criteria, including potential extra credit opportunities.
* A defined deadline for submission.
* Emphasis on the importance of design consistency throughout the implementation process.
