Software Incident Report Capture and Scripting

ComplexĀNavalĀcontrolĀsystemsĀgoĀthroughĀnumerousĀroundsĀofĀrigorousĀtestingĀoftenĀspanningĀmultipleĀyears.ĀAsĀtesters executeĀformalizedĀassessments during these test events,Āissues arise, and the issues are documented in software problem reports (SPRs). Multiple factors may limit the ability of a tester to properly document issues for future replication or investigation, such as the rapid pace and sensitivity at which the tests are performed. When the issue gets assigned to adeveloper,ĀsignificantĀdataĀrequiredĀtoĀrepeatĀorĀcategorizeĀtheĀissueĀmayĀnotĀbeĀavailableĀdueĀtoĀlackĀofĀdocumentation oramplifyingĀinformation.ĀSituationsĀlikeĀtheseĀleadĀtoĀaĀsignificantĀnumberĀofĀproblemĀreportsĀgoingĀunresolvedĀand delivered in the deployed product.ĀAltronĀisĀproposingĀtoĀconductĀresearchĀandĀdevelopmentĀ(R&D)ĀtoĀdetermineĀtheĀtechnicalĀfeasibilityĀofĀcreatingĀaĀnovel technologythatĀwillĀperformĀdataĀaggregationĀandĀdataĀanalyticsĀtoĀcorrelateĀsystemĀinputs,ĀsystemĀlogsĀandĀmetadataĀto supportĀSPR capture.As the data types fed into this correlation algorithm increase, an ontology will be created that categorizesĀandĀdetailsĀtheĀbugs. TheseĀcapturedĀdetailsĀwillĀhelpĀunburdenĀtestersĀfromĀhavingĀtoĀinvestigateĀmanyĀbugs themselves. Instead, they can create a SPR with the details this technology provides and continue with their test plan. With this comprehensiveĀdatasetĀcapturedĀbyĀthe technology,ĀdevelopersĀwillĀhaveĀreliableĀrecreationĀandĀamplifyingĀinformationĀat theirĀdisposalĀtoĀdiagnoseĀissues.