Formal refinement patterns for goal-driven requirements elaboration
SIGSOFT '96 Proceedings of the 4th ACM SIGSOFT symposium on Foundations of software engineering
Entity-Relationship Modeling: Foundations of Database Technology
Entity-Relationship Modeling: Foundations of Database Technology
A Reference Model for Requirements and Specifications
IEEE Software
Design Methods for Software Systems: YOURDON, Statemate and Uml
Design Methods for Software Systems: YOURDON, Statemate and Uml
Formal Modeling of Large Domains
APSEC '96 Proceedings of the Third Asia-Pacific Software Engineering Conference
Participatory task modelling: users and developers modelling users' tasks and domains
TAMODIA '04 Proceedings of the 3rd annual conference on Task models and diagrams
Conceptual modelling of web information systems
Data & Knowledge Engineering
A view of 20th and 21st century software engineering
Proceedings of the 28th international conference on Software engineering
Towards a formal foundation for domain specific modeling languages
EMSOFT '06 Proceedings of the 6th ACM & IEEE International conference on Embedded software
Pragmatics of storyboarding for web information systems: usage analysis
International Journal of Web and Grid Services
Requirements Analysis & System Design
Requirements Analysis & System Design
A theory of duration calculus with application
Domain modeling and the duration calculus
From conceptual modeling to requirements engineering
ER'06 Proceedings of the 25th international conference on Conceptual Modeling
Towards a theory of genericity based on government and binding
ER'06 Proceedings of the 25th international conference on Conceptual Modeling
Hi-index | 0.00 |
Application domain description precedes requirements engineering, and is the basis for the development of a software or information system that satisfies all expectations of its users. The greatest challenge in this area is the evolution of the application domain itself. In this paper we address this problem by explicit consideration of application cases that are defined by user profiles and intentions and the system environment, i.e. scope and context. User profiles and intentions are captured through the concept of persona. We show how the application domain description can be mapped to requirements and discuss engineering of application domain descriptions.