Data Flow Analysis in Software Reliability

Fosdick, Lloyd D.; Osterweil, Leon J.

doi:10.1145/356674.356676

Cited by 218 publications

(55 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Fosdick and Osterweil [13] were the first to suggest applying program analysis techniques to address the challenges of software reliability. Their Dave system used data flow analysis to detect "data flow anomalies" that are symptomatic of programming errors.…”

Section: Historical Contextmentioning

confidence: 99%

Checking Concurrent Typestate with Access Permissions in Plural: A Retrospective

Bierhoff

Beckman²,

Aldrich³

2011

Engineering of Software

View full text Add to dashboard Cite

Objects often define usage protocols that clients must follow in order for these objects to work properly. In the presence of aliasing, however, it is difficult to check whether all the aliases of an object properly coordinate to enforce the protocol. Plural is a type-based system that can soundly enforce challenging protocols even in concurrent programs. In this paper, we discuss how Plural supports natural idioms for reasoning about programs, leveraging access permissions that express the programmer's design intent within the code. We trace the predecessors of the design intent idioms used in Plural, discuss how we have found different forms of design intent to be complimentary, and outline remaining challenges and directions for future work in the area.

show abstract

Section: Historical Contextmentioning

confidence: 99%

Checking Concurrent Typestate with Access Permissions in Plural: A Retrospective

Bierhoff

Beckman²,

Aldrich³

2011

Engineering of Software

View full text Add to dashboard Cite

show abstract

“…Initial work on data flow analysis was conducted by Fosdick and Osterweil. They defined a data flow anomaly as "a sequence of the events reference (r), definition (d), and undefinition (u) of variables in a program that is either erroneous in itself or often symptomatic of an error" [Fosd76a]. A software developer is required to specify all desirable and required sequences of events, the program is then analyzed to detect violations, which may arise from omitted and superfluous code errors.…”

Section: Techniques For Static Analysis Of Sequential Programsmentioning

confidence: 99%

SDS (Strategic Defense System) Software Testing and Evaluation: a Review of the State-of-the-Art in Software Testing and Evaluation with Recommended R&D Tasks

Youngblut¹,

Brykczynski²,

Salasin³

et al. 1989

View full text Add to dashboard Cite

896 19 037 IDA Memorandum M-496 is a related document which provides a comprehensive, annotated bibliography of the reference material acquired in the course of this work. IDA Memorandum M-513, another related document, is a collection of the papers provided by leading experts in testing and evaluation tech-* nology preparatory to an IDA workshop held in support of this work.The authors gratefully acknoledge the support given by all those who participated in the workshop and reviewed this paper. The insights and experience these people so willingly shared has been invaluable. In particular, special thanks go to the following people: IntroductionTesting and uvaluation are recognized as pivotal problems in the development of the Strategic Defense System (SDS). Consequently, a development approach combining design, prototyping, and simulation is being used to allow early evaluation of system requirements and designs. Loosely-coupled, decentralized system architectures are being examined for their facility to reduce the testing problem to a manageable level. But what testing and evaluation technology shall be used to ensure the reliability of, and provide the necessary level of confidence in, SDS software? The purpose of this report is to address this question. *For the past decade, software testing and evaluation have been relatively unpopular subjects. Why this happened is less important than its consequences. It has been a contributing factor to the lag between the state-of-the-art and state-of-the-practice, which is the largest of any in the diverse areas of software engineering, and has resulted in a shortage of research and development (R&D) resources and a small, weak research community. Since SDS prototype software is already being developed, software testing and evaluation are now critical concerns. The Strategic Defense Initiative Organization (SDIO) cannot * wait for testing and evaluation issues to pop up later in the development process (a traditional approach which has proven costly in the past), but must meet the challenge up front.Once the importance of this challenge is recognized, appropriate actions can be taken. There is a substantial body of testing and evaluation technology whose use in an industrial environment is ready to be investigated, preparatory to transitioning the technology into practice. The main body of this report * describes the current status of different areas of this technology. It also outlines a number of tasks for bringing promising elements of the technology into practice. While the use of advanced technology will certainly help, it is by no means sufficient to resolve all testing and evaluation problems. In particular, technology for the testing and evaluation of large, distributed and real-time software systems is still in its infancy. The final part of this report, therefore, recommends a number of tasks to extend the boundaries of technology to meet SDS needs.Testing and evaluation technology is not, by itself, enough to ensure improved practices. Policy must evolve ...

show abstract

“…C++), and then reasonable approaches to static analysis develop, e.g. dataflow analysis of software [28].…”

Section: Introductionmentioning

confidence: 99%

Formalizing the structural semantics of domain-specific modeling languages

Jackson

Sztipanovits

2008

Softw Syst Model

View full text Add to dashboard Cite

Abstract-Model-based approaches to system design are now widespread and successful. These approaches make extensive use of model structure to describe systems using domain-specific abstractions, to specify and implement model transformations, and to analyze structural properties of models. In spite of its general importance the structural semantics of modeling languages are not well-understood. In this paper we develop the formal foundations for the structural semantics of domain specific modeling languages (DSML), including the mechanisms by which metamodels specify the structural semantics of DSMLs. Additionally, we show how our formalization can complement existing tools, and how it yields algorithms for the analysis of DSMLs and model transformations.

show abstract

Data Flow Analysis in Software Reliability

Cited by 218 publications

References 16 publications

Checking Concurrent Typestate with Access Permissions in Plural: A Retrospective

Checking Concurrent Typestate with Access Permissions in Plural: A Retrospective

SDS (Strategic Defense System) Software Testing and Evaluation: a Review of the State-of-the-Art in Software Testing and Evaluation with Recommended R&D Tasks

Formalizing the structural semantics of domain-specific modeling languages

Contact Info

Product

Resources

About