DistributedDevelopment - Revision history

JaroslavTulach at 07:56, 14 August 2017

JaroslavTulach — Mon, 14 Aug 2017 07:56:08 GMT

←Older revision		Revision as of 07:56, 14 August 2017
Line 1:		Line 1:
-	Style of development that assembles the final application from pieces produced by many independent groups working on their own schedule, on their own projects. Greatly reduces time to market. Reduces total cost of ownership, yet increases the unpredictability of schedule - One needs to be ready that ~~downstream~~ projects fail to produce their deliverables on time and adapt own schedule to that.	+	Style of development that assembles the final application from pieces produced by many independent groups working on their own schedule, on their own projects. Greatly reduces time to market. Reduces total cost of ownership, yet increases the unpredictability of schedule - One needs to be ready that upstream projects fail to produce their deliverables on time and adapt own schedule to that.

	This style of development also heavily relies on concept of [[BackwardCompatibility]]. Only if, things that used to work in previous version of a library, continue to work in new version, one can upgrade pieces of a system without being afraid of destabilizing its previous functionality.		This style of development also heavily relies on concept of [[BackwardCompatibility]]. Only if, things that used to work in previous version of a library, continue to work in new version, one can upgrade pieces of a system without being afraid of destabilizing its previous functionality.

JaroslavTulach at 10:24, 30 September 2008

JaroslavTulach — Tue, 30 Sep 2008 10:24:18 GMT

←Older revision		Revision as of 10:24, 30 September 2008
Line 1:		Line 1:
	Style of development that assembles the final application from pieces produced by many independent groups working on their own schedule, on their own projects. Greatly reduces time to market. Reduces total cost of ownership, yet increases the unpredictability of schedule - One needs to be ready that downstream projects fail to produce their deliverables on time and adapt own schedule to that.		Style of development that assembles the final application from pieces produced by many independent groups working on their own schedule, on their own projects. Greatly reduces time to market. Reduces total cost of ownership, yet increases the unpredictability of schedule - One needs to be ready that downstream projects fail to produce their deliverables on time and adapt own schedule to that.

-	This style of development also heavily relies on concept of ~~backward compatibility~~. Only if, things that used to work in previous version of a library, continue to work in new version, one can upgrade pieces of a system without being afraid of destabilizing its previous functionality.	+	This style of development also heavily relies on concept of [[BackwardCompatibility]]. Only if, things that used to work in previous version of a library, continue to work in new version, one can upgrade pieces of a system without being afraid of destabilizing its previous functionality.

JaroslavTulach at 06:41, 24 August 2008

JaroslavTulach — Sun, 24 Aug 2008 06:41:14 GMT

←Older revision		Revision as of 06:41, 24 August 2008
Line 1:		Line 1:
-	Style of development that assembles the final application from pieces produced by many independent groups working on their own schedule, on their own projects. Greatly reduces time to market. Reduces total cost of ownership, yet increases the unpredictability of schedule - One needs to be ready that downstream projects fail to produce their deliverables on time and adapt own schedule to that.	+	Style of development that assembles the final application from pieces produced by many independent groups working on their own schedule, on their own projects. Greatly reduces time to market. Reduces total cost of ownership, yet increases the unpredictability of schedule - One needs to be ready that downstream projects fail to produce their deliverables on time and adapt own schedule to that.
		+
		+	This style of development also heavily relies on concept of backward compatibility. Only if, things that used to work in previous version of a library, continue to work in new version, one can upgrade pieces of a system without being afraid of destabilizing its previous functionality.

JaroslavTulach: New page: Style of development that assembles the final application from pieces produced by many independent groups working on their own schedule, on their own projects. Greatly reduces time to mark...

JaroslavTulach — Sat, 02 Aug 2008 19:50:04 GMT

New page: Style of development that assembles the final application from pieces produced by many independent groups working on their own schedule, on their own projects. Greatly reduces time to mark...

New page

Style of development that assembles the final application from pieces produced by many independent groups working on their own schedule, on their own projects. Greatly reduces time to market. Reduces total cost of ownership, yet increases the unpredictability of schedule - One needs to be ready that downstream projects fail to produce their deliverables on time and adapt own schedule to that.