Monday, June 20, 2011
- W1: 1st International Workshop on Variability in Software Architecture - [full day]
- W2: Architecting Cloud Computing Applications and Systems - [afternoon]
Friday, June 24, 2011
- W3: Architecture-Based Testing and System Validation Workshop - [full day]
- W4: Standards for (software) Architecture: An Assessment - [full day]
PAPER SUBMISSION (All Workshops follow the same format)
All workshops welcome a) future trend papers, describing ongoing research, new results, and future trends (up to 4 pages), b) research papers describing innovative and significant original research in the field (up to 8 pages), and c) industrial papers describing industrial experience, case studies, challenges, problems and solutions (up to 8 pages). Submissions must follow the IEEE conference proceedings format.
IMPORTANT DATES (These dates apply to all workshops)
Submission deadline: March 25, 2011
Notification of acceptance: April 18, 2011
Camera-ready due: April 22, 2011
June 20 2011, Boulder, Colorado, USA - In Conjunction with WICSA 2011
Variability is the ability of a software artifact to be changed for a specific context. Variability is primarily reflected in and facilitated through the software architecture. Also, the software architecture is the centerpiece of software systems and acts as reference point for many development activities, and many of today's software systems are built to accommodate variability. Thus, variability in software architecture should be well-understood and be treated as a first-class concern. The software architecture community acknowledges that variability is a concern of different stakeholders, and in turn affects other concerns.
Nevertheless, treating variability related to the architecture and all architecture aspects, as a cross-cutting concern, is currently not well understood. Therefore, VARSA 2011 aims at identifying critical challenges and progressing the state-of-the-art on variability in software architecture by exploring current and emerging methods, languages, notations, technologies and tools to model, implement, and manage variability at the software architecture level. We are particularly interested in industrial practice and experience. The goal of this edition of VARSA is to bring together researchers and practitioners interested in
- variability as it occurs in software architectures (types of variability, evolution of variability, etc.), particularly in relation to quality attributes (e.g., performance, security),
- implications of variability on emerging architecture paradigms (e.g., service-oriented architecture, self-adaptive systems, REST, cloud architectures, software ecosystems), and
- how variability can be facilitated in architecture descriptions (e.g., the use of architecture viewpoints and views to manage variability in architectures).
Topics of the workshop include but are not limited to:
- Methods, techniques, tools, notations, languages to handle variability in software architecture.
- Modeling variability in different architecture model types (e.g., information models or development models), rather than annotating component-and-connector models or feature models.
- Types of variability in software architecture.
- Architecture viewpoints and views to manage variability.
- Reference architectures for variability-intensive systems.
- Evaluation, resolution and evolution of variability in software architecture.
- Variability in emerging architecture paradigms (e.g., dynamic construction of applications, variability in large scale systems, SOA, cloud architectures, REST, software ecosystems).
- Variability to support runtime adaptation and in self-adaptive systems.
- Variability and quality attributes.
- Variability in software architecture as a cross-cutting concern beyond software product lines and product line architectures.
- Traceability between enterprise architecture and software architecture.
- Architecture patterns, styles and tactics for variability.
- Experience reports and best practices from industry, empirical studies.
Matthias Galster, University of Groningen, Netherlands
Paris Avgeriou, University of Groningen, Netherlands
Danny Weyns, Katholieke Universiteit Leuven, Belgium
Tomi Mannisto, Aalto University, Finland
- Top -
June 20, 2011, Boulder, Colorado, USA. In Conjunction with WICSA 2011
Cloud Computing is a often discussed topic in the ICT industry right now. Organisations large and small, in anticipation of the promise of 'reduced capital expenditure', 'perceived infinite scalability' and 'reduced IT cost and complexity' are busily evaluating cloud computing, and in some cases adopting cloud computing to supplement their existing enterprise IT portfolio.
This workshop on 'Architecting Cloud Computing Applications' aims to provide a forum for both software architecture researchers and practitioners to share ideas, research outputs, evaluation results, proof of concept experiences, and production systems lessons learnt around cloud computing, we particularly encourage the discussions of cloud computing from the 'consumer' viewpoint, that is, from the large enterprise (including Government) perspective, issues and concerns related to the adoption of cloud computing.
We solicit paper submissions in the following topics:
- software architecture to cross the boundary of local server, private cloud and across public clouds
- relationship between enterprise and software architecture views of cloud computing
- architecting cloud applications to achieve software qualities (including performance, high availability, high elasticity)
- cloud computing architecture styles, patterns and viewpoints
- architecture description language and model driven architecture for cloud computing
- application monitoring and management across local data centres and public clouds
- business process management and workflow across cloud platforms
- designing data architectures for cloud computing
- relationship between service oriented architecture approaches to cloud computing analysis and design
- enterprise architecture issues related to cloud computing
- integrating existing/legacy systems with cloud applications
- cost benefit and risk analysis and management of cloud computing
- migrating to cloud computing
- roles and responsibilities of software architects in the cloud computing ecosystem
- Industrial experiences and case studies on architecting cloud based systems
June 24, 2011, Boulder, Colorado, USA. In Conjunction with WICSA 2011
Architecture-based testing and system validation involves the use of architecture to involve better outcomes to the process of assuring that a delivered system satisfies its requirements. "Better outcomes" can mean shorter validation time, higher confidence results, or less expensive testing (for example, by using architectural analysis to eliminate the need for certain tests). This workshop aims to bring together researchers and practitioners to produce an emerging picture of the state of the practice in architecture-based testing and system validation, promising research approaches, and practical problems that could be solved by directed research.
Important topics include using architecture to produce test artifacts, using analysis of architecture to make certain tests unnecessary, Fault models associated with particular architecture styles or patterns, Architectural design approaches that make systems more testable, Testing implementations for conformance to architecture, Using architectural arguments to shorten the testing for a new version of a fielded system, Using architecture to for predictive analysis about a system, Architectural viewpoints for testing, and Model-based testing of/with architecture
Bedir Tekinerdogan (contact), Bilkent University, Turkey
Paul Clements, SEI, Software Engineering Institute, USA
Michel Chaudron, Leiden University, The Netherlands
Eoin Woods, Artechra, UK
Henry Muccini, University of L'Aquila, Italy
Andrea Polini, University of Camerino, Italy
- Top -
June 24 2011, Boulder, Colorado, USA. In Conjunction with WICSA 2011
IEEE 1471 was first approved in 2000, while informal standards such as Kruchten’s “4+1 Views” and approaches such as RM ODP predate IEEE 1471. Other frameworks address system and/or enterprise concerns, such as GERAM and ISO 15704, Zachman Framework, the Dod Architecture Framework and related frameworks such as MODAF and TOGAF. ISO is finishing a revision of ISO/IEC 42010:2007 (the ISO adoption of IEEE Std 1471-2000). Thus the last decade provides a rich set of standards to consider.
The language and concepts of IEEE 1471 have since become embedded in a wide range of practices, although not always retaining their original form. The influence of 1471 has been considerable, if not always obvious.
This workshop looks at both our experience with architecture standards and where standardization should proceed in the future. Relevant topics include:
- Theoretical and Practical aspects of using ANSI/IEEE 1471
- Relevance/Effectiveness/Experience with specific architecture standards
- Connections between software architecture standards and other standards (e.g ISO/IEC 12207 and ISO/IEC 15288, the system and software life-cycle standards)
- Connections within the existing de-jure/de-facto standards (e.g. relationship between IEEE 1471 and TOGAF or DODAF)
Mark Maier, Aerospace Corporation, USA
David Emery, DSCI, USA
- Top -