Tech Tree of Choices - Revision history

Marcin: /* Concept */

2020-06-23T23:47:25Z

Concept

← Older revision		Revision as of 23:47, 23 June 2020
Line 1:		Line 1:
	=Concept=		=Concept=
	This is a list of the various possible implementations for a given technology.		This is a list of the various possible implementations for a given technology, for its modules, or for its parts.

	The tech tree is important as it is a survey of possible implementations. The tech tree is particularly important in a Construction Set approach to developing technology because the Construction Set approach can produce different implementations of a technology with less effort than a non-modular approach. Thus, different implementations should be considered and documented. Even though one implementation may be chosen, other implementations should be considered for future work.		The tech tree is important as it is a survey of possible implementations. The tech tree is particularly important in a Construction Set approach to developing technology because the Construction Set approach can produce different implementations of a technology with less effort than a non-modular approach. Thus, different implementations should be considered and documented. Even though one implementation may be chosen, other implementations should be considered for future work.

Marcin: /* Protocol */

2018-04-26T19:22:33Z

Protocol

← Older revision		Revision as of 19:22, 26 April 2018
Line 28:		Line 28:
	=Protocol=		=Protocol=

			#For collaborative editing, use Google Presentations or Coggle to work collaboratively in realtime.
	#Use [[Coggle]] to generate Tree and embed Tech Tree in wiki. You can drag and drop images into Coggle.		#Use [[Coggle]] to generate Tree and embed Tech Tree in wiki. You can drag and drop images into Coggle.
	#Embed the docuement on a wiki page		#Embed the docuement on a wiki page
	#Start a page on the wiki: <nowiki>''http://opensourceecology.org/wiki/Machine or Module Name - Tech_Tree_of_Choices''</nowiki>		#Start a page on the wiki: <nowiki>''http://opensourceecology.org/wiki/Machine or Module Name - Tech_Tree_of_Choices''</nowiki>
	#Use an Edit link at the bottom of the embed so that the image can be updated readily.		#Use an Edit link at the bottom of the embed so that the image can be updated readily.

Marcin: /* Concept */

2017-02-03T16:57:12Z

Concept

← Older revision		Revision as of 16:57, 3 February 2017
Line 2:		Line 2:
	This is a list of the various possible implementations for a given technology.		This is a list of the various possible implementations for a given technology.

	The tech tree of ~~choices~~ is important in a Construction Set approach to developing technology because the Construction Set approach can produce different implementations of a technology with less effort than a non-modular approach. Thus, different implementations should be considered and documented. Even though one implementation may be chosen, other implementations should be considered for future work.		The tech tree is important as it is a survey of possible implementations. The tech tree is particularly important in a Construction Set approach to developing technology because the Construction Set approach can produce different implementations of a technology with less effort than a non-modular approach. Thus, different implementations should be considered and documented. Even though one implementation may be chosen, other implementations should be considered for future work.

	For example, a hay rake can have several implementations - such as a linear rake and a rotary rake. The one that offers the best fit or highest performance to OSE Specification is chosen for the GVCS.		For example, a hay rake can have several implementations - such as a linear rake and a rotary rake. The one that offers the best fit or highest performance to OSE Specification is chosen for the GVCS.

			==Definition of Done==
			The tech tree mapping should take place until the particular [[Working Team]]

	=Implementation=		=Implementation=

Marcin: /* Protocol */

2017-01-25T17:30:35Z

Protocol

← Older revision		Revision as of 17:30, 25 January 2017
Line 27:		Line 27:
	#Use [[Coggle]] to generate Tree and embed Tech Tree in wiki. You can drag and drop images into Coggle.		#Use [[Coggle]] to generate Tree and embed Tech Tree in wiki. You can drag and drop images into Coggle.
	#Embed the docuement on a wiki page		#Embed the docuement on a wiki page
	#Start a page on the wiki: <nowiki>''opensourceecology.org/wiki/Machine or Module Name - Tech_Tree_of_Choices''</nowiki>		#Start a page on the wiki: <nowiki>''http://opensourceecology.org/wiki/Machine or Module Name - Tech_Tree_of_Choices''</nowiki>
	#Use an Edit link at the bottom of the embed so that the image can be updated readily.		#Use an Edit link at the bottom of the embed so that the image can be updated readily.

Marcin: /* Protocol */

2017-01-25T17:30:22Z

Protocol

← Older revision		Revision as of 17:30, 25 January 2017
Line 27:		Line 27:
	#Use [[Coggle]] to generate Tree and embed Tech Tree in wiki. You can drag and drop images into Coggle.		#Use [[Coggle]] to generate Tree and embed Tech Tree in wiki. You can drag and drop images into Coggle.
	#Embed the docuement on a wiki page		#Embed the docuement on a wiki page
	#Start a page on the wiki: <nowiki>opensourceecology.org/wiki/Machine or Module Name - Tech_Tree_of_Choices</nowiki>		#Start a page on the wiki: <nowiki>''opensourceecology.org/wiki/Machine or Module Name - Tech_Tree_of_Choices''</nowiki>
	#Use an Edit link at the bottom of the embed so that the image can be updated readily.		#Use an Edit link at the bottom of the embed so that the image can be updated readily.

Marcin: /* Protocol */

2017-01-25T17:30:05Z

Protocol

← Older revision		Revision as of 17:30, 25 January 2017
Line 26:		Line 26:

	#Use [[Coggle]] to generate Tree and embed Tech Tree in wiki. You can drag and drop images into Coggle.		#Use [[Coggle]] to generate Tree and embed Tech Tree in wiki. You can drag and drop images into Coggle.
			#Embed the docuement on a wiki page
			#Start a page on the wiki: <nowiki>opensourceecology.org/wiki/Machine or Module Name - Tech_Tree_of_Choices</nowiki>
	#Use an Edit link at the bottom of the embed so that the image can be updated readily.		#Use an Edit link at the bottom of the embed so that the image can be updated readily.
	~~#Start a page on the wiki: opensourceecology.org/wiki/Tech_Tree_of_Choices_-(Machine or Module Name). Use official module or machine name from [[Dozuki]].~~

Marcin: /* Sample using Coggle */

2017-01-25T17:20:35Z

Sample using Coggle

← Older revision		Revision as of 17:20, 25 January 2017
Line 22:		Line 22:

	Download full document: [[File:techtreechoices.pdf]]		Download full document: [[File:techtreechoices.pdf]]

	~~=Sample using Coggle=~~

	~~<html><iframe width='1100' height='700' src='https://embed.coggle.it/diagram/52532c8f812beaa94a051f7e' frameborder='0' allowfullscreen></iframe> </html>~~

	=Protocol=		=Protocol=

Marcin at 17:19, 25 January 2017

2017-01-25T17:19:50Z

← Older revision		Revision as of 17:19, 25 January 2017
Line 1:		Line 1:
	=Concept=		=Concept=
	This is a list of the various possible implementations ~~of a working mechanism~~ for a given technology.		This is a list of the various possible implementations for a given technology.

	The tech tree of choices is important in a Construction Set approach to developing technology because the Construction Set approach can produce different implementations of a technology with less effort than a non-modular approach. Thus, different implementations should be considered and documented. Even though one implementation may be chosen, other implementations should be considered for future work.		The tech tree of choices is important in a Construction Set approach to developing technology because the Construction Set approach can produce different implementations of a technology with less effort than a non-modular approach. Thus, different implementations should be considered and documented. Even though one implementation may be chosen, other implementations should be considered for future work.

	For example, a hay rake can have several implementations - such as a linear rake and a rotary rake. The one that offers the ~~most~~ performance ~~according~~ to OSE Specification is chosen for the GVCS.		For example, a hay rake can have several implementations - such as a linear rake and a rotary rake. The one that offers the best fit or highest performance to OSE Specification is chosen for the GVCS.

	=Implementation=		=Implementation=

Marcin: /* Implementation */

2015-12-08T18:16:26Z

Implementation

← Older revision		Revision as of 18:16, 8 December 2015
Line 12:		Line 12:

	To document, it is helpful to use a spreadsheet, google drawing, or other cloud editable format - allowing other contributors to build upon your work in realtime. The. Est strategy would be to save offline copies of cloud documents as backups, while maintaining the working copy editable by anyone in order to foster zero access barriers to collaboration. It has been our experience that vandalism is not a big issue, as previous versions can be restored readily in the document history, just like on the wiki.		To document, it is helpful to use a spreadsheet, google drawing, or other cloud editable format - allowing other contributors to build upon your work in realtime. The. Est strategy would be to save offline copies of cloud documents as backups, while maintaining the working copy editable by anyone in order to foster zero access barriers to collaboration. It has been our experience that vandalism is not a big issue, as previous versions can be restored readily in the document history, just like on the wiki.

			Templates created for the Tech Tree should become commits to our Development Methodology Construction Set - where we build the scalable Development method alongside the GVCS tools.

	=Sample Technology Tree of Choices=		=Sample Technology Tree of Choices=

Marcin: /* Concept */

2015-12-08T18:14:49Z

Concept

← Older revision		Revision as of 18:14, 8 December 2015
Line 5:		Line 5:

	For example, a hay rake can have several implementations - such as a linear rake and a rotary rake. The one that offers the most performance according to OSE Specification is chosen for the GVCS.		For example, a hay rake can have several implementations - such as a linear rake and a rotary rake. The one that offers the most performance according to OSE Specification is chosen for the GVCS.

			=Implementation=
			To document a tech tree of choices, list the different parts, modules, or components of a machine (these should be documented in the [[Systems Engineering Breakdown Diagram]], and list the different ways that these can be implemented.

			To make this clear and understandable to others, you may want to consider using diagrams, screenshots of examples, links to examples, etc.

			To document, it is helpful to use a spreadsheet, google drawing, or other cloud editable format - allowing other contributors to build upon your work in realtime. The. Est strategy would be to save offline copies of cloud documents as backups, while maintaining the working copy editable by anyone in order to foster zero access barriers to collaboration. It has been our experience that vandalism is not a big issue, as previous versions can be restored readily in the document history, just like on the wiki.

	=Sample Technology Tree of Choices=		=Sample Technology Tree of Choices=