Commits

Herbert Breunung committed 50e8655

main working steps of CP

  • Participants
  • Parent commits 5eff8b4
  • Branches sp3

Comments (0)

Files changed (1)

doc/CompleteProgramming.pod

 
 5.) New tools like hg or git allow new workflows which solve pending problems.
 
+
 =head3 Main Goal
 
 Highest aim of CP is the conscience the code is produced with. As result you get
    * room for experiments and changes without trouble
 
 
-=head2 Phases of Development
+=head3 Principles
 
-Even if productive software is never done and you wand to get something usefull
+   * All code and data of the project go into one repository.
+   * If there is something missing write it down and commit.
+   * There are no development phases in CP. You always try to be productive.
+   * Even the initial list of needed features is part of the documentation.
+
+   * Before implementing new functionality (not just a lib call),
+     write a small prototype with just that function.
+   * There is a seperate branch for all these prototypes to stay in.
+   * When th  
+
 
 
 =head2 Details
 
-=head3 Defining Task
+=head3 Defining Task and completness
 
 main task
 
 
 =head3 Maintenance
 
+Even if productive software is never done and you wand to get something usefull
 
 
 =over 4