Page 132 - Navy Journal 219

Navy Journal 2019

Figure 6: Spiral Model SDLC

1. Planning objectives 2. Risk analysis and
or Identify altemet resolving
solutions.

Design

Code
4. Plan the next Phase 3. Develop the next
Test
level of product
Release
Source: Tutorial, S. (n.d.). SDLC Spiral Model. Retrieved July 21, 2019, from
w3schools.in: https://www.w3schools.in/sdlc-tutorial/spiral-model/

Let us now concentrate on our main point of discussion. We intend to
mitigate pitfalls of SDLC in the software development project of BN by
correlation with the Boehm’s software RM framework. It is already seen that
traditional waterfall SDLC is not conducive to RM framework. Almost all the
software developed in BN followed this traditional SDLC. As such the first step
is to adopt the spiral model or many other modern SDLC models where the RM
plans are embedded within. At first instance, it is seen that spiral model costs
time and it is complex in nature comparing to the waterfall model. However, the
experience and observation of BN software development projects reveals that
rather adopting spiral model would reduce the development time and would be
simpler for better understanding by the users. A chunk of problem solution would
be easier to handle with the risk management and resolution than being over
burden with the intention of completing the whole project step by step and with
frequent changes of software requirements. With the frequent and unplanned
change in requirements also results complexities to the overall design and
development. On that note, the proposed spiral SDLC might be beneficial for BN
software development project. However, the next challenge would be to
accommodate RM framework with the SDLC. Practitioners suggest that the
effective utilization of both SDLC and RM techniques require experience of the

124