Concept: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
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]]. | |||
[[Category:Concept]] | [[Category:Concept]] | ||
Revision as of 22:27, 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.