Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • E escet
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare
    • Locked Files
  • Issues 87
    • Issues 87
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Eclipse ProjectsEclipse Projects
  • Eclipse ESCET (Supervisory Control Engineering Toolkit)
  • escet
  • Issues
  • #370
Closed
Open
Issue created May 27, 2022 by Dennis Hendriks@ddennisMaintainer

Create configurable and reusable CIF precondition checker

Currently, each application has its own precondition checker, e.g., CifToUppaalPreChecker, CifToSupremicaPreChecker, etc. There is a lot of duplication between them. It may be nice to have a single, configurable and reusable precondition checker, in the cif.common project.

Obviously, different applications/transformations have different preconditions. Therefore, each precondition check should be configurable. We could have an enum with all possible preconditions, and then applications just make a selection from the enum literals and pass that the precondition checker, along with the specification to be checked.

The benefits are:

  • Reduced effort to make new precondition checkers.
  • Consistent precondition violation messages for all applications.
  • Less code duplication and maintenance.
Assignee
Assign to
Time tracking

Copyright © Eclipse Foundation, Inc. All Rights Reserved.     Privacy Policy | Terms of Use | Copyright Agent