Concept: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 7: | Line 7: | ||
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. | 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 Drawing Template]]. | #To write a concept, start a google doc based on the [[Google Drawing Template]] - click edit below the template to get to the viewable document, and make a copy of the document | ||
#Name that document Machine_Name_Concept | |||
#Embed in wiki, in a page named Machine_Name_Concept. If there is a naming conflic, add some more words to your title, such as Machine_Name_Version#_Concept. | |||
[[Category:Concept]] | [[Category:Concept]] | ||
Revision as of 22:29, 12 October 2013
The Design Concept is the first implementation of the Requirement into an actual design.
The distinction between Requirement and Concept may be unclear - 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 Drawing Template - click edit below the template to get to the viewable document, and make a copy of the document
- Name that document Machine_Name_Concept
- Embed in wiki, in a page named Machine_Name_Concept. If there is a naming conflic, add some more words to your title, such as Machine_Name_Version#_Concept.