Patterns in property specifications for finite-state verification
Proceedings of the 21st international conference on Software engineering
Mastering the requirements process
Mastering the requirements process
LSCs: Breathing Life into Message Sequence Charts
Formal Methods in System Design
Software Engineering
A Field Guide to Boxology: Preliminary Classification of Architectural Styles for Software Systems
COMPSAC '97 Proceedings of the 21st International Computer Software and Applications Conference
Formal Methods for Software Architectures: Third International School on Formal Methods for the Design of Computer, Communication, and Software Systems--Software Architectures, Sfm 2003 (Lecture Notes in Computer Science, 2804)
Specifying and executing requirements: the play-in/play-out approach
OOPSLA '02 Companion of the 17th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
A scenario based notation for specifying temporal properties
Proceedings of the 2006 international workshop on Scenarios and state machines: models, algorithms, and tools
Semantics of interactions in UML 2.0
HCC '03 Proceedings of the 2003 IEEE Symposium on Human Centric Computing Languages and Environments
Journal of Systems and Software
| Hi-index | 0.00 |
Informal and abstract user requirement specifications are usually complemented by formal and detailed system requirement specifications. While user requirements provide a high level description of what services the system is expected to provide, system requirements provide a more technical specification of how that services should be provided by the system. One of the relevant problems that arise during the Requirement Engineering process is the result of failing to make a clear transition between different levels of requirements description. Goal of this paper is to introduce a graphical tool for requirements refinement which guides software architects while moving from user requirements to (architec-tural-level) system requirements. The tool makes use of a previous work that gives a simple but expressive graphical formalism, based on UML2.0 Sequence Diagrams, for specifying temporal properties.