Towards an integrated model for functional and user interface requirements

Rabeb Mizouni, Daniel Sinnig, Ferhat Khendek

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

2 Scopus citations


Despite the widespread adoption of UML as a standard for modeling software systems, it does not provide adequate support for specifying User Interface (UI) requirements. It has become a common practice to separately use UML use cases for specifying functional requirements and task models for modeling UI requirements. The lack of integration of these two related models is likely to introduce redundancies and inconsistencies into the software development process. In this paper, we propose an integrated model, consisting of use case and task models, for capturing functional and UI requirements. Both artifacts are used in a complementary manner and are formally related through so-called Anchors. Anchors are use case steps that require further elaboration with UI-specific interactions. These interactions are explicitly captured in associated task models. The formal semantics of the integrated model is given with finite state automata.

Original languageBritish English
Title of host publicationHuman-Centred Software Engineering - Third International Conference, HCSE 2010, Proceedings
Number of pages8
StatePublished - 2010
Event3rd International Conference on Human-Centred Software Engineering, HCSE 2010 - Reykjavik, Iceland
Duration: 14 Oct 201015 Oct 2010

Publication series

NameLecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)
Volume6409 LNCS
ISSN (Print)0302-9743
ISSN (Electronic)1611-3349


Conference3rd International Conference on Human-Centred Software Engineering, HCSE 2010


  • Finite State Automata
  • Functional Requirements
  • Integrated Requirements Model
  • Task Models
  • UML Use Cases
  • User Interface Requirements


Dive into the research topics of 'Towards an integrated model for functional and user interface requirements'. Together they form a unique fingerprint.

Cite this