Notations For Software Specification And Design (Panel Discussion)

ABSTRACT

Software development involves the accomplishment of distinct functions such as problem definition, requirements engineering, system architecture design, etc. The major ingredients contributing to the accomplishment are creativeness, a level of experience, and a formal or informal methodology. To that end, a methodology can be thought of as the sum of four parts: (1) a collection of basic ideas containing a certain spirit or viewpoint (principles), (2) techniques which apply the basic ideas, (3) a set of tools for employing the techniques to the “real-world” problems, and (4) an overall procedure describing when to use the tools and techniques. The concept of a notation (graphical, linguistic, or tabular mechanism used for displaying or formulating ideas) is the keystone to the utilization of a methodology. The objective of this session is to deepen our understanding of the role of notations in the areas of requirements engineering and software design.

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.1 Requirements/Specifications

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.2 Design Tools and Techniques

General Terms:
Design