Development process » History » Version 56
Greg Burri, 03/04/2011 12:34 AM
1 | 3 | Greg Burri | h1. Development process |
---|---|---|---|
2 | 1 | Greg Burri | |
3 | 54 | Greg Burri | Here is a little list of the development stages involve in Aybabtu. |
4 | 2 | Greg Burri | |
5 | 54 | Greg Burri | # [[Brainstorming]]. |
6 | # [[Functional definition]]. |
||
7 | # Defining of technologies, [[libraries]] and [[tools]]. |
||
8 | # Creating of some [[prototypes]] to validate the point above. They will be reused during the implementation stage. |
||
9 | 56 | Greg Burri | # Technical specifications. [[Protocols]], [[algorithms]] and [[persistent data]]. Some prototypes can be added to test algorithms or anything else. |
10 | 54 | Greg Burri | # [[Architecture]] of components and theirs interface. -> Component Diagrams. |
11 | # Modeling of each components. -> Class diagram, sequence diagram, state diagram, etc.. |
||
12 | # Implementation of each component with unit tests, unit benchmarks, and code coverage. Once a component is near finished, a another person of the team will read the code and criticize it. |
||
13 | 53 | Greg Burri | # Alpha version. |
14 | 46 | Greg Burri | ** All features are implemented. |
15 | 54 | Greg Burri | ** Only developers have access to it |
16 | 51 | Greg Burri | # Beta versions. |
17 | 54 | Greg Burri | ** The tag _1.0.0 beta1_ is created. |
18 | 52 | Greg Burri | ** Testing with people who didn't participate in the project. |
19 | 53 | Greg Burri | ** Profiling, optimizing, simplification and stabilisation. See [[Stabilisation process]] |
20 | 51 | Greg Burri | ** After some corrected bugs an another beta is created if necessary (beta1, beta2, etc..). |
21 | 1 | Greg Burri | # Final Release \o/ |
22 | 55 | Greg Burri | ** The _1.0_ branch is created |
23 | 54 | Greg Burri | ** The tag _1.0.0_ is created |
24 | 45 | Greg Burri | # Define the future integration workflow[1] with _git_ and Goto 1.. |
25 | |||
26 | fn1. http://www.whygitisbetterthanx.com/#any-workflow |