BASE - Development information - Development process

Development process

NOTE! This document is outdated and has been replaced with newer documentation. See Development process and other important procedures

This document describes the development process we try to use in this project. This is not carved in stone and deviations may occur.

Last updated: $Date: 2011-06-27 14:06:13 +0200 (må, 27 jun 2011) $

For each part in the development we should follow the following procedure:

1. Group meeting

The group should have a short meeting and discuss the current situation. Problem areas should be identified (not solved!).
A single meeting may of course discuss several boxes.
A follow-up meeting should be held at the end of the analysis phase.
The person who is going to make the analysis, design and development is responsible for taking notes. They should be kept until the analysis and design phase has been finished.

2. Analysis and design

Create an diagram of the classes including their properties, links and associations. Use the already existing diagrams and code as a template.
The diagram should also have information about cache and proxy settings.
Write a short document about the diagram, especially things that are not obvious and explain any deviations from the recommendations found in the data layer coding guidelines.
If there are any problems with the existing code, these should be solved at this stage. Write some prototype code for testing if necessary.
Group meeting to verify that the specified solution is ok, and to make sure everybody has enough knowledge of the solution.

3. Create the classes for the data layer

If step 2 is properly done, this should not take long.
Follow the data layer coding guidelines
At the end of this step, go back and have a lock at the diagram/documentation from the analysis and design phase and make sure everything is still correct.

4. Create the corresponding classes in the core layer

For simple cases this is also easy. Other cases may require more effort.
Most of the code already exists in one form or another. To a great extent it is just a matter of rearranging everything.
If needed, go back to the analysis and design phase and do some more investigations. Make sure the documentation is updated if there are changes.

5. Create test code

Use the existing test code. In most cases it should not require any big modifications.

6. Problems

If you encounter any problems, arrange a group meeting. Someone else may have the solution!