Dhiren,
I want to upload the assignment by the end of the weekend.
So I am also busy with the documentation.
In the requirements they only ask a list with assumptions.
So i think If you submit anything more you should keep it
short and clear.
So i don't think a explanation is required where you evaluate all
options that are available with all cons and pros and
then come to your conclusion. I do think this would be too much.
I think a design decision might look like this:
copied from petstore:
SFSB is used because
"
1.
Thread safety
2. Lifecycle management
3. Client type Neutral
4. Scalable
"
I will do the following:
0. A list with links to all paragraphs
1. A list with assumptions
2. I list with design decisions. (e.g explain why you used SFSB)
3. Scope
4. Add some appendixes (could be: 1 definitions used; 2. List with JSPs + function; 3. List with Classes+function; 4. Patterns uses; 5. something about each element in QoS requirements)
I think this will make the document easy to navigate.
probably the grader will be most interested in:
- assumptions
- design decisions
- Qos
- Patterns Used
what do you think?
Am I missing something important?