Concept - Revision history

Marcin: Redirected page to Conceptual Design

2017-01-24T19:59:40Z

← Older revision		Revision as of 19:59, 24 January 2017
Line 1:		Line 1:
	~~The Design Concept is the first step of implementing the machine Requirement into an actual design.~~		#redirect [[Conceptual Design]]

	The distinction between Requirement and Concept may be unclear - as a Requirement may be so detailed that it specifies actual technology/design choices. In the limit of a fully-detailed Requirement - we have a concept. In the limit of a concept being filled in with technical details - we have a Technical Design.

	~~=Protocol=~~

	~~A concept should be in the form of a cloud, collaboratively editable document such as a google doc which allows various parts of a design to be detailed.~~

	#~~To write a concept, start a google doc based on the~~ [[~~Google Drawing Template]] - click edit below the template to get to the viewable document, and make a copy of the document~~
	~~#Name that document Machine_Name_Concept~~
	~~#Embed in wiki, in a page named Machine_Name_Concept. If there is a naming conflic, add some more words to your title, such as Machine_Name_Version#_Concept.~~


	~~[[Category:Concept~~]]

Marcin at 22:30, 12 October 2013

2013-10-12T22:30:18Z

← Older revision		Revision as of 22:30, 12 October 2013
Line 1:		Line 1:
	The Design Concept is the first ~~implementation~~ of the Requirement into an actual design.		The Design Concept is the first step of implementing the machine Requirement into an actual design.

	The distinction between Requirement and Concept may be unclear - as a Requirement may be so detailed that it specifies actual technology/design choices. In the limit of a fully-detailed Requirement - we have a concept. In the limit of a concept being filled in with technical details - we have a Technical Design.		The distinction between Requirement and Concept may be unclear - as a Requirement may be so detailed that it specifies actual technology/design choices. In the limit of a fully-detailed Requirement - we have a concept. In the limit of a concept being filled in with technical details - we have a Technical Design.

Marcin: /* Protocol */

2013-10-12T22:29:39Z

Protocol

← Older revision		Revision as of 22:29, 12 October 2013
Line 7:		Line 7:
	A concept should be in the form of a cloud, collaboratively editable document such as a google doc which allows various parts of a design to be detailed.		A concept should be in the form of a cloud, collaboratively editable document such as a google doc which allows various parts of a design to be detailed.

	#To write a concept, start a google doc based on the [[Google Drawing Template]].		#To write a concept, start a google doc based on the [[Google Drawing Template]] - click edit below the template to get to the viewable document, and make a copy of the document
			#Name that document Machine_Name_Concept
			#Embed in wiki, in a page named Machine_Name_Concept. If there is a naming conflic, add some more words to your title, such as Machine_Name_Version#_Concept.


	[[Category:Concept]]		[[Category:Concept]]

Marcin at 22:27, 12 October 2013

2013-10-12T22:27:44Z

← Older revision		Revision as of 22:27, 12 October 2013
Line 1:		Line 1:
	In the ~~system~~ design ~~process, a '''concept''' provides the introductory material on a technology that serves as a springboard to technical development~~. ~~It may include:~~		The Design Concept is the first implementation of the Requirement into an actual design.

	* History of the ~~idea~~		The distinction between Requirement and Concept may be unclear - as a Requirement may be so detailed that it specifies actual technology/design choices. In the limit of a fully-detailed Requirement - we have a concept. In the limit of a concept being filled in with technical details - we have a Technical Design.
	* Commercial examples
	* Inputs and Outputs needed		=Protocol=
	* How well it meets [[OSE Specifications]], goals, and requirements.
	* Relationship to other concepts		A concept should be in the form of a cloud, collaboratively editable document such as a google doc which allows various parts of a design to be detailed.
	* Preliminary drawings, designs, calculations, parts ~~lists, or other documentation~~
	* Explanations of ~~why certain designs are preferred~~		#To write a concept, start a google doc based on the [[Google Drawing Template]].
	* Performance and efficiency
	* Scaling to different sizes

	[[Category:Concept]]		[[Category:Concept]]

Marcin at 01:52, 9 August 2013

2013-08-09T01:52:24Z

← Older revision		Revision as of 01:52, 9 August 2013
Line 5:		Line 5:
	* Inputs and Outputs needed		* Inputs and Outputs needed
	* How well it meets [[OSE Specifications]], goals, and requirements.		* How well it meets [[OSE Specifications]], goals, and requirements.
	::* Relationship to other concepts		* Relationship to other concepts
	:* Preliminary drawings, designs, calculations, parts lists, or other documentation		* Preliminary drawings, designs, calculations, parts lists, or other documentation
	:* Explanations of why certain designs are preferred		* Explanations of why certain designs are preferred
	:* Performance and efficiency		* Performance and efficiency
	:* Scaling to different sizes		* Scaling to different sizes

	[[Category:Concept]]		[[Category:Concept]]

Marcin at 01:52, 9 August 2013

2013-08-09T01:52:14Z

← Older revision		Revision as of 01:52, 9 August 2013
Line 2:		Line 2:

	* History of the idea		* History of the idea
	:* Commercial examples		* Commercial examples
	:* Inputs and Outputs needed		* Inputs and Outputs needed
	:* How well it meets [[OSE Specifications]], goals, and requirements.		* How well it meets [[OSE Specifications]], goals, and requirements.
	:* Relationship to other concepts		::* Relationship to other concepts
	:* Preliminary drawings, designs, calculations, parts lists, or other documentation		:* Preliminary drawings, designs, calculations, parts lists, or other documentation
	:* Explanations of why certain designs are preferred		:* Explanations of why certain designs are preferred

Marcin at 01:52, 9 August 2013

2013-08-09T01:52:00Z

← Older revision		Revision as of 01:52, 9 August 2013
Line 1:		Line 1:
	In the system design process, a '''concept''' provides the introductory material on a technology that serves as a springboard to technical development. It may include:		In the system design process, a '''concept''' provides the introductory material on a technology that serves as a springboard to technical development. It may include:

	:* History of the idea		* History of the idea
	:* Commercial examples		:* Commercial examples
	:* Inputs and Outputs needed		:* Inputs and Outputs needed

Marcin at 01:51, 9 August 2013

2013-08-09T01:51:44Z

← Older revision		Revision as of 01:51, 9 August 2013
Line 1:		Line 1:
	In the system design process, a '''concept''' provides the introductory material on a technology that serves as a springboard to technical development. Multiple concepts can be candidates for a given function. Choosing the best option among them is called "Analysis and Trade Studies", but you first need to list the options and what is known about their technical characteristics.		In the system design process, a '''concept''' provides the introductory material on a technology that serves as a springboard to technical development. It may include:

	~~Multiple concepts are listed as candidates by function, for example "portable energy" or "food". If more room is needed, include links to detailed information from a summary page.~~

	~~Concept descriptions should include:~~

	* A title - preferably use common terms used outside the OSE project to help search for more information.
	* Keywords - additional terms related to the concept for search and link purposes
	* Description - A summary to introduce the concept and its features
	* Technical information - Whatever is known about the concept. Either include the data itself, or links to data elsewhere. Categories of information are not limited, but if known should include:

	:* History of the idea		:* History of the idea
Line 14:		Line 5:
	:* Inputs and Outputs needed		:* Inputs and Outputs needed
	:* How well it meets [[OSE Specifications]], goals, and requirements.		:* How well it meets [[OSE Specifications]], goals, and requirements.
	:* Relationship to other concepts ~~or functions~~		:* Relationship to other concepts
	:* Preliminary drawings, designs, calculations, parts lists, or other documentation		:* Preliminary drawings, designs, calculations, parts lists, or other documentation
	:* Explanations of why certain designs are preferred		:* Explanations of why certain designs are preferred
	:* Performance and efficiency		:* Performance and efficiency
	:* Scaling to different sizes		:* Scaling to different sizes
	~~:* Uncommon items needed~~

	[[Category:Concept]]		[[Category:Concept]]

DanielRavenNest at 13:02, 10 May 2011

2011-05-10T13:02:59Z

← Older revision		Revision as of 13:02, 10 May 2011
Line 1:		Line 1:
	In the system design process, a [[concept]] provides the introductory material on a technology that serves as a springboard to technical development. Multiple concepts can be candidates for a given function. Choosing the best option among them is called "Analysis and Trade Studies", but you first need to list the options and what is known about their technical characteristics.		In the system design process, a '''concept''' provides the introductory material on a technology that serves as a springboard to technical development. Multiple concepts can be candidates for a given function. Choosing the best option among them is called "Analysis and Trade Studies", but you first need to list the options and what is known about their technical characteristics.

	Multiple concepts are listed as candidates by function, for example "portable energy" or "food". If more room is needed, include links to detailed information from a summary page.		Multiple concepts are listed as candidates by function, for example "portable energy" or "food". If more room is needed, include links to detailed information from a summary page.

DanielRavenNest at 13:02, 10 May 2011

2011-05-10T13:02:21Z

← Older revision		Revision as of 13:02, 10 May 2011
Line 1:		Line 1:
	A [[concept]] provides the introductory material on a technology that serves as a springboard to technical development. ~~Concepts~~ should include the ~~basic~~ concept ~~proper, relationship~~ to ~~other products~~, ~~design rationale, and calculations (~~to ~~shake down specific implementations)~~. ~~Concepts~~ should ~~be direct expressions~~ of [[OSE Specifications]].		In the system design process, a [[concept]] provides the introductory material on a technology that serves as a springboard to technical development. Multiple concepts can be candidates for a given function. Choosing the best option among them is called "Analysis and Trade Studies", but you first need to list the options and what is known about their technical characteristics.

			Multiple concepts are listed as candidates by function, for example "portable energy" or "food". If more room is needed, include links to detailed information from a summary page.

			Concept descriptions should include:

			* A title - preferably use common terms used outside the OSE project to help search for more information.
			* Keywords - additional terms related to the concept for search and link purposes
			* Description - A summary to introduce the concept and its features
			* Technical information - Whatever is known about the concept. Either include the data itself, or links to data elsewhere. Categories of information are not limited, but if known should include:

			:* History of the idea
			:* Commercial examples
			:* Inputs and Outputs needed
			:* How well it meets [[OSE Specifications]], goals, and requirements.
			:* Relationship to other concepts or functions
			:* Preliminary drawings, designs, calculations, parts lists, or other documentation
			:* Explanations of why certain designs are preferred
			:* Performance and efficiency
			:* Scaling to different sizes
			:* Uncommon items needed

	[[Category:Concept]]		[[Category:Concept]]