Call for paper 〔OPEN〕

My submissions

Registration 〔OPEN〕

My tickets

〔CLOSED〕
Introduction

In software engineering there has traditionally been a distinction between high-level architecting and low-level implementation activities such as coding. Those who are developing and maintain the software are often not engaged in early design phases of the software; junior software programmers tend to lack design thinking and architectural skills. On the other hand, architects are often blamed for not knowing how to write good code or not being engaged in low-level (often technical) challenges of implementing a software system. This causes a knowledge gap which results in software quality issues such as an implementation that is drifted from initial design, missing architectural choices in the code or incorrect implementation of architectural decisions.

 

The continuous shift towards reducing upfront architecture design efforts, and the popularity of practices such as test-first development, highlight the importance of bridging the software implementation practices with new architecting notions, practices and tools. BRIDGE'16 aims to bring the community of architects, developers, and testers together to identify and formulate challenges related to designing, implementing and maintaining the architecture.

Call for paper

Submission Topics

Research, position, and experience papers are invited on any topic that addresses the intersection of architecture and implementation. Examples might include:

  • Tools and techniques for stimulating design thinking into developers coding activities
  • Architecture Prototyping to test and validate quality concerns
  • Architecture refactoring tools and techniques
  • Processes/practices/tools that support co-development of design and implementation
  • Reactive Design vs. Proactive Design
  • Evolutionary Architecting and Design
  • Assessment techniques and metrics for measuring compliance of architecture against code
  • Transforming architectures to source code in model-driven engineering processes
  • Tool-support to the various informational and processing needs (e.g., visualization of interactions among architectural and requirements knowledge)
  • Traceability between requirements, architectural solutions and implementation
  • Industrial studies and empirical studies on architecture prototyping, architecture refactoring, code first design, test driven design
Submit Comment
Verify Code Change Another
All Comments
Important Date
  • Conference Date

    May 14

    2016

    to

    May 15

    2016

  • May 15 2016

    Registration deadline

Contact Information