Hotspots: Admin Pages | Turn-in Site |
Current Links: Case Final Project Summer 2007
M5: Team Design
Team Design
Welcome to M5! This was the UML, Sequence Diagram, and
general "how will the classes interact" milestone.
Make sure to read the book for this part, as UML and
Sequence Diagrams are very difficult to just produce
out of nowhere. And remember: start early ;)
General UML Tips
- Make sure to cover the interactions between your classes
accurately. Do not just stick lines connecting everything
and call it "done." Use the appropriate lines and arrows!
- Get a program to help you. A UML design program will make
your diagrams look a lot nicer and may be able to help you
out!
General Sequence Diagram Tips
- If you made detailed scenarios for M3, this should not be
too bad. Just make sure you know what is getting sent between
two classes and when.
- Good sequence diagrams may help you with the programming and
better refined methods to accomplish the task laid out by your
diagrams.
Contract Tips and Error Handling
- Trust contracts designate how classes will communicate with
each other to ensure an error-free interaction. Keep in this
in mind when thinking about the pre/post conditions.
- On a basic level, you probably would have no outside input
except from users in the GUI. If this is the case, we recommend
error handling where the input comes in from.
Everything Else Tips!
- Good GUI mockups will help with the overall design and implementation
of the GUI. Trust us.
- A centralized system architecture is what we ultimately went with,
but do not discount other methods. Use the one you like, or (like in
our case) plays best to the overall intent of the program.
- BEGIN CODING! This will allow you to revise your classes now as you
go, and will save you the surprise later of how much your cards may
not have accounted for.
Our Successes and Failures
Success:
- Our diagrams looked pretty nice.
- Hit all of the requirements in a timely manner, due to...
starting early!
Failures
- Took us a while to figure out what we needed to do, because
- only one or two of us actually had the book.
- Diagrams had a few errors on them which we could have caught
- had we understood the diagrams and UML better.
Our Diagrams!
Our UML Diagram:
Our Sequence Diagrams:
Our trust contracts:
Our system architecture:
Trust Boundaries
CCS GUI Mockup
POS GUI Mockup
Supplier GUI Mockup
Link to this Page
- Team Apathy2 last edited on 23 April 2009 at 10:43 pm by 128.61.127.211