Non-functional aspects including time constraints, distribution and fault tolerance are critical in the design and implementation of distributed real-time systems. As a result, it is well recognized that non-functional requirements should be considered at the earliest stages of system development life cycle. The ability to model non-functional properties (such as timing constraints, availability, performance, and security) at the system requirements level not only facilitates the task of moving towards real-time design, but ultimately supports the early detection of errors through automated validation and verification. In this paper, we introduce a novel approach to describe availability features in Use Case Maps (UCM) specifications. The proposed approach relies on a mapping of availability architectural tactics to UCM components. We illustrate the application of our approach using the In Service Software Upgrade (ISSU) feature on IP routers.

-- DanielAmyot - 15 Feb 2012


  • Please feel free to discuss this article directly on this page. Constructive comments are welcomed! Please sign your TWiki name.

FormForVirtualLibrary edit

Title Exploring Early Availability Requirements Using Use Case Maps
Authors J. Hassine and A. Gherbi
Type Conference
Conference/Journal Title SDL 2011: Integrating System and Software Modeling
Volume/Number LNCS 7083
Editors I. Ober and I. Ober
Publisher Springer-Verlag
Month July
Year 2011
Pages 54-68
DOI 10.1007/978-3-642-25264-8_6
Keywords Availability, NFR, UCM
Topic revision: r1 - 15 Feb 2012, 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