UNIVERSITY OF DAR ES SALAAM

COLLEGE OF INFORMATION AND

COMMUNICATION TECHNOLOGIES
                DEPARTMENT O F COMPUTER
SCIENCE AND ENGINEERING
SOFTWARE PROJECT MANAGEMENT
ASSIGNMENT 2
COURSE CODE: IS 384
GROUP 4

S/N NAME REGISTRATION

NUMBER
1 TOMEKA 2019-04-12632
WINFRIDA
2 XIBONA, 2019-04- 12918
JESSE A.
3 WOISO 2019-04-13149
GABRIELA.
4 MWALUKISA 2019-04-08989
WALTER
The final year project chosen was, The Small
Business Formalization Information System. The main
objective of this project is to develop a small
businesses formalization that will guide a business
owner through the process of formalization
personalized for their type of business and redirect
them to the respective regulators registration
systems. This guidance will be accompanied with pre-
emptive instructions of necessary requirements for
registration at each regulator. The system will have a
loan management module, also to help manage the
disbursement and repayment of loans offered by a
microfinance organization. This main objective will be
achieved through the following specific objectives,
establishment of system requirements for both
collection and analysis, examining the regulations
required during the formalization process, designing
the small business formalization information system
specification, implement a working prototype of the
system with web application and USSD application
module and to evaluate the performance of the
system.
The methodology used will be the Parallel
Development Methodology. This methodology is a
modification of the commonplace Waterfall
Methodology. The Waterfall Methodology has a
variety of weaknesses including a lengthy time frame.
Parallel Development addresses this issue by
subdividing the project into subprojects that each are
developed within the same time period, therefore
project will be divided into two sub-projects: the web
application sub-project and USSD application sub-
project. Hence, Parallel Development allows the
system to be delivered in a shorter time period than
with the conventional Waterfall Methodology.
The team members on this project are the software
developer, business analyst and the stakeholder
involved.
The expected outcomes of this project will be based
on the solutions offered; these solutions will be vital
for these informal firms in helping them commit to the
process of formalising their business. It will make the
entire process of formalisation easier and more
accessible. And also help with the loans that would be
offered by the organisation to which the system will
be implemented for. The system will prepare
businesses through each process of formalisation and
assist them before they begin application at the
respective authorities.
The following is the critical analysis of the risk
management process using the risk identification
framework;

Risk Identification Table;

Risk Types Possible Risks Affects

Technology 1. New technology Product

being used to
 implement the
USSD
methodology
2. Implementation of
USSD technology
that has policy
rules requiring
payment of money
this could lead to
pending
implementation
3. Servers in the
meantime have
been implemented
in the Heroku
cloud server

Legal 1. Misunderstandi Busines

ng agreements s
between
stakeholder

People 1. Coding skills Busines

are limited, s and
according to Product
the
technologies
introduced in
the project
2. Illness of the
members
involved

Requirement 1. Changes in the Busines

requirements s and
needed by the Product
 client
2. Misunderstandi
ng of customer
requirements

Tools 1. The USSD Product

codes must be
paid
2. Simulation
environment of
USSD is
insufficient
3. Difficulty in
integration due
to the parallel
development of
each of the
modules to be
implemented

Estimation 1. The time and Busines

task scheduling s and
of activities Product
being
underestimated
2. The size of the
software
modules being
underestimated

Organisation 1. Organisation Busines

s steering s
committee
changes
direction of the
organisation
Risk Analysis

On this part we assess probability and seriousness of

each risk. Probability may be very low, low, moderate,
high or very high and the risk consequences might be
catastrophic, serious, tolerable or insignificant.

Risk Probability Effects

New technology low serious

being used to
implement the
USSD
methodology

Servers in the moderate serious

meantime have
been implemented
in the Heroku cloud
server

Misunderstanding low moderate

agreements
between
stakeholders

Coding skills are moderate moderate

limited, according
to the technologies
introduced in the
project

Illness of the low moderate

members involved

Misunderstanding moderate serious

of customer
 requirements

Difficulty in high catastrophic

integration due to
the parallel
development of
each of the
modules to be
implemented

Organisation moderate serious

steering committee
changes direction
of the organisation

Risk Planning

On this part we consider each risk and develop a

strategy to manage that risk. Different strategies can
be used; Avoidance strategies, minimization
strategies and contingency plans.

Risk Strategy

Misunderstanding of Prepare brief questions

customer requirements to ask customers before
the analysis and design.

Difficulty in integration There should be a

due to the parallel coding and testing way
development of each of of development even
the modules to be when its parallel.
implemented

Organisation steering There should be a

committee changes contractual basis on
direction of the
 organisation each of the stages.

Misunderstanding Stakeholders must

agreements between agree themselves
stakeholders before deciding the
requirements for the
system.

Servers in the meantime There should be a

have been implemented backup on the system
in the Heroku cloud implementations
server this could be a
problem due to updates
or fixes.

Illness of the members Reorganize team so

involved that there are more
overlap of work and
people that understand
each other’s jobs.

Risk Monitoring

On this part we assess each identified risk regularly to

decide whether or not it is becoming less or more
probable. Also, we assess whether the effects of the
risk have changed during the lifecycle of the project

Risk Type Potential Indicators

Technology Presence of many reported technolo

problems and faults, troubleshooting

Legal Poor stakeholder’s morale and minim

follow up.

People Poor relationship between team me

 and misunderstanding on many issu

Requirement Many requirements change request

Stakeholders complain on system h
design.

Tools Complaints about USSD API, comp

verification issues on documents us
system

Estimation Delayed to meet agreed timeline an

Organisations Organizational gossip, poor organiz

structure.