Introduction to Pathmaker

A Suggested Life Cycle for a Pathmaker Application
Using Pathmaker—An Overview
3–14 067867 Tandem Computers Incorporated
Description of each requester in this application, including:
Name of the requester
Screen layout
End user’s terminal type
Function keys to be used and their associated actions
Data the requester expects to receive as parameters
Data the requester must send to each service invoked (request message)
Data the requester must pass as parameters to each requester invoked
Help text for end user
Service packaging information
Name of the server
List of services that are to be packaged in each server
Note As an alternative to producing a written design document, the application designers can use Pathmaker
development screens to record much of the design information. The resulting catalog can then serve as a
starting point for the application developers.
Planning In this phase of the application life cycle, decisions must be made to allocate the
resources needed to implement the design. These decisions should include:
Identification of team members
Assignment of specific tasks
What equipment is to be used (system, volumes, processors, printers, and so on)
Schedules
Change procedures
Training plan
The Pathmaker product is not generally used for this life cycle phase.