Rapidly locating and understanding errors using runtime monitoring of architecture-carrying code
Pages 20 - 25
Abstract
Finding and understanding errors in software that is deployed in the field and tested by beta testers or used in production is a difficult and often time consuming task. If the feedback to the developers is naïvely composed of log messages, stack traces, and informal user feedback, it might not contain enough information to locate the erroneous fragments efficiently. It is thus slowing the dynamics in rapid continuous software engineering scenarios. These errors can more easily be found when the code is explicitly designed to carry architectural specifications by intertwining structure and behavior models with the rest of the code. With architecture-carrying code, (1) the steps leading to single errors can be replayed for understanding and debugging; (2) statistical information about errors can be related to structure elements and behavior branches. In this paper we present our idea of architecture-carrying code and its application for error understanding to support rapid continuous software engineering.
References
[1]
M. Balz. Embedding Model Specifications in Object-Oriented Program Code – A Bottom-Up Approach for Model-Based Software Development. PhD thesis, Univeristy of Duisburg-Essen, 2011.
[2]
A. Brown, J. Conallen, and D. Tropeano. Introduction: Models, Modeling, and Model-Driven Architecture (MDA) Model-Driven Software Development. In S. Beydeda, M. Book, and V. Gruhn, editors, Model-Driven Software Development, chapter 1. Springer, Berlin/Heidelberg, 2005.
[3]
G. Kiczales, J. Lamping, A. Mendhekar, C. Maeda, C. Lopes, J.-M. Loingtier, and J. Irwin. Aspect-oriented programming. In ECOOP. SpringerVerlag, 1997.
[4]
M. Konersmann and M. Goedicke. A Conceptual Framework and Experimental Workbench for Architectures. In M. Heisel, editor, Software Service and Application Engineering, volume 7365 of Lecture Notes in Computer Science, pages 36–52. Springer Berlin Heidelberg, 2012.
[5]
M. P. Luz and A. R. da Silva. Executing UML Models. In 3rd Workshop in Software Model Engineering (WiSME 2004), 2004.
[6]
U. A. Nickel, J. Niere, J. P. Wadsack, and A. Zündorf. Roundtrip Engineering with FUJABA. In Proc of 2nd Workshop on Software-Reengineering (WSR), Bad Honnef, Germany, 2000.
[7]
B. Shneiderman. The Eyes Have It: A Task by Data Type Taxonomy for Information Visualizations. In Proceedings of the 1996 IEEE Symposium on Visual Languages, pages 336–343, Sep 1996.
[8]
S. Sicard, F. Boyer, and N. De Palma. Using components for architecture-based management: The self-repair case. In Proceedings of the 30th International Conference on Software Engineering, ICSE ’08, pages 101–110, New York, NY, USA, 2008. ACM.
[9]
A. van Hoorn, J. Waller, and W. Hasselbring. Kieker: A framework for application performance monitoring and dynamic software analysis. In Proceedings of the 3rd joint ACM/SPEC International Conference on Performance Engineering (ICPE 2012), pages 247–248. ACM, April 2012.
Index Terms
- Rapidly locating and understanding errors using runtime monitoring of architecture-carrying code
Recommendations
Understanding and Detecting Harmful Code
SBES '20: Proceedings of the XXXIV Brazilian Symposium on Software EngineeringCode smells typically indicate poor design implementation and choices that may degrade software quality. Hence, they need to be carefully detected to avoid such poor design. In this context, some studies try to understand the impact of code smells on the ...
Understanding code snippets in code reviews: a preliminary study of the OpenStack community
ICPC '22: Proceedings of the 30th IEEE/ACM International Conference on Program ComprehensionCode review is a mature practice for software quality assurance in software development with which reviewers check the code that has been committed by developers, and verify the quality of code. During the code review discussions, reviewers and ...
Code-carrying theory
SAC '08: Proceedings of the 2008 ACM symposium on Applied computingCode-Carrying Theory (CCT) is an alternative to the Proof-Carrying Code (PCC) approach to secure delivery of code. With PCC, code is accompanied by assertions and a proof of correctness or of other required properties. The code consumer does not accept ...
Comments
Information & Contributors
Information
Published In
June 2014
62 pages
ISBN:9781450328562
DOI:10.1145/2593812
- Program Chairs:
- Matthias Tichy,
- Jan Bosch,
- Michael Goedicke,
- Magnus Larsson
Copyright � 2014 Owner/Author.
Permission to make digital or hard copies of part or all of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for third-party components of this work must be honored. For all other uses, contact the Owner/Author.
Sponsors
In-Cooperation
- TCSE: IEEE Computer Society's Tech. Council on Software Engin.
Publisher
Association for Computing Machinery
New York, NY, United States
Publication History
Published: 03 June 2014
Check for updates
Author Tags
Qualifiers
- Article
Conference
ICSE '14
Sponsor:
Upcoming Conference
Contributors
Other Metrics
Bibliometrics & Citations
Bibliometrics
Article Metrics
- 0Total Citations
- 102Total Downloads
- Downloads (Last 12 months)3
- Downloads (Last 6 weeks)0
Reflects downloads up to 15 Oct 2024
Other Metrics
Citations
View Options
Get Access
Login options
Check if you have access through your login credentials or your institution to get full access on this article.
Sign in