This class manages elements specified on the command line, and produces "specified" and "included" data sets, needed by the doclet environment, as well as querying an elements' visibility or inclusion. A. Initialization phase: the class is initialized with the options table by the caller. Some program elements may not be specified via specific options, such as packages, classes, these are set with the use of setter methods, such setClassArgList and setClassDeclList. B. Scan and decode phase: this is performed by scanSpecifiedItems, to identify the modules specified on the command line, modules specified with qualified packages and qualified subpackages, the modules so identified are used to initialize the module system. C. Intermediate phase: before the final analysis can be done, intermediate methods can be used to get specified elements from the initialization phase, typically used to parse sources or packages specified on the command line. D. Analysis phase: the final analysis is performed to determine the packages that ought to be included, as follows: 1. computes the specified modules, by considering the option "expand-requires", this must be done exhaustively, as the package computation phase expects a completed module graph, in order to check the target of a qualified export is in the included set. 2. computes the packages that must be documented, by considering the option "show-packages", also if only exported packages are to be considered, then also check for qualified packages, and include only those packages whose target is in the included set. 3. compute the specified packages, as part of this, first compute the subpackages and exclude any packages, if required. 4. Finally, compute the types found by previous parsing steps, noting that, all enclosed types (nested types) must also be considered. E. Finally, this class provides methods to obtain the specified sets, which are frozen and cached in the analysis phase, the included sets, are computed lazily and cached for future use. An element can be checked if it should be documented, in which case, the element is checked against the included set and the result is cached, for performance reasons. Definitions: Fully included: an element is included and some or parts of it components are included implicitly, subject to a selection criteria of its enclosed children. Included: if the item should be documented. Rules for processing: 1. A specified element, meaning an element given on the command-line, and exposed via specified elements collections. 2. Expand-contents, an internal pseudo term, meaning it is part of the recursive expansion of specified elements, meaning, the modules are expanded first, then the packages contained in the expanded modules, and then the types contained within the packages, to produce the collections returned by the methods getInclude{Module|Package|Type}Elements(), this is a downward expansion. 3. An included element, meaning it should be documented, and exposed via isIncluded, this enclosing element (module, package) is recursively included.