Towards an integrated model for functional and user interface requirements

Authors:
Rabeb Mizouni;Daniel Sinnig;Ferhat Khendek
Affiliations:
College of Information Technology, UAE University, Al-Ain, UAE;Faculty of CS and Elec. Engineering, University of Rostock, Germany;Dept. of Electrical & Computer Eng., Concordia University, Montreal, Canada
Venue:
HCSE'10 Proceedings of the Third international conference on Human-centred software engineering
Year:
2010

Citing 8
Cited 0

Integrating development of task and object models

Communications of the ACM
Behaviour model elaboration using partial labelled transition systems

Proceedings of the 9th European software engineering conference held jointly with 11th ACM SIGSOFT international symposium on Foundations of software engineering
Using an interaction model as a resource for communication in design

CHI '05 Extended Abstracts on Human Factors in Computing Systems
An Integration of Task and Use-Case Meta-models

Proceedings of the 13th International Conference on Human-Computer Interaction. Part I: New Trends
Towards a UML profile for interaction design: the wisdom approach

UML'00 Proceedings of the 3rd international conference on The unified modeling language: advancing the standard
Bridging the gap: empowering use cases with task models

Proceedings of the 2nd ACM SIGCHI symposium on Engineering interactive computing systems
Mapping concurtasktrees into UML 2.0

DSVIS'05 Proceedings of the 12th international conference on Interactive Systems: design, specification, and verification
Generating UML diagrams from task models

CHINZ '03 Proceedings of the 4th Annual Conference of the ACM Special Interest Group on Computer-Human Interaction

Quantified Score

Hi-index	0.00

Visualization

Abstract

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.