josh@polaris.UUCP (Josh Knight) (02/26/86)
reposting due to network problems...
%A T.G. Peck
%T Worldwide Systems Engineering
%J IBM Sys. J.
%V 24
%N 3/4
%P 182-188
%D DEC 1985
%X IBM systems engineering celebrates its 25th anniversary in 1985.
This paper provides a perspective of the part systems engineering has
played in the success of IBM in the information processing business
during that 25-year period. The history of systems engineering in
worldwide systems engineer functions are examined. The relationships
among marketing, systems engineering and customers are discussed. Also
discussed are career paths for systems engineers. Expectations and
challenges for systems engineering in the future are explored.
%A W. Boos
%T HONE: The IBM Marketing Support System
%J IBM Sys. J.
%V 24
%N 3/4
%P 189-199
%D DEC 1985
%X The storage, retrieval, and dissemination of data pertaining to a large,
complex product line is made possible by the Hands-On Network
Environment (HONE) discussed in this paper. HONE provides on-line
interactive support to marketing, systems and administrative personnel,
and most recently, to customers. The evolution of HONE is presented.
Discussed in detail are new HONE distributed processing capabilities now
enabled under an advanced network architecture. In that environment,
the processing power and data bases of HONE and the other host systems
will be interconnected and support the speed and processing autonomy of
IBM Personal Computers as workstations.
%A S. Agassi
%T Performance Considerations for a Distributed Data Processing System
Designed for High Availability
%J IBM Sys. J.
%V 24
%N 3/4
%P 200-211
%D DEC 1985
%X The high-availability requirements of computerized systems that are
needed to meet the objectives of the organization are being acknowledged
more and more by the data processing community. The paper presents the
planning process for a distributed data processing system designed to
meet high availability requirements. This process was performed as a
system engineering activity in order to asses the feasibility of the
presented approach, which was proposed to a customer.
%A K.P. Hein
%T Information System Model and Architecture Generator
%J IBM Sys. J.
%V 24
%N 3/4
%P 212-235
%D DEC 1985
%X The advent of integrated, shared-data systems has made it increasingly
necessary to address the applications development process from the
architectural and manufacturing perspective rather than from a
build-as-you-go job shop viewpoint. Although the Business Systems
Planning (GSP) methodology provides an enterprise-wide strategic
Information Systems plan, it is still at an abstraction level that
leaves the traditional gap between "requirements" and implementation
untouched. The Information System Model and Architecture Generator
(ISMOD) tool complements and enhances BSP by mechanizing the planning
process, thus providing a facility to narrow this gap by allowing
orderly and consistent top-to-bottom architectural decomposition of the
enterprise environment. It is an enterprise planning vehicle and not an
implementation system, but it is the first critical component to support
an integrated systems architecture effort. It automates and, to a large
extent, formalizes a laborious requirements documentation process
preceding code development, and it does this "top to bottom," from a
global, enterprise-wide, information requirements viewpoint. This paper
discusses the overall architectural concepts of integrated data systems
development, the place of ISMOD within it, and the specific facilities,
techniques, and information provided by the system.
%A M.M. Ghiotti
%T A Single-System Interface Using the IBM 3270-PC
%J IBM Sys. J.
%V 24
%N 3/4
%P 236-248
%D DEC 1985
%X Many businesses use a variety of terminal types connected to central host
computers. Presented here is a rationale and the experience gained with
a single terminal type -- the IBM 3270-PC -- interconnected with hosts
via the Application Program Interface to achieve enhanced user
efficiency.
%A J. Newton
%T Strategies for Problem Prevention
%J IBM Sys. J.
%V 24
%N 3/4
%P 248-263
%D DEC 1985
%X A philosophy of preventing problems from occurring in a data processing
installation rather than reacting to problems is becoming increasingly
necessary. The institution of comprehensive and formally managed
testing strategies is an important step in this direction. Such
strategies are discussed, and it is shown that they also support
disaster backup/recovery plans.
%A B.M. Yelavich
%T Customer Information Control System -- An Evolving System Facility
%J IBM Sys. J.
%V 24
%N 3/4
%P 264-278
%D DEC 1985
%X Presented is an overview of the present CICS architecture. Discussed
is the evolution of that original design as a transaction management
system that accommodates data base management, operating systems, and
input and output devices as well as hardware of increasing numbers and
complexity. User needs past and present are analyzed with a view toward
understanding how CICS might evolve in the future.
%A R.C. Brooks
%T An Approach to High Availability in High-Transaction-Rate Systems
%J IBM Sys. J.
%V 24
%N 3/4
%P 279-293
%D DEC 1985
%X In business enterprises, it is important that high availability be
maintained in the computer systems used by the enterprises, particularly
in systems that have high transaction rates. A way of maintaining high
availability is discussed, including the implementation that should be
undertaken and the design issues involved. Some additional steps for
further improvements are also offered.
%A B.R. Buckelew
%T The System Planning Grid: A Model for Building Integrated Information
Systems
%J IBM Sys. J.
%V 24
%N 3/4
%P 294-306
%D DEC 1985
%X Information systems have evolved as a result of technological advances
and the increasing demand for information. Over the past few years,
systems that developed separately are being forced to merge. This paper
describes a model for building a set of integrated architectural
guidelines to ensure that a "system" is being built. The use of the
System Planning Grid as a model for setting product standards and
organizational responsibilities will also be discussed.
%A M.W. Mudie
%A D.J. Schafer
%T An Information Technology Architecture for Change
%J IBM Sys. J.
%V 24
%N 3/4
%P 307-315
%D DEC 1985
%X This paper defines a technology architecture for information processing
corporations. It describes a matrix of processing environments
consisting of three processing types: production, decision support, and
office; three processing locations: centralized, departmental, and
workstation; and a methodology for implementing applications in those
environments. Key to the architecture is a supporting framework
comprising the communications network, a data service function, an
office services function, enabling software, and support organizations.
This approach is designed to provide an integrated information system to
support organizations whose business environment is changing, and where
flexibility, responsiveness to change and cost effectiveness are vital.
The approach is representative of methods used by systems engineers in
assisting customers to decide on a system configuration that best suits
their needs.
%A C.P. Grossman
%T Cache-DASD Storage Design for Improving System Performance
%J IBM Sys. J.
%V 24
%N 3/4
%P 316-334
%D DEC 1985
%X This paper discusses three examples of a cache-DASD storage design.
Precursors and developments leading up to the IBM 3880 Storage Control
Subsystems are presented. The development of storage hierarchies is
discussed, and the role of cache control units in the storage hierarchy
is reviewed. Design and implementations are presented. Other topics
discussed are cache management, performance of the subsystem, and
experience using the subsystem. It is shown that a cache as a
high-speed intermediary between the processor and DASD is a major and
effective step toward matching processor speed and DASD speed.
--
Josh Knight, IBM T.J. Watson Research
josh at YKTVMH on BITNET, josh.yktvmh@ibm-sj.arpa
...!philabs!polaris!josh