Eliciting and capturing business goals to inform a product line's business case and architecture

Authors:
Paul Clements;John D. McGregor;Len Bass
Affiliations:
Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA;Department of Computer Science, Clemson University, Clemson, SC;Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA
Venue:
SPLC'10 Proceedings of the 14th international conference on Software product lines: going beyond
Year:
2010

Citing 4
Cited 0

Goal decomposition and scenario analysis in business process reengineering

CAiSE '94 Proceedings of the 6th international conference on Advanced information systems engineering
Software Architecture in Practice

Software Architecture in Practice
Goal-Oriented Requirements Engineering: A Guided Tour

RE '01 Proceedings of the Fifth IEEE International Symposium on Requirements Engineering
Experiences with Product Line Development of Multi-Discipline Analysis Software at Overwatch Textron Systems

SPLC '07 Proceedings of the 11th International Software Product Line Conference

Quantified Score

Hi-index	0.00

Visualization

Abstract

Business goals constitute an important kind of knowledge for a software product line. They inform the product line's business case and they inform its architecture and quality attribute requirements. This paper establishes the connection between business goals and a product line's business case and architecture. It then presents a set of common business goal categories, gleaned from a systematic search of the business literature that can be used to elicit an organization's business goals from key stakeholders. Finally, it presents a well-defined method, which we have tried out in practice, for eliciting and capturing business goals and tying them to quality attribute requirements.