{"id":3648,"date":"2016-03-26T05:12:34","date_gmt":"2016-03-26T05:12:34","guid":{"rendered":"http:\/\/course.oeru.org\/ds4oer\/?page_id=3648"},"modified":"2016-03-26T05:12:34","modified_gmt":"2016-03-26T05:12:34","slug":"blueprint-components","status":"publish","type":"page","link":"https:\/\/course.oeru.org\/ds4oer\/learning-pathways\/designing-a-blueprint\/blueprint-components\/","title":{"rendered":"Blueprint components"},"content":{"rendered":"
\n
\n
\n
\n
\n
\n
\n
\n
\"\"<\/a> <\/p>\n
Visualising your design<\/div>\n<\/div>\n<\/div>\n

A design blueprint is a high-level plan that guides collaborators through the process of designing and contributing to the development of an open course. Its purpose is to visualise the overall “architecture” of the course to guide the design, development, and cooperation process.<\/p>\n

In open design, less is more<\/span><\/h2>\n

Open design is highly iterative, and the transparent and dynamic nature of collaborative OER development means that open design blueprints tend to be less detailed when compared with the standard production model at most instructional design departments. A wiki is always a draft in the sense that an edit can be made at any time to refine and improve the design as more information comes to light. The detail of the subcomponents of the design will be expanded as the development progresses. In open design, we reduce the need for a detailed master plan before development commences by openly publishing planning documents (records of meetings, draft storyboards and outlines, inventories, and evaluations of existing OERs for reuse, etc.) as development of a course matures.\n<\/p>\n

Nonetheless, a high-level summary of an open proposed course development is recommended. A shared design blueprint can\n<\/p>\n