 |
|
|
Use cases: 10 points
- They should have 2 (or so) fully dressed use cases.
- The fully
dressed use cases should show all possible paths through that part of
the system.
- The brief use cases should show some thought into what
the final implementation of the final system.
Domain model: 15 points
- The domain model should be fairly detailed, showing a good amount of
thought went into creating it.
- 3-5 points were deducted if there was not more than (roughly) 6-8
classes and interactions among them.
System sequence diagram: 10 points
- If it captures some scenario of the use case, 10 points were
awarded.
Operation contracts: 10 points
- Points were deducted if not more than 5 operation contracts were
identified.
Language choice: 5 points
- This doesn't have to be much -- just a paragraph or two describing
what language they selected and why they picked that particular
one.
Code base: 50 points
- The code base should be about 500 lines per group member.
- If very far from the target of loc, around 30-40 marks were reduced.
- It should be a fully working system -- it doesn't have to do very
much, but it need to be fully working. If it is a web-based
system, then they should include a link (most likely in the readme) as
to where one can use the system online. Each code base will have
to be executed.
- If the code did not execute due to some error or absence of some
library, 5 points were deducted.
- 5 points were deducted if a readme file was not included.
- It should have some comments -- enough so that one understands
what's going on; the comments don't have to be verbose.
|
|
