Hotspots: Admin Pages | Turn-in Site |
Current Links: Cases Final Project Summer 2007
Fall 2005 Milestone 2 Grading Criteria
- Design - 55%
- 20% CRC Cards
- 25% UML class diagrams
- Provides sufficient coverage of project
- Conveys a coherent design (follows UML standards)
- Should include how your design integrates with BookMorph and other major Squeak classes that you will be using in your design
- 10% Additional Design Documentation (scenarios, use cases, etc.)
- Implementation - 45%
- Automatically Resizing Text - 15%
- Decreasing the Size with More Text - 10%
- Increasing the Size with Less Text - 5%
- Link-to-a-Page - 15%
- Create link works - 5%
- Pressing the link works - 5%
- The link works after rearranging pages - 5%
- Insert-an-image Morph - 15%
- Select an image - 5%
- Rotate an image 90 degrees - 5%
- Scale to fit - 5%
What to turn in in class
- Your design
- Class diagram (hand in hardcopy)
- CRC cards (photocopy them and turn in a copy) Keep your original cards as we'll be adding to these for later milestones.
- Any other documentation about your design
What to turn in on the turnin swiki
- Your code for the three implementation part
- A ReadMe file to how to get it to work
What to do after turning everything in
- Schedule a block of time with your TA to demonstrate your implementation part and to get feedback on your design part. The TA will load your code from the turnin site.
- Note: Your TA will grade your design. If there are serious problems with your design, use your TA as a resource to fix them before Milestone 3 is due.
- This is the major design portion of the milestones. You should sit down with your group and think through what you feel will be involved with the rest of the project.
- Please plan carefuly. We want class diagrams and CRC cards. Anything else you include is always welcome to clarify your design decisions.
- CRC cards are used to discover what the requirements for a system are and begin to understand how various components will interact with each other.
- Your CRC is yet another way of describing your design, in terms of class colaborators. Think of this as another design view.
- The UML portion will be graded based on whether or not we look at it and can understand what you've designed and if it will work.
- Necessarily, grading design is going to be subjective so it will be advantageous to your grade to set up a time with your grading TA to present your design and demo your code. (HINT! HINT!)
- You should turn in a UML class diagram, and CRC cards. Any addional UML or writeup would also greatly clarify your design and would be appreciated.
- State Diagrams
- UI Mockups
- Use Cases
- Sequence Diagrams
- As always, give us a readme file that explains anything you think may not be clear.
Links to this Page