Phoenix is based on a modular, or component based, framework. This design philosophy results in a flexible and robust application platform for future expansion, promotes interchangeability between major and minor system components, and permits development of new, specialized tools through the use of the Phoenix API (Application Programming Interface). Contact Certara Support for information on contracting with Certara to use the API.
This type of architecture is called a plug-in architecture because components 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 analysis, 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 function, such as analysis or data manipulation. An operational object is the smallest functional unit within Phoenix.
Using Certara’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 analysis.
Phoenix allows users to work in an MDI (Multiple Document Interface) or an SDI (Single Document Interface) environment. Workflows, operational objects, and datasets 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.
A user of Phoenix will create projects that consist of one or more workflows of connected operational objects. For details on these concepts see:
Last modified date:6/26/19
Legal Notice | Contact Certara
© 2019 Certara USA, Inc. All rights reserved.