Assisting Decision Making in Requirements Reconciliation

Debbie Richards*, Kathrin Boettger

*Corresponding author for this work

Research output: Chapter in Book/Report/Conference proceedingConference proceeding contributionpeer-review

2 Citations (Scopus)


Capturing a consistent, complete and valid set of requirements is a critical prerequisite for designing systems that are useful and usable. One popular technique for capturing the main chunks of functionality from the user's point of view is the specification of use cases by the development team. While there may be agreement at this high level, there are often differences in what each stakeholder perceives as the steps of the use case description. Often the description reflects the views of one or a few dominant individuals resulting in incomplete use case descriptions that do not represent the requirements of the whole group. In our approach, known as RECOCASE as we use a CASE tool to assist requirements RECOnciliation, the group identify and then asynchronously capture multiple requirements viewpoints. The use case descriptions are entered in natural language and automatically processed by our system to produce a concept lattice. The concept lattice is used to reveal common ground and differences between the stakeholders. Our group process enables conflicts to be identified and resolved, where possible, using our negotiation strategies and resolution operators.

Original languageEnglish
Title of host publicationProceedings of the Seventh International Conference on CSCW in Design
EditorsWeiming Shen, Jano Moreira de Souza, Jean-Paul Barthes, Zongkai Lin
Place of PublicationRio de Janeiro, Brazil
Number of pages6
ISBN (Print)8528500500
Publication statusPublished - 2002
EventProceedings of the Seventh International Conference on CSCW in Design - Rio de Janeiro, Brazil
Duration: 25 Sept 200227 Sept 2002


OtherProceedings of the Seventh International Conference on CSCW in Design
CityRio de Janeiro


Dive into the research topics of 'Assisting Decision Making in Requirements Reconciliation'. Together they form a unique fingerprint.

Cite this