Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
A
AF3
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 258
    • Issues 258
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 8
    • Merge Requests 8
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • af3
  • AF3
  • Issues
  • #3509

Closed
Open
Opened Dec 05, 2020 by Dummy AF3-Dev@dummy-af3-dev

rework OCRA refinement

At present the verification using OCRA contracts works as follows:

  1. For the atomic components the property is tested against the behaviour
  2. for the composite components the property is tested for the refinement. The user in this case has to provide the list of refining contracts and the tool tries to prove the property using these contracts

This causes usability issues as the suer needs to define a lot of contracts, and also the contracts at lower levels mimic the behaviour.

For the tutorial and in the future we want to give an option to the user such that contracts at composite components can also be verified against the behaviour.

My approach to this issue is: if no refining contract is specified then verify the specification against the behaviour otherwise use the refinement.

(from redmine: issue id 3509, created on 2018-09-10)

Assignee
Assign to
Backlog
Milestone
Backlog
Assign milestone
Time tracking
None
Due date
None
Reference: af3/af3#3509