Strategic Scenario-Based Valuation of Product Line Roadmaps

Wesselius, Jacco

doi:10.1007/978-3-540-33253-4_2

Cited by 9 publications

(2 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Requirements must be allocated into releases using requirement prioritization and valuation methods that enable the most crucial requirements to be implemented and released first 42, 43. The methods are typically based on trade‐off analysis between the economic values and implementation costs and resource constraints associated with the requirements 42, p. 140 and 22, 44. Moreover, all stakeholders do not have the same relative importance and each stakeholder may valuate each requirement very differently 43, 45, 46.…”

Section: Meta‐requirements Of the Is Design Product Theory For Thementioning

confidence: 99%

See 1 more Smart Citation

An information systems design product theory for the class of integrated requirements and release management systems

Käkölä

Koivulahti-Ojala

Liimatainen³

2010

J. Softw. Maint. Evol.: Res. Pract.

View full text Add to dashboard Cite

High‐tech companies conducting product development need to collect and analyze requirements effectively, plan and implement releases, and allocate requirements to appropriate releases. Requirements and release management are complicated because development activities typically are scattered across multiple sites, involve multiple partners in different countries, leverage various development methods and tools, and are realized through various organizational arrangements such as release projects in organizations structured around products and permanent release teams in organizations responsible for the long‐term development and maintenance of strategic software and hardware assets. Flexible, scalable, and secure groupware‐based support for the activities provides substantial payoffs. Yet, the extant literature provides little theoretical guidance for designing and using requirements and release management systems (RRMS) in multi‐site, multi‐partner environments. This article develops the meta‐requirements and a meta‐design of an Information Systems Design Product Theory for the class of RRMS based on a case study in a global company and a literature review. The theory is scalable to meet the needs of global companies but simple enough so that small and medium‐sized companies can also leverage it to implement requirements and release management solutions. Copyright © 2010 John Wiley & Sons, Ltd.

show abstract

Section: Meta‐requirements Of the Is Design Product Theory For Thementioning

confidence: 99%

“…A commonly enacted software product line governance model and a strategic product line roadmapping process should be instituted to ensure that the organization is ready for multi‐site development 8, 22. All sites should use compatible processes, methodologies, tools, and terminology as much as possible to enact the governance model 4.…”

Section: Introductionmentioning

confidence: 99%

An information systems design product theory for the class of integrated requirements and release management systems

Käkölä

Koivulahti-Ojala

Liimatainen³

2010

J. Softw. Maint. Evol.: Res. Pract.

View full text Add to dashboard Cite

show abstract

An information systems design product theory for the class of integrated requirements and release management systems

Käkölä

Koivulahti-Ojala

Liimatainen³

2012

J. Softw. Maint. Evol.: Res. Pract.

View full text Add to dashboard Cite

SUMMARYHigh-tech companies conducting product development need to collect and analyze requirements effectively, plan and implement releases, and allocate requirements to appropriate releases. Requirements and release management are complicated because development activities typically are scattered across multiple sites, involve multiple partners in different countries, leverage various development methods and tools, and are realized through various organizational arrangements such as release projects in organizations structured around products and permanent release teams in organizations responsible for the long-term development and maintenance of strategic software and hardware assets. Flexible, scalable, and secure groupwarebased support for the activities provides substantial payoffs. Yet, the extant literature provides little theoretical guidance for designing and using requirements and release management systems (RRMS) in multi-site, multi-partner environments. This article develops the meta-requirements and a meta-design of an Information Systems Design Product Theory for the class of RRMS based on a case study in a global company and a literature review. The theory is scalable to meet the needs of global companies but simple enough so that small and medium-sized companies can also leverage it to implement requirements and release management solutions.

show abstract

Supporting commonality-based analysis of software product lines

et al. 2011

View full text Add to dashboard Cite

Software Product Line (SPL) engineering is a cost effective approach to developing families of similar products. Key to the success of this approach is to correctly scope the domain of the SPL, identifying the common and variable features of the products and the interdependencies between features. In this paper, we show how the commonality of a feature (i.e., the reuse ratio of the feature among the products) can be used to detect scope flaws in the early stages of development. SPL domains are usually modeled by means of feature diagrams following the FODA notation. We extend classical FODA trees with unrestricted cardinalities, and present an algorithm to compute the number of products modeled by a feature diagram and the commonality of the features. Finally, we compare the performance of our algorithm with two other approaches built on top of boolean logic SAT-solver technology such as cachet and relsat.

show abstract

Strategic Scenario-Based Valuation of Product Line Roadmaps

Cited by 9 publications

References 6 publications

An information systems design product theory for the class of integrated requirements and release management systems

An information systems design product theory for the class of integrated requirements and release management systems

An information systems design product theory for the class of integrated requirements and release management systems

Supporting commonality-based analysis of software product lines

Contact Info

Product

Resources

About