A pattern-based approach to generate code from API usage scenarios

Authors:
Johannes Koskinen;Anna Ruokonen;Tarja Systä
Affiliations:
Institute of Software Systems, Tampere University of Technology, Tampere, Finland;Institute of Software Systems, Tampere University of Technology, Tampere, Finland;Institute of Software Systems, Tampere University of Technology, Tampere, Finland
Venue:
Nordic Journal of Computing - Selected papers of the fourth nordic workshop on UML and software modelling (NWUML'06), June 12-14, 2006
Year:
2006

Citing 8
Cited 1

A cookbook for using the model-view controller user interface paradigm in Smalltalk-80

Journal of Object-Oriented Programming
Building application frameworks: object-oriented foundations of framework design

Building application frameworks: object-oriented foundations of framework design
Design and use of software architectures: adopting and evolving a product-line approach

Design and use of software architectures: adopting and evolving a product-line approach
Towards agent-oriented assistance for framework instantiation

OOPSLA '00 Proceedings of the 15th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Design of Rules for Transforming UML Sequence Diagrams into Java code

APSEC '02 Proceedings of the Ninth Asia-Pacific Software Engineering Conference
SmartBooks: A Step Beyond Active-Cookbooks to Aid in Framework Instantiation

TOOLS '99 Proceedings of the Technology of Object-Oriented Languages and Systems
Profile-Based Approach to Support Comprehension of Software Behavior

ICPC '06 Proceedings of the 14th IEEE International Conference on Program Comprehension
Run-time monitoring of architecturally significant behaviors using behavioral profiles and aspects

Proceedings of the 2006 international symposium on Software testing and analysis

Behavioral profiles—a way to model and validate program behavior

Software—Practice & Experience

Quantified Score

Hi-index	0.01

Visualization

Abstract

The usage of an API of a software system requires learning and knowledge about the API itself. In tutorials, an API usage is typically described by giving a couple of example applications and some example code fragments. While such examples are useful and illustrative for the application developer, it is often difficult for her to separate application-specific parts from the API-specific ones, and further to distinguish optional and mandatory parts. In this paper we discuss an approach and tool support for guiding the application developer in API usage in a step-by-step fashion. As the examples are often sequential by their nature, we use UML sequence diagrams to describe possible API usage scenarios. We propose pattern-based tool support to exploit such sequence diagrams and to generate the application code in a semi-automated way.