Browse Prior Art Database

Integrating Structured Analysis and Structured Design

IP.com Disclosure Number: IPCOM000114319D
Original Publication Date: 1994-Dec-01
Included in the Prior Art Database: 2005-Mar-28
Document File: 4 page(s) / 167K

Publishing Venue

IBM

Related People

Bent, SG: AUTHOR [+4]

Abstract

A software development methodology is disclosed that simplifies the transition from Structured Analysis to Structured Design. This methodology eliminates the need for a separate design phase modeling constructs by allowing structural information to be made part of the system model created in the analysis phase. This integration results in a methodology that provides a more natural means for specifying what is normally provided by structured design but without an explicit structured design phase or the need for structure charts.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 33% of the total text.

Integrating Structured Analysis and Structured Design

      A software development methodology is disclosed that simplifies
the transition from Structured Analysis to Structured Design.  This
methodology eliminates the need for a separate design phase modeling
constructs by allowing structural information to be made part of the
system model created in the analysis phase.  This integration results
in a methodology that provides a more natural means for specifying
what is normally provided by structured design but without an
explicit structured design phase or the need for structure charts.

      Structured Analysis and Design is a well-known methodology for
specifying the design of complex software systems.  One aspect of
this methodology that remains problematic is the transition from
analysis phase to design phase.  The concepts and modeling constructs
used in the two different phases of are significantly different.  The
analysis phase focuses on specifying the process, control, and
information aspects of a system using functional decomposition.  The
design phase focuses on the architecture or final structure of the
system in terms of modules and their interactions.  The process of
transforming design artifacts produced using Structured Analysis into
design artifacts for Structured Design purposes is generally
considered one of the most difficult tasks for a developer using this
methodology.  There are no well-defined approaches to the problem.
Even well-known texts on this methodology provide little advice on
how to move from analysis to design.  The solution disclosed here
eliminates the need for a separate structured design model by
integrating it with structured analysis.  This integration results in
a methodology that provides a more natural means for specifying what
is normally provided by structured design but without an explicit
structured design phase or even the need for structure charts.

      The following describes the concept of Successive
Disambiguation (SDa) and its realization as a Structured Analysis for
real-time systems (SA/RT) methodology in a Computer Aided Software
Engineering (CASE) tool.  The goal of SDa is to arrive at a single
semantic interpretation for a given SA/RT  model.  While traditional
SA/RT  using data flow diagrams, state transition diagrams, and
entity/relationship diagrams has been in wide use for many years,
models so constructed often contain sufficient ambiguity as to
require an extensive Structured Design phase prior to implementation.

      In contrast to this, the SA/RT  methodology presented here
allows the modeler to add successive levels of detail, as
annotations, until the desired level of "disambiguation" is reached.
In addition, this methodology offers significant advances in data
flow modeling including reusable data processes which directly
support the modeling of recursion and co-processing as well as reuse,
strong typing for flows and stores, and hiera...