Have a look at the right side of your screen. This is the Project Explorer window, and within it two tabs are visible.
The first - the Project Browser tab - contains a reference to all group, application and test nodes created for the active project. The project node, named BaseStation, contains an application node named BaseStation; the application node contains a list of all of the source files required to build the UMTS base station application. (Though the project and application nodes have the same name, this is not a requirement.)
The second tab - the Asset Browser tab - lets you browse all of your source and test files. If the selected Sort Method is By File, you are presented with a file-by-file listing of test scripts, source code and source code dependents (such as header files). Note how each header file can be expanded to display every class, function, and method declaration, while each source file can be expanded to display every defined object and method or function. Double-clicking any test script/source file/header file node will open its contents within the OneTest Embedded editor; double-clicking any class declaration or method definition node will open the relevant source file/header file to the very line of code at which the definition/declaration occurs.
There are two other sort methods as well on the Asset Browser. The first, By Object, lets you filter down to classes and methods, independent of the source files. The second, By Directory
You may have noticed along one of the toolbars at the top of the UI that the TDP you selected in the New Project Wizard is listed in a dropdown box. In fact, this is not a reference to the TDP, it is a reference to the Configuration whose base TDP was the one you selected in the wizard - in the case of this tutorial, it is a TDP supporting C++. (Recall that the Configuration allowed you to select the TDP designed for use with C language files. Configurations are initially named after their base TDP, but this name can be changed.) Should you have multiple configurations for the same project, use this dropdown box to select the active Configuration for execution.
Finally, to the right of the Configuration dropdown list is the Build button. This button is used to build your application for application nodes and the test harness for test nodes. The test harness consists of:
source files needed to build the application of interest
a test driver
The Build Options button lets the user decide from which point the build process should initiate and what runtime analysis features should be used. The runtime analysis features do not have to be used at the same time; this Build Options window provides a quick and simple method for deselecting undesired runtime analysis features immediately prior to execution of the build process.
Armed with this knowledge, proceed to Exercise Two.