Recording the reasons for design decisions
ICSE '88 Proceedings of the 10th international conference on Software engineering
Design rationale: the argument behind the artifact
CHI '89 Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
A Two-Person Inspection Method to Improve Programming Productivity
IEEE Transactions on Software Engineering
Practical programmer: inspections—some surprising findings
Communications of the ACM
An encompassing life cycle centric survey of software inspection
Journal of Systems and Software
Software Inspection
Using Group Support Systems for Software Inspections
IEEE Software
Stakeholder Identification in the Requirements Engineering Process
DEXA '99 Proceedings of the 10th International Workshop on Database & Expert Systems Applications
Surfacing Tacit Knowledge in Requirements Negotiation: Experiences Using Easy Win Win
HICSS '01 Proceedings of the 34th Annual Hawaii International Conference on System Sciences ( HICSS-34)-Volume 1 - Volume 1
HICSS '01 Proceedings of the 34th Annual Hawaii International Conference on System Sciences ( HICSS-34)-Volume 1 - Volume 1
EasyWinWin: Managing Complexity in Requirements Negotiation with GSS
HICSS '02 Proceedings of the 35th Annual Hawaii International Conference on System Sciences (HICSS'02)-Volume 1 - Volume 1
Contribution structures [Requirements artifacts]
RE '95 Proceedings of the Second IEEE International Symposium on Requirements Engineering
Tailoring a COTS Group Support System for Software Requirements Inspection
Proceedings of the 16th IEEE international conference on Automated software engineering
The Role of Inspection in Software Quality Assurance
IEEE Transactions on Software Engineering
METRICS '03 Proceedings of the 9th International Symposium on Software Metrics
Collaboration Engineering with ThinkLets to Pursue Sustained Success with Group Support Systems
Journal of Management Information Systems
Field Experiences with eXtreme Programming: Developing an Emergency Response System
Journal of Management Information Systems
Software Process Tailoring: An Empirical Investigation
Journal of Management Information Systems
Mining Trading Partners' Preferences for Efficient Multi-Issue Bargaining in E-Business
Journal of Management Information Systems
Modifiers for Quality Assurance in Group Facilitation
Groupware: Design, Implementation, and Use
Early development of graphical user interface (GUI) in agile methodologies
Journal of Computational Methods in Sciences and Engineering
Negotiation-collaboration in formal technical reviews
CRIWG'09 Proceedings of the 15th international conference on Groupware: design, implementation, and use
Generating user stories in groups
CRIWG'09 Proceedings of the 15th international conference on Groupware: design, implementation, and use
Modifiers: Increasing richness and nuance of design pattern languages
Transactions on pattern languages of programming II
FASE'06 Proceedings of the 9th international conference on Fundamental Approaches to Software Engineering
Hi-index | 0.00 |
Collaboration is essential in many mission-critical activities. Consequently, numerous methods and tools are available supporting collaborative processes such as strategic planning, risk management, requirements definition, and so on. These methods typically emphasize the collaborative, value-creating activities, but there is often less emphasis on quality aspects. Quality assurance (QA) techniques have been wellknown in engineering for a long time, and their effectiveness and efficiency has been empirically evaluated in many domains. In this paper, we propose to integrate repeatable QA techniques and collaborative processes. We evaluate our idea in the context of a collaborative process for requirements negotiation. We propose pre-process techniques to be used before the actual negotiation, in-process techniques for checking quality during a negotiation, as well as post-process inspection techniques. These techniques help a project team reduce unnecessary complexity and to mitigate risks stemming from defects in requirements negotiation results. We present the results of a feasibility study we conducted to test our approach.