Bahir Dar University

Bahir Dar Institute of Technology (BiT)

Faculty of Computing
Department of Software Engineering
Risk Management Course

Team Members
1. Mintesnot Desta……………………………………….1011089
2. Million Sharbe………………………………………......1011088
3. Tomas Fasil…….………………………………...........1010840

Submitted to: Mrs Solome.

Submitted date: May 13, 2022 G.C
 2

Acknowledgement

We would like to thank our teacher Solome. for giving us this assignment, it has been a learning
experience for us. It has enabled us to better understand risk management techniques and how to
implement them in our projects. We would also like to thank those that helped us by giving us
the necessary information to complete this assignment, we would not have been able to finish
this assignment without your help.
 3

Risk Management in Ethiopian Educational Augmented Reality

AppStore with localized augmented reality Apps

1. Identify five risks related with your industrial project.

Risk 1: There is no expertise in 3D modeling and Augmented reality apps delivery

time will be extended.
Risk type: Technical risk

Risk 2: The required hardware (GPU) for 3D modeling is expensive and the team
members can’t afford that.
Risk type: Operational risk

Risk 3: The Mobile app must be developed using flutter and we do not have
expertise in flutter and dart programming language; the Mobile app may not be
completed on time.
Risk type: Technical risk

Risk 4: Our project heavily uses NPM Module; and it has high security risk of NPM
Phishing attack.
Risk type: Technical risk

Risk 5: The team is late on project deliverables, AppStore (0%) and Apps (20%),
while delivery date is impending.
Risk type: Schedule risk
 4

Risk 1: There is no expertise in 3D modeling and Augmented reality apps delivery

time will be extended.
Id BYD01 Risk Information Sheet Identified: 6/9/2014

Priority: 1 Statement: There is no expertise in 3D modeling and Augmented

Probability: High reality app development so, delivery time will be extended.

Impact: High Origin: Mintesnot Class: Program Assigned to: Million

constraint- Skill
Timeframe: Near
Context: The App store we are building will be shipped with AR and VR educational and
entertainment apps and the expertise required to develop such apps requires knowledge in 3D
modelling and the Vuforia engine, which our team members are not adept in.

Mitigation Strategy:
1. Million will see to it that the best tutorials are sought for. Due 6/25

2. The team will get training on 3D modelling and the Vuforia engine. Due 7/30

3. Million will get current status of the risk BYD01 mitigation and check how well things are
going. Due 7/5.
4. Million will revise and resubmit risk BYD01. Due 7/15.

Contingency plan and trigger:

Request additional help from other sources if we can’t get training
to help with training or get the apps from on time
third party developers.

Status: Status Date:

Million found Udemy tutorials on 3D modelling for free. 9/5/2014
Group discussion occurred on what we have learned. 9/6/2014
Each person got assigned which model to design. 9/7/2014
Risk closed – knowledge on the subject has been acquired 9/8/2014
– risk no longer exists.
Approval: Mintesnot- Project Closing Date: 9/12/2014 Closing Rationale:
team coordinator Sufficient knowledge has
been acquired.
 5

Risk 2: The required hardware (GPU) for 3D modeling is expensive and the team
members can’t afford that.
Id BYD02 Risk Information Sheet Identified: 9/10/2014

Priority: 4 Statement: The required hardware (GPU) for 3D modeling is

Probability: High expensive and the team members can’t afford that.

Impact: High Origin: Tomas Class: Program Assigned to:

constraint- Skill Mintesnot
Timeframe: Near
Context: The development of 3D models that are interactive requires high graphics
processing, which requires computers designed for that purpose, which are expensive and our
team members don’t own any.

Mitigation Strategy:
1. Mintesnot will see to it that online processing power can be acquired. Due 9/11

2. Mintesnot will check the reliability of found online processing power. Due 9/12

3. Tomas will get current status of the risk BYD03 mitigation and check how well things are
going. Due 7/30.

4. Mintesnot will revise and resubmit risk BYD03. Due 9/30.

Contingency plan and trigger:

Request additional help from the University if we can’t get online
to acquire processing power from other sources processing power for free
or ask friends to help with lending some processing.

Status: Status Date:

Mintesnot found 3 free online processing power suppliers. 7/30/2014
After reliability test Mintesnot decided it’s not worth it to 8/1/2014
use the free version since it is not reliable.
After much consideration Mintesnot found a friend who is 8/2/2014
willing to lend his PC, which has high processing power and
pre-installed 3D modelling software.
Risk closed – 3D modelling has begun – risk no longer 8/6/2014
exists.
Approval: Million- Project team Closing Date: 8/6/2014 Closing Rationale: 3D
leader modelling has begun.
 6

Risk 3: The Mobile app must be developed using flutter and we do not have
expertise in flutter and dart programming language; the Mobile app may not be
completed on time.
Id BYD03 Risk Information Sheet Identified: 01/9/2014

Priority: 3 Statement: The Mobile app must be developed using flutter and we
Probability: High do not have expertise in flutter and dart programming language; the
Mobile app may not be completed on time.
Impact: Catastrophic Origin: Class: Program Assigned to: Million
Mintesnot Constraint: Time
Time frame: Near
Context: We decided to build the mobile app by flutter and dart programming language
because its multi-platform and have nice full feature of design with material design but we
did not have the expertise of it to build using flutter one of our team member only have
expertise on Android programming using JAVA.

Mitigation Strategy:
1. Mintesnot will study the official flutter documentation for its current version. Due 4/15.

2. Mintesnot will use video tutorials to ger a better understanding of how flutter works. Due
3/11.

3. Million will get current status of the risk BYD03 mitigation and check how well things are
going. Due 5/1.

4. Mintesnot will revise and resubmit risk BYD03. Due 6/20.

Contingency plan and trigger:

The mobile version of the project will be if we can’t improve our
Transferred to flutter mobile developers technical skills in the flutter
for better development and arrival time. SDK and Dart language on time

Status Status Date:

We purchased highly rated flutter tutorial from Udemy 01/9/2014
Integrating flutter SDK in Android Studio IDE started 5/9/2014
07/9/2014
Setting up the Flutter environment on working PC Finished
09/9/2014
Risk Closed: Required Knowledge is gained and project
setup Successfully completed
 7

Approval: Tomas– Project team Closing Date: 05/9/2014 Closing Rationale: Risk
coordinator completed successfully;
probability = 0.
Risk 4: Our project heavily uses NPM Module; and it has high security risk of
NPM Phishing attack.

Id BYD1 Risk Information Sheet Identified: 26/8/2014

Priority: 5 Statement: Our project heavily uses NPM Module; and it has high
Probability: High security risk of NPM Phishing attack.
Impact: Catastrophic Origin: Mintesnot Class: Program Assigned to: Million
Constraint: Security
Time frame: Near
Context: We will develop the web version of the project using NODE JS JavaScript runtime
environment and expressJS framework but due to high dependence of NODEJS on NPM
Modules we may have high security risk of NPM Phishing attack on our project after
deployment.
Mitigation Strategy:
1. Million will review/revise NPM Modules Official documentation for how to safely install
npm modules. Due 4/15.

2. Million will check the current installed NPM modules for their reliability and vulnerability.
Due 3/11.

3. Million will check with QA about how well things are going in their areas.
Due 5/1.
4. Million will revise and resubmit Module test Facility schedules based on above actions.
Due 6/20.
Contingency plan and trigger:
In any issues the project will be Version controlled if security issues should
using GitHub so it will be rolled back to the previous persist in our project
stable version without those Vulnerability issues.
Status: Status Date:
Research on official NPM documentation started for better risk free NPM 2/9/2014
modules.
Pushing the project to GitHub Repository done without NPM modules. 2/9/2014
During any NPM Module installation modules with vulnerability Report 01/9/2014
from the CMD removed.
Risk closed: by removing vulnerability issue NPM Modules and 02/9/2014
By installing vulnerability free, secure and trusted NPM Modules from
official NPM Module website.
 8

Approval: Tomas- Project Closing Date: 02/9/2014 Closing Rationale:

team coordinator Risks mitigated
successfully with
solving initial issues.
Risk 5: The team is late on project deliverables, AppStore (0%) and Apps (20%),
while delivery date is impending.

Id BYD05 Risk Information Sheet Identified: 9/12/2014

Priority: 2 Statement: The team is late on project deliverables, AppStore (0%)

Probability: High and Apps (20%), while delivery date is impending.
Impact: Catastrophic Origin: Million Class: Program Assigned to: Tomas
Constraint: Time
Time frame: Near
Context: Our project deliverables include a fully functional app store and 3-5 augmented
reality apps but development is progressing at a very low pace with app store development
at 0% and apps development at 20% due to team members being busy and knowledge being
of insufficient but delivery time is impending.
Mitigation Strategy:
1. Tomas will see to it that app development is started after risk BYD03 is mitigated.

2. Tomas will see to it that app store development is started after risk BYD04 is mitigated and
app development reaches 35%

3. Mintesnot will get current status of the risk BYD05 mitigation and check how well things
are going. Due 5/1.

4. Tomas will revise and resubmit Module test Facility schedules based on above actions.
Due 6/20.
Contingency plan and trigger:
Research additional problems with the risk that
that should be mitigated and see to it that risks if team members can’t
BYD03 and BYD05 are not holding back progress develop deliverables rapidly
App and Appstore development.

Status: Status Date:

Since risk BYD03 has been mitigated app development has 8/5/2014
started progressing.
App development reached 35% and Appstore development 9/5/2014
has been started.
Development is progressing well and seems like delivery 9/15/2014
 9

date can be met.

Risk closed – Progress is established – risk has been 9/10/2014
mitigated.

Approval: Million– Project team Closing Date: 9/12/2014 Closing Rationale:

leader Deliverable progress
has been established

Conclusion

We have identified 5 risks that are related to our project and using Tri –level attribute evaluation
method decided to give a value for impact, probability and timeframe. Each risk has been given
priority levels which is required for ranking of risks which is used to indicate the gravity of the
risk and to decide which should be mitigated first. With a team member of three we have
distributed each risk and assigned responsibilities for each risk, each responsible person has the
accountability, authority and responsibility for the risk he has been given.

By using the risk information sheet, we have been able to identify the risk and described them in
an easy and understandable manner; we have analyzed each risk and assigned them measures
with their appropriate value; we have planned for different mitigation actions and strategies to
take for each risk and tracked their status and how they have evolved during a certain period of
time for each risk.

By using risk management, we have been able to solve these uncertainties that we call risks that
could have evolved into problems, we have learned that, in the case where our project is
implemented in the real world, what we have done and extensive risk management will be most
beneficial and a necessity for project management which will lead us to ultimate success.