(Enter summary)
Abstract: Our thesis is very simple: elevating system development
from the module to the architecture level requires a
corresponding elevation in our tools for instrumenting,
monitoring, and debugging systems. While we have a long
history and mature technology for the former, we have just
begun to recreate these capabilities at the software
architecture level.
This paper describes two architecture level tools that utilize
architecture level instrumentation to monitor software
architectures through... (Update)
Context of citations to this paper: More
.... generated from the software architectural description, or there is an easily identifiable one to one architecture to implementation mapping [1][10] 16] we need to describe how those (primitive) events are related to higher level (composed) events. Many monitoring systems...
Cited by: More
The Role of Event Description in Architecting Dependable Systems - Dias, al. (2002)
(Correct)
Active bibliography (related documents): More All
0.2: The Software Architecture Renaissance - Paul Kogut
(Correct)
0.2: Architectural Design of Component Composition Using First Class.. - Sünbül (2000)
(Correct)
0.2: Design Connectors in Component Based Software Systems - Sünbül
(Correct)
Similar documents based on text: More All
0.1: Unknown - This Appendix Explains
(Correct)
0.1: Preprints FEAST Workshop III - February March Department
(Correct)
0.1: FEAST Workshop - June Department Of (1994)
(Correct)
BibTeX entry: (Update)
R. Balzer, "Instrumenting, Monitoring, & Debugging Software Architectures", 1997. http://citeseer.ist.psu.edu/balzer97instrumenting.html More
@misc{ balzer97instrumenting,
author = "R. Balzer",
title = "Instrumenting, Monitoring, & Debugging Software Architectures",
text = "R. Balzer, Instrumenting, Monitoring, & Debugging Software Architectures,
1997.",
year = "1997",
url = "citeseer.ist.psu.edu/balzer97instrumenting.html" }
Citations (may not include all citations):
265
Program Slicing (context) - Weiser - 1981
244
Abstractions for Software Architecture and Tools to Support ..
- Shaw, DeLine et al.
193
Specification and Analysis of System Architecture Using Rapi..
- Specification, System et al. - 1995
140
Using Program Slicing in Software Maintenance
- Gallagher, Lyle - 1991
135
Integrating Non-Interfering Versions of Programs (context) - Horwitz, Prins et al. - 1989
121
A Formal Approach to Software Architectures
- Allen, Garlan - 1992
110
Exploiting Style in Architectural Design Environments
- Garlan, Allen et al. - 1994
68
Operational Profiles in Software Reliability Engineering (context) - Musa - 1993
67
The Inscape Environment
- Perry - 1989
52
Program and Interface Slicing for Reverse Engineering (context) - Beck, Eichmann - 1993
52
Software Interconnection Models
- Perry - 1987
50
Debugging with Dynamic Slicing and Backtracking
- Agrawal, DeMillo et al. - 1993
42
An Introduction to Software Architecture (context) - Garlan, Shaw
38
Dynamic Slicing of Computer Programs (context) - Korel, Laski - 1990
34
Procedure Calls are the Assembly Language of Software Interc..
- Shaw - 1995
8
ACME: An Architectural Interchange Language (context) - Garlan, Monroe et al.
5
Software Architecture: Integrating Process and Technology (context) - Royce, Royce - 1991
1
Larry Augustin and Frank Belz (context) - of, Sets et al. - 1993
Documents on the same site (http://www.cs.wpi.edu/~cs562/s98/references.html): More
A Component- and Message-Based Architectural Style.. - Taylor.. (1996)
(Correct)
ACME: An Architecture Description Interchange Language - Garlan, Monroe, Wile (1997)
(Correct)
A Formal Basis for Architectural Connection - Allen, Garlan (1997)
(Correct)
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC