Lesson Specification: Difference between revisions
From MoodleDocs
No edit summary |
No edit summary |
||
Line 11: | Line 11: | ||
[[Lesson Test Plan|Lesson Test Plan]] | [[Lesson Test Plan|Lesson Test Plan]] | ||
==Scope of this Functional Specification== | ==Introduction== | ||
===Scope of this Functional Specification=== | |||
This document is about functional specification for Moodle lesson module. | This document is about functional specification for Moodle lesson module. | ||
===Glossary=== | |||
'''implementer''' | |||
The person or team who will turn this specification into a working product. | |||
'''requirement''' | |||
A need or necessary condition of the finished product. | |||
'''shall''' | |||
Used in the Requirements section 'shall' means that the item is absolutely necessary as stated. Example: The product shall support at least one million master records. | |||
'''should''' | |||
Used in the Requirements section 'should' means the item is desirable, but not required. Wishy-washy, but often unavoidable. Example: The product should maintain the same order of data entry fields as current system XYZ. These requirements will be implemented where feasible within the other constraints. | |||
'''TBD''' | |||
To Be Decided/Determined. | |||
'''user''' | |||
Person(s) who will deal with the completed product of this specification. | |||
==Requirements== | ==Requirements== |
Revision as of 03:11, 11 June 2008
Functional Specification Revisions: 0.1 - 11/06/2008 - Jerome Mouneyrac - Draft Version from existing module in Moodle 1.9
Audience: developers/designer/QA
Status: module implemented
Related Documents: Lesson Manual User / Documentation Lesson Smoke Test Lesson Test Plan
Introduction
Scope of this Functional Specification
This document is about functional specification for Moodle lesson module.
Glossary
implementer
The person or team who will turn this specification into a working product.
requirement
A need or necessary condition of the finished product.
shall
Used in the Requirements section 'shall' means that the item is absolutely necessary as stated. Example: The product shall support at least one million master records.
should
Used in the Requirements section 'should' means the item is desirable, but not required. Wishy-washy, but often unavoidable. Example: The product should maintain the same order of data entry fields as current system XYZ. These requirements will be implemented where feasible within the other constraints.
TBD
To Be Decided/Determined.
user
Person(s) who will deal with the completed product of this specification.
Requirements
Issues
User Interface
Creation page