Project Timeline

Intelligent Systems

This time line lists the major elements of the project along with suggested times for completing them. With the exception of three fixed deadlines (the dates your two reports are due and the date of the presentation), all dates are -- as a practical matter -- merely suggestions. But they are strong suggestions. Be wary of slipping too far from this schedule in either direction.

The deadlines are fixed. They will not be adjusted during the semester.

Week 1

Form a team, select a team leader, and settle on a project.

Weeks 2-4

Research your problem. Come to understand the task in detail. Understand the context in which the task is performed. Conduct interviews with relevant parties, including your domain experts. Begin to conceptualize the knowledge that underlies the task.

This is commonly referred to as the knowledge acquisition phase of the project. See these these suggestions for how to approach knowledge acquisition.

SUGGESTION: By the end of Week 4, produce a draft analysis of the problem that roughly satisfies the requirements of your midterm deliverable. If you produce such a document, I will be happy to review it and discuss it with you.

Weeks 5-7

Design your solution. Implement an architecture prototype that allows you to demonstrate your intended solution and to learn more about the problem.

SUGGESTION: By the end of Week 6, produce a draft of your midterm deliverable for review and modification.

REQUIREMENT: Submit your team's midterm deliverable to the instructor by 4:00 PM on Monday, February 28.

Weeks 8-14

Implement your solution. Go through at least two iterations of growing and refactoring the system. Test your solution at each step. Document your system on an ongoing basis.

Working as a team, you will want to be sure to integrate your code into the working program at frequent intervals. You will also want to conduct regular walkthroughs of your pseudo-code and code as a team.

SUGGESTION: Maintain a team library of code, test results, and documentation. This will make management of the developing system and changes to it much more convenient.

Week 14

Integrate code final pieces of the system. Perform final integration testing. Clean up code. Complete a draft of your System Documentation. Assign presentation responsibilities.

Week 15

Perform any last-minute code tasks. Complete final version of your System Documentation. Prepare final presentation. Perform dry run.

Week 16 (Finals Week)

Finalize presentation and any administrative details.

REQUIREMENT: Submit system documentation and final system to the instructor by 4:00 PM on Monday, May 2.

REQUIREMENT: Give the final presentation of your project during the final exam period, 8:00 AM-9:50 AM on Wednesday, May 4.

REQUIREMENT: Submit your evaluation of your team and your evaluation of the other presentation by the end of final exam period, 8:00 AM-9:50 AM on Wednesday, May 4.

REQUIREMENT: Submit your course notebook for final review by 4:00 PM on Friday, May 6.

Eugene Wallingford ..... ..... January 12, 2011