-
Notifications
You must be signed in to change notification settings - Fork 4
TA Feedback February 11
aewilson-ua edited this page Feb 12, 2015
·
2 revisions
- number your use cases!
- Some use cases should be split up. For instance, the use case with the goal "Editing/Deleting a claim" should be split into two use cases. If use cases have some parts in common, then split that out into another use case, and then include it as a precondition (eg. "user has navigated to a claim via use case __").
- don't forget your pre/post-conditions
- In your tests, make sure that you are asserting the correct behaviour. For instance, in your claim test testUseInvalidDate(), you assertTrue("Invalid Claim: Start date occurs after end date", claim.getEndDate.before(claim.getStartDate())); as I understand it, you want startDate to be before endDate, not the other way around.
- generally, your tests look good
- you're on the right track with use cases, but there is still lots left to do
- please make a wiki page that embeds all of the images
- where is the mockup? You should have a mockup that includes all screens, and a storyboard that covers one simple scenario
- the storyboard is huge! Just do " a non-trivial but coherent scenario of using your application" it does not need to be the entire app, or include alternate flows.
- your storyboard does need some extra information such as labels for transitions describing what the system has done etc.. You also need to describe what the user is trying to accomplish
- your .svg files don't work in firefox, please find a way to make them work there. Perhaps export from inkscape to plain svg?
- make sure that your UI lines up with your usecases (anything mentioned in the uses cases should show up in the mockups)
Don't forget this. I would rather you do it with tickets and milestones in the project's issue tracker than in the wiki. This doesn't take much more effort and will be more useful to you down the line.
- glossary looks nice :)
- Don't forget to "provide a list of useful informational references or links to related or competitive products." I don't need anything too detailed there, less than ten links with a brief description of each is fine.