Source

Kephra / doc / CompleteProgramming.pod

=head1 Complete Programming

This document describes the method the Kephra editor is developed with.
Its highest aim is to have at all times a usable program with the
highest quality at all levels while still letting programming be fun.


=head2 Overview

=head3 DISCLAIMER

I strongly dislike strict rules imposed on me and made fun of people that
produce theories with three letter acronyms that try to be the answer to everything.
But now I am standing here, trying to "sell" you yet another programming methodology.
That IS irony, isn't it?

=head2 Rational

Well, several reasons brought me here.

1.) All methodologies I know of overlook several aspects of the product.
    That includes even "documentation driven development",
    which gave important impulses for the creation of CP.

2.) I always wanted a sane balance between the old bureaucratic waterfall method
    and a bit too shortsighted, modern extreme or agile programming, combining
    sound planning and practicability.

=head2 Main Goal

Highest aim is the conscience the code is produced with. A superb overall
user experience as well as good code quality should be result of it. 


=head2 Phases of Development

Even if productive software is never done and you wand to get something usefull


=head3 Defining Task

main task

aprox. feature set

parts to do
   * documentation (user, programmer, comments)
   * logic
   * tests
   * supply libs 
   * visuals
   * configs

resources

what kind of team to solve it with

what technologies, languages, libs, os, other tools
fallback alternatives or areas you might expand into

=head3 Early Development

=head3 Normal Development

=head3 Maintenance



=over 4
=item * 
=back