Browse Prior Art Database

Function Customizing

IP.com Disclosure Number: IPCOM000082361D
Original Publication Date: 1974-Nov-01
Included in the Prior Art Database: 2005-Feb-28
Document File: 1 page(s) / 12K

Publishing Venue

IBM

Related People

Costa, DJ: AUTHOR

Abstract

An application for the customizing of code for users can be treated as a set of logical functions within program boundaries. Some of those functions, such as the code for the updating of a customer's amount due, must be done in whatever way the application has been designed, and cannot be changed without destroying the concept of the application. Other functions, such as the computation of unit cost or unit price, must be done, but the formula used for the computation is open to change. Still other functions, such as the computation of a minimum customer payment to be printed on the statement, are omitted from the application altogether, but could be added without disturbing the application fabric.

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

Page 1 of 1

Function Customizing

An application for the customizing of code for users can be treated as a set of logical functions within program boundaries. Some of those functions, such as the code for the updating of a customer's amount due, must be done in whatever way the application has been designed, and cannot be changed without destroying the concept of the application. Other functions, such as the computation of unit cost or unit price, must be done, but the formula used for the computation is open to change. Still other functions, such as the computation of a minimum customer payment to be printed on the statement, are omitted from the application altogether, but could be added without disturbing the application fabric.

Generally, a function has model records representing fields and calculations supporting that function in the applications. Function 213, for example, might be "credit limit checking", and this function would be represented by model records: - Defining a credit limit field. - Arithmetically comparing credit limit to amount due. - Printing a warning for a high amount due. The model records for function 213 would most likely be widely separated, not contiguous.

Function 213 would, typically, be represented by switch 213.

When switch 213 is on, it means that function 213 has been selected, and model records governed by switch 213 are active when encountered. Each model record is in some way associated with some function, although the connection may not be as simple as in the illustration for function 213. Some model record...