I started the design from the class diagram after going through the requirements and BDOM, but it seems really confusing so far. Basically I'm following the Cade's example for this. I'm wondering how have other people started out. Is it more feasible to start from the sequence or component diagrams before you jump into the class diagrams?
The assignment documentation (i.e. the Business Model) is purposely inaccurate and inconsistent (e.g. the supporting documentation does not reflect the use case diagrams or other use case forms etc.). Therefore, if you start by creating a class diagram you will very quickly come across a number of issues and conflicting requirements.
In order to assess the assignment correctly. My advice is to spend a lot of time performing some analysis on the requirements, identifying and resolving issues and assumptions. It is important to note that these should be recorded in your final return.
Once you have defined and documented your assumption of the requirements and have resolved any issues, you can then start the enjoyable stuff by creating a conceptual class diagram and start iterating through the use cases until you have created a sufficiently detailed realisation of each one.
Although the assignment does not state it, as it assumes that the student will adopt this approach, you do need to start the OOAD process at the beginning rather than in the middle. On a real project, assuming the Business Analyst was present, there would be a handover workshop or meeting to qualify any outstanding queries or issues but on this assignment you have to identify and make your own decisions.
Ian Roberts<br />Application Architect<br />SCJP, SCJD, SCEA, OCUP Fundamental