XM Conceptual Design: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
#'''Conceptual design''' is | #'''Conceptual design''' - this is where the lifetime design, high performance, low cost, modular design features are implemented. 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. | ||
##Read [[Refactored OSE Specifications]] | ##Read [[Refactored OSE Specifications]] | ||
##Pursuant to OSE Specifications, calculate power requirements | ##Pursuant to OSE Specifications, calculate power requirements |
Revision as of 04:04, 27 March 2012
- Conceptual design - this is where the lifetime design, high performance, low cost, modular design features are implemented. 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.
- Read Refactored OSE Specifications
- Pursuant to OSE Specifications, calculate power requirements
- Define size/scale/performance of the machine
- Motivate your design for low cost
- Motivate your design for performance
- Motivate your design for accuracy requirements
- Motivate your design for ease of fabrication
- Define components of a technology
- Define relationships between components
- Research open source prior art available for the design
- Publish open source prior art available for the design
- Define the relevance/adaptations required for the open source prior art to fit OSE Specifications
- Develop the required adaptations of OS prior art and implement that in the design at hand
- Specify other options available for implementation
- 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