Specification development for autonomous system behavior

Abstract

Before we can verify a system, we need a specification to verify it against. But defining a specification for an autonomous behavior is a challenging problem. In addition to simply describing what the system needs to do, we need to ensure that when non-experts specify desired behavior, they provide enough information to the designer without imposing a significant unnecessary cost or complexity burden on the developer. Combining a capability representation with a capability analysis table enables the definition of a boundary between the specification and the design.