This topic contains the following sections.
Welcome to Phoenix
Phoenix is a web-application that is used by government agencies, non-profit organizations and businesses in the private sector, to provide a central and consistent looking place where users can assembly, collaborate and securely share information with one another. It incorporates data management functions, calendars, blogs and map visualization tools, all in one package.
Phoenix can be deployed on any server running Microsoft Windows and Microsoft Sql Server, and is easily configured to fit in with an organization's current identity and practises.
This help file will attempt to document the Phoenix source code at a technical level.
Phoenix in Action
Phoenix was built with flexibility and adaptability in mind. The Phoenix source code was designed to form a platform on which a grander, more focused implementation of Phoenix would sit. With a few settings and minimal code changes, the entire application can be retooled to fit any market.
Below are screenshots of several implementations of Phoenix Version 2.9.
Who this document is targeted for
The Phoenix technical documentation is mainly for use by software developers that have been challenged to work directly with the Phoenix source code. It contains class documentation right down to the method, so it is ideally suited as a code campanion or reference manual. Individuals working at a higher, more abstract level, may also benefit from the UML diagrams, component diagrams and broader descriptive text.
What this document is not
This is not a manual describing how to use Phoenix. For information on how to use Phoenix, please visit the Phoenix Help Wiki which is available at http://help.decisiontools.ca.
Getting Started
This section introduces the Phoenix environment, terms used through the technical documentation and presents instructions on how to setup your development environment.
Get started now.
System Architecture
The System Architecture section includes Uml diagrams and overviews that describe the various components and how they fit together.
The Phoenix Solution
The Phoenix Solution section discusses how the solution is organized and begins to introduce how each component of Phoenix is implemented.
Phoenix Class Reference
The Phoenix Class Reference section is used as a reference for software developers that require access to the code and class libraries. Every assembly, namespace, class, property, method and event has been documented, including those marked as private. Class diagrams have also been included were needed.
Database Schema
The Phoenix database schema has been documented as much as possible. You will find descriptions of every table and a list of all stored procedures and functions that exist in the database.
