A Cost-Based Approach to Software Product Line Management

Schackmann, Holger; Lichter, Horst

doi:10.1109/iwspm.2006.1

Cited by 9 publications

(6 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This kind of analysis is based on the manager's personal convictions, and therefore, these types of approaches are not yet mature engineering processes. Other studies [22] measure effort levels by analyzing the product cycle evolution and, from that point of view, determining their costs.…”

Section: "Cost" Estimation In Splsmentioning

confidence: 99%

“…Previous studies related with SPLs modeling costs [16,17,18,19,20,25,22], measure the computed features as whole products. These approaches do not consider the order in which features are computed to generate a valid product.…”

Section: Process Algebras and Cost Analysismentioning

confidence: 99%

“…This formal extension is targeted to represent features as cost objects [22] and product lines as cost-based systems [23,24]. It will enable product-management decisions and cost estimations, even when products are in the earlier stages of the development process or in any iteration of the SPL.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Cost-related interface for software product lines

Camacho

Llana

Núñez

2016

Journal of Logical and Algebraic Methods in Programming

View full text Add to dashboard Cite

Software Product Lines modeling improves software development processes by automating system debugging and analysis. The objective of this paper focuses on extending the formal framework SPLA to represent features such as cost objects and comparisons between products in terms of production costs. We illustrate this extension with a practical example by modeling the creation of valid run-lists for Chef, a widely used configuration management tool. Also, we execute our formal specification in a distributed system using SCOOP and we provide strategies to optimize the effort required to compute a SPLA term.

show abstract

Section: "Cost" Estimation In Splsmentioning

confidence: 99%

Section: Process Algebras and Cost Analysismentioning

confidence: 99%

See 1 more Smart Citation

Cost-related interface for software product lines

Camacho

Llana

Núñez

2016

Journal of Logical and Algebraic Methods in Programming

View full text Add to dashboard Cite

show abstract

“…The fourth column contains the corresponding qualitative evidence in terms of references to the literature which contains the excerpts. [4], [26], [37], [39], [48], [59] Launch 897 [7], [13], [26], [34], [37], [48], [62], [69] Planning 2.165 [5], [8], [23], [37], [48] Strategy(/ies) 1.102 (784; 318) [4], [25], [26], [37], [39], [48], [59] Support 1.601 [37], [46], [48], [59], [69] Artifact Product(/s) 21.960 (18.915;3.045) [26], [37], [40], [43], [44], [69] Product Description(/s) 24 [4], [19], [37], [44], [ [25], [37], [40], [48], [68] Specification(/s) 442 (294; 148) [37], [41], …”

Section: Concept Hierarchiesmentioning

confidence: 99%

Developing a domain ontology for software product management

Botzenhardt

Maedche

Wiesner

2011

2011 Fifth International Workshop on Software Product Management (IWSPM)

View full text Add to dashboard Cite

Software product management has gained much attention in recent years for its positive influence on corporate success in software companies. However, despite its relevance and positive influence there is only little and vague guidance concerning software product management. There is no extensive body of knowledge as in Software Engineering or Project Management. The work presented in this paper aims at developing an adequate and precise conceptual representation of the software product management domain by means of creating a domain ontology. It defines domain-specific knowledge on a more fundamental level. The developed ontology captures basic aspects of the software product management domain and represents a reasonable approach to provide a common conceptual understanding of the domain. Software Product Management, Domain Ontology, Ontology Engineering

show abstract

“…1 Being aware of the impact of the finance office on the product requires the product manager to delve more deeply into the business aspects of her product and take a more businessfocused view, a facet of the role that has been the subject of previous discussions (see e.g., [8,9]). …”

Section: Introductionmentioning

confidence: 99%

Finance as a Stakeholder in Product Management

Konig¹

2009

2009 Third International Workshop on Software Product Management

View full text Add to dashboard Cite

The traditional literature of software product management focuses on sales, marketing and executive management as key internal stakeholders for the product manager. However in public companies and private companies positioning for a public offering, the importance of reported accounting revenue can cause the finance office to become a significant additional stakeholder. The concerns of finance can cause significant impacts on the offering, apart from those driven by market needs and other stakeholders. The struggle to balance these competing interests is particularly acute for B2B software offerings during the market entry phase, offerings that include a significant service component and offerings delivered under a software-as-a-service (SaaS) arrangement. This paper will describe some of the common concerns of the finance office, describe the impacts to the offering they create, and offer suggestions to the product manager on how to address those concerns.

show abstract

A Cost-Based Approach to Software Product Line Management

Cited by 9 publications

References 1 publication

Cost-related interface for software product lines

Cost-related interface for software product lines

Developing a domain ontology for software product management

Finance as a Stakeholder in Product Management

Contact Info

Product

Resources

About