Sharing Developers' Mental Models through Source Code Annotations

Sulír, Matúš; Nosal, Milan

doi:10.15439/2015f301

Cited by 10 publications

(12 citation statements)

References 20 publications

(22 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…First, a list of features in the application was drawn from the results of our previous experiment [12]. Among other activities, seven participants were asked to create one annotation type for each concern (i.e., a feature or other intention behind pieces of code) they recognized in the application.…”

Section: Methodsmentioning

confidence: 99%

See 1 more Smart Citation

Exposing Runtime Information through Source Code Annotations

SulĂr¹,

Porubãn²

2017

AEI

View full text Add to dashboard Cite

Many tools support exploration and analysis of various run-time properties of programs. However, the results produced by these tools are often discarded or stored in custom external files. We discuss an approach where data obtained when executing the program are written as Java annotations over program elements. First, the viability of this approach is demonstrated by a feature annotator, which assigns features to corresponding methods. Second, we describe other types of run-time information that we consider suitable for inclusion in the source code. We also suggest two possible workflows how generated annotations can be used in the development process.

show abstract

Section: Methodsmentioning

confidence: 99%

“…Concern annotations [12,14] are annotations acting as hints for developers, informing them about intentions behind a code element. Originally, they were intended to be inserted manually into the source code, preferably by programmers writing the code.…”

Section: Annotationsmentioning

confidence: 99%

Exposing Runtime Information through Source Code Annotations

SulĂr¹,

Porubãn²

2017

AEI

View full text Add to dashboard Cite

show abstract

“…PAL executes annotated methods in parallel and uses the meta information from its annotations to efficiently tailor the parallelized code for the distributed platform that it runs on. 49 Moreover, Thomas proposes an interactive annotation tool for Eclipse IDEs that help with identifying security vulnerabilities in early development stages. 21 Joy et al propose a technique that automatically injects annotations into code segments based on their estimated execution time.…”

Section: Projects Utilizing Java Annotationsmentioning

confidence: 99%

“…The research proposes annotations that specify what aspect(s) a system component is involved in (eg, @Encoding, @Persistence). 49 Moreover, Thomas proposes an interactive annotation tool for Eclipse IDEs that help with identifying security vulnerabilities in early development stages. Developers use the proposed annotations to supply the deployment team with information about the security vulnerabilities of their software components.…”

Section: Projects Utilizing Java Annotationsmentioning

confidence: 99%

@PT: Unobtrusive parallel programming with Java annotations

Mehrabi

Giacaman

Sinnen

2018

Concurrency and Computation

View full text Add to dashboard Cite

Parallel computing techniques have been supported by programming languages in two major ways: either library-based APIs or extended language constructs. Library-based features are portable and offer fine-grained control on parallelization details. However, they rely on individual programmer skills; thus, they may lead to inconsistent implementations and considerable code restructurings. On the contrary, language constructs promote environments that largely conceal the details of parallel programming techniques. However, they normally reduce programmer control over the granularity of parallelization and impose additional development concepts and compilation requirements that may sacrifice ease of use and portability. Therefore, approaches that balance between programmer control on parallelization details, intuitiveness of concepts, and portability can gain priority over other paradigms. In this paper, we discuss @PT (Annotation Parallel Task), a parallel computing framework that proposes Java annotations, standard Java components, as its language constructs. @PT takes an object-oriented approach on efficient execution and management of asynchronous tasks, with a special focus on GUI-responsive applications.This paper presents the annotation-based programming interface of the framework and its fundamental parallelization concepts. Furthermore, it studies the usability and performance of @PT by comparisons with other Java parallelization approaches in a set of standard benchmarks. The observations suggest that @PT maintains a simple programming interface, whereas it performs efficiently in different parallel computing domains. INTRODUCTIONThe proliferation of multi-core systems has encouraged support for parallel computing in shared-memory systems. The support is often offered in the form of libraries (eg, TPL and PLINQ in C# 1 ) or language constructs (eg, OpenMP 2 ). The majority of library-based approaches provide APIs that cover a wide range of fine-grained functions that can be combined to form flexible and efficient implementations for different parallel computing domains. Assembling and combining these functions for building a working system remains the responsibility of individual programmers. Here, the quality of software design depends on the programming approaches that are practiced by individuals. Reliance on the technical abilities and coding styles of individuals leads to inconsistent implementation and performance standards, some of which can be inefficient and complex to modify.In order to overcome the risks mentioned above, approaches such as Microsoft, PPL, 3 Java Streams, 4 SKePU, 5 and FastFlow 6 offer library APIs that implement frequent parallel processing patterns. Examples of these patterns are: map, reduce, farm, pipeline, asynchronous tasks, and so on. 5The pre-built components of these APIs improve consistency and efficiency across different implementations. In addition, these patterns can be composed to form bigger parallel applications. However, one needs to know what pattern to choose f...

show abstract

“…Different structuring of code provides different views on software. Although dynamic structuring has been reported [16], [21], it was not achieved at the file system level, but using a particular editor. Our approach provides use case and test views, which are synchronized at the file system level and can be used simultaneously.…”

Section: E Experience With the Approachmentioning

confidence: 99%

Use Case Driven Modularization as a Basis for Test Driven Modularization

Bystrický¹,

Vranić²

2017

Proceedings of the 2017 Federated Conference on Computer Science and Information Systems

View full text Add to dashboard Cite

Abstract-While in waterfall-like processes changes are expected to happen mostly after the main development has finished, agile approaches have incorporated response to changes into the main development itself, which raises the importance of the ability to respond to changes effectively to a sine qua non. Changes are specified from the perspective of how users actually use systems, i.e., usage scenarios, which does not correspond to a common object-oriented code modularization. In their complete form, usage scenarios can be directly observed in user acceptance tests. Unit tests reveal parts of usage scenarios, too. Logically, tests follow the modularization of the code they are related to. Thus, in common object-oriented code, user acceptance tests, which play a very important role in any kind of software development process and which follow the procedural modularization, would be scattered and, consequently, hard to maintain. In this paper, we propose a new approach capable of achieving test driven modularization, i.e., organizing code according to tests. Besides pure test driven modularization, which can be based on user acceptance tests, unit tests, or both, the approach also enables combining use case and test driven modularization.

show abstract

Sharing Developers' Mental Models through Source Code Annotations

Cited by 10 publications

References 20 publications

Exposing Runtime Information through Source Code Annotations

Exposing Runtime Information through Source Code Annotations

@PT: Unobtrusive parallel programming with Java annotations

Use Case Driven Modularization as a Basis for Test Driven Modularization

Contact Info

Product

Resources

About