Development:Lesson Specification: Difference between revisions
From MoodleDocs
No edit summary |
No edit summary |
||
| Line 42: | Line 42: | ||
==Use Cases== | ==Use Cases== | ||
===UCXXX1 Create a lesson=== | ===UCXXX1 Create a lesson=== | ||
====Base scenario | ====Base scenario==== | ||
====Pre conditions==== | ====Pre conditions==== | ||
*An empty lesson has been created | |||
*(a) The system displays the course page | |||
*(b) The system displays the lesson page | |||
====Post conditions==== | ====Post conditions==== | ||
Revision as of 03:29, 11 June 2008
Functional Specification Revisions:
- 0.1 - 11/06/2008 - Jerome Mouneyrac - Draft Version from existing module in Moodle 1.9
- 1.0 - XX/XX/XXXX - Jerome Mouneyrac - Final Version for 1.9
Audience: user/implementer/QA
Status: approved/module implemented
Related Documents:
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 module.
requirement
- A need or necessary condition of the finished module.
shall
- Used in the Requirements section 'shall' means that the item is absolutely necessary as stated.
should
- Used in the Requirements section 'should' means the item is desirable, but not required. Wishy-washy, but often unavoidable.
TBD
- To Be Decided/Determined.
user
- Person(s) who will deal with the completed module of this specification.
Requirements
Issues
User Interface
Creation page
Use Cases
UCXXX1 Create a lesson
Base scenario
Pre conditions
- An empty lesson has been created
- (a) The system displays the course page
- (b) The system displays the lesson page
