게임 이론적 접근을 통한 효과적인 윈윈 요구사항 협상 기법

다국어 초록 (Multilingual Abstract)

With changing software industry structure, the emerging concept called Software Ecosystems (SECO) has various challenges that software engineers have to overcome. In marketdriven software product development, they should have the capability to offer high value products to their own business and their customers in order to being competitive. Each stakeholder’s perspectives and interests should be reconciled in terms of requirements so that engineers can offer high value products through requirements selection. Existing works have just mentioned the need of requirements negotiation between stakeholders without proposing detailed guidelines or practice. In this work, a systematic Requirements Negotiation process is proposed to resolve conflicts of interests of stakeholders in SECO. The interests of stakeholders are analyzed based on goal-based requirements engineering. The rationale of requirements conflict is structured for management. A stepwise requirements negotiation process aims at resolving requirements conflict by applying game theory concepts based on self-interested behaviors of stakeholders.

참고문헌 (Reference)

1 "https://victorpalau.net/2009/08/10/games-open-source-people-play/"

2 "http://www.infoq.com/news/2010/11/game-theory-and-agile"

3 "http://leadinganswers.typepad.com/leading_answers/2010/11/aligning-pmos-using-gam e-theory.html"

4 Chapman, G., "Using game theory to examine incentives in influenza vaccination behavior" 23 (23): 1008-1015, 2012

5 Khurum, Mahvish, "The software value map—an exhaustive collection of value aspects for the development of software intensive products" 25 (25): 711-741, 2013

6 Manikas, Konstantinos, "Software ecosystems–a systematic literature review" 86 (86): 1294-1306, 2013

7 Karlsson, Lena, "Requirements engineering challenges in market-driven software development-An interview study with practitioners" 49 (49): 588-604, 2007

8 Gorschek, Tony, "Requirements abstraction model" 11 (11): 79-101, 2006

9 Fricker, Samuel, "Requirements Engineering:Foundation for Software Quality" Springer Berlin Heidelberg 60-66, 2010

10 Veliz, Gonzalez, "Requirements Engineering in Open Innovation and Software Ecosystems-Exploring the requirements engineering practices in the industry in the context of Open Innovation and Software Ecosystems"

11 Daniels, Jesse, "Quantitative methods for tradeoff analyses" 4 (4): 190-212, 2001

12 Milne, Alastair, "Power and politics in requirements engineering: embracing the dark side?" 17 (17): 83-98, 2012

13 Van Lamsweerde, Axel, "Goal-Oriented Requirements Engineering: A Guided Tour" IEEE Computer Society 249-262, 2001

14 Madani, Kaveh, "Game theory and water resources" 381 (381): 225-238, 2010

15 Hazzan, Orit, "Extreme Programming and Agile Processes in Software Engineering" Springer Berlin Heidelberg 74-81, 2005

16 Jansen, Slinger, "Defining Software Ecosystems: A Survey of Software Platforms and Business Network Governance" 41-56, 2013

17 Valenca, George, "Competition and collaboration in requirements engineering: A case study of an emerging software ecosystem" 2014

18 Yin, Robert K, "Case study research: Design and methods" Sage publications 2013

19 Lee, Seok Won, "Case Study Methodology Designed Research in Software Engineering Methodology Validation" 117-122, 2004

20 Valença, George, "Analysing Requirements Negotiation in Software Ecosystems with Multi-Agent Systems Techniques" 44-51, 2013

21 A. Aurum, "A value-based approach in requirements engineering: explaining some of the fundamental concepts, in: International Conference on Requirements Engineering: Foundation for Software Quality(REFSQ’07), 11-12 Trondheim Norway" 4542 : 109-115, 2007

22 Barney, Sebastian, "A product management challenge: Creating software product value through requirements selection" 54 (54): 576-593, 2008