What This Document Is
This is a lab assignment for CSC 305, a Software Engineering course at the University of Rhode Island. The assignment centers around applying software engineering principles – specifically task decomposition and project scheduling – to a seemingly non-technical project. Students will utilize industry-standard project management software to model and plan a complex process. The core exercise involves translating a set of initial requirements into a detailed, actionable plan.
Why This Document Matters
This assignment is crucial for students learning to bridge the gap between abstract goals and concrete implementation. It’s particularly beneficial for those seeking to understand how software engineering methodologies apply beyond traditional software development scenarios. Students preparing for roles in project management, systems analysis, or any field requiring structured planning will find this exercise valuable. It’s best used as a practical application following introductory lectures on requirements gathering and project scheduling techniques.
Common Limitations or Challenges
This assignment does *not* provide a pre-defined solution or a step-by-step guide to completing the task. Students are expected to independently analyze the provided information, identify missing elements, and construct a comprehensive project plan. It also doesn’t offer instruction on the recipe itself – the focus is entirely on the *process* of planning, not the outcome of baking. Access to the assignment details is required to fully understand the scope and specific deliverables.
What This Document Provides
* A real-world inspired scenario for applying software engineering principles.
* Guidance on utilizing a popular project management tool (Microsoft Project).
* A framework for practicing task decomposition – breaking down a large goal into smaller, manageable steps.
* Instructions for creating a requirements document based on a provided template.
* A team-based learning experience to foster collaboration and problem-solving skills.
* Clear expectations for deliverables, including a project file submission.
