Page 133 - Navy Journal 219

Software Project ...

project managers. However, this is to be considered that the whole discussion is
made from clients’ point of view. Our goal is to ensure safe software
development practices from our contracted partners. To do so we need to have
sufficient awareness on the fact of project failure and the impacts of different risk
factors like requirement volatility. If the users are self-aware on this issue then
the RM frameworks can be easily implemented and contracted software
development firms would be guided accordingly. However, the best
implementation strategy for introducing software RM technique is to induct it
gradually so that the BN software development culture can be gradually adjusted
to the risk management practices and risk driven process model as advised by
Boehm. The existing culture of software development in BN is concentrating on
the traditional idea of developing software to automate everything and that the
responsibility lies to the developer to make it full-prof. The visualization of the
users is still impaired by renowned software of big companies like Microsoft.
The ideas of visualizing transformation of own requirement into a customized
software development has to be developed. The next step is to identify an initial
small scale project to implement software RM embedded in the spiral SDLC.
Risk identification and prioritization will be the key aspects on this small scale
project which will create the culture conducive to the transformation of present
methodologies used in BN software development projects.
Concluding Remarks
The software ‘Hall of Shame’ is envisioned to grow longer and longer in
the near future. The list will be increased with the increase number of software
project runway or failure. The reason is very simple; everything we see around us
is intended to be automated trough software development. The organizations
around the globe want their systems to be user friendly and profitable at the same
time. The booming software development industries also facilitate to do more
projects in a competitive mood but at the cost of creating software junks which
are unusable and unsatisfied to the clients. The most significant loss of software
project failure is the time spent on the project and the loss of data in some cases.
However, the most devastating effect is the loss of confidence on automation.
BN software development projects so far are about 80% successful with
their intended use. However, if safe software development practices and culture
cannot be introduced then several projects might be jeopardized in terms of their
utilization. To prevent so, an attempt has been made in this paper to

125