Behavioral patterns for software requirement engineering

  • Authors:
  • Ayaz Isazadeh;Glenn H. MacEwen;Andrew Malton

  • Affiliations:
  • Electrical Engineering and Computer Science from Princeton University;Department of Computing and Information Science at Queen's University, Kingston, Ontario;Department of Computing and Information Science at Queen's University, Canada

  • Venue:
  • CASCON '95 Proceedings of the 1995 conference of the Centre for Advanced Studies on Collaborative research
  • Year:
  • 1995

Quantified Score

Hi-index 0.00

Visualization

Abstract

A software behavioral pattern is a typical pattern of event interaction at the level of modules up to independent software components. Behavioral patterns are specified using a form of D. Harel's Statecharts, and we call them type-charts . They provide a semantic basis for presenting software architecture and configuration from a behavioral point of view.We introduce the notation for typecharts and discuss the uses to which they will be put. A catalogue of formally specified behavioral patterns (basic architectural "plans") is envisaged from which a software requirements engineer can select and refine to produce further plans, and present and record the software behavioral requirements. An example of this process is presented.