Risk & Mitigation list - SCEA 5 assignment

[Ashwin Pai]

Hey Guys,

I am working on my SCEA5 assignment and wanted to clarify on the "Risks & Mitigation List". Does this refer to the risks that I have taken care of in my design ? or does this refer to the risks the application could face post implementation?

Thanks
Ashwin

[Wilmar Rodriguez]

This question concerns about technical risks on your proyect and their mitigation strategies, for example
What happens if the system can't have good scalability? , What if a lot of throughput?. What if a bad manageability?.
How you can fix this? This is the mitigation strategy.

[Hong Anderson]

For me, we need to identify risks in architecture and design level.

"What happens if the system can't have good scalability?"
That's not an option, it's a non-functional requirement that need to be satisfied.

We cannot just say like, what if we cannot design? what if our design is wrong?

Although it can happen, but we don't categorize that as a risk.

[Wilmar Rodriguez]

Yes i agree with you on scalability must be addressed in the design phase. But always is a Risk if the system grows.
The idea is detail the risk and its mitigation strategy. For example increase with vertical scalability(Horse Power), if not horizontal scalability for example
create a plan for clustering Web or EJB Tier, put oracle web cache, put load balancer, whatever.
This point is one of the first topics in SL425 SCEA5 Course.
Again i agree with you. The Java architect must orchestrate the correct design of the application including FR and NFR but risks are those situations maybe could be happen.

[J J Wright]

What's the wording associated with your risk and mitigation strategy requirement? My assignment specifically uses the term "technical risk". I don't see NFR as technical risks - you either achieve them or you don't. For me technical risks are more like the failure of a B2B component through network outage or the failure of a third-party back-end system upon which you rely. A mitigation strategy should deal with these gracefully rather than have the whole system fall over.

[Ashwin Pai]

Jonathan Aotearoa wrote:What's the wording associated with your risk and mitigation strategy requirement? My assignment specifically uses the term "technical risk". I don't see NFR as technical risks - you either achieve them or you don't. For me technical risks are more like the failure of a B2B component through network outage or the failure of a third-party back-end system upon which you rely. A mitigation strategy should deal with these gracefully rather than have the whole system fall over.

The assignment does say "technical risks".
This is what I was thinking too... possible system failures (not necessarily due to bad design) and how it could be handled.
eg:- DB corruption due to server failure is a risk and having daily/weekly bakups is a mitigation startegy.

However the assignment says.. "List the top three technical risks you have identified in the project and identify a mitigation strategy for each risk." Note it says "identified in the PROJECT".
Can this mean that although i have DESIGNED to meet the NFRs & FRs, it still could endup in not meeting the NFR due to say bad code? This would crop up when the app goes live and would have to be handle/solved. So, can not meeting the NFR be a risk ?

Thanks
Ashwin

[Wilmar Rodriguez]

I agree with you Ashwin Pai -> 3 Top 'Technical Risks' in the PROJECT and mitigation Strategies

[J J Wright]

One of the most succinct definitions I've come across to date is as follows:

"technical risk is the product of the probability of a technical event and the cost of that event"

[J J Wright]

I stand corrected. I think if you use this definition it's perfectly OK to classify a failure to scale or an inability to easily change as a technical event. After all you could easily classify a failure to handle integration issues as a failure to meet availability requirements if they result in a complete system failure.

[Rahula Krishnan]

HI All,


Can i include risk and mitigation in assignment deliverable, which is already address in my design?


Thanks
rahul

[shekar hari]

Yes, you need to document them clearly. See replies above.

[Rahula Krishnan]

OK. thanks. One more question.. how can i show the integrated application in the class diagram. Actually i have one application which is already developed, its shared as API, i need to integrate that application in to my application. Please let me know, whether i need to show the inegrated API in class diagram or not . .. if yes, How can i show the integrated API's in my class diagram ?? i means which UML component i need to use.