MoodleNet whitepaper: Difference between revisions
From MoodleDocs
Doug Belshaw (talk | contribs) No edit summary |
Doug Belshaw (talk | contribs) No edit summary |
||
| Line 7: | Line 7: | ||
<blockquote>A white paper is an authoritative report or guide that informs readers concisely about a complex issue and presents the issuing body's philosophy on the matter. It is meant to help readers understand an issue, solve a problem, or make a decision. ([https://en.wikipedia.org/wiki/White_paper Wikipedia])</blockquote> | <blockquote>A white paper is an authoritative report or guide that informs readers concisely about a complex issue and presents the issuing body's philosophy on the matter. It is meant to help readers understand an issue, solve a problem, or make a decision. ([https://en.wikipedia.org/wiki/White_paper Wikipedia])</blockquote> | ||
The intended audience for this white paper includes, but is not limited to: developers, educators, analysts, site administrators, and instructional designers. It will be written by [https://docs.moodle.org/dev/User:Doug_Belshaw Doug Belshaw], MoodleNet Lead, with input from staff at HQ as well as community members. | The intended audience for this white paper includes, but is not limited to: developers, educators, analysts, site administrators, and instructional designers. It will be written, in the open on this page, by [https://docs.moodle.org/dev/User:Doug_Belshaw Doug Belshaw], MoodleNet Lead, with input from staff at HQ as well as community members. | ||
== Examples of useful white papers == | |||
* [https://wwwimages2.adobe.com/content/dam/acom/en/products/xmp/Pdfs/xmp_whitepaper.pdf Adobe XML Metadata Framework] | |||
== Planning == | |||
* Abstract | |||
* Introduction | |||
** Brief history of Moodle | |||
** Context from which the MoodleNet project has developed | |||
** Reason why now is the right time for MoodleNet project | |||
* Scenarios | |||
** Scenario 1: New user (educator) | |||
** Scenario 2: Site admin | |||
** Scenario 3: Learner | |||
** Scenario 4: Instructional designer | |||
** Scenario 5: Developer | |||
* What is MoodleNet? | |||
** Examples of similar products / services | |||
** System overview | |||
** Benefits in various scenarios | |||
* Technical Specification | |||
** Enabling technologies | |||
** | |||
* Conclusion | |||
* Acknowledgements | |||
* References | |||
Revision as of 11:28, 16 November 2017
To ensure the aims and objectives of MoodleNet are understood by all parts of the Moodle community, we are putting together a white paper that will serve as a touchstone as the project develops.
A white paper is an authoritative report or guide that informs readers concisely about a complex issue and presents the issuing body's philosophy on the matter. It is meant to help readers understand an issue, solve a problem, or make a decision. (Wikipedia)
The intended audience for this white paper includes, but is not limited to: developers, educators, analysts, site administrators, and instructional designers. It will be written, in the open on this page, by Doug Belshaw, MoodleNet Lead, with input from staff at HQ as well as community members.
Examples of useful white papers
Planning
- Abstract
- Introduction
- Brief history of Moodle
- Context from which the MoodleNet project has developed
- Reason why now is the right time for MoodleNet project
- Scenarios
- Scenario 1: New user (educator)
- Scenario 2: Site admin
- Scenario 3: Learner
- Scenario 4: Instructional designer
- Scenario 5: Developer
- What is MoodleNet?
- Examples of similar products / services
- System overview
- Benefits in various scenarios
- Technical Specification
- Enabling technologies
- Conclusion
- Acknowledgements
- References
