XM Conceptual Design: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
(Created page with "Conceptual design is articulated. This takes place in the form of a Systems Engineering Breakdown Diagrams - which outlines all the components of a given GVCS technology and how ...")
 
No edit summary
 
(11 intermediate revisions by the same user not shown)
Line 1: Line 1:
Conceptual design is articulated. This takes place in the form of a Systems Engineering Breakdown Diagrams - which outlines all the components of a given GVCS technology and how they relate to one another. For each component, the Breakdown Diagram should also include possible implementation paths - focusing on those paths that build on existing open source projects, on available documentation, and on other available prior art. The work of OSE is founded on determining a specific implementation path from the above options - determined by best fit to OSE Specifications - from which a prototype implementation path is determined. Successive prototypes may choose different implementation paths - depending on prototype testing results.
'''Conceptual design''' is a representation of the product with realistic arrangement and dimensioning of components - as informed in general by [[OSE Specifications]]. The distinction between a Conceptual Design and a Technical Design is that the Technical Design specifies exact dimensions, tolerances, and materials used - whereas the conceptual design specifies approximate dimensions, and it may not include tolerances and materials. A conceptual design is not a reliable representation that allows a product to be built successfully, whereas Technical Design does produce exact and replicable builds.
Read Refactored OSE Specifications
 
Pursuant to OSE Specifications, calculate power requirements
Conceptual design is not media-specific. The conceptual design may take the form of 3D computer models, concept design in a full CAD package, a wooden model, or it could be as simple as drawings on the back of an envelope.
Define size/scale/performance of the machine
 
Motivate your design for low cost
In the next step, the Specification, these priciples are converted to desired performance specifications - for a single (but flexible) instance of the device. Everything looks good on paper so far.
Motivate your design for performance
 
Motivate your design for accuracy requirements
#Read [[Refactored OSE Specifications]]
Motivate your design for ease of fabrication
#Pursuant to OSE Specifications, calculate power requirements
Define components of a technology
#Define size/scale/performance of the machine
Define relationships between components
#Motivate your design for low cost
Research open source prior art available for the design
#Motivate your design for performance
Publish open source prior art available for the design
#Motivate your design for accuracy requirements
Define the relevance/adaptations required for the open source prior art to fit OSE Specifications
#Motivate your design for ease of fabrication##Define components of a technology
Develop the required adaptations of OS prior art and implement that in the design at hand
#Define relationships between components
Specify other options available for implementation
#Research open source prior art available for the design
Specify a specific instance suitable for prototyping
#Publish open source prior art available for the design
Draw an editable diagram of the specific instance
#Define the relevance/adaptations required for the open source prior art to fit [[OSE Specifications]]
Populate a Task Management Platform with the above components that need to be developed
#Develop the required adaptations of OS prior art and implement that in the design at hand
Recruit developers to execute and add tasks to the basic platform.
#Specify other options available for implementation
Promote active developers of the project to Project Leader Status. In conjunction with the GVCS Project Curator, this is the leading stakeholder in the project who has a direct interest in developing or using the technology; main overseer of physical project development and fabrication, and works with GVCS Project Curator on quality control for adherence to OSE Specifications
#Specify a specific instance suitable for prototyping
#Draw an editable diagram of the specific instance
#Populate a Task Management Platform with the above components that need to be developed
#Recruit developers to execute and add tasks to the basic platform.
#Promote active developers of the project to Project Leader Status. In conjunction with the [[GVCS Project Curator]], this is the leading stakeholder in the project who has a direct interest in developing or using the technology; main overseer of physical project development and fabrication, and works with GVCS Project Curator on quality control for adherence to [[OSE Specifications]]
 
=Links=
*[[Conceptual Design]]
 
[[Category:XM]]

Latest revision as of 18:45, 24 December 2018

Conceptual design is a representation of the product with realistic arrangement and dimensioning of components - as informed in general by OSE Specifications. The distinction between a Conceptual Design and a Technical Design is that the Technical Design specifies exact dimensions, tolerances, and materials used - whereas the conceptual design specifies approximate dimensions, and it may not include tolerances and materials. A conceptual design is not a reliable representation that allows a product to be built successfully, whereas Technical Design does produce exact and replicable builds.

Conceptual design is not media-specific. The conceptual design may take the form of 3D computer models, concept design in a full CAD package, a wooden model, or it could be as simple as drawings on the back of an envelope.

In the next step, the Specification, these priciples are converted to desired performance specifications - for a single (but flexible) instance of the device. Everything looks good on paper so far.

  1. Read Refactored OSE Specifications
  2. Pursuant to OSE Specifications, calculate power requirements
  3. Define size/scale/performance of the machine
  4. Motivate your design for low cost
  5. Motivate your design for performance
  6. Motivate your design for accuracy requirements
  7. Motivate your design for ease of fabrication##Define components of a technology
  8. Define relationships between components
  9. Research open source prior art available for the design
  10. Publish open source prior art available for the design
  11. Define the relevance/adaptations required for the open source prior art to fit OSE Specifications
  12. Develop the required adaptations of OS prior art and implement that in the design at hand
  13. Specify other options available for implementation
  14. Specify a specific instance suitable for prototyping
  15. Draw an editable diagram of the specific instance
  16. Populate a Task Management Platform with the above components that need to be developed
  17. Recruit developers to execute and add tasks to the basic platform.
  18. Promote active developers of the project to Project Leader Status. In conjunction with the GVCS Project Curator, this is the leading stakeholder in the project who has a direct interest in developing or using the technology; main overseer of physical project development and fabrication, and works with GVCS Project Curator on quality control for adherence to OSE Specifications

Links

Retrieved from "https://wiki.opensourceecology.org/index.php?title=XM_Conceptual_Design&oldid=183521"