Did you write about your architecture and design in general to elaborate on it? It seems like a lot of people do even though it's not "officially" required.
Also - how many pages were you assumptions?
Some may notice I asked Chi this too. Trying to determine how much detail to put in the explaining what I did.
Joined: Jan 29, 2003
here is a summary of my design
1. class diagram - I have 17 classes. The diagram is based on BDN. I added only one or two new classes based on the BDN. So, my class diagram is quite simple. If you view the BDN as core, I added surrounding classes using common design pattern. They are presented in stereotype, e.g. SLSB. I didn't add any method() or attribute, because I think these should be development issues.
2. component diagram - I used MVC, but didn't use any specific framework. based on cade's example, I elaborate each view/controller/model/external system/legacy system. Most of the components is to be implemented in development. Quite detail, but I didn't use package to represent components. If you read cade's book, you will get my idea.
The main reason I use detail component is I have very little idea how to use only package, consolidated component to elaborate. if you design the package and have corresponding classes inside, pls refer other posts.
3. sequence diagram - I have 7 sequence diagram. each use case has one. alternative solution has their own.
addtional: one deployment diagram,
Assumptions are explained for each diagram. You may think a consolidated assumptions will be better. I also addressed functional, non-functional services.
Overall, I used common design patterns. Not heavy, cause I think unless necessary, it is not really needed to put too many patterns. Also, the project, if it is to be implemented, it has to follow some general approach supported oy particular app server. So, I didn't really use all design patterns in the petstore.
The percentage of lossing mark for each part is similar. It might be because I ommited details of BDN.