What This Document Is
This material provides an overview of the core project for CSCI 599: Software Engineering for Embedded Systems at the University of Southern California. It outlines the logistical framework for a team-based development effort, focusing on the resources available to students and the expectations surrounding their use. The document also begins to introduce the primary software framework – Prism – that will be central to the project, hinting at its architectural components and potential applications. It’s a foundational piece for students embarking on a significant hands-on experience within the course.
Why This Document Matters
Students enrolled in CSCI 599, particularly those beginning work on the class project, will find this information essential. It’s most valuable *before* team formation and initial project planning, ensuring everyone understands the available tools, lab access procedures, and the overall scope of the undertaking. Those unfamiliar with embedded systems development or the Prism framework will benefit from the initial conceptual overview presented here. Understanding the outlined expectations regarding lab usage and academic integrity is crucial from the outset.
Common Limitations or Challenges
This document serves as an introductory guide and does *not* provide detailed, step-by-step instructions for project implementation. It doesn’t include specific coding examples, detailed architectural designs, or complete API references for Prism. It also doesn’t cover the full scope of the project requirements, which will be elaborated upon in subsequent lectures and assignments. It’s a starting point, not a comprehensive manual.
What This Document Provides
* An outline of the team structure for the class project.
* Information regarding available hardware resources, including PocketPCs and related peripherals.
* Details about the Embedded Systems Lab, including its location and available software.
* A preliminary introduction to the Prism-MW software framework and its core concepts.
* An overview of expected student conduct and lab usage policies.
* Initial discussion points regarding the overall design approach for the project.
