Describing and assessing availability requirements in the early stages of system development

Jameleddine Hassine*

*Corresponding author for this work

Research output: Contribution to journalArticlepeer-review

8 Scopus citations

Abstract

Non-functional aspects such as timing constraints, availability, and fault tolerance are critical in the design and implementation of distributed real-time systems. As a result, it is becoming crucial to model and analyze non-functional requirements at the early stages of the software development life cycle. The widespread interest in dependability modeling and analysis techniques at the requirements phase provides the major motivation for this research. This paper presents a novel approach to describe and validate high-level availability requirements using the Use Case Maps (UCM) language of the ITU-T User Requirements Notation standard. The proposed approach relies on a mapping of availability architectural tactics to UCM models. The resulting extensions are described using a metamodel and are implemented within the jUCMNav tool. Early assessment and characterization of the means to achieve availability are then performed using a matrix representation allowing for feature-based availability composition and reasoning. We demonstrate the applicability of our approach through a case study of lawful intercept and ACL-based forwarding features on IP routers.

Original languageEnglish
Pages (from-to)1455-1479
Number of pages25
JournalSoftware and Systems Modeling
Volume14
Issue number4
DOIs
StatePublished - 22 Oct 2015

Bibliographical note

Publisher Copyright:
© 2013, Springer-Verlag Berlin Heidelberg.

Keywords

  • Architectural tactics
  • Availability
  • Availability analysis
  • Non-functional requirements
  • URN
  • Use Case Maps

ASJC Scopus subject areas

  • Software
  • Modeling and Simulation

Fingerprint

Dive into the research topics of 'Describing and assessing availability requirements in the early stages of system development'. Together they form a unique fingerprint.

Cite this