ACM Home Page
Please provide us with feedback. Feedback
Using Eclipse to demonstrate positive static assurance of Java program concurrency design intent
Full text PdfPdf (376 KB)
Source OOPSLA workshop on eclipse technology eXchange archive
Proceedings of the 2003 OOPSLA workshop on eclipse technology eXchange table of contents
Anaheim, California
Pages: 99 - 103  
Year of Publication: 2003
Authors
Aaron Greenhouse  Carnegie Mellon University, Pittsburgh, PA
T. J. Halloran  Carnegie Mellon University, Pittsburgh, PA
William L. Scherlis  Carnegie Mellon University, Pittsburgh, PA
Sponsors
IBM : IBM
SIGPLAN: ACM Special Interest Group on Programming Languages
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 2,   Downloads (12 Months): 15,   Citation Count: 1
Additional Information:

abstract   references   cited by   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/965660.965681
What is a DOI?

ABSTRACT

Assuring and evolving concurrent programs requires understanding the concurrency-related design decisions used in their implementation. Source code often does not reveal these design decisions because they may not have purely local manifestations in the code, or because they cannot be inferred from code. As a result, this design intent is usually not expressed, and it is therefore generally infeasible to assure that concurrent programs are free of race conditions.We describe a prototype Eclipse-based tool developed as part of research toward a practicable approach to capturing and assuring design intent. Through the use of annotations and composable static analyses we can help assure consistency of code and intent as both evolve. The dominant design consideration for the tool is the principle of "early gratification"---some assurance can be obtained with minimal or no annotation effort, and additional increments of annotation or other effort are rewarded with additional increments of assurance.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

1
 
2
3
4
 
5
 
6
7

Collaborative Colleagues:
Aaron Greenhouse: colleagues
T. J. Halloran: colleagues
William L. Scherlis: colleagues