Making Every Student a Winner: The WinWin Approach in Software Engineering Education
暂无分享,去创建一个
[1] Barry W. Boehm,et al. Software requirements negotiation: some lessons learned , 1998, Proceedings of the 20th International Conference on Software Engineering.
[2] Bashar Nuseibeh,et al. Requirements engineering: a roadmap , 2000, ICSE '00.
[3] Barry W. Boehm,et al. Theory-W Software Project Management: Principles and Examples , 1989, IEEE Trans. Software Eng..
[4] Barry W. Boehm,et al. Applying WinWin to quality requirements: a case study , 2001, Proceedings of the 23rd International Conference on Software Engineering. ICSE 2001.
[5] Sara Jones,et al. Rescue an integrated method for specifying requirements for complex sociotechnical systems , 2005 .
[6] Barry W. Boehm,et al. Identifying quality-requirement conflicts , 1996, Proceedings of the Second International Conference on Requirements Engineering.
[7] Barry W. Boehm,et al. Developing Groupware for Requirements Negotiation: Lessons Learned , 2001, IEEE Softw..
[8] Robert O. Briggs,et al. EasyWinWin: managing complexity in requirements negotiation with GSS , 2002, Proceedings of the 35th Annual Hawaii International Conference on System Sciences.
[9] Jay F. Nunamaker,et al. Collaboration Engineering with ThinkLets to Pursue Sustained Success with Group Support Systems , 2003, J. Manag. Inf. Syst..
[10] Barry W. Boehm,et al. Software requirements as negotiated win conditions , 1994, Proceedings of IEEE International Conference on Requirements Engineering.
[11] Paul Grünbacher,et al. Tool Support for Distributed Requirements Negotiation , 2003 .
[12] Daniel Port,et al. Evaluating individual contribution toward group software engineering projects , 2003, 25th International Conference on Software Engineering, 2003. Proceedings..
[13] Barry W. Boehm,et al. Using the WinWin Spiral Model: A Case Study , 1998, Computer.