It's not a secret anymore!
The moose likes Architect Certification (SCEA/OCMJEA) and the fly likes assumptions Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Certification » Architect Certification (SCEA/OCMJEA)
Bookmark "assumptions" Watch "assumptions" New topic


Leonardo Penha
Ranch Hand

Joined: Feb 15, 2002
Posts: 68
One of the deliverable for the project (part 2) is a list of assumptions made during the process of coming up with the architecture and design.
I have a few questions about this document:
- Should this be sent in HTML format or plain text?
- What kind of assumptions should we list? Can anyone give any examples?
- What if we disagree with the way the use cases were written? Would that be an assumption?

Sivasundaram Umapathy
Ranch Hand

Joined: Aug 10, 2002
Posts: 360
My answers
1. HTML is the format mentioned by SUN.
2. Anything,which you feel is vital to prove,that your design meets the requirements.It can be the assumptions on untold requirements or possible business flows to something like technological assumptions like xyz technology of J2EE will not be used in my design for so and so reasons.
3.Use cases depict the core business flows which is nothing but the funtional requirements of the system.Hence even if you disagree with it,you still need to implement them in your design.

Co-Author - SCMAD Exam Guide - ISBN:9780070077881
Author - Java certification success, Part 4: SCEA
Billy Tsai
Ranch Hand

Joined: May 23, 2003
Posts: 1304
for example: assuming that the system doesnt support internationalization.

BEA 8.1 Certified Administrator, IBM Certified Solution Developer For XML 1.1 and Related Technologies, SCJP, SCWCD, SCBCD, SCDJWS, SCJD, SCEA,
Oracle Certified Master Java EE 5 Enterprise Architect
I agree. Here's the link:
subject: assumptions
It's not a secret anymore!