Kapture® Overview
Kapture® helps a user develop requirements that can be verified. In doing so, the requirements have all the attributes typically looked for in software requirements standards. They are atomic, clear, concise, unambiguous and self-sufficient. With the additional healthiness checks, they are also self-consistent thus avoiding issues such as conflicting requirements. These assured attributes assist a developer in a number of ways:
• Because they are clear and concise, they are easily communicated to software designers, test case or other verification process developers as well as to certifiers
• Verification is much more straightforward because the requirements are verifiable
• Errors that would typically be made in requirements development are avoided thus saving significant cost which would have been incurred when errors were found later in the development life cycle
• Changes to requirements can be quickly incorporated and checked
Developed to be used in conjunction with the D-RisQ's Modelworks® tool as part of a formal methods based automatic verification process, Kapture® can be used as a powerful stand-alone tool providing software requirements which can still be verified by traditional (costly) manual review and test methods.
Kapture® in the work flow
Requirements can be written directly into Kapture® and configuration managed by the creation and saving of the file version or the exporting to a configuration management tool. Tracing to system requirements can be included if desired. Using Kapture® requirements, the design process can then begin. Kapture® therefore can be used in any life cycle process, traditional, agile, etc. Tracing information to the design can be inserted if required. Similarly, test cases can be developed and appropriate tracing can be included. The user may also wish to designate individual requirements as being safety or security related and can tag them with how they are to be verified; there is a specific tag for D-RisQ Modelworks® if this intended to be used.
Kapture® and Certification
As a by-product of writing in Kapture®, some certification credit under various software standards may be claimed. If using DO-178C, the Formal Methods Supplement DO-333 will apply if using a formal development process because Kapture® provides formal semantics to the requirements.
Data Dictionary
In Kapture®, modes (or states) and signals can be defined in the Data Dictionary which can be used in writing requirements.
Modes and signals can be referred to in definitions and requirements. Such cross-references are shown as underlined text. If a signal or mode’s name is altered, all existing cross references are adjusted to use the new name. A cross-reference can be jumped to by using the menu options that are shown when right-clicking on an expression,
DISCOVER MOREDefinitions...
Definitions in Kapture® allow you to give a unique textual description for an expression to help make other definitions or requirements easier to read and maintain.
Once a definition has been created, it can be cross-referenced by referring to a definition identifier in an expression. Cross references are shown by underlining text, and can be jumped to using the menu selection shown when right clicking on an expression.
DISCOVER MOREUser defined functions...
Function definitions in Kapture® allow the creation of user-defined functions that satisfy the following constraints:
1. Functions cannot contain references to user-defined definitions, though can reference other functions subject to the next constraint.
2. Functions cannot be recursive or mutually recursive. Thus, a user-defined function cannot contain a call to itself either directly or indirectly through a call to another function.
Note the first of these constraints might be relaxed in a future version of the Kapture® tool.
Once a function definition has been created it can be used as a user-defined operator within an expression.
DISCOVER MORE1. Functions cannot contain references to user-defined definitions, though can reference other functions subject to the next constraint.
2. Functions cannot be recursive or mutually recursive. Thus, a user-defined function cannot contain a call to itself either directly or indirectly through a call to another function.
Note the first of these constraints might be relaxed in a future version of the Kapture tool.
Once a function definition has been created it can be used as a user-defined operator within an expression.
Assumptions...
Assumptions are completely informal descriptions of any contextual information about the environment in which a system is to operate. Kapture® does not make any use of assumptions other than to allow this information to be recorded
1. Functions cannot contain references to user-defined definitions, though can reference other functions subject to the next constraint.
Templates...
All of the templates in Kapture® can be viewed from the Template Viewer tab
Modes and signals can be referred to in definitions and requirements. Such cross-references are shown as underlined text. If a signal or mode’s name is altered, all existing cross references are adjusted to use the new name. A cross-reference can be jumped to by using the menu options that are shown when right-clicking on an expression,
DISCOVER MOREExport
Kapture® provides the opportunity to export a Kapture® project to different formats:
· CSV - ideal for automated processing
• HTML spreadsheet - ideal for viewing within spreadsheet application such as Microsoft® Excel®
· HTML - ideal for viewing as a document
· XML - ideal for automated processing
· ModelWorks - format required for D-RisQ’s ModelWorks tool for checking whether a Math Work’s Simulink / Stateflow model implements the requirements.
Kapture® can either export the entire project to the chosen format or a filtered selection of records.
