Conceptual Design

From Open Source Ecology
Revision as of 13:49, 10 March 2017 by Jose.urra (talk | contribs) (This is a request to add some of the ideas expressed in a Comment about Concepts, Requirements, and Specifications)
Jump to navigation Jump to search

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.

  1. 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
  2. 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.
  3. Name that document Machine_Name_Concept
  4. 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.