WICSA 2005:Reverse Engineering and Software Architecture

From WICSA Conference Wiki

Jump to: navigation, search

What is the relationship between software architecture and reverse engineering? Why are we meeting together? What is there to talk about while we are all here in Pittsburgh? Here are some thoughts on the subject that I wrote in my WCRE General Chair's message for its proceedings book:

Media:WCRE 2005 Gen Chair message.pdf

What should the key points of discussion be between these two communities?

  • Integration of Architecting process (forward) with Reverse Architecting Process (RK)
  • Traceability between the architecture artefacts and code artefacts (RK)
  • Really integrate Architecture Artefacts in (Software) Configuration Management to improve traceability and save evolution (RK)
  • (and here)

Comment on Traceability between the Architecture Artefacts and Code Artefacts

Getting practical support (read efficient integrated tools) for establishing traceability and checking for consistency is an important topic to me as a practitioner. Evolving software and maintaining the software very much pivots around ensuring that the implementation does not violate the architecture eventhough the code is done off-shore or the architects keep changing. To paraphrase Boochs keynote, our tribal memory is not sufficient for us.

Retrieved from "http://wwwp.dnsalias.org/wiki/WICSA_2005:Reverse_Engineering_and_Software_Architecture"
Personal tools