Requirements - Revision history

Marcin at 23:21, 25 January 2023

2023-01-25T23:21:10Z

← Older revision		Revision as of 23:21, 25 January 2023
Line 1:		Line 1:
			=What is it?=

			'''Requirements are a part of a development process. The limit of requirements in their completion is a specification, which in turn is the actual design in the limit of completion of a specification.'''

	=Protocol for Machines=		=Protocol for Machines=

Marcin at 20:08, 26 September 2019

2019-09-26T20:08:31Z

@@ Line 1: / Line 1: @@
 =General=
 Requirements are the necessary features of a given product, process, or development pathway. The requirements can apply to machine design, design of a website, design of a Template, design of a software tool, etc.
@@ Line 25: / Line 32: @@
 A Requirement should include Specifications. In the Open Source Product Development method, the specification should be approved by the technical [[Leadership]].
 =Links=
 *[[List of OSE Requirements]]

Marcin: /* Protocol for Machines */

2019-09-26T20:07:57Z

Protocol for Machines

← Older revision		Revision as of 20:07, 26 September 2019
Line 27:		Line 27:
	=Protocol for Machines=		=Protocol for Machines=

	*Start with a [[Requirements Spreadsheet]] or equivalent.		*Start with a [[Requirements Spreadsheet]] or equivalent which contains all the required information.
	*Fill it out for your machine. Include simple diagrams and flowcharts.		*Fill it out for your machine. Include simple diagrams and flowcharts.
	*Publish in the Development Spreadsheet for a given machine~~. If you don't have edit privileges, use the [[Pull Request]] form. If you join a given development team, you may be given further edit privileges~~.		*Publish in the Development Spreadsheet for a given machine.

	=Links=		=Links=
	*[[List of OSE Requirements]]		*[[List of OSE Requirements]]

Marcin: /* Machines */

2019-09-26T19:29:53Z

Machines

← Older revision		Revision as of 19:29, 26 September 2019
Line 23:		Line 23:
	The Specification narrows the development path from a general idea to a specific implementation. The specification is a distillation of the Conceptual Design (how it's done) and Design Rationale (why it's done in a particular way) into a specific set of design parameters.		The Specification narrows the development path from a general idea to a specific implementation. The specification is a distillation of the Conceptual Design (how it's done) and Design Rationale (why it's done in a particular way) into a specific set of design parameters.

	A Requirement should include Specifications. In the Open Source Product Development method, the specification should be approved by the technical ~~leadership~~.		A Requirement should include Specifications. In the Open Source Product Development method, the specification should be approved by the technical [[Leadership]].

	=Protocol for Machines=		=Protocol for Machines=

Marcin: /* Machines */

2019-09-26T19:29:21Z

Machines

← Older revision		Revision as of 19:29, 26 September 2019
Line 23:		Line 23:
	The Specification narrows the development path from a general idea to a specific implementation. The specification is a distillation of the Conceptual Design (how it's done) and Design Rationale (why it's done in a particular way) into a specific set of design parameters.		The Specification narrows the development path from a general idea to a specific implementation. The specification is a distillation of the Conceptual Design (how it's done) and Design Rationale (why it's done in a particular way) into a specific set of design parameters.

	~~The specific items that a~~ Requirement should ~~have includes~~ Specifications. In the Open Source Product Development method, the specification should be approved by the technical ~~lead, such that the general development workflow includes:~~		A Requirement should include Specifications. In the Open Source Product Development method, the specification should be approved by the technical leadership.

	=Protocol for Machines=		=Protocol for Machines=

Marcin: /* Machines */

2019-09-26T19:27:02Z

Machines

← Older revision		Revision as of 19:27, 26 September 2019
Line 11:		Line 11:
	=Machines=		=Machines=

	When applied to machine development, Requirements are the features that the given machine must have. These are based on the general concept of the GVCS - machines that meet or exceed industry standards, and are sufficient to build a post-scarcity village infrastructure for 150 people.		When applied to machine development, Requirements are the features that the given machine must have. These are based on the general concept of the [[GVCS]] - machines that meet or exceed industry standards, and are sufficient to build a post-scarcity village infrastructure for 150 people.

	Requirements for OSE machines are based on [[Module Based Design]] ~~- we~~ focus on a design language where we identify a finite set of modules, and these modules are used to build any of the [[GVCS]] machines. While there are 50 machines, there may be ~200 modules which are used through all the machines~~. The specific number~~ of ~~modules decreases with time as multi-purpose modules are substituted into the Set~~.		Specifically, requirements must follow [[OSE Specifications]]. OSE Spec is an exhaustive list of properties, and Requirement writers must be familiar with the interpretation of OSE Specifications as they apply to determining the specific requirement.

			Of all the Specifications, the most important may be (1) open source, (2) modularity, (3) scalability, and (4) product ecology - assuming the underlying property of appropriate technology for creating democratic society.

			Requirements for OSE machines are based on [[Module Based Design]]. We focus on a design language where we identify a finite set of modules, and these modules are used to build any of the [[GVCS]] machines. While there are 50 machines, there may be ~200 types of modules which are used through all the machines - which create a [[Pattern Language]] for building all kinds of artifacts.

	The motivation is that instead of building a fixed number of machines, we can build an infinite number of machines by combining the modules in different ways.		The motivation is that instead of building a fixed number of machines, we can build an infinite number of machines by combining the modules in different ways.

Marcin: /* Machines */

2019-09-26T19:17:47Z

Machines

← Older revision		Revision as of 19:17, 26 September 2019
Line 13:		Line 13:
	When applied to machine development, Requirements are the features that the given machine must have. These are based on the general concept of the GVCS - machines that meet or exceed industry standards, and are sufficient to build a post-scarcity village infrastructure for 150 people.		When applied to machine development, Requirements are the features that the given machine must have. These are based on the general concept of the GVCS - machines that meet or exceed industry standards, and are sufficient to build a post-scarcity village infrastructure for 150 people.

	Requirements for OSE machines are based on Module Based Design - we focus on a design language where we identify a finite set of modules, and these modules are used to build any of the [[GVCS]] machines. While there are 50 machines, there may be ~200 modules which are used through all the machines. The specific number of modules decreases with time as multi-purpose modules are substituted into the Set.		Requirements for OSE machines are based on [[Module Based Design]] - we focus on a design language where we identify a finite set of modules, and these modules are used to build any of the [[GVCS]] machines. While there are 50 machines, there may be ~200 modules which are used through all the machines. The specific number of modules decreases with time as multi-purpose modules are substituted into the Set.

	The motivation is that instead of building a fixed number of machines, we can build an infinite number of machines by combining the modules in different ways.		The motivation is that instead of building a fixed number of machines, we can build an infinite number of machines by combining the modules in different ways.

Newt at 20:13, 5 March 2017

2017-03-05T20:13:21Z

← Older revision		Revision as of 20:13, 5 March 2017
Line 1:		Line 1:
	=General=		=General=
	Requirements are the necessary features of a given product, process, or development pathway. The requirements can apply to machine be design, design of a website, design of a Template, design of a software tool, etc.		Requirements are the necessary features of a given product, process, or development pathway. The requirements can apply to machine design, design of a website, design of a Template, design of a software tool, etc.

	In order for OSE's development process to be coherent and comprehensive, the requirements for each of its designs, processes, etc must be transparent so that collaborators follow the same, ~~interoperable~~ standards of development.		In order for OSE's development process to be coherent and comprehensive, the requirements for each of its designs, processes, etc must be transparent so that collaborators follow the same, inter-operable standards of development.

	The goal of using ~~interoperable~~ standards is scalability of the development process: inviting a wide range of contributors worldwide to add to the project in a meaningful way. Without such structure, a project lacks the organization required for a meaningful contribution to the human economic process and human progress.		The goal of using inter-operable standards is scalability of the development process: inviting a wide range of contributors worldwide to add to the project in a meaningful way. Without such structure, a project lacks the organization required for a meaningful contribution to the human economic process and human progress.

	OSE's experiment revolves around creating impactful, open source product development processes which do not suffer from the inefficiency of scale nor the monopolization of power typical of large-scale human endeavors.		OSE's experiment revolves around creating impactful, open source product development processes which do not suffer from the inefficiency of scale nor the monopolization of power typical of large-scale human endeavors.

Newt: spelling correction

2017-03-05T20:11:03Z

spelling correction

← Older revision		Revision as of 20:11, 5 March 2017
Line 1:		Line 1:
	=General=		=General=
	Requirements are the necessary features of a given product, ~~pelrocess~~, or development pathway. The requirements can apply to machine be design, design of a website, design of a Template, design of a software tool, etc.		Requirements are the necessary features of a given product, process, or development pathway. The requirements can apply to machine be design, design of a website, design of a Template, design of a software tool, etc.

	In order for OSE's development process to be coherent and comprehensive, the requirements for each of its designs, processes, etc must be transparent so that collaborators follow the same, interoperable standards of development.		In order for OSE's development process to be coherent and comprehensive, the requirements for each of its designs, processes, etc must be transparent so that collaborators follow the same, interoperable standards of development.

Marcin: /* Protocol for Machines */

2015-12-27T22:30:11Z

Protocol for Machines

← Older revision		Revision as of 22:30, 27 December 2015
Line 26:		Line 26:
	*Fill it out for your machine. Include simple diagrams and flowcharts.		*Fill it out for your machine. Include simple diagrams and flowcharts.
	*Publish in the Development Spreadsheet for a given machine. If you don't have edit privileges, use the [[Pull Request]] form. If you join a given development team, you may be given further edit privileges.		*Publish in the Development Spreadsheet for a given machine. If you don't have edit privileges, use the [[Pull Request]] form. If you join a given development team, you may be given further edit privileges.

			=Links=
			*[[List of OSE Requirements]]