RE-UML: A component-based system requirements analysis language

Sajjad Mahmood, Richard Lai*

*Corresponding author for this work

Research output: Contribution to journalArticlepeer-review

9 Scopus citations

Abstract

Requirements analysis and component selection is widely recognized as an interrelated process that plays a central role in overall component-based system (CBS) development. Fundamental to the success of CBS is a requirement analysis model in which both stakeholders and candidate components balance the conflicting interests between what is needed and what is available. The effectiveness of CBS relies heavily on a system analyst's expertise to select suitable components. Owing to the lack of a language that could describe component alternatives with respect to stakeholder requirements, there is a need to develop one to describe CBS requirement analysis. In this paper, we present an extension to unified modelling language (UML) named RE-UML with a formal semantics utilizing Prolog programming language to support CBS requirements analysis. It helps balance the conflicts between what is required for a CBS-to-be and what features are supported by candidate components. RE-UML extends the UML sequence diagrams with a satisfaction interaction frame and mapping operators to model matching criteria between stakeholder demands and candidate component features. Further, associations between requirements and candidate components are introduced to model risk assessment and conflict resolutions during CBS requirements analysis. To demonstrate the usefulness of RE-UML, its application to the Seven-Eleven Japan software system is also presented.

Original languageEnglish
Pages (from-to)901-922
Number of pages22
JournalComputer Journal
Volume56
Issue number7
DOIs
StatePublished - Jul 2013

Keywords

  • component-based system
  • requirements analysis
  • unified modelling language

ASJC Scopus subject areas

  • General Computer Science

Fingerprint

Dive into the research topics of 'RE-UML: A component-based system requirements analysis language'. Together they form a unique fingerprint.

Cite this