The OSS movement, which originated from a pragmatic need to share code among individuals, has grown to become a major force behind inter-organizational reuse of platforms, components and code. The use of open source software to build single or family of systems (i.e., product line development) appears to be a profitable way to quality software products. On the other hand, because of the diverse use of open source software, product line development is an attractive way of working in open source communities. The configuration mechanisms used in open source communities may be applicable within software product lines variability management. In addition, product line organizations are usually involved in distributed development, which works very efficiently within open source communities, leading to high quality products. However, at present, there is limited interaction between the open source and product line development communities.

There are several questions related to the quality and architectural aspects of the of open source software that need to be answered. The aim for the workshop is to explore what different communities (i.e., software architecture, software quality, software product lines, and open source software) whose work is closely related can learn from each other and to develop a better understanding of how these communities can benefit from each other.  The workshop deals with the following issues:

  1. The challenges of quality assurance of open source components
  2. The architectural approaches used in open source components and their support for seamless integration of open source components in new systems and product lines.
  3. The strengths and limitations of quality assurance and quality assessment approaches being used for selecting open source components
  4. How to improve architecture and quality information exchange between open source communities and OS component users?
  5. Community: Ownership, control and management of product line assets in an open source community
  6. Visibility of the code: when it is valuable to share proprietary code and how to take the right decision.
  7. Architecture Views: Creation of different levels of architecture visibility: proprietary, among closed consortium, public.
  8. Model driven and service oriented approaches is open source communities
  9. The role of (open) standards in the integration of open source software in product lines
  10. Product line requirements, roadmaps and planning in open source development
  11. Variability management: Using the open source community to evolve components and being explicit about variability
  12. Variability representation, management and tooling in an open source community
  13. Deployment: Open source for the platform and in applications
  14. Heterogeneous processes: Cohabitation of product line management and agile processes
  15. Tools: Open source asset management tools in product line development
  16. The meaning of domain and application engineering in an open source context
  17. Recovery and recognition of a product line in an open source asset base
  18. Architectural measures for dealing with heterogeneous license requirements on software assets
  19. Legal: Aspects dealing with evolutionary, variability or distribution of development relating to legal risks involving: liability, warranties, patent infringements etc.
RSS icon
View a printer-friendly version of this page
Page last updated: 09/03/2009