Abstract

There is a general consensus on the importance of good requirements engineering for achieving high-quality software. Functional requirements capture the intended behavior of the system in terms of services, tasks, or functions the system is required to perform, while non-functional requirements capture required properties of the system, such as timing, performance, and security. These non-functional requirements play a crucial role during system development life cycle serving as selection criteria for choosing among myriads of design decisions. The ability to model and validate the system non-functional properties at the requirements level supports the detection of design errors during the early stages of a software development life cycle and helps reduce the cost of later redesign activities. The widespread interest in time modeling and analysis techniques at the requirements phase provides the major motivation for this research. This paper presents a novel and fully automated approach to describe and validate high-level timed requirements using the Timed Use Case Maps language. We extend the, ITU-T standard User Requirements Notation, Use Case Maps metamodel with time requirements. The resulting extensions are implemented within the jUCMNav tool and formalized using Abstract State Machines allowing for automated simulation and analysis. We illustrate the applicability of our approach using a business process model (conference review process model) and a real-time system model (IP multicast routing case study).

-- DanielAmyot - 16 Mar 2014

Discussion

FormForVirtualLibrary edit

Title Early modeling and validation of timed system requirements using Timed Use Case Maps
Authors J. Hassine
Type Journal
Conference/Journal Title Requirements Engineering
Volume/Number
Editors
Publisher Springer
Month January
Year 2014
Pages
DOI 10.1007/s00766-013-0200-9
Keywords Requirements, Non-functional, Time modeling, Timed Use Case Maps (TUCM), User Requirements Notation (URN), Abstract State Machines (ASM), jUCMNav

Topic revision: r2 - 16 Mar 2014, DanielAmyot
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback