Courseware Scenario
From LiquidPubWiki
Contents |
Introduction
The courseware project is about maintaining a collection of materials related to a specific subject. It could be seen as a virtual library or repository in which materials are kept. This repository is maintained by a closed community. As in an editorial, the changes and updates could be approved by special members playing roles of Editors.
The life cycle of these projects involves a continuous evolution of a) the repository itself by adding new materials and of b) each material by keeping it up to date with the new versions. These activities could be free (members update the materials as they want), or require a consensus through an evaluation phase.
Considering that the materials should be made public, the project members must be allowed to create views or snapshot of the repository and assign them a visibility (to everybody or selected users). These snapshots create a collection of specific materials (and versions of them).
Books could be developed using this approach, but in this case, the book would be broke down into chapters as different materials of the repository. This way the authors could maintain updated the chapters and publish editions (take snapshots) more often. In general, the courseware could allow the publication of arbitrary kind of materials: ebooks, talking books, course support materials, code library, etc. Any global concept that require being up to date.
Roles
In this scenario there are no special roles for the courseware project members, that is, everyone share the same plain role. Nonetheless, access rights are assigned to members in order to provide differentiated permissions.
Artifacts
In this scenario we found the following complex artifacts: the courseware, class syllabus and class material.
The Courseware
A main artifact in this scenario is courseware, which is composed of arbitrary kinds of heterogeneous materials. This means that courseware as a complex artifact evolves as new artifacts become part of it or its current artifacts evolve. Thus, this artifact can be subject of the following processes:
- Elaboration process: This process is composed of an iteration over evolution and publication phases. By evolution we mean adding new materials and new versions of existing materials.
- more..
Class syllabus
The class syllabus is another artifact that is developed collaboratively by courseware project members. It could be subject to the following processes:
- Elaboration process: This process is composed of the phases of elaboration, review and publication.
- Review process: This review is collaborative. We can view this process as a peer-review one.
Class Material
- I'll probably take this out of here..' :-/
The class material represents different kind of documents that can be put in the repository as part of the courseware. These materials can be any of books, slides, exercises, or code.
Data model
Functional requirements
http://spreadsheets.google.com/pub?key=pFiqGdICxhJKXF20GBnPkeA&gid=4
Uses cases
Test cases
See also
- Requirements main article
