Today, RE conference in Karlskrona is starting with a great set of excellent workshops and tutorials. For me and my research, the RE is the most important conference. Therefore, I am extremely happy to present two pieces of recent work: A research paper on Openness and Requirements: Opportunities and Tradeoffs in Software Ecosystems, where we investigated how professionals in product teams of the IBM CLM Ecosystem are affected by the complexity of software ecosystems in their daily work. And a poster on EAM: Ecosystemability Assessment Method, where report on developing a framework that allows organizations to setup their development environment and architecture in a way that optimally supports the vision of a software ecosystem. In this post, I share pre-prints of both papers.
Openness and Requirements: Opportunities and Tradeoffs in Software Ecosystems
Eric Knauss, Daniela Damian, Alessia Knauss, and Arber Borici. In Proceedings of 22nd International Requirements Engineering Conference (RE ’14), pg. 213-222, Karlskrona, Sweden, 2014.
Abstract: A growing number of software systems is characterized by continuous evolution as well as by significant interdependence with other systems (e.g. services, apps). Such software ecosystems promise increased innovation power and support for consumer oriented software services at scale, and are characterized by a certain openness of their information flows. While such openness supports project and reputation management, it also brings some challenges to Requirements Engineering (RE) within the ecosystem. We report from a mixed-method study of IBM’s CLM ecosystem that uses an open commercial development model. We analyzed data from interviews within several ecosystem actors, participatory observation, and software repositories, to describe the flow of product requirements information through the ecosystem, how the open communication paradigm in software ecosystems provides opportunities for ’just-in-time’ RE, as well as some of the challenges faced when traditional requirements engineering approaches are applied within such an ecosystem. More importantly, we discuss two tradeoffs brought about the openness in software ecosystems: i) allowing open, transparent communication while keeping intellectual property confidential within the ecosystem, and ii) having the ability to act globally on a long-term strategy while empowering product teams to act locally to answer end-users’ context specific needs in a timely manner.
Keywords: requirements engineering; software ecosystem; mixed method
Presentation: Thursday, 28th of August, 13:30, JBuilding, Ground floor
EAM: Ecosystemability Assessment Method
Eric Knauss and Imed Hammouda. In Proceedings of 22nd International Requirements Engineering Conference (RE ’14), pg. 319-320, Karlskrona, Sweden, 2014.
Abstract: In this extended abstract, we present the ecosystemability assessment method as a means to assess the extent to which a software system, represented by its architecture and its development environment, supports the vision of ecosystem.
Keywords: software ecosystem, architecture
Presentation: Wednesday, 27th of August, 15:30 (Lightning Talks): J1610 and Thursday, 28th of August, 15:30 (Poster Session), JBuilding, Ground floor