Skip to main content

Estimating the Software Product Value during the Development Process

  • Conference paper
Product-Focused Software Process Improvement (PROFES 2012)

Part of the book series: Lecture Notes in Computer Science ((LNPSE,volume 7343))

Abstract

Nowadays software companies are facing a fierce competition to deliver better products but offering a higher value to the customer. In this context, software product value has becoming a major concern in software industry, leading for improving the knowledge and better understanding about how to estimate the software value in early development phases. Other way, software companies encounter problems such as releasing products that were developed with high expectations, but they gradually fall into the category of a mediocre product when they are released to the market. These high expectations are tightly related to the expected and offered software value to the customer. This paper presents an approach for estimating the software product value, focusing on the development phases. We propose a value indicators approach to quantify the real value of the development products. The aim is early identifying potential deviations in the real software value, by comparing the estimated versus the expected. We present an internal validation to show the feasibility of this approach to produce benefits in industry projects.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 39.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Barbacci, M.R.: Software quality attributes and architecture tradeoffs. Tech. rep., Software Engineering Institute (2003)

    Google Scholar 

  2. Barney, S., Aurum, A., Wohlin, C.: A product management challenge: Creating software product value through requirements selection. J. Syst. Archit. 54, 576–593 (2008), http://portal.acm.org/citation.cfm?id=1374864.1375268

    Article  Google Scholar 

  3. Boehm, B., Biffl, S., Aurum, A., Erdogmus, H., Grünbacher, P.: Value-Based Software Engineering. Springer (2006)

    Google Scholar 

  4. Cedergren, S., Larsson, S.: Improving traceability by focusing on value during development. In: de Madrid, U.P. (ed.) Proceedings of the 1st International Workshop on Value-Based Software Traceability (VALSOT 2011) in XP 2011 Conference (2011)

    Google Scholar 

  5. Day, E., Crask, M.R.: Value assessment the antecedent of customer satisfaction. Journal of Consumer Satisfaction, Dissatisfaction and Complaining Behavior 13 (2000)

    Google Scholar 

  6. International function point users group, T: Function Point Counting Practices Manual. The International Function Point Users Group, 191 Clarksville Road Princeton Junction, NJ 08550 U.S.A., release 1.4.1 edn. (April 2000)

    Google Scholar 

  7. IEEE: IEEE recommended practice for software requirements specifications (1998), http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=720574

  8. International Organization for Standardization: ISO/IEC 9126 Information Technology - Software Product Quality (November 1999)

    Google Scholar 

  9. International Organization for Standardization: ISO/IEC 12207:2008 Systems and Software Engineering - Software life cycle processes (2008)

    Google Scholar 

  10. International Organization for Standardization: ISO/IEC FCD 25010: Systems and software engineering - Software product Quality Requirements and Evaluation (SQuaRE) - Quality models for software product quality and system quality in use (July 2009)

    Google Scholar 

  11. Jacobson, I., Booch, G., Rumbaugh, J.: The unified software development process. Addison-Wesley Longman Publishing Co., Inc., Boston (1999)

    Google Scholar 

  12. Keane: Application rationalization. Tech. rep., Keane (2011)

    Google Scholar 

  13. Kruchten, P.: Architectural blueprints: The ”4+1” view model of software architecture. IEEE Software 12(6), 42–50 (1995)

    Article  Google Scholar 

  14. Ojala, P.: Experiences of a value assessment for products. Softw. Process. 14, 31–37 (2009), http://portal.acm.org/citation.cfm?id=1507322.1507324

    Google Scholar 

  15. Ojala, P.: Value of project management: a case study. WSEAS Trans. Info. Sci. and App. 6, 510–519 (2009), http://portal.acm.org/citation.cfm?id=1553642.1553659

    Google Scholar 

  16. Oxford Dictionaries (2011), http://oxforddictionaries.com/definition/indicator

  17. SAVE International: Value methodology standard and body of knowledge (June 2007)

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2012 Springer-Verlag Berlin Heidelberg

About this paper

Cite this paper

Castro, O., Espinoza, A., Martínez-Martínez, A. (2012). Estimating the Software Product Value during the Development Process. In: Dieste, O., Jedlitschka, A., Juristo, N. (eds) Product-Focused Software Process Improvement. PROFES 2012. Lecture Notes in Computer Science, vol 7343. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-31063-8_7

Download citation

  • DOI: https://doi.org/10.1007/978-3-642-31063-8_7

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-642-31062-1

  • Online ISBN: 978-3-642-31063-8

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics