Structured analysis for Requirements Definition (abstract only)

  • Authors:
  • Douglas T. Ross;Kenneth E. Schoman, Jr.

  • Affiliations:
  • -;-

  • Venue:
  • ICSE '76 Proceedings of the 2nd international conference on Software engineering
  • Year:
  • 1976

Quantified Score

Hi-index 0.00

Visualization

Abstract

Requirements Definition encompasses all aspects of system development prior to actual System Design. We see the lack of an adequate approach to Requirements Definition as the source of major difficulties in current systems work. This paper examines the needs for Requirements Definition, and proposes meeting those objectives with three interrelated subjects: Context Analysis, Functional Specification, and Design Constraints. Requirements Definition replaces the widely-used, but never well-defined term “requirements analysis”. The purpose of this paper is to present, in a comprehensive manner, concepts that apply throughout Requirements Definition (and, by implication, to all of system development). The paper discusses the functional architecture of systems, the characteristics of good requirements documentation, the personnel involved in the process of analysis, and management guidelines that are effective even in complex environments. The paper then outlines a systematic methodology that incorporates, in both notation and technique, the concepts previously introduced. Reference is made to actual Requirements Definition experience and to practicable automated support tools that may be used with the methodology.