The WinWin Approach: Using a Requirements Negotiation Tool for Rationale Capture and Use
暂无分享,去创建一个
[1] Jay F. Nunamaker,et al. Lessons from a Dozen Years of Group Support Systems Research: A Discussion of Lab and Field Findings , 1996, J. Manag. Inf. Syst..
[2] Anthony M. Armocida. The Seven Habits of Highly Effective People , 1992 .
[3] Barry W. Boehm,et al. A spiral model of software development and enhancement , 1986, Computer.
[4] Barry W. Boehm,et al. Theory-W Software Project Management: Principles and Examples , 1989, IEEE Trans. Software Eng..
[5] Barry W. Boehm,et al. Requirements that Handle IKIWISI, COTS, and Rapid Change , 2000, Computer.
[6] Barry Boehm,et al. A collaborative spiral software process model based on Theory W , 1994, Proceedings of the Third International Conference on the Software Process. Applying the Software Process.
[7] Vasant Dhar,et al. Supporting Systems Development by Capturing Deliberations During Requirements Engineering , 1992, IEEE Trans. Software Eng..
[8] Ellis Horowitz,et al. Software Cost Estimation with COCOMO II , 2000 .
[9] 佚名. THE SEVEN HABITS OF HIGHLY EFFECTIVE PEOPLE高效人士的七种习惯 , 2003 .
[10] Barry W. Boehm,et al. Software requirements as negotiated win conditions , 1994, Proceedings of IEEE International Conference on Requirements Engineering.
[11] Barry W. Boehm,et al. Anchoring the Software Process , 1996, IEEE Softw..
[12] William L. Ury,et al. Getting to Yes , 2019, Boy on the Bridge.
[13] Barry W. Boehm,et al. Developing Groupware for Requirements Negotiation: Lessons Learned , 2001, IEEE Softw..