Enhancing Object-Oriented Programming Comprehension Using Optimized Sequence Diagram

Srinivasan, Madhusudan; Lee, Young; Yang, Jeong

doi:10.1109/cseet.2016.37

Cited by 3 publications

(2 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The goal of model extraction methods is to create a model of a software design based on code or execution traces. In general, models can be extracted statically from source code and/or dynamically from execution traces [25], e.g., sequence diagrams [29], state machines [28], or software architecture from code [8]. Model extraction approaches do not aim to propagate changes to the code, but they are used for model-based analysis and communication.…”

Section: Related Workmentioning

confidence: 99%

Same but Different: Consistently Developing and Evolving Software Architecture Models and Their Implementation

Konersmann

Goedicke

2020

Ernst Denert Award for Software Engineering 2019

View full text Add to dashboard Cite

As software architecture is a main driver for the software quality, source code is often accompanied by software architecture specifications. When the implementation is changed, the architecture specification is often not updated along with the code, which introduces inconsistencies between these artifacts. Such inconsistencies imply a risk of misunderstandings and errors during the development, maintenance, and evolution, causing serious degradation over the lifetime of the system. In this chapter we present the Explicitly Integrated Architecture approach and its tool Codeling, which remove the necessity for a separate representation of software architecture by integrating software architecture information with the program code. By using our approach, the specification can be extracted from the source code and changes in the specification can be propagated to the code. The integration of architecture information with the code leaves no room for inconsistencies between the artifacts and creates links between artifacts. We evaluate the approach and tool in a use case with real software in development and with a benchmark software, accompanied by a performance evaluation.

show abstract

Section: Related Workmentioning

confidence: 99%

Same but Different: Consistently Developing and Evolving Software Architecture Models and Their Implementation

Konersmann

Goedicke

2020

Ernst Denert Award for Software Engineering 2019

View full text Add to dashboard Cite

show abstract

“…A step-by-step log of commands executed by a program is called a program trace (or just a trace or tracing). The importance of the traces has been frequently mentioned earlier to both developing program code (Abualese et al, 2017;Fittkau et al, 2015;Feng et al, 2018;Kashima et al, 2015;Kadar et al, 2016;Khoury et al, 2017;Khoury et al, 2019;Perez & Abreu, 2016) and programming education (Aggarwal et al, 2018;Paaßen et al, 2016;Srinivasan et al, 2016;Terada, 2005).…”

Section: Introductionmentioning

confidence: 99%