Last modified 12 years ago Last modified on 10/15/09 23:00:42

0. The Setup

This is a step-by-step tutorial for installing the tools used during Sophie 2.0 development.

Accounts creation. In order to communicate with team members, you must create the following accounts:

  • Google groups: Developers Mail Group, Users Mail Group.
  • Skype account: provide it to our Human Resource Manager and you will be included in the group chat.
  • SVN/Trac accounts: ask someone from the team for these.

Workstation setup. Every machine in the office should have at least two users: one for private usage (you choose your username and password) and one for public usage(ask a team member for the username and password). A text editor is necessary (for example, Notepad++, you can download it from Other important software: web browser, PDF reader, Flash player, Skype, Sophie (

SVN setup. Subversion (SVN) is the version control system that we use. On Windows you can use TortoiseSVN (download it from The official site of SVN is There you can find SVN binaries for other OSs. You must install the Subversion client in order to continue to the next step.

Repository setup. Once you have installed SVN, you can download the repository on your own machine. Basically, this means that you will have your own copy of the project. In Windows, just select a folder on your drive, right click and select SVN Checkout. Further explanation for the repository links / structure / rules for committing can be found at PLATFORM_STANDARDS_REPOSITORY. Before you continue on to the next step, you should know how to submit a file to the repository (for example, your daily report).
1) Create the new file in the desired folder (for reports, it is /manage/reports/{current iteration}/. The format of reports is explained below, in the "Process" chapter).
2) Use "svn add" to schedule the file for committing to the repository.
3) Use "svn commit" to commit it. Attention: committing without comment is NOT allowed!
A sample book concerning subversion can be found at

JDK. Since Sophie 2.0 is written in Java, it requires the Java Development Kit (JDK) to develop for it, and Java Runtime Environment to run it. JDK can be downloaded and installed from

Maven setup. Maven is a software tool for Java project management and build automation. Downloads and installation instructions are located at A tutorial for building with Maven has been written and is available here: PLATFORM_DEPLOYMENT_BUILD_MAVEN. If you build the project with maven, you would probably need to open sophie2-platform/old/lib/readme.txt and read the lines at the end.

Eclipse setup. The software platform we use for developing Sophie 2.0 is Eclipse. First of all, the installation: Download the latest Eclipse version from and install it to your computer. Then, modify your compiler settings according to the COMPILER_SETTINGS document. The next two steps, Subclipse installation and Maven integration, are described in PLATFORM_INFRASTRUCTURE_OVERVIEW. The most important for these is that they are Eclipse plugins, which integrate the subversion and maven functionalities in Eclipse. The M2 plugin is required for loading our maven project in Eclipse. Once you have installed the plugins, you can follow the steps from PLATFORM_DEPLOYMENT_BUILD_ECLIPSE, which describes how to import Sophie 2.0 in Eclipse and run the FakeAuthor configuration.
You now have everything you'll need to develop for Sophie 2.0! :)

1. The Project

The Goal. The most important aspect of a project is its goal. Our project's goal is to take the all of Sophie 1.0's best aspects and to optimize them, while at the same time adding new features and removing others.

Schedule. The Sophie 2.0 project is organized into approximately 600 tasks, each with one or more revisions (in total approximately 2000). These tasks have several states, and you will learn about them in the next chapter. The tasks are divided into 12 sprints (iterations). Each sprint is approximately one month long. The methodology used for the project's scheduling is not exactly SCRUM, but is similar to SCRUM. For more information as to what SCRUM means, you can read

Layers. Task names are also grouped into several development layers:

  • PLATFORM: specifies coding standards, platform structure, plugin structure, as well as tools for building the project.
  • CORE: the smallest layer; it provides fundamental functionalities for every part of the platform. It includes the properties library (ProLib), logging, and modularity.
  • BASE: provides basic GUI (menus, halos, palettes, layout).
  • MAIN and EXTRA: these contain the main functionality, which makes Sophie 2.0 a complete platform. They are split according to dependencies, so that MAIN does not depend on EXTRA.
  • SCS: Sophie community server. It includes the Trac system we use, the Subversion, and provides information for the external contributors.
  • S2S: Sophie 2.0 server. This is the server product.
  • SUPPORTING_ARTIFACTS: the project schedule, the backlog, and the process are categorized as supporting artifacts.
  • END_PRODUCT: here are a few tasks related to application tuning and the creation of user help.

Additional. The non-development side of the project is described in the PROJECT_OVERVIEW document. This includes information about Astea Solutions, Sophie, the license we use, and other things you may find interesting and useful.

2. The Process

This chapter includes the states of each task until it is completed, the rules you have to follow when performing a task, including some good/bad examples.
Generally speaking, every task must first be analyzed, then a design must be prepared, and finally the design can be implemented. If the task is a coding one, its implementation is tested. After each phase, a review is made. The tasks, sorted by iterations, can be looked at The exact task states and much more are described and regularly updated at PROCESS. This document is fundamental, so read it carefully. Also, tasks are of several different types. For an explanation what the types are, read PLATFORM_STANDARDS_GENERAL.
Every state of a task is important. However, here are our current recommendations for performing various actions:

The process is executed with the help of Trac, which is the issue tracking system we use. If you have problems using it, please go to TracGuide.

3. The Product

Design. Here can be found some of Sophie 2.0's main design features.

  • Plugins: software units. In the context of our project, "plugin" is the same as a module or bundle. In Eclipse, these are actually represented as different projects. Have a look at platform structure. There you can see where modules are located and what their structure is. Decomposition to plugins of Sophie 2.0 is one of the most important things that can be dome for the project. If you need to create a new module, one way to do this is described in how to create a new module.
  • Extensions / Extension points: these are used to reverse the dependencies so that we do not have cyclic dependencies in the project. The other advantage of extensions is that they provide extensible functionality.
  • Editions: different standalone subsets of the Sophie 2.0 platform. Sophie 2.0 has three editions: Author, Reader, and Server. The page dedicated to editions provides information about the plugin editions structure.
  • Distributions: the distribution is the end product a user will see on his/her hard drive after installing the edition. In order to be fully functional, a distribution has to provide executables and/or some other needed resources. The problem here is the way in which we provide these items, and the solution is the /distrib directory (look again at platform structure).
  • High-level design: this refers to the Model-View-Controller (MVC) design pattern. Its purpose is to define how the model and view interact with each other. There is an MVC tutorial at CORE_MVC_BASE. There is a problem with the standard MVC pattern: it is too complicated for this particular project. This is why Properties are introduced here. Therefore, each model in Sophie 2.0 is defined by a property. This way the controller is replaced by Logics and this simplifies the whole pattern. The properties are represented by the ProLib library, and you can read the important Properties tutorial here: PRO_LIB_CORE_TUTORIAL. This page defines useful code templates for properties.

4. Extras

You will likely encounter a problem you will not be able to resolve on your own. You can always find help in:

Useful Links:


You can write your comments here.