A Case Study in Incremental Architecture-Based Re-engineering of a Legacy Application

Abi-Antoun, Marwan; Coelho, Wesley

doi:10.1109/wicsa.2005.5

Cited by 6 publications

(9 citation statements)

References 25 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The exact language for method specifications is shown in Figure 1. 1 States for each port. We associate with each port a set of mutually exclusive states.…”

Section: Typestate Protocolsmentioning

confidence: 99%

“…HillClimber demonstrates stochastic local search algorithms for constraint satisfaction problems (CSP). It was reengineered to ArchJava by Abi-Antoun and Coelho [1] and consists of about 16,000 lines of code including 9 main components and over 75 classes. Figure 11 partially describes the architecture of HillClimber showing the components and connections relevant for this case study.…”

Section: Case Study: Hillclimbermentioning

confidence: 99%

“…add m to callers 10. end if 11. end if 12. end for each 13. end for each 14. end for each 15. return callers [1]. Instances of these components and their connections, except for HillNode and HillEdge, are created and initialized in the top-level component Hill.…”

mentioning

confidence: 99%

See 2 more Smart Citations

A Language-based Approach to Specification and Enforcement of Architectural Protocols

Bierhoff¹,

Kehrt²,

Han³

et al. 2010

View full text Add to dashboard Cite

Software architecture research has proposed using protocols for specifying the interactions between components through ports. Enforcing these protocols in an implementation is difficult. This paper proposes an approach to statically reason about protocol conformance of an implementation. It leverages the architectural guarantees of the ArchJava programming language. The approach allows modular reasoning about implementations with callbacks, recursive calls, and multiple instances of component types. It uses a dataflow analysis to check method implementations and a summary-based interprocedural analysis to reason modularly about component composition. The approach is limited to static architectures but can handle multiple instances for component types and arbitrary nesting of components. We tested the implementation on a case study, and the results suggest that the approach can be scaled to large software applications.

show abstract

“…The exact language for method specifications is shown in Figure 1. 1 States for each port. We associate with each port a set of mutually exclusive states.…”

Section: Typestate Protocolsmentioning

confidence: 99%

Section: Case Study: Hillclimbermentioning

confidence: 99%

See 1 more Smart Citation

A Language-based Approach to Specification and Enforcement of Architectural Protocols

Bierhoff¹,

Kehrt²,

Han³

et al. 2010

View full text Add to dashboard Cite

show abstract

“…Some language-based solutions, e.g., ArchJava [6], specify architectural hierarchy and instances directly in code. But ArchJava's breaking extensions restrict how objects are used and require re-engineering an existing Java system [10].…”

Section: Conformance Stagementioning

confidence: 99%

“…Like ArchJava [6], Scholia integrates architectural intent into source code, but instead of extending Java with architectural components and ports, Scholia uses language support for annotations. The evaluation in this paper did not require re-engineering a system to follow ArchJava's rules [10]. In this paper, we only added annotations to the code and typechecked them using a tool.…”

Section: Related Workmentioning

confidence: 99%

Enforcing Conformance between Security Architecture and Implementation

Abi-Antoun¹,

Barnes²

2009

View full text Add to dashboard Cite

Analysis at the level of a runtime architecture matches the way experts reason about security or privacy better than a purely code-based strategy. However, the architecture must still be correctly realized in the implementation.We previously developed Scholia to analyze, at compile time, communication integrity between arbitrary object-oriented code, and a rich, hierarchical intended runtime architecture, using typecheckable annotations. This paper applies Scholia to security runtime architectures. Having established traceability between the target architecture and the code, we extend Scholia to enforce structural architectural constraints. At the code level, annotations enforce local, modular constraints. At the architectural level, predicates enforce global constraints. We validate the end-to-end approach in practice using a real 3,000-line Java implementation, and enforce its conformance to a security architecture designed by an expert.Abi-Antoun was supported in part by DARPA grant #HR00110710019, NSF grant CCF-0546550, and Army Research Office grant #DAAD19-02-1-0389 entitled "Perpetually Available and Secure Information Systems."Barnes was supported in part by the Office of Naval Research (ONR), United States Navy, N000140811223 as part of the HSCB project under OSD, by the US Army Research Office (ARO) under grant numbers DAAD19-02-1-0389 ("Perpetually Available and Secure Information Systems") to Carnegie Mellon University's CyLab and DAAD19-01-1-0485, and by the Software Engineering Institute at CMU. The views and conclusions described here are those of the authors and should not be interpreted as representing the official policies, either expressed or implied, of any funding agency, the US government, or any other entity. Report Documentation PageForm Public reporting burden for the collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington VA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to a penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number.

show abstract

Componentising a Scientific Application for the Grid

Parlavantzas

Getov

Morel

et al.

Achievements in European Research on Grid Systems

View full text Add to dashboard Cite

Building and evolving Grid applications is complex. Component-based development has emerged as an effective approach to building flexible systems, but there is little experience in applying this approach to Grid programming. This paper presents our experience with reengineering a high performance numerical solver to become a component-based Grid application. The adopted component model is an extension of the generic Fractal model that specifically targets grid environments. The paper provides qualitative and quantitative evidence that componentisation has improved the modifiability and reusability of the application while not significantly affecting performance.

show abstract

A Case Study in Incremental Architecture-Based Re-engineering of a Legacy Application

Abstract: Abstract

Cited by 6 publications

References 25 publications

A Language-based Approach to Specification and Enforcement of Architectural Protocols

A Language-based Approach to Specification and Enforcement of Architectural Protocols

Enforcing Conformance between Security Architecture and Implementation

Componentising a Scientific Application for the Grid

Contact Info

Product

Resources

About