1 / 4

Navigating Design Issues for ESC/Java: A Trial-and-Error Approach

This document discusses critical design issues for the ESC/Java tool, focusing on aspects like private variables in specifications, modifies clauses, interface specifications, and vector-bounds checking. It highlights an iterative design process where navigation through design space should be guided by trial-and-error and field feedback. The emphasis is on building adaptable tools rather than fixating on the specifics of the first iteration. Recommendations include anticipating changes, understanding Java syntax, and limiting the time spent on annotation design to facilitate effective user engagement.

ronat
Télécharger la présentation

Navigating Design Issues for ESC/Java: A Trial-and-Error Approach

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ESCJ 15:Design issues for ESC/JavaApril 2nd, 1997 • Private variables in spec’s? • Modifies clauses? • Specifications for interfaces? • Vector-bounds checking? • Monitor invariants? • Module-initialization checking? • Abstract state?

  2. Iterative design process • Claim: We should navigate this design space by trial-and-error, getting feedback from the field. • Implication: We should be less concerned with the particulars of the first version of the tool and very concerned that what we build can be easily modified

  3. Look at design-space breadth first • Identify what’s likely to be stable • Java syntax • Translation to guarded commands [?] • Anticipate what’s likely to change • Desugaring of specifications • “Additional” annotations (e.g., invariants, LL)

  4. Implications for user manual • Limit time spent designing annotations • Don’t use as primary basis for building checker

More Related