Conceptual Design: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 11: | Line 11: | ||
#To write a concept, start a google doc based on the [[Google Slides Template]] - click edit below the template to get to the viewable document, and make a copy of the document | #To write a concept, start a google doc based on the [[Google Slides Template]] - click edit below the template to get to the viewable document, and make a copy of the document | ||
#Include [[Design Rationale]] information for as many aspects of the design as possible. The Design Rationale should frequently refer to [[OSE Specifications]] as the basis. | #Include [[Design Rationale]] information for as many aspects of the design as possible. The Design Rationale should frequently refer to [[OSE Specifications]] as the basis. | ||
#Name that document Machine_Name_Concept | #Name that document Machine_Name_Concept. See [[Taxonomy]] for information on naming projects. | ||
#Embed in wiki, in a page named Machine_Name_Concept. If there is a naming conflict, add some more words to your title, such as Machine_Name_Version#_Concept. | #Embed in wiki, in a page named Machine_Name_Concept. If there is a naming conflict, add some more words to your title, such as Machine_Name_Version#_Concept. | ||
Revision as of 01:56, 26 September 2019
The Design Concept is the first step of implementing the machine Requirement into an actual design.
The distinction between Requirement and Concept may be blurred - 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 Slides Template - click edit below the template to get to the viewable document, and make a copy of the document
- Include Design Rationale information for as many aspects of the design as possible. The Design Rationale should frequently refer to OSE Specifications as the basis.
- Name that document Machine_Name_Concept. See Taxonomy for information on naming projects.
- Embed in wiki, in a page named Machine_Name_Concept. If there is a naming conflict, add some more words to your title, such as Machine_Name_Version#_Concept.