Originally posted by H. Hafer:
May I justify from the numbers of your artifacts that one of your goals was to provide the most simple solution as possible?
Especially the number of bulletpoints in your assumptions file is very appealing
Now don't tell my that your diagrams are terribly complex and contain tons of elements each
Originally posted by Parag Doshi:
did you have to change the business domain model relationships to complete your design( things like association btw flight/segment, multiplicity etc)?
Originally posted by Harish Ramchandani:
In the 'client-tier' package, I had two subpackage (One for each type of client). To make it simple, I just put only ONE component in each package and attached a note containing all screen names that the system will have. In this way, you can avoid putting so many components (one for each screen ) in your component diagram without loosing any information.
And ofcourse, your core business logic will be implemented in EJB-Tier that will be used by both type of clients. That means, there is no duplication there. You just have to use different business delegates that will delegate the client request to EJB-Tier.
Hope this helps.