Congratss
Here some tips:
http://www.selikoff.net/2010/11/17/jeanne%E2%80%99s-sceaocmjca-5-part-23-experiences/
http://scea5-passingpart2and3.blogspot.com.br/
http://sceacertification.blogspot.in/2011_12_01_archive.html
http://javalogue.blogspot.com.br/2011/01/romancing-scea-completing-part-2-3.html
http://java.dzone.com/articles/my-path-scea-5
http://theholyjava.wordpress.com/2010/07/21/my-path-to-scea-5/
Pay attention on the extraction of requirements:
- Description of the company's history.
- Description of the legacy systems.
- Description of use cases.
- Description of the infrastructure required.
-Assignment document is incomplete, unclear and not practical. You are free to make any reasonable assumptions yourself: that is why part of the delivery is a document where you describe your assumptions and how they affected your solution.
Link texts cited with each type of non-functional requirement:
- Look at all documents that informed the descriptions attached to each requirement.
- Example:
*) number of demand for system usage and expectation = increase scalability.
*) response time for something = end-user performance.
*) response time te = communication between systems performance.
Consider FR making hiposteses:
- Suppose something already there and do nothing and just document "such a thing already exists and so I will not do anything."
- Suppose something is not there, adding this to your project requirements consider in the proposed architecture. Take care to not complicate your project. Document this assumption too!
Consider NFR making hiposteses:
- Security, scalability, performance, integration, and transactionality gui. Document this assumption too!
Atention - Do not assume anything that will complicate your project, just assume things that are missing and that will give a quality in your project.
Regards
