Glossary
This glossary provides terms and definitions for IBM Engineering Lifecycle Optimization - Publishing.
A
- Access permission
- A privilege that permits the access or use of an object.
- Application server
- A server program in a distributed network that provides the execution environment for an application program.
- Artifact
- An entity that is used or produced by a software or systems development process. Examples of artifacts include designs, requirements, source files, plans, scripts, simulations, models, test plans, and binary executable files.
- Attribute
-
- Descriptive information that provides important details about a module, requirement, discussion, or element.
- A defined quality and values that can be assigned to an artifact. For example, a work item artifact might have a 'priority' or 'severity' attribute.
C
- Class path
- A list of directories and JAR files that contain resource files or Java™ classes that a program can load dynamically at run time.
- Configuration layer
- A customized set of metadata that can be used to configure data sources and variables.
- Connection
-
- A set of properties, such as URI, user credentials, and configuration context that is required to communicate with a specific remote system.
- A resource that contains a data source URL and authentication details, which can be associated to data sources.
D
- Data source
- The source of data itself, such as a database or XML file, and the connection information necessary for accessing the data.
- Data source schema
- An XML or JSON-based file that defines the structure and properties of the data source.
- Document-style report
- The result of running a document template, after supplying any required runtime parameters, is the generated output such Microsoft Word, Excel, HTML, PDF, or XSL-FO formats. This term is not common; often the generic term 'document' is sufficient.
- Document-style report generation
- The process of applying a template to a data provider/source to generate a document-style report.
- Document specification
- The specification of document templates, data sources, and output formats that are used to generate a document-style report. The 'document specification' is referred to as a 'report' in Publishing Document Builder. See also report.
- Document template or template
- A reusable document-style report layout that can be used to set the presentation of part of a query or document-style report definition. Each template includes information about data source schemas, variables, and styles. The file extension of the template is Document Template Archive (.dta). In some cases, a template might call additional variables to be supplied at the time the report is run or executed.
- DOORS® extension language (DXL)
- A scripting language used in IBM DOORS.
E
- Element
- Palette items that can be added to a template.
I
- Iteration
- In agile development, a set period of time in which work is completed. Sprints can vary in length, for example, in the range 1 - 4 weeks, but typically have a fixed duration within a project.
M
- Master page
- The definition of the header, footer, and watermark for a document-style report to generate.
- Metadata
- Data that describes the characteristics of data; descriptive data.
- Module
- A structured document-style report that is composed of multiple requirement artifacts. Structure can be created in a module by modifying the order and hierarchy of the artifacts.
P
- Package
- A product or component that is specifically designed for installation by IBM Installation Manager.
- Post-command condition
- Environmental and state condition that must be fulfilled after document-style report generation. See also pre-command condition.
- Pre-command condition
- Environmental and state condition that must be fulfilled before document-style report generation. See also post-command condition.
Q
- Query
- A specification for a set of data retrieved from a data source.
R
- Repository (repo)
- A persistent storage area for data and other application resources.
- Report
- The specification of the parts of a document-style report to generate, as defined by document templates such as for the table of contents, front cover, body, index, back cover, output formats, and privacy settings in Publishing Document Builder. The 'report' is referred to as a 'document specification' in the Publishing Studio or Launcher. See also document specification.
- Representational State Transfer (REST)
- A software architectural style for distributed hypermedia systems like the World Wide Web. The term is also often used to describe any simple interface that uses XML (or YAML, JSON, plain text) over HTTP without an additional messaging layer such as SOAP.
- Requirement
- A condition or capability that a system must provide. This condition is either derived from user needs or stated in a contract, standard, specification, or other document-style report.
- Resource
- In IBM Engineering Lifecycle Optimization - Publishing, an item that is used in or produced by the document-style report generation process. Resources include document templates, document specifications, scripts, and style sheets.
S
- Schema
- See XML schema.
- Snippet
- In IBM Engineering Lifecycle Optimization - Publishing, a document template that contains only the elements for reuse in other document templates.
- Style sheet
- A set of formatting rules that specify the standard appearance for a document-style report.
T
- Tag
- An identifier that groups related artifacts.
V
- Variable
- In IBM Engineering Lifecycle Optimization - Publishing, a customized data attribute that is defined for a template and whose value can be assigned or calculated when a document-style report is generated.
- View
- A subset of information that can be displayed by applying filters or sorting.
W
- Web application (web app)
- An application that is accessible by a web browser and that provides some function beyond static display of information, for instance by allowing the user to query a database. Common components of a web application include HTML pages, JSP pages, and servlets.
- Widget
- A portable, reusable application or piece of dynamic content that can be placed into a web page, receive input, and communicate with an application or with another widget.
X
- XML schema
- A mechanism for describing and constraining the content of XML files by indicating which elements are allowed and in which combinations. XML schemas are an alternative to Document Type Definitions (DTDs) and can be used to extend functionality in the areas of data typing, inheritance, and presentation.