Abstract
We consider a set of programs a family when it pays to look at their common aspects before looking at their differences. For commercial software developers the implications are twofold: First, making rational decisions about product-line processes and products requires the ability to answer the question: “Does it pay?” Second, whether or not something pays is ultimately a business (rather than software engineering) question. In short, making sound software engineering decisions requires understanding the business implications of those decisions, and vice versa. This paper describes work in progress to develop a product-line process model and common value metric that adequately link product value drivers (what it pays) with the software engineering decisions that affect those drivers. We describe a systematic approach to quantifying the return on both product and process improvements, based on common software engineering principles and a common value metric, customer value .
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
F. M Bass and W. Talarzyk,, “Attitude Model for the Study of Brand Preference,” Journal of Marketing Research, 9 February, 1972, 93–9.
L. Bass, P. Clements, and R. Kazman, Software Architecture in Practice, Addison Wesley, 1998.
R. Belk, “An Exploratory Assessment of Situational Effects in Buyer Behavior,” Journal of Marketing Research, 11 May, 1974, 156–162.
R. Belk, “Situational Variables and Consumer Behavior,” Journal of Consumer Research, 2(3), 1975, 157–64.
G.R. Campbell, Jr., S. Faulk, and D. Weiss, Introduction to Synthesis, INTRO_SYNTHESIS_PROCESS-90019-N, Software Productivity Consortium, Herndon, VA, 1990.
G.R. Campbell, Jr., J. O’Connor, C. Mansour, and J. Turner-Harris, “Reuse in Command and Control Systems, IEEE Software, September, 1994.
M. Conway, “How Do Committees Invent?,” Datamation, April, 1968, 37–45.
D. Cuka and D. M. Weiss, “Engineering Domains: Executable Commands as an Example,” Proceedings of the 5th International Conference on Software Reuse, Victoria, Canada, June 1–5,1998, 26–34.
J. DeBaud and K. Schmid, “A Systematic Approach to Derive the Scope of Product Lines,” Proceedings: 21 st International Conference on Software Engineering (ICSE 99), Los Angeles, CA, June 1999.
E.W. Dijkstra, “Notes on Structured Programming,” In Structured Programming, O.J. Dahl, E. W. Dijkstra, and CA. Hoare, eds., Academic Press, London, 1972.
S.R. Faulk, “Achieving Industrial Relevance with Academic Excellence: Lessons from the Oregon Master of Software Engineering,” Proceedings, 22nd International Conference on Software Engineering, Limerick, Ireland, June 2000.
R.R. Harmon and K. A. Coney, “The Persuasive Effects of Source Credibility in Buy and Lease Situations,” Journal of Marketing Research, May, 1982: 255–60.
R.R. Harmon and G. Laird, “Linking Marketing Strategy to Customer Value: Implications for Technology Marketers,” Proceedings of the Portland International Conference on Management of Engineering and Technology, July, 1997, 896–900.
J. R Hauser and Don Clausing (1988), “The House of Quality,” Harvard Business Review, May-June, 63–73.
McConnell, S. (1996), Rapid Development: Taming Wild Software Schedules, Redmond, WA: Microsoft Press, 647 pp.
D. Millington, and J. Stapleton, “Developing an R&D Standard,” IEEE Software, September, 1995 54–55.
D.L. Parnas, “On the Criteria to Be Used in Decomposing a System into Modules,” Comm. ACM, 15, Dec. 1972, 1053–1058.
D. L Parnas, “On the Design and Development of Program Families,” IEEE Transactions on Software Engineering, v. SE-2, No. 1, March, 1976, 1–9.
D. L. Parnas, “Designing Software for Ease of Extension and Contractions,” IEEE Transactions on Software Engineering, v. SE-5, March, 1979, 128–138.
D. M. Raffo, “Modeling Software Processes Quantitatively and Assessing the Impact of Potential Process Changes on Process Performance”, Ph.D. Dissertation, Graduate School of Industrial Administration, Carnegie Mellon University, 1996. UMI #9622438.
D. M. Raffo, M. Vandeville, and Martin, “Software Process Simulation to Achieve Higher CMM Levels,” Journal of Systems and Software, Vol. 46, No. 2/3 (15 April 1999).
D. M. Raffo and M. I. Kellner, “Empirical Analysis in Software Process Simulation Modeling” Journal of Systems and Software, (Forthcoming 2000)
G. L. Urban and S. H. Star, Advanced Marketing Strategy: Phenomena, Analysis, and Decisions, Englewood Cliffs, NJ: Prentice Hall, 1991.
D.M. Weiss and C.T.R. Lai, Software Product Line Engineering: A Family-Based Software Development Process, Addison-Wesley, 1999.
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2000 Springer Science+Business Media New York
About this chapter
Cite this chapter
Faulk, S.R., Harmon, R.R., Raffo, D.M. (2000). Value-Based Software Engineering (VBSE). In: Donohoe, P. (eds) Software Product Lines. The Springer International Series in Engineering and Computer Science, vol 576. Springer, Boston, MA. https://doi.org/10.1007/978-1-4615-4339-8_12
Download citation
DOI: https://doi.org/10.1007/978-1-4615-4339-8_12
Publisher Name: Springer, Boston, MA
Print ISBN: 978-1-4613-6949-3
Online ISBN: 978-1-4615-4339-8
eBook Packages: Springer Book Archive