RAAP: A requirements analysis and assessment process framework for component-based system (Invited paper)

Richard Lai*, Sajjad Mahmood, Shaoying Liu

*Corresponding author for this work

Research output: Contribution to journalArticlepeer-review

5 Scopus citations

Abstract

Success of a Component Based System (CBS) depends heavily on the selection of the right components. In reality, components are usually designed for general purposes and finding the ideal ones is often very difficult. The CBS requirements process is hence more complicated than the conventional approach. In this paper, we present a Requirements Analysis and Assessment Process (RAAP) for CBS that can provide quantitative information and guidelines for stakeholders to evaluate the suitability of the components for a given set of requirements. Subsequently, they will be able to select the most appropriate components that best satisfy their needs, taking into consideration the risks involved and the conflicts that could arise as a result of selecting certain components earlier in the process. RAAP consists of three phases: (i) requirements characterization which elicits user requirements; (ii) top-down analysis which calculates the degree of satisfaction of a component and the amount of risks involved; and (iii) trade-off analysis which identifies and resolves the potential conflicts in requirements after certain components have been selected. We also present an application of RAAP to the Seven Eleven Japan system.

Original languageEnglish
Pages (from-to)1050-1066
Number of pages17
JournalJournal of Software
Volume6
Issue number6
DOIs
StatePublished - Jun 2011

Keywords

  • Component based system
  • Requirements analysis
  • Risk assessment
  • Software metrics

ASJC Scopus subject areas

  • Software
  • Human-Computer Interaction
  • Artificial Intelligence

Fingerprint

Dive into the research topics of 'RAAP: A requirements analysis and assessment process framework for component-based system (Invited paper)'. Together they form a unique fingerprint.

Cite this