Putting non-functional requirements into software architecture

  • Authors:

  • Xavier Franch;Pere Botella

  • Affiliations:

  • Dept. Llenguatges i Sistemes Informàtics (LSI), Universitat Politècnica de Catalunya (UPC), c/Jordi Girona 1-3 (Campus Nord), 08034 Barcelona, Catalonia (Spain);Dept. Llenguatges i Sistemes Informàtics (LSI), Universitat Politècnica de Catalunya (UPC), c/Jordi Girona 1-3 (Campus Nord), 08034 Barcelona, Catalonia (Spain)

  • Venue:
  • IWSSD '98 Proceedings of the 9th international workshop on Software specification and design
  • Year:
  • 1998

Quantified Score

Hi-index 0.00

Visualization

Abstract

This paper presents an approach for incorporating non-functional information of software systems into software architectures. To do so, components present two distinguished slots: their non-functional specification, where non-functional requirements on components are placed, and their non-functional behaviour with respect to these requirements. Also, connector protocols may describe which non-functional aspects are relevant to component connections. We propose a notation to describe non-functionality in a systematic manner, and we use it to analyse two particular aspects of the meeting scheduler case study, user interaction and performance.