Page 130 - Navy Journal 219

Navy Journal 2019

has more significance than others. Almost all of the completed software projects
in BN has suffered the unrealistic schedule and could not make the deadline. To
prevent this, software requirements are to be scrubbed, developing a prototype
with piloting and then incremental development technique may be adopted.
From observation, it is also identified that software projects in BN are vulnerable
to develop wrong software function. Finally, software projects of BN are very
much vulnerable to wrong user interface as the users wish is given priority over
the development complexities.
Figure 5. Software Risk Items
A Top Ten List of Software Risk Items
RISK ITEM RISK MANAGEMENT TECHNIQUES

1. Personnel shortfalls -Staffing with top talent; job matching;
teambuilding; morale building; cross-training;
prescheduling key people
2. Unrealistic schedules -Detailed multisource cost & schedule
and budgets estimation; design to cost; incremental
development; software reuse; requirements
scrubbing
3. Developing the wrong -Organization analysis; mission analysis;
software functions ops-concept formulation; user surveys;
prototyping; early users’ manuals
4. Developing the wrong -Prototyping; scenarios; task analysis
user interfacting
5. Gold plating -Requirements scrubbing; prototyping;
cost-benefit analysis; design to cost
6. Continuing streams of -High change threshold; information hiding;
requirements changes incremental development (defer changes to
later increments)

7. Shortfalls in externally -Benchmarking; inspections; reference
furnished components checking; compatibility analysis
8. Shortfalls in externally -Reference checking; pre-award adults;
performed tasks award-fee contacts; competitive design or
prototyping; teambuilding
9. Real-time performance -Simulation; benchmarking; modeling;
shortfalls prototyping; intrumentation; tuning
10. Staining computer Tecnical snslysis; cost-benifit analysis;
science capabilities prototyping; reference checking
Source: Boehm, B. (1989). Software Risk Management. ESEC 89: 2nd European
Software Engineering Conference (pp. 1-19). Coventry, UK: Springer- Verleg.

122