 Welcome to the Phase Conformance Test Suite Learning Series. This learning series is intended for those users who are interested in learning how to use the Conformance Test Suite, those who have experienced issues with the CTS, or want to develop with the FACE Technical Standard, version 3. The CTS Learning Series contains high-level topics called chapters, which contain instructional videos. The intention is to provide instructions from setting up a CTS environment to successfully testing a FACE Unit of Conformance, or UOC. Each chapter will first provide an introductory video to introduce the topic of that chapter. Each video in each chapter will cover different, yet interconnected information. At the end of each video, there will be a section describing the next video in the series. There is only one video in Chapter 1, which is this video. Let's get started. By the end of Chapter 1, the user will be able to understand basic background information required to use the CTS, understand the basic required inputs to test software with the CTS, understand the CTS's usage in the FACE Conformance process, and understand the CTS's operation at a high level. The CTS is an essential tool in the effort for a software supplier to achieve FACE Conformance for their UOC candidate. The CTS allows for VA's, or verification authorities, to easily test FACE Conformance requirements that are machine testable. This greatly reduces the time required to investigate FACE Conformance requirements within a particular UOC. It also allows the user to preliminarily test their UOC candidate while in development, before formally submitting the candidate for verification. There are multiple versions of the CTS, as shown. The CTS corresponds to a major version number and core-agendum version number of the FACE Technical Standard. For example, for FACE Technical Standard 3.0, the CTS is named CTS 3.0. This is then followed by an update number, starting at 0, meaning initial release, and incrementing by 1 for each public release to the FACE Consortium. The most up-to-date released versions of the CTS are found on www.opengroup.org, slash FACE, documents and tools, FACE publications, Conformance test suites. The CTS Learning Series will use CTS version 3 for all videos, unless otherwise specified. The Conformance Test Suite consists of four tools to evaluate a FACE Unit of Conformance, or UOC, four conformance to the FACE Technical Standard. The tools include the USMIDL Generator, slash DIG, which stands for Data Model to IDL Generator, IDEAL, the DMVT, which stands for Data Model Validation Tool, slash DAVT, Data Architecture Validation Tool, and the FACE Conformance application. Although the series is focused on using the CTS as a whole, it is important to understand the basics of the FACE Technical Standard, FACE Data Models, and how the CTS operates. This video will cover the basics of the Technical Standard, Data Models, and how the CTS operates, but more detailed information is contained in the CTS User Manual and the FACE Technical Standard. The FACE Technical Standard defines architectural segments, interfaces, requirements of each software component of the reference architecture, and APIs required by a UOC. This also includes APIs that are not allowed to be used by UOCs. The Technical Standard also lists other specific standards that must be included for FACE Conformance, as required. Finally, the FACE Technical Standard defines a data architecture to ensure the data is fully described when communicated between software components. In order to achieve FACE Conformance, the writer of a FACE UOC must perform the necessary steps in the FACE Conformance process. This includes having a verification authority, or VA, to verify that the UOC is fully conformant to the FACE Technical Standard. This is an intensive process where the VA tests the UOC in question for allowed and disallowed APIs and interfaces via the CTS and via manual inspection, as some tests are not machine testable. After a VA has verified a UOC, the software supplier must submit their verified UOC to the FACE Certification Authority, or CA, and FACE Library Administrator to be fully FACE Conformant. The CTS tests for conformance to the FACE Technical Standard, where only required APIs are defined, implemented, and used, based on the type of FACE segment the UOC is. The CTS also tests all requirements identified in the Conformance Verification Matrix, or CVM, that have the verification method marked Test. Whether the UOC operates as intended is the responsibility of the software supplier. The CTS requires some artifacts to successfully test a UOC. A configured project configuration file and a configured toolchain configuration file are required to test the UOC, while a UOP supplied model, said USM, is optional depending on the type of UOC. The toolchain configuration file, commonly said TCFG, or toolchain, allows the user to define a target environment for a UOC to be tested against. The contents of toolchain configuration files and how to construct them will be expanded upon in future chapters. The project configuration file, commonly said PCFG, or project configuration, allows the user to define UOC-specific options, such as interfaces used by the UOC. The contents of project configuration files and how to construct them will also be expanded upon in future chapters. For now, it is important to note that the user must define the directory for gold standard library generation, or GSLs, in the project configuration file. The face technical standard defines a face data architecture, which includes the idea of a conceptual, logical, and platform data model. The face consortium provides an SDM, or shared data model, which contains high-level conceptual model attributes, logical model measurements, and measurement systems. When required, the software supplier must create a USM, which defines conceptual and logical entities that can use the attributes, measurements, and measurement systems from the SDM to form the platform model. More information about constructing data models will be provided in later chapters, and is already provided in the Face Reference Implementation Guide, or RIG. Now that all required artifacts and background information has been explained, the operation of the CTS tools working together can be accurately described. When a USM is required, it is used to generate header files, which are utilized in some segment-specific tests. This is achieved by generating what is called the gold standard libraries. To do this, the CTS invokes the USM IDL generator, slash dig, to convert the USM into IDL, or interface description language. Then, the ideal compiler is invoked. Ideal generates data structures and typed interfaces based on the user's selected options in the project configuration file. Finally, the Face Conformance application constructs header files based on the typed interfaces that were generated by Ideal and the selected interfaces from the PCFG. These files are generated in the directory where the user specified the GSL directory to be. The user must then write definitions to the generated header files. These are called factory functions. After the factory functions are defined, the user must provide their location to their PCFG file. To test for conformance, users can press the arrow at the top right of the project configuration builder. This first invokes the DMVT, slash DAVT, which checks the USM for correctness. Then, the CTS performs all conformance tests and produces a conformance test report. The CTS also contains a feature to run conformance tests via command line on both Windows 10 and Linux. Both using the graphical user interface and command line are equivalent in function. How to operate the CTS via command line will be detailed in future chapters. Thank you for watching. This concludes chapter 1 of the Face CTS Learning series. In the next chapter, environment setup and installation on CentOS 7 and Windows 10, we will discuss the installation environment of, download of, and the successful start of the CTS.