Design Choices document

[Garandi Garandi]

I am done with the application code, trying to write design choices documnet, but don't know how to start it, and what should be the formate?
Thank you
Garandi

[John Smith]

Here is what I put in:
1. Abstract
2. General Considerations
3. RMI vs. Serialized Objects Over Socket Connections
4. Modifying vs. Extending the Data class
5. Server design
6. Database Record Locking
7. Simplifying data access
8. Client design
9. Exception Handling
10. Record Search Algorithm
11. User Interface
Eugene.

[Garandi Garandi]

Eugene,
Could you please tell me a bit more about the following sections.
1. Abstract
2. General Considerations
7. Simplifying data access
Thank you
Garandi

[John Smith]

Could you please tell me a bit more about the following sections.
1. Abstract
2. General Considerations
7. Simplifying data access

In Abstract, describe the purpose of the document. In General Considerations, you may want to state your assumptions and your primary reasons for your design, such as
a) The application must be easy to use
b) The application design must be clear and extendible
c) The junior-level programmers must be able to maintain the application
d) The application should use well-known data structures and algorithms to implement its features.
In Simplifying Data Access, you can discuss how you abstracted away the differences between the remote vs local database access (if you did), as well as your use of facade or data service object (if you did it that way).
Eugene.

[Matt Ghiold]

Eugene,
Check your pm.
Thanks,
-Matt

[John Smith]

Check your pm

Huh? What's "pm"?
Eugene.

[Aruna Raghavan]

Eugene,
He may be asking you to check your personal mail

[Aruna Raghavan]

Correction, private mail.

[John Smith]

Correction, private mail.

Oh, thanks, I was afraid "pm" means "post mortem", or "proper manners", or "pending matrimony"
Eugene.

[Matt Ghiold]

PM = Private message, sorry for the scare!
-Matt