This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
VIRE: Sailing a Blue Ocean with Value-Innovative Requirements
January/February 2008 (vol. 25 no. 1)
pp. 80-87
Sangsoo Kim, Korea University
Hoh Peter In, Korea University
Jongmoon Baik, Information and Communications University
Rick Kazman, University of Hawaii
Kwangsin Han, Korean Asset Management Corp.
An effective way for software development organizations to survive in competitive markets is to make competition irrelevant through requirements that create new value. Value-Innovative Requirements Engineering is a novel requirements-engineering process to support this market approach. VIRE is based on the blue-ocean strategy for creating an uncontested new market space that satisfies new customer desires and needs. The VIRE process guides the creation of new value for potential customers, using blue ocean?s ERRC (eliminate, reduce, raise, and create) requirements analysis process as well as quantitative requirements analyses. A case study shows how VIRE created significant new market value.

1. D.P. Kelly and B. Culeton, "Process Improvement for Small Organizations," Computer, Oct. 1999, pp. 41–47.
2. K.C. Dangle et al., "Software Process Improvement in Small Organizations: A Case Study," IEEE Software, Nov./Dec. 2005, pp. 68–75.
3. W.C. Kim and R. Mauborgne, Blue Ocean Strategy, Harvard Business School Press, 2005.
4. W.C. Kim and R. Mauborgne, "Value Innovation—the Strategic Logic of High Growth," Harvard Business Rev., July–Aug. 2004, pp. 172–180.
5. B. Boehm and H. In, "Identifying Quality-Requirement Conflicts," IEEE Software, Mar. 1996, pp. 25–35.
6. B.S. El-Haik, Axiomatic Quality, John Wiley &Sons, 2005.
7. R. Kazman, H. In, and H. Chen, "From Requirements Negotiation to Software Architecture Decisions," Information and Software Technology, Dec. 2004, pp. 511–520.
8. N.P. Suh, "Design-In of Quality through Axiomatic Design," IEEE Trans. Reliability, vol. 44, no. 2, June 1995, pp. 256–264.
9. K. Yang and B.S. El-Haik, Design for Six Sigma, McGraw-Hill, 2003.
10. A.R. Hevner et al., "Design Science in Information Systems Research," Management Information Systems Quarterly, vol. 28, no. 1, 2004, pp. 75–105.
1. W.C. Kim and R. Mauborgne, Blue Ocean Strategy, Harvard Business School Press, 2005.
2. W.C. Kim and R. Mauborgne, "Value Innovation—The Strategic Logic of High Growth," Harvard Business Rev., July–Aug. 2004, pp. 172–180.
3. M. Erder and P. Pureur, "QFD in the Architecture Development Process," IEEE IT Pro, Nov./Dec. 2003, pp. 44–52.
4. K. Yang and B.S. El-Haik, Design for Six Sigma, McGraw-Hill, 2003.
5. W.K. Chan and K.M. Yu, "TRIZ-Aided Technology Mapping for Information System Implementation," Proc. 2004 IEEE Int'l Eng. Management Conf., IEEE Press, 2004, pp. 239–243.
6. M. Moore et al., "Quantifying the Value of Architecture Design Decisions: Lessons from the Field," Proc. 25th Int'l Conf. Software Eng. (ICSE 03), IEEE CS Press, 2003, pp. 557–562.
7. H.W. Jung, "Optimizing Value and Cost in Requirements," IEEE Software, July/Aug. 1998, pp. 67–74.
8. R. Kazman, H. In, and H. Chen, "From Requirements Negotiation to Software Architecture Decisions," Information and Software Technology, Dec. 2004, pp. 511–520.
9. B. Boehm and L.G. Huang, "Value-Based Software Engineering: A Case Study," Computer, Mar. 2003, pp. 33–41.

Index Terms:
requirements engineering, customer satisfaction, value innovation, value-based software engineering
Citation:
Sangsoo Kim, Hoh Peter In, Jongmoon Baik, Rick Kazman, Kwangsin Han, "VIRE: Sailing a Blue Ocean with Value-Innovative Requirements," IEEE Software, vol. 25, no. 1, pp. 80-87, Jan.-Feb. 2008, doi:10.1109/MS.2008.27
Usage of this product signifies your acceptance of the Terms of Use.