Changes between Version 34 and Version 35 of DEVELOPMENT_OVERVIEW

11/26/08 21:34:33 (12 years ago)




    v34 v35  
    4 =0. The Setup= 
     4= 0. The Setup = 
    55This is a step-by-step tutorial for installing the development tools, used during Sophie2 development. [[BR]] 
    66'''Accounts creation'''. In order to communicate with the team members, you must create the following accounts: 
    7  * Google groups: [ Developers Mail Group],  
    8 [ Users Mail Group]. You must have a gmail account to apply for a mambership. 
     7 * Google groups: [ Developers Mail Group], [ Users Mail Group]. You must have a gmail account to apply for a mambership. 
    98 * Skype account: provide it to our Human Resource Manager and you will be included in the group chat. 
    109 * SVN/Trac accounts: ask someone from the team for these.[[BR]] 
    2524You already have everything needed to develop Sophie2 :) 
    27  =1. The Project= 
     26= 1. The Project = 
    2827 '''The Goal'''. The most important part of a project is its goal. So, the goal of our project is to take the good aspects of Sophie and optimize them, as well as to remove the bad ones. [[BR]] 
    2928'''Schedule'''. The Sophie2 project is split into about 600 tasks, each with one or more revisions (totally, about 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 about 1 month long. The methodology used for the schedule of the project is not exactly SCRUM, but is similar to it. For more information what SCRUM is, read []. [[BR]] 
    3938'''Additional'''. The non-development side of the project is described in the [wiki: PROJECT_OVERVIEW] document. There you can read some things about Astea, Sophie, the license we use, and other useful things. 
    41 =2. The Process= 
     40= 2. The Process = 
    4241This chapter includes the states of each task until it is completed, the rules you have to follow when performing a task, some good/bad examples. The "writing reports" thing is also placed here. [[BR]] 
    4342Generally speaking, every task must first be analyzed, then a design must be made, and finally the design is 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 [wiki: PROCESS]. This document is fundamental, so read it carefully. [[BR]] 
    4948The process is executed with the help of Trac - the issue tracking system we use. If you have problems with using it, go to [wiki: TracGuide]. 
    51 =3. The Product= 
     50= 3. The Product = 
    5251'''Design'''. Here will be some of the main design features, which are present in Sophie2.  
    5352 * Plugins: software units. In the context of our project, "plugin" is the same as module, or bundle. In eclipse, they are actually represented as different projects. Have a look at [wiki: PLATFORM_STRUCTURE platform structure]. There you can see where modules are located and what their structure is.[[BR]] 
    5857 * High-level design. This refers to the Model-View-Controller (MVC) design pattern. Its idea is to define how the model and the view interact each other. There is a MVC tutorial at [wiki: CORE_MVC_BASE]. There is a problem with the standard MVC pattern, and it is that it becomes too complicated in this particular project. This is why Properties are introduced here. So, each model in Sophie2 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: [wiki: PRO_LIB_CORE_TUTORIAL]. [wiki: PRO_LIB_CORE_CODE_TEMPLATES This page] defines useful code templates for properties. [[BR]] 
    60 =4. Extras=  
     59= 4. Extras =  
    6160You will certainly encounter a problem you cannot resolve on your own. You can find help:  
    6261 * In the [wiki: FAQ] section