CS384 HW#2

Due: Monday Jan 30, via repository electronic committal
This is a team assignment. Turn in a doc/384-hw2.html that summarizes your activities and results, with a list of what relevant files to look for in the repository, and where.

You are to perform a one-week sprint. Include on your required sprint work list the following two elements in addition to what your team identifies as its goals for the week.

Part 0:

E-mail me (ASAP after class) your team's summary of this week's goals, if you haven't yet.

Write a more complete list of tasks (things to do; agile people would call it a "backlog") needed to complete your project by the end of the semester. This is more or less everything you know is needed. You should include appropriate items like major pieces of software functionality getting implemented and integrated, tested, documented, etc.

Part 1: Planning

Develop either a Gantt chart or a PERT chart for the semester. Identify 2 OR MORE intermediate deliverable levels of functionality at which you would plan to demo your stuff in class, prior to the end-of-semester delivery.

Place it in a doc/plan/ with a makefile, export an image file for the chart, embed that within an appropriate surrounding document called plan.tex / plan.pdf.

Part 2: Fleshing Design, Skeleton'ing C++

Add use cases as needed. For example, 12 use cases might not be close to enough. Integrate the rest of your UML diagrams into your SSDD, your "master plan" for your project.

Cross-check UML diagrams against each other. For example if a sequence diagram contains classes, those classes should appear in a class diagram. All entities in all graphica.