SAA

Systems Application Architecture (SAA) is IBM's blueprint for future software development in any organization using or interacting with IBM computers. It represents IBM's attempt to bring order to the chaotic world of computer software and software development.

Grochow's text addresses the many questions that arise concerning the emergence of SAA. It tries to reduce the uncertainty that organizations, software developers, and end-users have towards the challenge of SAA. SAA: A Guide to Implementing IBM's System Application Architecture provides readers with both technical and managerial perspectives on what it means to implement IBM's System Application Architecture.

• Part I: What Is SAA?
  1. A Common Strategy
  1. Simple Concept, Difficult Implementation
  2. The Four Components of SAA
  3. Common User Understanding
  1. The Need for a Consistent Interface
  2. The SAA Solution: Common User Access
  4. Common Developer Understanding
  1. The SAA Common Programming Interface
  2. Object-oriented Environment
  3. Relationship of CPI and CUA
  5. Distributed Computing Strategy
  1. Variations of a Theme
  2. Common Communications Support in SAA
  3. Relations of CCS and CPI
  6. Enterprise Computing Strategy
  1. Enterprise Applications
  2. Enterprise Data
  3. An Approach to Application Portability
  7. Implementation
  1. SAA Evolution
  2. Major SAA Software Announcements
  8. The SAA Logo
  1. The "New" SAA Logo
  2. Adding Color
  9. The Impact of the Common Strategy
  2. Operating Environments
  1. SAA Operating Systems
  2. Role of "Participating Environments"
  1. CICS and IMS Data Communications in SAA
  2. VSE's Relationship to SAA
     A Nor-participant: PC-DOS
  3. Relationship of AIX to SAA
  3. Common User Access
  1. Goals of CUA
  1. Familiar, intuitive Environment
  2. Consistent Environment
  2. The Development of CUA
  1. The First CUA Definition
  2. The Second CUA Definition
  3. Future CUA Definition
  3. CUA Advanced Interface
  1. Graphical Model
  2. Workplace Model
  4. CUA Basic Interface
  1. Text Model
  2. Entry Model
  5. Implementing CUA-Conforming Applications
  4. Common Programming Interface
  1. Languages
  1. COBOL
  2. FORTRAN
  3. C
  4. RPG
  5. PL/I
  6. Procedures Language
  2. Application Generator
  1. Application Development
  2. Application Execution
  3. Support Services
  1. Presentation Interface
  2. Dialog Interface
  3. Database Interface
  4. Query Interface
  5. Communications Interface
  1. Hidden Communications in Enabling Software
  6. Repository Interface
  4. Other Application Support Services
  1. Help
  2. Application Manager
  5. Distributed Data
  1. Distributed Relational Data
  1. Implementation in DB/2 and SQL/DS
  2. Implementation in OS/2 EE Database Manager
  2. Distributed File Management
  5. Common Communication Support
  1. OSI vs. SNa vs. SAA
  2. Using the Layered Model
  2. Data Link Controls
  1. Local Area Network Data Link Protocols
  1. Token-Ring
  2. Other Networks
  2. Synchronous Data Link Control (SDLC)
  3. X.25 Packet Switched Networks
  3. Network
  1. SNA Type 2.1 Node Architecture
  4. Session Services
  1. Program-to-Program Communications
  1. Implementation and the CPI
  5. Application Services
  1. Document Interchange Architecture
  2. SNA Distribution Services
  3. SNA Management Services
  4. Distributed Data Management Architecture
  5. Distributed Relational Data Architecture
  6. OSI Application Layer Service
  6. Data Streams
  1. Document Context Architectures
  1. Mixed Object
  2. Revisable Form Text
  2. 3270 Data Stream
  3. Intelligent Printer Data Stream
  4. Character Data Representation Architecture
  7. Objects
  8. CCS Summary
  6. OfficeVision: SAA Application Software
  1. General Capabilities
  2. An SAA Software Family
  1. OfficeVision Application Architecture
  3. Cooperative Processing in OfficeVision
  4. Common User Access in OfficeVision
  1. The OfficeVision Workplace
  5. Integrating Other Applications
  6. The (Possible) Paperless Office
  7. AD/Cycle: The SAA Application Development Environment
  1. The Tools of AD/Cycle
  2. Application Development Platform
  3. The Repository
• Part II: Implementing SAA
  8. The SAA Implementation Plan
  1. Issue Locator
  2. Major Steps in the Implementation of SAA
  3. Implementing the Plan
  1. Creating the SAA Planning Committee
  2. Technology Transfer Issues
  1. Impact on the IS Department
  2. Who Is the Agent of Change?
  3. Assessing the Risks in the Plan
  4. The Cost of SAA Implementation
  5. Measuring Success
  1. Quality and Productivity in the Organization
  2. Establishing Productivity and Quality Measures
  1. Productivity Measurement
  2. Quality Measurement
  3. SAA Impact Measurement
  9. A Basic Strategy
  1. Issue Locator
  2. Outline for an "SAA Statement of Direction"
  3. Basic Strategy
  1. Commitment to the System Application Architecture Approach
  1. Viewing Computing as an "Enterprise" Resource
  2. Creating an Application Architecture
  2. Overall Implementation Strategy
  3. Common User Access
  4. Common Programming Interface
  5. Distributed and Cooperative Processing
  6. Operating System and Enabling Software
  7. Hardware and Communications
  8. Application Development Environment
  9. Training
  10. Creating a Strategic Software Architecture
  1. Issue Locator
  2. Developing An Application Architecture
  1. Defining Application Architecture
  2. Tiered Application Functions
  3. SAA and Application Architecture
  3. What Does "Object-oriented" Really Mean?
  1. A Brief Tutorial on Object-Orientation
  1. Formal Definition
  2. Design and Analysis
  3. Development
  2. What About Object-oriented Databases?
  3. Why Are Object-Oriented Systems So Important?
  4. Selecting a Programming Language
  1. C vs. COBOL
  1. What Happened to Pascal?
  2. Scientific and Engineering Languages
  3. A Role for Ada
  4. Artificial Intelligence Languages
  5. Other Architectures
  1. The UNIX Strategy
  2. Digital's Application Integration Architecture and Network Application Support
  3. Unisys's Solution Generation Environment
  6. The Importance of SAA Compliance
  1. Viewpoint of a Software Vendor
  1. What Will They Really Do?
  2. How Can You Tell If Software Is SAA Compliant?
  1. SAA Compliance As a Software Selection Criterion
  2. IBM's Role
  11. Designing for Common User Access
  1. Issue Locator
  2. What CUA Means
  1. Providing Consistency
  2. Allowing User Control
  3. Providing Feedback
  4. Hiding Complexity
  5. Object-Action Orientation
  6. Avoiding Modes
  3. Picking the Right CUA Model
  1. Performance Implications of the Text Model on NPTs
  2. Designing Applications to Use Multiple Windows
  4. Implementation Alternatives
  1. Presentation Manager, Dialog Manager, and Easel
  1. SAA Compliance with PM, DM, and Easel
  2. Is Windows a Viable Choice?
  3. Implementing the CUA Workplace Model
  4. Implementing CUA on the NPT
  5. Implementations in Other Environments
  1. The X Window System
  2. OSF/Motif
  3. NewWave
  12. Designing Cooperative Processing Applications
  1. Issue Locator
  2. Distributed Processing
  1. Drawing the Line
  2. Developing a Distribution Strategy
  1. An Example
  3. Rules of Thumb for Cooperative Processing
  4. Two-Tier vs. Three-Tier Architecture
  5. Performance of Distributed Applications
  6. Distributed Processing and Network Traffic Patterns
  3. Transparency and Single-system Image
  1. A Conceptual Model of System Transparency
  2. An Expanded Role for the PWS
  1. A Dual Strategy: NPT and PWS
  4. Distributing Data
  1. Distributed Data Strategies
  2. Client-Server Strategies
  1. Remote Data Services
  2. Distributed Data Management
  3. The X Window System
  4. Third Party Client-Server Systems
  3. Database Design for Portability
  5. Developing Distributed and Cooperative Processing Among SAA and non-SAA Applications
  1. Cross-Vendor Solutions
  6. Using Distributed Functions in Enabling and System Software
  1. Remote Procedure and Data in OS/2 EE
  2. CICS OS/2
  1. Software Update via the Host
  3. Program-to-Program Communications
  13. System Control and Application Enabling
  1. Issue Locator
  2. System/370 Operating System
  1. What About Batch Processing?
  2. CICS and IMS/TM
  3. OS/400: An Object-oriented Approach
  4. The Strategic Role of OS/2 EE
  1. Assessing OS/2
  2. OS/2 vs. DOS for Developers
  3. OS72 as a LAN Server OS
  4. Installable File System
  5. AIX and UNIX
  14. Hardware and Communications
  1. Issue Locator
  2. Processors
  1. Distributing the MIPS
  2. The Mainframe Will Still Be There
  3. How Many Workstations Are Enough?
  1. Workstation Configurations
  1. The 286 Is Dead; Long Live the 386
  2. PS/2 vs. the Clones
  4. Secondary Storage
  15. Application Development Environment
  1. Issue Locator
  2. Creating an ADE for SAA
  1. The Role of Methodology
  2. Are the Right Tools Available?
  3. Role of the Repository
  1. IBM's Repository
  2. The Repository is a Distributed Database
  3. The Repository in Configuration Management
  1. The Source Code Library Manager
  2. VM/Software Engineering
  4. Relation to the IRDS Standard
  4. An Application Development Environment
  1. An ADE Architecture
  2. Where Do You Do Development?
  1. ASCII to EBCDIC and Back Again
  3. Selecting Your Tools
  1. AD/Cycle Tools to Implement SAA
  16. Education and Training
  1. Issue Locator
  2. SAA Education As an Ongoing Process
  3. Developing a Common Curriculum
  4. SAA Publications
  5. SAA Support Organization
  17. What About the Future?
  1. Filling in the Holes
  1. Common User Access
  2. Common Programming Interface
  1. Non-relational Databases
  3. Common Communications Support
  4. Environments
  2. SAA and Open Systems
  3. Future Architectures
  4. Future Outlook

It's hard to believe anyone fell for this. Still, there is interesting concepts in here, and if nothing else, you may sound like an authority to the younger programmers in the company if you learn the lingo.