After completing this course, the student should be able to:
 

	Describe Common User Access (CUA) guidelines which include design principles and models that direct the development of the end user interface
	Explain common Programming Interface (CPI) definitions which specify languages and services software developers can use to develop SAA-compliant applications
	Identify Common Communications Support (CCS) specifications which define the architectures and protocols used to interconnect devices, applications, systems and networks in order to allow the interchange of data

Common User Access
Describes the CUA component of SAA.
 

	Design Principles What the CUA component entails.  The benefits of following CUA standards.  Two CUA design principles.
	PWS Models Three models for the end user interface for use with programmable workstations.
	NPT Models Two models for the end user interface for use with non-programmable terminals.

Common Programming Interface
Examines the CPI component of SAA.
 

	Languages What the CPI component involves.  The benefits of following CPI standards.  The elements of the CPI language set.
	Services The support services interfaces the CPI defines.  The link between the CUA and the CPI.  Relationship of CPI elements to the three components of an application.

Common Communications Support
Describes the CCS component of SAA.
 

	CCS Overview What the CCS component entails.  The origin of elements of the CCS.  Outline of the CCS six-layer communications model.
	CCS Elements Description of the elements in the first three layers of the CCS communications model.
	More CCS Elements Description of the elements in the last three layers of the CCS communications model.  The relationship between the CPI and the CCS.