Theme-based literate programming

Kacofegitis, A.; Churcher, Neville

doi:10.1109/apsec.2002.1183079

Cited by 5 publications

(3 citation statements)

References 26 publications

(47 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In literate programming, use cases would be represented by chunks of code that would be then woven into the rest of the code. Derivative of literate programming is theme-based literate programming [20], which enhances LP with themes. Themes allow to integrate text into chunks enabling to maintain links between use cases and code similar to our approach.…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Preserving use case flows in source code: Approach, context, and challenges

Bystrický

Vranić

2017

COMSIS J

View full text Add to dashboard Cite

Being able to see use case steps directly in code would make the intent expressed by the code more comprehensible and easier to maintain. In this paper, an approach to preserving use case flows (of events) in source code called InFlow is presented within a broader context of its application in the software development process along with the issues that remain as challenges. The approach preserves individual steps of use case flows in the form of their counterpart statements, as well as their ordering. This is achieved by mimicking each use case flow by a sequence of method implementations with each step of the use case flow corresponding to one statement in one of these methods, enabled by the annotation named InFlow. A study of implementing an audio streaming service using InFlow, DCI, and aspect-oriented software development with use cases has been performed and assessed using several metrics in order to determine the level of preserving use case flows in source code. Although InFlow introduces a lot of indirect references to code, the overall results speak in favor of InFlow. DCI adds more complexity to following a use case flow in code than other two approaches. Complexity of making a change to a use case flow ended up with closely matching results. But InFlow guarantees traceability of use case implementation from the domain model implementation.

show abstract

Section: Related Workmentioning

confidence: 99%

“…Code comprehension can be improved with documentation or formally written tests, but connections between the executed code and these have to be maintained [20]. Notable are behavioral tests, which describe scenarios from the perspective of users.…”

Section: Introductionmentioning

confidence: 99%

Preserving use case flows in source code: Approach, context, and challenges

Bystrický

Vranić

2017

COMSIS J

View full text Add to dashboard Cite

show abstract

“…The Desert environment built by Steve Reiss and his students at Brown [14,15]-focussing as it does on programming rather than other aspects of the life-cycle, and on presenting all the views in a single tool-approaches our ideal more closely, although Desert still treats programs as text objects that are stored in files. Theme-based literate programming [7] is based on a similar ideal. Our focus on treating a program as a higher-level abstraction, of which any given view is just that-a view-draws on several additional sources, which we now describe.…”

Section: Introductionmentioning

confidence: 99%

The case for multiple views

Black¹,

Jones

2004

"Workshop on Directions in Software Engineering Environments (WoDiSEE2004)" W2S Workshop - 26th International Conference on Sof

View full text Add to dashboard Cite

We argue that viewing a program as a linear sequence of symbols on paper or on a display is outmoded and unnecessarily restrictive. Instead, programs should be regarded as complex multi-dimensional artifacts on which linear text provides but one possible view. Freeing ourselves from these restrictions is very difficult: it requires not only a modest amount of new technology, but also a qualitative change in the way that programmers think. However, the potential benefits are enormous. Multiple views make it easier to understand complex programs, and provide a unifying framework for many common program transformations. In addition, Multiple views provide a solution for language designers trying to choose between competing alternatives: provide the advantages of both, but in different views.

show abstract

Software Knowledge Capture and Acquisition: Tool Support for Agile Settings

Correia¹,

Aguiar

2009

2009 Fourth International Conference on Software Engineering Advances

View full text Add to dashboard Cite

Theme-based literate programming

Cited by 5 publications

References 26 publications

Preserving use case flows in source code: Approach, context, and challenges

Preserving use case flows in source code: Approach, context, and challenges

The case for multiple views

Software Knowledge Capture and Acquisition: Tool Support for Agile Settings

Contact Info

Product

Resources

About