This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I am studying the risks of an architecture (part 2) and was wondering if you can help by suggesting possible risks that may occur commonly. Any possibility is welcome, since I'm just studying (I'm not making the risks of my project). I thought the following risks:
- Security - account hijacking.
- Communication with external systems - ensuring communication time
- Scalability - the system does not deal with the volume of access.
- Exchange of persistence mechanism - possible exchange for DBMS, NoSQL, LDAP or wherever (I really dont know if it is classified as risk ...)
Please suggest any others that may occur ...
I do not agree with you. I believe we can talk about anything of OCMJEA, since that is not an assignment of specific candidate....
You guys look like they are turning this certification on a magical mystery ...
I really do not understand why ....
Anyway, thank you.
author and jackaroo
If you are trying to understand something that is outside of your domain knowledge then it is reasonable to ask questions about the domain. The example given is that if you have an assignment that revolves around an airline reservation system, but you know nothing about airlines, then it is reasonable to ask what they mean by a "leg" of a flight.
If you are asking any question that contains the actual text from your assignment, or that the answer to your question could be copied / pasted into a submission, then it will not be allowed. It does not matter what your motivations for asking the question are - it matters whether someone can use the answer in their submission
It is that last point that causes the most issues, and that is affecting you. In the assignment, candidates have to talk about risks and mitigation strategies. In asking for people to "[suggest] possible risks", you may provide a real candidate with a list of risks that they may not have thought of. This could result in them passing the exam without having the knowledge themselves.
My understanding is that this is partially a problem with perception of who should be attempting to complete this assignment / get certified.
I believe Sun (Oracle) believes that they (Oracle) are stating that successful candidates are qualified to be architects. As such, collaboration is undesirable since many architects do not get that luxury in their full time jobs.
I believe that many of the real candidates are attempting the assignment / certification as a learning experience - something to help them become an architect one day. As a learning experience then collaboration is a good thing.
At the end of the day, Sun / Oracle own the certification, so it is their rules that apply. They have asked us not to allow collaboration on this certification, and that is what we have to do.