FFSE 2001

1
FFSE 2001 Workshop Schedule

• --- MORNING ---
• 930 Opening Welcome
• 940 2 long presentations (Kahl, García-Cabrera)
  discussion
• 1100 Coffee break
• 1130 long presentation (Ramil) discussion
• 1230 Lunch
• --- AFTERNOON ---
• 1430 2 short presentations (Aaltonen, Andrade)
  discussion
• 1500 2 short presentations (Heckel, Zhao)
  discussion
• 1530 2 short presentations (Lanza, Wermelinger)
  discussion
• 1600 Coffee break
• 1630 2 short presentations (Mens, Said)
  discussion
• --- WRAP UP ---
• 1700 Additional discussion
• 1730 Conclusion and final remarks

2
Some General Questions

• Which aspects of sofware evolution need to be
  automated by tools?
• Where and how can formalisms help us with this
  support?
• How can we build formal tools that are as general
  and flexible as possible?
• language independent customisable by the user
• independent of life-cycle phase tool
  interoperability
• scalable to large-size software for
  design-time/run-time evolution
• for forward/reverse/re-engineering before/during/a
  fter evolution
• for facilitating/supporting/analysing for
  what/why/how of evolution

3
FFSE 2001 Workshop Schedule

• MORNING
• 930 Opening Welcome
• 940 Long presentations
• Kahl Software evolution via hierarchical
  hypergraphs
• García-Cabrera et al. Evolution of hypermedia
  systems
• Discussion on single versus multiple formalisms
• 1100 Coffee break
• 1130 Long presentation
• Lehman et al. The role of formalisms in studying
  software evolution
• Discussion on how versus what and why of
  software evolution
• 1230 Lunch

4
FFSE 2001 Workshop Schedule

• AFTERNOON
• 1430 Short presentations
• Aaltonen et al. Evolution based on formalised
  abstraction hierarchy
• Andrade et al. Coordination contracts, evolution
  and tools
• Discussion on separation of concerns and
  different rates of change
• 1500 Short presentations
• Heckel et al. Graph transformation as meta
  language for evolution
• Zhao. Change impact analysis for architectural
  evolution
• Discussion on
• layer (architecture, analysis, design,
  implementation)
• provide support before / during / after
  evolution
• time (design-time, run-time) of evolution

5
FFSE 2001 Workshop Schedule

• AFTERNOON (CONTINUED)
• 1530 Short presentations
• Lanza et al. Flexible query engine for
  understanding evolution
• Wermelinger et al. Graph transformation for
  architectural reconfiguration
• Discussion on logic versus algebraic approaches
• 1600 Coffee break
• 1630 Short presentations
• Mens. Transformational software evolution by
  assertions
• Said et al. Transformation of binary relations
  into associations and nested classes
• Discussion on scalability, efficiency,
  automation and usability of tools

6
FFSE 2001 Workshop Schedule

• WRAP UP
• 1700 Additional Discussion
• Quantitative versus qualitative approaches
• Transformational versus declarative approaches
• Uniformity of tools for forward, reverse, and
  re-engineering?
• Types of artifacts that can change (code,
  models, diagrams, hardware, documentation)
• Need for tool support to anticipate / facilitate
  / support / analyse evolution
• 1730 Conclusion and final remarks
• 1930 Dinner?

7
FWO WOGFormal Foundations of Software Evolution

• FUTURE WOG-FUNDED WORKSHOPS
• June 18, 2001 University Eötvös Loránd, Budapest,
  Hungary
• ECOOP workshop on Object-Oriented Architectural
  Evolution
• http//prog.vub.ac.be/OOAE/
• November 26-27, 2001 Katholieke Universiteit
  Leuven, Leuven, Belgium
• First International Working Conference on Network
  Security
• http//www.cs.kuleuven.ac.be/conference/inetsec01/
  
• September ??, 2002 Near Barcelona, Spain
• Two workshops co-located with International
  Conference on Graph Transformation
• Workshop on Software Evolution Through
  Transformations
• Workshop on Graph-Based Tools

8
FWO WOGFormal Foundations of Software Evolution

• WORKSHOP REFUND POLICY
• A maximum of 15.000 BEF (371,84 Euro) can be
  refunded per participant.
• Only transportation and accomodation can be
  refunded.
• CSMR conference registration is NOT refunded.
• Original receipts of expenses should be handed
  over to Tom Mens, together with
• Full participant name
• Affiliation (institution, address, e-mail, phone,
  fax)
• Bank account