Browse Prior Art Database

Software Development Library User Interface

IP.com Disclosure Number: IPCOM000111634D
Original Publication Date: 1994-Mar-01
Included in the Prior Art Database: 2005-Mar-26
Document File: 2 page(s) / 189K

Publishing Venue

IBM

Related People

Redpath, RJ: AUTHOR

Abstract

Software library management is inherently a complicated process reported by customers. The customer is faced with a sea of components,parts,access lists, and more. In many instances, the customer does not know what tool to use or what next step to take.

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

Software Development Library User Interface

      Software library management is inherently a complicated process
reported by customers.  The customer is faced with a sea of
components,parts,access lists, and more.  In many instances, the
customer does not know what tool to use or what next step to take.

      Current software library development applications are
user-interface tool centric.  The model is based on windowed lists
and dialogs for performing library management.  To improve the
library management for development, a unique object centric user
interface is employed for software library management.  In the Figure
is the aforementioned object centric user interface.  The approach is
to provide visual relationships of graphic elements for effective
communication of the hierarchy of library management as a whole.  The
structure is described in this document.

      A consistent model of the project is presented to the user for
all operations of the software library management.  Operations on
objects are provided through context menus.  The context of the menu
is directly related to the object.  The user will establish a
relationship of the object and operations on it.  The process is
object centric which will lead the user.

      The hierarchy presentation will eliminate screen clutter and
provide effective transversal and selectability of the information
for products.

      The structure is the following.  The project is the root node.
Under a project is the user node and component nodes.  Under
components is the access list and notification list.  Multiple
projects can be added to this client area.

      To check the access list for a component, the customer simply
opens the access list node...