2003
DOI: 10.1016/s0065-2458(03)58002-0
|View full text |Cite
|
Sign up to set email alerts
|

Transformation-Oriented Programming: A Development Methodology for High Assurance Software

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1

Citation Types

0
3
0

Year Published

2004
2004
2006
2006

Publication Types

Select...
4
2

Relationship

3
3

Authors

Journals

citations
Cited by 7 publications
(3 citation statements)
references
References 27 publications
0
3
0
Order By: Relevance
“…The closed nature of the SSP's execution environment enables the class loading activities of the SSP to be performed statically, prior to execution. Under these conditions, the functionality of a class loader is well suited to a transformation-oriented implementation [Winter et al 2003]. This section gives an overview of the strategic programming language TL, which we will use to implement an abstract version of the class loader core.…”
Section: An Overview Of Tlmentioning
confidence: 99%
“…The closed nature of the SSP's execution environment enables the class loading activities of the SSP to be performed statically, prior to execution. Under these conditions, the functionality of a class loader is well suited to a transformation-oriented implementation [Winter et al 2003]. This section gives an overview of the strategic programming language TL, which we will use to implement an abstract version of the class loader core.…”
Section: An Overview Of Tlmentioning
confidence: 99%
“…The closed nature of the SSP's execution environment enables the class loading activities of the SSP to be performed statically, prior to execution. Under these conditions, the functionality of a class loader is well suited to a transformationoriented implementation [25]. This section gives an overview of the strategic programming language TL which we will use to implement an abstract version of the class loader core.…”
Section: An Overview Of Tlmentioning
confidence: 99%
“…The manipulation of software artifacts such as specifications and program source code through rewriting is an active area of research [3][5] [7][13] [14][23] [27][24] [30]. Driving this research is the idea that the repeated application of a set of simple rewrite rules can effect a major change in a software artifact.…”
Section: Introductionmentioning
confidence: 99%