Write a Blog >>
ECSA 2020
Mon 14 - Fri 18 September 2020 L'Aquila, Italy

The Industry Track at ECSA 2020 will bring together practicing architects and software architecture researchers from local, European, and worldwide communities. We are seeking experience reports from industry that share challenges, successful practices, failures, and other lessons learned while analyzing, designing, implementing, evaluating, and evolving architectures.

Call For Papers

The Industry Track at ECSA 2020 will bring together practicing architects and software architecture researchers from local, European, and worldwide communities. We are seeking experience reports from industry that share challenges, successful practices, failures, and other lessons learned while analyzing, designing, implementing, evaluating, and evolving architectures.

In particular, we are interested in the following themes and topics:

  • Architectures for emerging technologies. Positive and negative experiences with modern concepts, technologies and platforms – including, but not limited to:
    • Artificial intelligence and machine learning
    • Big data and blockchain
    • Internet of Things (IoT) and advanced cyber-physical/embedded systems
    • Microservices and reactive systems
    • Social networks and online games
    • Software-defined infrastructure (infrastructure as code)
  • Domain-specific challenges for architects and architectures:
    • Challenges in a particular industry or business sector, for instance: what makes it hard (and interesting) to be an architect in this domain?
    • Changing quality attribute priorities and overcoming cultural legacy when transitioning from non-software products and services to digital ones: for instance, technology or business model disruption (market dynamics), impact of/on regulation (or lack thereof), legacy system migration issues
    • The interplay between software architecture and enterprise architecture, for example conflicts between the value propositions and business models of a company and its organizational structure in business and IT
  • Architectural patterns, principles, and technologies supporting stakeholders in development, integration and system administration:
    • Architecting/implementing Domain-Driven Design (DDD), architecturally evident coding styles
    • API design and management; (micro-)service identification, specification, and realization; service meshes and gateways
    • Event sourcing and streaming; messaging and integration with Apache Kafka, GraphQL, gRPC, MQTT and RESTful HTTP and other protocols
    • DevOps: CI/CD, automation/provisioning languages such as Terraform, Chef, Puppet; cyber security
    • Hosting options/deployment paradigms such as serverless computing, (function-as-a-service), cloud service and deployment models, edge and fog computing; associated technologies e.g. Docker, Kubernetes
  • Cross-cutting methods and practices:
    • Agile architecting
    • Architectural governance on enterprise and all other levels: corporate, business, solution/product/service
    • Software architecture as a service for risk and project managers (e.g., design for auditability, compliance by design)
    • Data and architecture: data provenance/governance, dealing with General Data Protection Regulation (GDPR) compliance, consent management
    • Dealing with technical debt, tactics and strategies for surviving the past and moving to the future (legacy management and modernization
  • Notations for architecture specification and documentation:
    • Agile modeling and sketching
    • Domain-Specific Languages (DSLs) for software architects and Architecture Description Languages (ADLs)
    • DSLs and ADLs supporting container management and DevOps practices
    • Containers as components/architectural elements
    • Ad hoc design specifications vs. after-the-fact documentation
  • Social and organizational aspects:
    • KPIs and incentive structures for making architectures work
    • Ethics as a set of architecturally significant requirements and design concerns: for example: awareness and prioritization challenges, codes of conduct, impact on architectural practices and tools
    • “Self management as an ITA”: priorities, threats, tactics
    • Career planning for software architects: competences and skill profiles, continued education (staying current), certification programs
    • Soft skills: trainings, coaching, and mentoring

The ECSA 2020 Industry Track will help to bridge the gap between academia and industrial practice by establishing an open communication and discussion environment. It will offer researchers and practitioners the opportunity to interact with fellow professionals and develop new ideas and skills for addressing industrial problems, research proposals, or collaboration opportunities.

There are several ways to contribute:

  • Presentations: Presentations in the Industry Track are focused on practices and experiences related to software architecture from industry. Submissions are in the form of extended abstracts that summarize the content of the presentation. A presenter bio should be included.
  • Tutorials: Tutorials in the Industry Track are focused on software architecture best practices, architectures for emerging technologies, or any other software architecture industry topic of interest. Submission should include motivation, description, and presenter bio(s). In addition to the proposal, at least three representative sample slides from the tutorial should be submitted.
  • Full Papers: Full papers submitted to the Industry Track describe lessons learned, best practices from enterprise-scale industry projects and significant experiences gained from deploying or trialing a particular method, approach, or tool related to any topic of software architecture.

We discourage submissions that are mainly product or company marketing because they do not foster the open communication and discussion environment of the ECSA Industry Track.

Submissions

Contributions are to be submitted electronically (PDF) to Easy Chair. Please indicate “ECSA 2020 Industrial Track” in the category field. All contributions must be original, not published, accepted or submitted for publication elsewhere. Submissions will undergo a rigorous peer review process. They will be reviewed by three members of the Industry Track Program Committee. Submissions will be selected based on potential for originality, quality, discussion, soundness, and practical relevance.

Proceedings

Accepted papers full papers will be published in the main Springer LNCS volume of the conference. Presentations and tutorials will be published in the Springer Communications in Computer and Information Science (CCIS). The page limit for full papers is 16 pages in Springer LNCS style; the page limit for presentations and tutorials is eight pages in Springer CCIS Style. Based on the originality, quality, and relevance of their submission, the authors of full papers rejected to the Industry may be invited to contribute to the ECSA 2020 Poster track.

The best accepted papers and presentations will be invited to submit for the Insights column in IEEE Software.

Important Dates

Full papers:

  • Submissions due: May 18, 2020
  • Notification of acceptance: June 22, 2020
  • Camera ready versions due: July 6, 2020

Presentations and Tutorials:

  • Submissions due: June 24, 2020
  • Notification of acceptance: July 13, 2020
  • Camera ready versions due: July 20, 2020

Note: All deadlines are 23:59h AoE (anywhere on Earth)