Win a copy of Clojure in Action this week in the Clojure forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Risk and Mitigation of assignment (SCEA part 2)

 
Marco Lombardo
Ranch Hand
Posts: 71
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I was investing to find a Risk (and relative Mitigation) non my assignment (part2 on scea).
Such risks are purely technical or other (functional, costs, etc...)?
I find on my assignment a part where there are uptime system and response time requirements... are these risks?
Can you give me some guidance on how to find certain risk on assignment part?

Thanks
 
Remko Strating
Ranch Hand
Posts: 893
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I don't know what you mean by risk and migration management. I would believe this related to project management and not to the service design itself.

Within the design you could consider to take measures for the requirements of the customer. These are like the availability, reliability capacity, performance, maintainability of your design. Normally you would capture this requirements from your customer and based your design on his wishes and what he wants to pay for it.

I haven't seen an assignment yet, but I believe that you have to show that you can design a J2EE-solution and can explain why you did so, but maybe I'm wrong. I would just use the standard solutions and explain why I use them in the case. If you do that I believe you're fine and don't make things to complicated.






 
Rishi Shehrawat
Ranch Hand
Posts: 218
Hibernate Java Spring
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
"Uptime system and response time requirements" are non functional requirements (NFR) that need to be addressed by your proposed design/solution. In my opinion you will need to show/highlight the design decisions that you have taken to address these NFR's.
 
Remko Strating
Ranch Hand
Posts: 893
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
True.

First you need to address which Uptime system and response time requirements the customer needed and why. Par example a system with a lot of human interaction needs normally response times between 2-3 seconds on the other hand a system which is processing documents for the administration could wait for minutes to interact.

I believe showing that you can handle this process is more important than the result itself. The last is depending on technology and will change the first is depending on your skill which improves.
 
Marco Lombardo
Ranch Hand
Posts: 71
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Risk and Mitigation List is a section of deliverables in scea part2.
It takes 16 points of 160 total points of part2 of the exam.
Anyone know a guidance to identifiy them?
 
Remko Strating
Ranch Hand
Posts: 893
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
So they want to test your project management skills.

Risk Management

The way I do it.

Make the design.

Think over possible threats of your design. What can go wrong?
What are the problems of the customer and system if it happens?
What is the probability if it happens? What is the impact it happens?
What kind of measures are you taken if it happens?

Put this assessment in a list and you're done. I will concentrate myself on items which I can influence in the design, because you're making a design.
 
Marco Lombardo
Ranch Hand
Posts: 71
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I would understand better the phrases:

"What is the probability if it happens? What is the impact it happens?
What kind of measures are you taken if it happens?"


My questions are:
Already in the development of my design do I predict how solve these threats ?
Or I have to stop my project, and predict how I will change my design if these threats will occur?

Thanks
 
P Das
Ranch Hand
Posts: 123
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
To me, "technical risk" has never been a clear term: for example, if the assignment is based on incomplete premises (use cases), would it or would it not constitute technical risk? Then, the term used, "mitigation", is only one way to respond to a risk, other ways are transfer, acceptance, etc.
 
Marco Lombardo
Ranch Hand
Posts: 71
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Anyone can help me about my following questions about scea part2:

Already in the development of my design do I predict how solve these threats ?
Or I have to stop my project, and predict how I will change my design if these threats will occur?

Thanks
 
Remko Strating
Ranch Hand
Posts: 893
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Just how you believe you will handle the risk if the threat occurs.

You could decide to stop the project if it happens (retention of the risk)

You could decide to make a redesign (avoidance/prevention of the risk)

 
Claudiu Dumitrescu
Greenhorn
Posts: 29
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You can think as risks, problems like network or hardware failure during a process execution. How do you intend to address this? Do you have a solution and does the risk justify the solution costs?

Of-course, some of the requirements can become a risk when the system is taken out of the limit specified by the client. For example: the client might state that the number of contemporary users is between 1 and 100. And you should design the system with this limitation in mind. But what happens when there will be more users: do you address this risk, or the costs are to high to justify a solution the client does not see it as necessary?

 
I agree. Here's the link: http://aspose.com/file-tools
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic