risk assessment individual week 2 3 
Risk Information Sheet
Risk id:1
Risk name: Downtime that Stevens company don’t expect may extend
Date: January 11, 2015
Probability: 65%
Impact: High
Description:
The time period that the company expects for the migration of data may extend unexpectedly thus increasing the downtime of data thus affecting its availability (Racherla, et al., 2010).
Refinement/Context:
Data migration tools may not be as effective and fast.
Power outages without backup plans in mind
Mitigation/Monitoring:
Adoption of multicore computer architecture and virtualization to reduce the maintenance window
Management/Contingency plan:
Have backup plans in case of power outages
Quality personnel with expertise in both SQL server and oracle.
Current Status:
In process
Originator:
Tamesha Timberlake
Risk Information Sheet
Risk id:2
Risk name: Budget Overrun
Date: January 11, 2014
Probability: 39%
Impact: Moderate
Description:
The amount the company uses in this exercise overruns the budget that the company expects for this process.
Refinement/context:
Re-purchasing of tools
Expenses that are initially not seen or unlikely to occur
Mitigation/Monitoring:
There is need to ensure that all expenses are on initially budget before the exercise starts
Monitor all the tools for faulty before starting any migration
Management/Contingency plan:
Continuous monitoring of migration tools
Thorough planning prior to migration
Current Status:
In process
Originator:
Tamesha Timberlake
Risk Information Sheet
Risk id:3
Risk name: Consumer or Brand Impact
Date: January 11, 2015
Probability: 25%
Impact: moderate
Description:
Data migration involves customer business data such that any loss to this data or its unavailability makes severe negative public relation impact.
Refinement/context:
Interruption and loss of customer/consumer data
Mitigation/Monitoring:
Make sure data migration is transparent by having distributed databases
Management/Contingency plan:
Inform the consumers and clients on the
Risk id:1
Risk name: Downtime that Stevens company don’t expect may extend
Date: January 11, 2015
Probability: 65%
Impact: High
Description:
The time period that the company expects for the migration of data may extend unexpectedly thus increasing the downtime of data thus affecting its availability (Racherla, et al., 2010).
Refinement/Context:
Data migration tools may not be as effective and fast.
Power outages without backup plans in mind
Mitigation/Monitoring:
Adoption of multicore computer architecture and virtualization to reduce the maintenance window
Management/Contingency plan:
Have backup plans in case of power outages
Quality personnel with expertise in both SQL server and oracle.
Current Status:
In process
Originator:
Tamesha Timberlake
Risk Information Sheet
Risk id:2
Risk name: Budget Overrun
Date: January 11, 2014
Probability: 39%
Impact: Moderate
Description:
The amount the company uses in this exercise overruns the budget that the company expects for this process.
Refinement/context:
Re-purchasing of tools
Expenses that are initially not seen or unlikely to occur
Mitigation/Monitoring:
There is need to ensure that all expenses are on initially budget before the exercise starts
Monitor all the tools for faulty before starting any migration
Management/Contingency plan:
Continuous monitoring of migration tools
Thorough planning prior to migration
Current Status:
In process
Originator:
Tamesha Timberlake
Risk Information Sheet
Risk id:3
Risk name: Consumer or Brand Impact
Date: January 11, 2015
Probability: 25%
Impact: moderate
Description:
Data migration involves customer business data such that any loss to this data or its unavailability makes severe negative public relation impact.
Refinement/context:
Interruption and loss of customer/consumer data
Mitigation/Monitoring:
Make sure data migration is transparent by having distributed databases
Management/Contingency plan:
Inform the consumers and clients on the
References: Racherla, S., Bajaj, V., Knebel, E., Korn, G., Kutepova, A., Newell, G., et al. (2010). IBM Information Infrastructure Solutions Handbook. IBM Redbooks, 2010, from www.books.google.com Rozanski, N., & Woods, E. (2011). Software Systems Architecture: Working with Stakeholders Using Viewpoints and Perspectives. Addison-Wesley, 2011, from www.books.googlr.com