Browse Prior Art Database

The VIEWS Method and Tool

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

Publishing Venue

IBM

Related People

Bent, SG: AUTHOR [+4]

Abstract

A software engineering method (called VIEWS) is disclosed as well as its embodiment as Computer Aided Software Engineering (CASE) tool. VIEWS supports both traditional and object-oriented development with its Real-Time Structured Development Method and the Object - Oriented Application Development Method. Both of these methods are integrated into a consistent semantic model, and can be used independently or together. VIEWS covers the development life-cycle from initial requirements discovery through analysis, design, code, and test.

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

The VIEWS Method and Tool

      A software engineering method (called VIEWS) is disclosed as
well as its embodiment as Computer Aided Software Engineering (CASE)
tool.  VIEWS supports both traditional and object-oriented
development with its Real-Time Structured Development Method and the
Object - Oriented Application Development Method.  Both of these
methods are integrated into a consistent semantic model, and can be
used independently or together.  VIEWS covers the development
life-cycle from initial requirements discovery through analysis,
design, code, and test.

      As illustrated in the Figure, VIEWS integrates both structured
and object-oriented methods and supports a variety of analysis and
design techniques and development aids including the following:
  o  Hierarchical Requirements Specification
  o  Event-Scenario Diagrams
  o  Object-Oriented Analysis and Design
  o  Real-Time Structured Analysis
  o  Entity-Relationship Modeling
  o  Extended Finite State-Machine Modeling
  o  &cpp.  Code Generation from Class Diagrams
  o  Reverse Engineering for C and &cpp.
  o  Configurable Document Generation
  o  Distributed, Multi-user, Configuration Management Support
  o  Design Integrity Reports
  o  Interactive Method Validation Rules
  o  Context-Sensitive Help
  o  Highly Integrated Diagrams and Techniques

      The Hierarchical Requirements technique allows analysts to
capture, organize and track both user and internal requirements.  It
enables the user to collect and partition abstract requirements of a
software product into a hierarchical structure.  These requirements
then serve as a reference for the subsequent modeling effort
throughout the analysis, design, and development phases.  The
requirement statements are organized in a hierarchical fashion with
the most abstract at the top.  Focusing on each abstract requirement,
additional subordinate requirements are solicited or determined.
Sub-requirements are documented to clarify the meaning and intent of
its parent requirement in the hierarchy.  Each lower-level
requirement can be similarly refined until the desired level of
detail is obtained.  Each requirement may be given several attributes
to further clarify and organize the requirements model.  Requirements
can be tracked (forward and reverse) to the subsequent, formal
modeling components.

      Event Scenario Modeling is a technique for specifying the
dynamic interactions between the components of a system over time.
Scenario diagrams can be used to graphically illustrate complex
time-ordered interactions between any combination of users, software
components / systems, and hardware devices.  On an Event Scenario
Diagram, components of a system appear as vertical bars.
Interactions between the nodes are represented as message or command
flows that are processed within the target node.  The vertical axis
of the nodes represents time.  Conversations or dialogs bet...