Use your domain diagram (UML) and CRC cards in order
to create a first draft of your
class diagram:
Use one 3x5 card for each class in your domain diagram.
Write the name of the class on the card.
Next, for each card, write a one-sentence description of the
class's main "responsibility." If a
class has multiple responsibilities,
consider breaking it down into smaller classes, each with a
single responsibility. (Create new cards for the new classes.)
On the left side of each card, write a list of the things
the class must know or do in order to
carry out its responsibility.
A class is likely to "collaborate" with other classes in order to fulfill its responsibilities.
List these collaborators on the right side of the card.
Walk through each Use Case describing how it is realized
through the collaboration of your classes.
If there are gaps, create new classes to take on the identified responsibilities.
Photograph each of your CRC cards and upload the images to your trac.
Work on your prototype. It is due next Sunday.
You may have already started developing code but if not you soon will.
Your team has to come to an
agreement on the coding practices you will use.
You might begin to develop a policy by
addressing two major issues.
-
Naming policy: You should establish a policy
for creating names for variables, methods, classes,
etc. Here are some questions you should consider:
Does your naming convention distinguish between private and public data and methods?
Will names be formatted for readability?
Does your policy emphasize descriptive names, particularly ones that refer to real-world concepts
instead of programming language concepts?
Does your policy prevent practices that
cause common bugs such as names mispelled to make them
shorter, hard to read characters (e.g. l and 1)
Does your policy ensure booleans are named so that their true meaning is clear.
-
Documentation: You should establish a documentation policy (a la CS70).
Upload your work to your trac.
Phase 2 Management Plan Details
-
Weekly meetings
-
Weekly goal stack based on priorities
-
Tickets with time estimates
-
Team member work logs
Review Rubrics for Upcoming Deliverables
Mike Erlinger
Last Modified Thursday, 20-Sep-2012 13:00:35 PDT