Using obstacle analysis to identify contingency requirements on an unpiloted aerial vehicle

Lutz, Robyn R.; Patterson-Hine, Ann; Nelson, Stacy; Frost, Chad; Tal, Doron; Harris, Robert N.

doi:10.1007/s00766-006-0039-4

Cited by 30 publications

(17 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In order to discover features for a future air space management software system, exploratory creativity was followed during the analysis of requirements and emergent system properties [122]. Lutz and colleagues [115] presented an approach that performed KAOS Obstacle Analysis to explore requirements in a space defined by obstacles for a safety-critical, autonomous system. Salinesi et al [167] proposed a prototype tool that performed requirements-based product configurations within constraints.…”

Section: On the Way To Creative Requirementsmentioning

confidence: 99%

Stakeholders' social interaction in requirements engineering of open source software

Bhowmik

2014

2014 IEEE 22nd International Requirements Engineering Conference (RE)

View full text Add to dashboard Cite

In this work, we use the phrase "stakeholders' social interaction" to indicate interaction among stakeholders regarding the software system that takes place through some communication means, such as posting comments and artifacts over the issue tracking system.We investigate the influence of stakeholders' social interaction in different RE activities, in particular, requirements identification, creativity in RE, and requirements implementation of OSS systems. This research enables us to gain valuable insights to generate guidelines for enhancing software engineering practice in relevant areas.

show abstract

Section: On the Way To Creative Requirementsmentioning

confidence: 99%

Stakeholders' social interaction in requirements engineering of open source software

Bhowmik

2014

2014 IEEE 22nd International Requirements Engineering Conference (RE)

View full text Add to dashboard Cite

show abstract

“…SFTA is a top-down, backward search technique that has been used successfully to find the possible software-related causes of a hazard or failure, e.g., on spacecraft [19]. SFTA has also been used to identify obstacles (such as false assumptions or unreliable behavior) to achieving the high-level goals (requirements) on an Unpiloted Aerial Vehicle [20]. The work [21] uses, in a synergistic manner, Fault Tree Analysis, Failure Mode and Effect Analysis (FMEA) and UML state-charts to derive, structure and integrate safety requirements of controlling software.…”

Section: Related Workmentioning

confidence: 99%

“…There are several systematic ways to discover misuse cases, although no technique can assure completeness. Successful techniques include guideword-based inquiries for each use case [13], scenario-based searches [26], checklist-based investigations of historically troublesome features [30], automated contingency analysis [20], and use of completeness criteria [31]. Depending on the domain, multiple techniques have been used in combination.…”

Section: A Proposal For Eliciting Randarmentioning

confidence: 99%

Reliability and Availability Requirements Engineering within the Unified Process Using a Dependability Analysis and Modeling Profile

Bernardi

Merseguer

Lutz

2010

2010 European Dependable Computing Conference

View full text Add to dashboard Cite

Abstract-In this paper, we propose an integration of the Unified Process and a Dependability Analysis and Modeling (DAM) profile to support quantifiable, testable reliability and availability requirements (R&AR) elicitation and completeness analysis. Specifically, we are interested in improved identification and specification of R&AR and their associated assumptions. This is accomplished through an iterative workflow that is consistent with the Unified Process and attaches DAM stereotypes to use and misuse cases. Fault-tree analysis helps determine and mitigate combinations of faults that could impede R&AR achievement. The workflow steps are demonstrated and evaluated on an intrusion protection service for critical infrastructures.

show abstract

“…Contingency handling defines requirements for detecting, identifying, and responding to anomalous events. A process for contingency analysis during design has been developed 29 and is being implemented in the ADAPT domain. The approach involves two steps: (1) to integrate in a single model the representation of the contingencies and of the data signals and software monitors required to identify those contingencies and (2) to use tool-supported verification of the diagnostics design to identify gaps in coverage of the contingencies.…”

Section: B Contingency Analysismentioning

confidence: 99%

Evaluation, Selection, and Application of Model-Based Diagnosis Tools and Approaches

Poll

Patterson-Hine

Camisa

et al. 2007

AIAA Infotech@Aerospace 2007 Conference and Exhibit

Self Cite

View full text Add to dashboard Cite

Model-based approaches have proven fruitful in the design and implementation of intelligent systems that provide automated diagnostic functions. A wide variety of models are used in these approaches to represent the particular domain knowledge, including analytic state-based models, input-output transfer function models, fault propagation models, and qualitative and quantitative physics-based models. Diagnostic applications are built around three main steps: observation, comparison, and diagnosis. If the modeling begins in the early stages of system development, engineering models such as fault propagation models can be used for testability analysis to aid definition and evaluation of instrumentation suites for observation of system behavior. Analytical models can be used in the design of monitoring algorithms that process observations to provide information for the second step in the process, comparison of expected behavior of the system to actual measured behavior. In the final diagnostic step, reasoning about the results of the comparison can be performed in a variety of ways, such as dependency matrices, graph propagation, constraint propagation, and state estimation. Realistic empirical evaluation and comparison of these approaches is often hampered by a lack of standard data sets and suitable testbeds. In this paper we describe the Advanced Diagnostics and Prognostics Testbed (ADAPT) at NASA Ames Research Center. The purpose of the testbed is to measure, evaluate, and mature diagnostic and prognostic health management technologies. This paper describes the testbed's hardware, software architecture, and concept of operations. A simulation testbed that

show abstract

Using obstacle analysis to identify contingency requirements on an unpiloted aerial vehicle

Cited by 30 publications

References 15 publications

Stakeholders' social interaction in requirements engineering of open source software

Stakeholders' social interaction in requirements engineering of open source software

Reliability and Availability Requirements Engineering within the Unified Process Using a Dependability Analysis and Modeling Profile

Evaluation, Selection, and Application of Model-Based Diagnosis Tools and Approaches

Contact Info

Product

Resources

About