Automated merge with file:///home/gavenkoa/site/hg/admin-doc
authorOleksandr Gavenko <gavenkoa@gmail.com>
Thu, 08 Jan 2009 17:54:50 +0200
changeset 16 b6100dd42e1e
parent 13 137879ea4f4a (current diff)
parent 15 1b3d578ff75c (diff)
child 17 a0c29be69a91
Automated merge with file:///home/gavenkoa/site/hg/admin-doc
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/proj-managment.rst	Thu Jan 08 17:54:50 2009 +0200
@@ -0,0 +1,49 @@
+-*- mode: outline; coding: utf-8; fill-column: 78 -*-
+
+* Cowboy coding.
+
+Software development where the developers have autonomy over the development
+process.
+
+No external management or management that controls only non-development
+aspects of the project, such as its nature, scope, and feature set. (The
+"what", but not the "how").
+
+See:
+
+  http://en.wikipedia.org/wiki/Cowboy_coding
+
+* Waterfall model.
+
+The waterfall model is a sequential development process, in which development
+is seen as flowing steadily downwards (like a waterfall) through the phases of
+requirements analysis, design, implementation, testing (validation),
+integration, and maintenance.
+
+В оригинальной модели водопада Ройса фазы идут в таком порядке:
+
+  1. Определение требований
+  2. Проектирование
+  3. Конструирование (также «реализация» либо «кодирование»)
+  4. Интеграция
+  5. Тестирование и отладка (также «верификация»)
+  6. Инсталляция
+  7. Поддержка
+
+See:
+
+  http://en.wikipedia.org/wiki/Waterfall_model
+
+* Spiral model.
+
+The spiral model is a software development process combining elements of both
+design and prototyping-in-stages, in an effort to combine advantages of
+top-down and bottom-up concepts.
+
+This model of development combines the features of the prototyping model and
+the waterfall model. The spiral model is intended for large, expensive and
+complicated projects.
+
+See:
+
+  http://en.wikipedia.org/wiki/Spiral_model