Page 125 - Navy Journal 219
P. 125
Software Project ...
Pitfalls of SDLC and Software Risk Management
Research of failed software projects indicates that the problems could have
been avoided or reduced if there had been an early intervention with
identification and resolution of the high risk element (Boehm, Software Risk
Management: Principles and Practices, 1991). The early intervention demands
the careful dissection of SDLC. SDLC in simple terms is a framework defining
tasks performed at each step in the software development process. The life cycle
defines a structured process to improve the quality of the software and its optimal
utilization. SDLC is basically followed by the software development team
aiming to produce quality software exceeding customer’s requirement,
deadlines, and cost estimates. Though, SDLC is seen as the tool of software
developers but the role played by the customer in each of the step is huge. In fact,
SDLC involves all stake holders and the process inherits risks in each step. The
term ‘risk’ is commonly defined as a measure of probability and severity of
adverse effects. According to Haimes, risk is defined as “a combination of the
probability of undesirable event with the magnitude of each and every
foreseeable consequence (damage to property, loss of money, injury to people,
lives lost, and so on)” (Haimes, 1991). In line of project management, risk is
identified as the degree of exposure to negative events and their probable
consequences (Barki, Rivard, & Talbot, 1993).
Figure 2. Basic Waterfall Software Development Life Cycle
Analysis • Requirements
Analysis
Requirements • Project
Specification and
Specification Brief
Design • Design and
Document Prototype
• Installation,
Implementation Demo and
Feedback
Testing and • Identify and
Integration Resolve Bugs
Operation and • Technical
Maintenance Support
Source: The Techtalk Journal (https://tech-talk.org/2015/01/21/system-development-
life-cycle-sdlc-approaches/)
117

