Continuous clarification and emergent requirements flows in open-commercial software ecosystems.
Saved in:
| Title: | Continuous clarification and emergent requirements flows in open-commercial software ecosystems. |
|---|---|
| Authors: | Knauss, Eric1 eric.knauss@cse.gu.se, Yussuf, Aminah2 aminah.yussuf@gmail.com, Blincoe, Kelly2 kelly.blincoe@gmail.com, Damian, Daniela2 danielad@cs.uvic.ca, Knauss, Alessia2 alessiaknauss@gmail.com |
| Source: | Requirements Engineering. Mar2018, Vol. 23 Issue 1, p97-117. 21p. |
| Subjects: | Software ecosystems, Software engineering, New product development, Stakeholders, Innovation adoption |
| Abstract: | Software engineering practice has shifted from the development of products in closed environments toward more open and collaborative efforts. Software development has become significantly interdependent with other systems (e.g. services, apps) and typically takes place within large ecosystems of networked communities of stakeholder organizations. 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 requirements engineering-related challenges within the ecosystem, such as managing dynamic, emergent contributions from the ecosystem stakeholders, as well as collecting their input while protecting their IP. In this paper, we report from a study of requirements communication and management practices within IBM®’s Collaborative Lifecycle Management® product development ecosystem. Our research used multiple methods for data collection, including interviews within several ecosystem actors, on-site participatory observation, and analysis of online project repositories. We chart and 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—and which relies on emergent contributions from the ecosystem stakeholders—, 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 by the openness in software ecosystems: (1) allowing open, transparent communication while keeping intellectual property confidential within the ecosystem and (2) 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. A sufficient level of openness facilitates contributions of emergent stakeholders. The ability to include important emergent contributors early in requirements elicitation appears to be a crucial asset in software ecosystems. [ABSTRACT FROM AUTHOR] |
| Copyright of Requirements Engineering is the property of Springer Nature and its content may not be copied or emailed to multiple sites without the copyright holder's express written permission. Additionally, content may not be used with any artificial intelligence tools or machine learning technologies. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.) | |
| Database: | Engineering Source |
|
Full text is not displayed to guests.
Login for full access.
|
|
| FullText | Links: – Type: pdflink Text: Availability: 1 |
|---|---|
| Header | DbId: egs DbLabel: Engineering Source An: 128053727 AccessLevel: 6 PubType: Academic Journal PubTypeId: academicJournal PreciseRelevancyScore: 0 |
| IllustrationInfo | |
| Items | – Name: Title Label: Title Group: Ti Data: Continuous clarification and emergent requirements flows in open-commercial software ecosystems. – Name: Author Label: Authors Group: Au Data: <searchLink fieldCode="AR" term="%22Knauss%2C+Eric%22">Knauss, Eric</searchLink><relatesTo>1</relatesTo><i> eric.knauss@cse.gu.se</i><br /><searchLink fieldCode="AR" term="%22Yussuf%2C+Aminah%22">Yussuf, Aminah</searchLink><relatesTo>2</relatesTo><i> aminah.yussuf@gmail.com</i><br /><searchLink fieldCode="AR" term="%22Blincoe%2C+Kelly%22">Blincoe, Kelly</searchLink><relatesTo>2</relatesTo><i> kelly.blincoe@gmail.com</i><br /><searchLink fieldCode="AR" term="%22Damian%2C+Daniela%22">Damian, Daniela</searchLink><relatesTo>2</relatesTo><i> danielad@cs.uvic.ca</i><br /><searchLink fieldCode="AR" term="%22Knauss%2C+Alessia%22">Knauss, Alessia</searchLink><relatesTo>2</relatesTo><i> alessiaknauss@gmail.com</i> – Name: TitleSource Label: Source Group: Src Data: <searchLink fieldCode="JN" term="%22Requirements+Engineering%22">Requirements Engineering</searchLink>. Mar2018, Vol. 23 Issue 1, p97-117. 21p. – Name: Subject Label: Subjects Group: Su Data: <searchLink fieldCode="DE" term="%22Software+ecosystems%22">Software ecosystems</searchLink><br /><searchLink fieldCode="DE" term="%22Software+engineering%22">Software engineering</searchLink><br /><searchLink fieldCode="DE" term="%22New+product+development%22">New product development</searchLink><br /><searchLink fieldCode="DE" term="%22Stakeholders%22">Stakeholders</searchLink><br /><searchLink fieldCode="DE" term="%22Innovation+adoption%22">Innovation adoption</searchLink> – Name: Abstract Label: Abstract Group: Ab Data: Software engineering practice has shifted from the development of products in closed environments toward more open and collaborative efforts. Software development has become significantly interdependent with other systems (e.g. services, apps) and typically takes place within large ecosystems of networked communities of stakeholder organizations. 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 requirements engineering-related challenges within the ecosystem, such as managing dynamic, emergent contributions from the ecosystem stakeholders, as well as collecting their input while protecting their IP. In this paper, we report from a study of requirements communication and management practices within IBM®’s Collaborative Lifecycle Management® product development ecosystem. Our research used multiple methods for data collection, including interviews within several ecosystem actors, on-site participatory observation, and analysis of online project repositories. We chart and 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—and which relies on emergent contributions from the ecosystem stakeholders—, 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 by the openness in software ecosystems: (1) allowing open, transparent communication while keeping intellectual property confidential within the ecosystem and (2) 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. A sufficient level of openness facilitates contributions of emergent stakeholders. The ability to include important emergent contributors early in requirements elicitation appears to be a crucial asset in software ecosystems. [ABSTRACT FROM AUTHOR] – Name: AbstractSuppliedCopyright Label: Group: Ab Data: <i>Copyright of Requirements Engineering is the property of Springer Nature and its content may not be copied or emailed to multiple sites without the copyright holder's express written permission. Additionally, content may not be used with any artificial intelligence tools or machine learning technologies. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract.</i> (Copyright applies to all Abstracts.) |
| PLink | https://search.ebscohost.com/login.aspx?direct=true&site=eds-live&db=egs&AN=128053727 |
| RecordInfo | BibRecord: BibEntity: Identifiers: – Type: doi Value: 10.1007/s00766-016-0259-1 Languages: – Code: eng Text: English PhysicalDescription: Pagination: PageCount: 21 StartPage: 97 Subjects: – SubjectFull: Software ecosystems Type: general – SubjectFull: Software engineering Type: general – SubjectFull: New product development Type: general – SubjectFull: Stakeholders Type: general – SubjectFull: Innovation adoption Type: general Titles: – TitleFull: Continuous clarification and emergent requirements flows in open-commercial software ecosystems. Type: main BibRelationships: HasContributorRelationships: – PersonEntity: Name: NameFull: Knauss, Eric – PersonEntity: Name: NameFull: Yussuf, Aminah – PersonEntity: Name: NameFull: Blincoe, Kelly – PersonEntity: Name: NameFull: Damian, Daniela – PersonEntity: Name: NameFull: Knauss, Alessia IsPartOfRelationships: – BibEntity: Dates: – D: 01 M: 03 Text: Mar2018 Type: published Y: 2018 Identifiers: – Type: issn-print Value: 09473602 Numbering: – Type: volume Value: 23 – Type: issue Value: 1 Titles: – TitleFull: Requirements Engineering Type: main |
| ResultId | 1 |
