Each object consists of a set of groups combining different object fields and links to other objects. An object has at least one group and one field or one link to other object. In the generated application each object will be represented by the corresponding database table; each field by the corresponding field in the table; each link by one or two fileds in the table and possibly by some intremediate table depending on type of link.

By default Atlantis Universe Object Editor generates 2 application forms for each class:

• The form for view and modify the properties for the single object instance (ObjectNameDetail).
• The form showing the list of all object instances in the database and allowing managing the list: add, modify, delete the instances; perform search an instance in the list specifying the custom conditions (ObjectNameList).

The trial edition allows you only to backup your Delphi settings: in order to restore them, you'll have to buy full version. 2012-05-25: fixed a bug finding infos about third party components.
 
Partially restricted
Source: None

• Dependency Viewer: Displays PE file dependencies, missing functions and libraries.
• PE Viewer: Displays various information about PE file including Borland package information. It is also intended as an example for JclPeImage unit.
• ToolHelp Viewer: Displays list of currently running processes on the system and many related information.
• Resource fix utility for Windows 95: Fixes 'Large resources corruption bug'.
• ScreenJPG: Simple tool for converting bitmap to JPEG.

• 1. Source code versions management
• handle multiple projects or libraries with the same program;
• allow tracking source code versions with detailed commits;
• can access to a PVCS tracker (more trackers are coming) and link the commits to the tickets;
• allow automated source code backup (without any commit to document: it’s like a daily snapshot of your files);
• backups can be local (on your hard drive) or remote (on a distant drive);
• you can make a visual "diff" and compare source code versions side by side in the graphical user interface;
• you can see pictures (PNG, JPEG, bitmap, icon) within the main user interface;
• diff storage between version is very optimized, and use little disk space;
• storage is based on .zip files and plain text files, so it’s easy to work with.
• 2. Automated Documentation
• follow a typical Design Inputs -> Risk Assessment -> Software Architecture -> Detailed Design -> Tests protocols -> Traceability matrix -> Release Notes workflow;
• initial (marketing-level) Design Input can be refined into more precise Software Requirement Specifications;
• Design Inputs can evolve during the project life: all documentation stay synchronized and you will have to maintain the DI and their description only at one place;
• therefore, the process is meant to be compliant with the most precise documentation protocols (like IEC 62304);
• only one text file, formated like a Wiki, contains the whole documentation;
• it's very easy to add pictures, or formated source code (Pascal, C, C++, C#, plain text) into the documentation;
• word files are created from this content, with full table of contents, picture or source code reference tables, unified page layout, customizable templates;
• it's easy to add tables to your document, or link to other part or external resources;
• you can even put pure RTF content into your documentation;
• pictures are centralized and captioned, people involved in the documentation are maintained once for the whole documentation;
• document version numbering and cross-referencing is handled easily;
• for Pascal projects, the source code is parsed and all interface architecture is generated from the source;
• it's easy to browse classes, variables and functions from the documentation, and add reference to them to your document;
• the source code description can also be located in an external .sae file, therefore your original source code tree won't necessary be changed by the adding of comments;
• all references are cross-linked: Software Architecture Document is created from the source code, and also is able to highlight the classes or methods - involved in implementing every Design Input, from the Software Design Document;
• integrated GraphViz component, in order to create easily diagrams from plain text embedded into your documentation;
integrated fully featured text editor, with word wrapping, Wiki-syntax buttons and keyboard shortcuts, and spell checking;
• a step by step Wizard is available to create a new project, from supplied template files;
• another Wizard is already available, to browse your documentation workflow, and check its consistency or set up its parameters;
• the documentation is integrated to the Version tracking system above.

• Set up the options on screen, then apply them to your selected projects.
• Includes the option to only apply certain settings, while leaving other existing settings alone.
• Save and Load profiles for easy switching between eg. Release and Development.
• Build all projects with the required options withing the program.