Technical data

Phoenix

Getting Started Guide

» This type of architecture is called a plug-in architecture because compo-

nents or plug-ins, which are discrete functional units in Phoenix, can be

added and removed without affecting the core application. Each plug-in

provides a specific function. Descriptive statistics, noncompartmental anal-

ysis, and linear mixed effects modeling are all plug-ins created for use with

the Phoenix platform.

»A plug-in is a “black box” that performs some operation on input data and

outputs the results. Plug-ins are referred to internally as operational

objects. An operational object is an object in Phoenix that performs a func-

tion, such as analysis or data manipulation. An operational object is the

smallest functional unit within Phoenix.

» Using Pharsight’s API, any developer can create new functions and add

those functions to the Phoenix platform without compromising the stability

of the application. Phoenix at its core does not carry out any useful analytic

tasks. Phoenix requires plug-ins in order to perform any meaningful analy-

sis.

» Phoenix allows users to work in an MDI (Multiple Document Interface) or

an SDI (Single Document Interface) environment. Workflows, operational

objects, and data sets can be opened in their own window separate from the

main Phoenix interface, or users can choose to work completely within the

Phoenix user interface.

Phoenix Terminology

This section contains terms that are unique to Phoenix and are used throughout

the application.

» BQL Rules folder - contains BQL rule sets.

» Code folder - contains PML and WinNonlin ASCII code. Also contains

NONMEM, S-PLUS, and SAS scripts, as well as any imported text or rich

text format (*.rtf) files.

» Columns tab - tab used to display column headers when a worksheet is

selected. The Columns tab allows users to change column header names,

change column data types to either numeric or string, assign units to a col-

umn header, and change the way data is displayed a worksheet.

» Context associations - context associations are inputs in an operational

object. These inputs must have a data type mapped to them. Examples of