Page 134 - Navy Journal 219
P. 134

Navy Journal 2019


             correlate the established theory  of risk  mitigation.  The  most successful risk
             management practice to date is ‘Boehm’s six step of risk management
             framework’. Analyzing this software RM technique the inherent risk factors of
             unrealistic scheduling, developing wrong software functions, and developing
             wrong user interface has been correlated with BN software development
             projects. Accordingly, the risk management techniques are discussed to mitigate
             these risk factors.
                  However, throughout this process the most interesting thing found is the
             requirement of awareness build up among the users of BN on software
             development life cycle. Knowledge on the software development process might
             yield considerable  amount of mitigation of  risk factors. Hence, the first and
             foremost thing in this regard is to build understanding among the users and
             practitioners of BN on the process of software development and then gradually
             the technique of RM can be embedded with our own style of software
             development life cycle. Our final goal is to maximize naval strategic and
             operational process by improving the project management technique, which is
             possible only when we understand the value of software development project.

             Bibliography

             1. Barki, H., Rivard, S., & Talbot, J. (1993). Toward and Assessment of Software
             Development Risk. Journal of Management Information Systems , 203-219
             2.  Boehm, B. (1989).  Software Risk Management. ESEC'89: 2nd European
             Software Engineering Conference (pp. 1-19). Coventry, UK: Springer- Verleg

             3. Boehm, B. (1991). Software Risk Management: Principles and Practices. The
             Premier Electronics Industry Conference of the Northwest (pp. 32-40). Portland:
             Northcon/@91
             4. Charette, R. N. (2005). Why Software Fails. NA: IEEE Spectrum

             5. Gantz, J. F., Christiansen, C. A., & Gillen, A. (2006). The Risks of Obtaining
             and Using Pirated Software. IDC White Paper , 1-12
             6. Goertzel, K. M., & Feldman, L. (2009). Software Survivability: Where Safety
             and Security Converge. Seatle:  American Institute of  Aeronautics and
             Astronautics, Inc





                                              126
   129   130   131   132   133   134   135   136   137   138