Page 124 - Navy Journal 219

Navy Journal 2019

development phase has gone in different way. Similar thing happened in a
renowned warehouse management software during 90s. The warehouse was
vanished from the eyes of the retailer’s automated distribution system. A sudden
malfunction somehow erased the warehouse’s existence, so that the goods routed
for the warehouse had been rerouted elsewhere. After three years, the warehouse
had to be sold off for huge loss (Charette, 2005). BN has introduced Enterprise
Resource Planning (ERP) software to automate the store, demand, and issue
management of her Naval Store Depot (NSD) Chattogram. The software is under
up-gradation to provide support in different geographical locations. Thousands
of line items are stored with digital information and started issuing over network
or internet. What will happen if there is intended or unintended software glitch in
the software in terms of inventory and issue management ! Besides, software
failure can imperil national security. Integrated and shared software like IBAS++
is very recently introduced in BN. This is very much vulnerable to national
security if the software fails. Before going into detail with the structured thoughts
on the software risk management, a generalized concept to be developed on the
causes of software project failures. Careful investigation on the literatures in this
aspect reveals that badly defined system requirements, unmanaged risks, poor
communication among customers (BN), developers (contracted software
development firms), and users (concerned offices for whose operational easiness
the software is being developed), and poor project management contributes to
project runway significantly.The generalized concept also includes a basic
understanding on Software Development Life Cycle (SDLC) and the inherent
pitfalls in it.

Figure 1. Software Hall of Shame

Source: Charette, R. N. (2005). Why Software Fails. NA: IEEE Spectrum.

116