Functional Specification Document Definition and Template - Revision history

Marcin: /* There is No Uniform Compiler */

2024-08-08T22:23:57Z

There is No Uniform Compiler

← Older revision		Revision as of 22:23, 8 August 2024
Line 26:		Line 26:
	=There is No Uniform Compiler=		=There is No Uniform Compiler=
	It should be noted that any build can be considered a fork - unless ALL of the build is ABSOLUTELY IDENTICAL. This is by direct analogy to software. When a software is run, it is compiled to the same product in all cases. In hardware, there is no uniform compiler. The 'compiler' includes tools, skills, supply chain, and other aspects of the production process. An identical supply chain is not guaranteed - parts may be different. All in all - it is very unlikely that 2 builds will be identical - unless they are produced in a specific production run at a specific production facility under tight quality control.		It should be noted that any build can be considered a fork - unless ALL of the build is ABSOLUTELY IDENTICAL. This is by direct analogy to software. When a software is run, it is compiled to the same product in all cases. In hardware, there is no uniform compiler. The 'compiler' includes tools, skills, supply chain, and other aspects of the production process. An identical supply chain is not guaranteed - parts may be different. All in all - it is very unlikely that 2 builds will be identical - unless they are produced in a specific production run at a specific production facility under tight quality control.

			Applied to the [[AI Apocalypse]], this means that it will be extremely difficult for AI to seize all of the hardware productive capacity of the planet - in a controllable, energy-efficient, maintainable way. Meaning that the human stewards of AI will gravitate away from AI Apocalypse towards a more collaborative (between humans and machines) solution.

	=Branches and Replications History=		=Branches and Replications History=

Marcin: /* Functional requirements */

2024-08-08T22:20:03Z

Functional requirements

← Older revision		Revision as of 22:20, 8 August 2024
Line 24:		Line 24:
	*"Can print at X rate"		*"Can print at X rate"

			=There is No Uniform Compiler=
	It should be noted that any build can be considered a fork - unless ALL of the build is ABSOLUTELY IDENTICAL. This is by direct analogy to software. When a software is run, it is compiled to the same product in all cases. In hardware, there is no uniform compiler. The 'compiler' includes tools, skills, supply chain, and other aspects of the production process. An identical supply chain is not guaranteed - parts may be different. All in all - it is very unlikely that 2 builds will be identical - unless they are produced in a specific production run at a specific production facility under tight quality control.		It should be noted that any build can be considered a fork - unless ALL of the build is ABSOLUTELY IDENTICAL. This is by direct analogy to software. When a software is run, it is compiled to the same product in all cases. In hardware, there is no uniform compiler. The 'compiler' includes tools, skills, supply chain, and other aspects of the production process. An identical supply chain is not guaranteed - parts may be different. All in all - it is very unlikely that 2 builds will be identical - unless they are produced in a specific production run at a specific production facility under tight quality control.

Takacsjd: Added a required section in the FS that lists out pages for FORKS of a DS, which would be individual builds. each build isn't going to be exactly the same as the DS, as explained in the functional requirements section.

2018-03-02T20:45:11Z

Added a required section in the FS that lists out pages for FORKS of a DS, which would be individual builds. each build isn't going to be exactly the same as the DS, as explained in the functional requirements section.

← Older revision		Revision as of 20:45, 2 March 2018
Line 34:		Line 34:
	===Design Synopsis===		===Design Synopsis===
	Here, you should see a list of parts of a module or what modules are going into a machine in the machine case.		Here, you should see a list of parts of a module or what modules are going into a machine in the machine case.


	===Link to branch DS document===		===Link to branch DS document===

			===Links to builds of this DS (FORKS)===

	==[Branch Name2] [Quick header describing how different i.e. 12" PVC D3D]==		==[Branch Name2] [Quick header describing how different i.e. 12" PVC D3D]==
Line 45:		Line 48:
	===Link to branch DS document===		===Link to branch DS document===

			===Links to builds of this DS (FORKS)===
	And so on...		And so on...

Marcin: /* Functional requirements */

2018-03-02T18:39:46Z

Functional requirements

← Older revision		Revision as of 18:39, 2 March 2018
Line 19:		Line 19:
	Functional requirements are a translation of '''[[OSE Specifications]]''' - which apply to all machines - into a more specific and focused requirement.		Functional requirements are a translation of '''[[OSE Specifications]]''' - which apply to all machines - into a more specific and focused requirement.

			Such as:
			*"All modules of this machine are OSE derived products and can be produced in the ecology"
			*"Prints a variety of materials (list materials)"
			*"Can print at X rate"

	i.e.		It should be noted that any build can be considered a fork - unless ALL of the build is ABSOLUTELY IDENTICAL. This is by direct analogy to software. When a software is run, it is compiled to the same product in all cases. In hardware, there is no uniform compiler. The 'compiler' includes tools, skills, supply chain, and other aspects of the production process. An identical supply chain is not guaranteed - parts may be different. All in all - it is very unlikely that 2 builds will be identical - unless they are produced in a specific production run at a specific production facility under tight quality control.
	-"All ~~modules of this machine~~ are ~~OSE derived products and can be~~ produced in ~~the ecology"~~
	~~-"Prints~~ a ~~variety of materials (list materials)"~~
	~~-"Can print~~ at ~~X rate"~~

	=Branches and Replications History=		=Branches and Replications History=

Marcin at 18:35, 2 March 2018

2018-03-02T18:35:15Z

← Older revision		Revision as of 18:35, 2 March 2018
Line 28:		Line 28:
	--This section should read like a history of each replication and branch from the core FS		--This section should read like a history of each replication and branch from the core FS

	===[Branch Name] [Quick header describing how different i.e. 12" PVC D3D]===		==[Branch Name] [Quick header describing how different i.e. 12" PVC D3D]==
	====Reason for Branching====		===Reason for Branching===
	Why was the project taken in this direction? how does this branch address an R&D need detailed in the FS requirements?		Why was the project taken in this direction? how does this branch address an R&D need detailed in the FS requirements?
	====Design Synopsis====		===Design Synopsis===
	Here, you should see a list of parts of a module or what modules are going into a machine in the machine case.		Here, you should see a list of parts of a module or what modules are going into a machine in the machine case.

	====Link to branch DS document====		===Link to branch DS document===

	===[Branch Name2] [Quick header describing how different i.e. 12" PVC D3D]===		==[Branch Name2] [Quick header describing how different i.e. 12" PVC D3D]==
	====Reason for Branching 2====		===Reason for Branching 2===
	Why was the project taken in this direction? how does this branch address an R&D need detailed in the FS requirements?		Why was the project taken in this direction? how does this branch address an R&D need detailed in the FS requirements?
	====Design Synopsis====		===Design Synopsis===
	Here, you should see a list of parts of a module or what modules are going into a machine in the machine case.		Here, you should see a list of parts of a module or what modules are going into a machine in the machine case.

	====Link to branch DS document====		===Link to branch DS document===

	And so on...		And so on...

Marcin at 18:34, 2 March 2018

2018-03-02T18:34:41Z

← Older revision		Revision as of 18:34, 2 March 2018
Line 15:		Line 15:
	The, you would eventually see a breach with a ''Machine'' DS that uses the Universal Axis DS		The, you would eventually see a breach with a ''Machine'' DS that uses the Universal Axis DS


			=Functional requirements=
	Functional requirements are a translation of '''[[OSE Specifications]]''' - which apply to all machines - into a more specific and focused requirement.		Functional requirements are a translation of '''[[OSE Specifications]]''' - which apply to all machines - into a more specific and focused requirement.

	~~=Functional requirements=~~
	i.e.		i.e.
	-"All modules of this machine are OSE derived products and can be produced in the ecology"		-"All modules of this machine are OSE derived products and can be produced in the ecology"

Marcin: /* Introduction */

2018-03-02T18:34:03Z

Introduction

← Older revision		Revision as of 18:34, 2 March 2018
Line 14:		Line 14:
	You'd have DS docuemnt branches with those printers and all those modules.		You'd have DS docuemnt branches with those printers and all those modules.
	The, you would eventually see a breach with a ''Machine'' DS that uses the Universal Axis DS		The, you would eventually see a breach with a ''Machine'' DS that uses the Universal Axis DS

			Functional requirements are a translation of '''[[OSE Specifications]]''' - which apply to all machines - into a more specific and focused requirement.

	=Functional requirements=		=Functional requirements=

Takacsjd at 08:26, 21 February 2018

2018-02-21T08:26:52Z

← Older revision		Revision as of 08:26, 21 February 2018
Line 24:		Line 24:
	--This section should read like a history of each replication and branch from the core FS		--This section should read like a history of each replication and branch from the core FS

	~~==[Branch Name]==~~
	===[Branch Name] [Quick header describing how different i.e. 12" PVC D3D]===		===[Branch Name] [Quick header describing how different i.e. 12" PVC D3D]===
	====Reason for Branching====		====Reason for Branching====
Line 31:		Line 30:
	Here, you should see a list of parts of a module or what modules are going into a machine in the machine case.		Here, you should see a list of parts of a module or what modules are going into a machine in the machine case.

	===Link to branch DS document===		====Link to branch DS document====

	==[Branch ~~Name 2~~]==		===[Branch Name2] [Quick header describing how different i.e. 12" PVC D3D]===
	===~~[Branch Name~~ 2~~] [~~Design ~~Summary (from DS) and Reason for branching]~~===		====Reason for Branching 2====
			Why was the project taken in this direction? how does this branch address an R&D need detailed in the FS requirements?
			====Design Synopsis====
	Here, you should see a list of parts of a module or what modules are going into a machine in the machine case.		Here, you should see a list of parts of a module or what modules are going into a machine in the machine case.

	===Link to branch DS document===		====Link to branch DS document====

	And so on.		And so on...

Takacsjd: /* [Branch Name] [Design Summary (from DS) and Reason for branching] */

2018-02-21T08:25:51Z

[Branch Name] [Design Summary (from DS) and Reason for branching]

← Older revision		Revision as of 08:25, 21 February 2018
Line 25:		Line 25:

	==[Branch Name]==		==[Branch Name]==
	===[Branch Name] [~~Design Summary (from DS) and~~ Reason for ~~branching]~~===		===[Branch Name] [Quick header describing how different i.e. 12" PVC D3D]===
			====Reason for Branching====
			Why was the project taken in this direction? how does this branch address an R&D need detailed in the FS requirements?
			====Design Synopsis====
	Here, you should see a list of parts of a module or what modules are going into a machine in the machine case.		Here, you should see a list of parts of a module or what modules are going into a machine in the machine case.

Takacsjd: /* Branches and Replications History */

2018-02-21T08:22:21Z

Branches and Replications History

← Older revision		Revision as of 08:22, 21 February 2018
Line 29:		Line 29:

	===Link to branch DS document===		===Link to branch DS document===

			==[Branch Name 2]==
			===[Branch Name 2] [Design Summary (from DS) and Reason for branching]===
			Here, you should see a list of parts of a module or what modules are going into a machine in the machine case.

			===Link to branch DS document===

			And so on.