CSE225 Grids and High
Performance Distributed Computing
Spring 2004
Professor Andrew A. Chien
Course
Project Planning
We will move quickly
to get a set of projects defined and your teams working effectively. The key steps and timeline include:
1)
Formation of Groups and Initial Project Definition (second
and third meeting of the class, 4/2 and 4/5)
2)
Initial Project Plans, 5 pages, (due 4/12), they should
include:
a)
A clear set of objectives (questions to be answered,
research apparatus to be built, code to be understood)
b)
A clear team (who’s on it and contact information – email,
phones, etc.)
c)
A clear set of responsibilities (who’s going to take lead
for what); which will evolve over time
d)
Technical Elements of each project should address
i)
Definition of the project focus: What are the questions?
ii)
Infrastructure and Strategy: How are the questions going to
be addressed?
(1)
Software, systems, resources which will be used
(2)
New deployment and functionality that will be achieved
iii)
Expected Outcomes: What will be the experiments and
evidence to answer the questions?
e)
Work on the projects should begin apace at this point
3)
Review of the Project Plans w/ Professor Chien (4/14, 4/16)
a)
Based on the submitted Initial Project Plans, we will have
15-30 minute meetings to refine and extend the plans
b)
These discussions will identify areas where more research,
exploration, and planning is needed and these changes will be reflected in the
Final Project Plan
4)
Final Project Plans, 15 pages, (due 4/23), these should
include in some detail
a)
Everything in the Initial Project Plan (revised if
appropriate)
b)
Improvements based on discussions with Professor Chien
c)
Background on the related work / technical knowledge
d)
A VERY detailed plan, including
i)
Obtaining access to the needed computing resources
ii)
Obtaining the relevant software
iii)
What will be built/configured
(1)
Software design
(2)
The implementation and testing plan for that design What
experiments will be done
iv)
What outcomes are expected
v)
What are the fallbacks if something doesn’t work out
vi)
Specific milestones that are clearly defined and provide
reasonable time for unexpected problems
5)
Midterm Project Checkup (5/12)
6)
Project Final Reports (Due Thursday, 6/10/2004)
1)
Project Presentations (6/11, 2-4pm, 4301 APM); Finals Week