Using concept lattices for requirements reconciliation

Debbie Richards*

*Corresponding author for this work

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

1 Citation (Scopus)


We have developed a requirements engineering process model based on viewpoint development. Our goal is to capture and reconcile a set of requirements in the form of use case descriptions so that a more complete and representative set of requirements will provide the basis for system design and development. Our technique converts the natural language sentences in each individual use case viewpoint into a formal context. We then apply Formal Concept Analysis to generate a concept lattice of the requirements. Our process model and tool allow viewpoints, use cases, sentences and phrases to be selected for comparison, tagging and reconciliation. The final product is a shared used case description that has been agreed upon by the project group. In this paper we provide an example developed by final year software engineering students who used the approach as a means to gain experience in the specification of use cases and the sometimes painful task of arriving at a shared view of the requirements before system design and development commenced. Our next step is evaluation with requirements engineers to develop a full-strength industrial product and process.

Original languageEnglish
Title of host publicationConcept Lattices, 2nd international conference on Formal Concept Analysis, ICFCA 2004
EditorsPeter Eklund
Place of PublicationBerlin; New York
PublisherSpringer, Springer Nature
Number of pages8
ISBN (Print)3540210431, 9783540210436
Publication statusPublished - 2004
Event2nd International Conference on Formal Concept Analysis, ICFCA 2004 - Sydney, Australia
Duration: 23 Feb 200426 Feb 2004


Other2nd International Conference on Formal Concept Analysis, ICFCA 2004


Dive into the research topics of 'Using concept lattices for requirements reconciliation'. Together they form a unique fingerprint.

Cite this