| Key resources for design outputs |
|---|
| Key resources for design outputs in MLE design. |
|
http://www.jiscinfonet.ac.uk/Resources/external-resources/MLE-diagram.pdf A workshop was held in the summer of 2002 to explore the possibility of developing an overall description of a Managed Learning Environment (MLE) in a diagrammatic form. This report is one of the outcomes of that workshop, and it aims to explore the use of tools such as diagramming and requirements gathering to focus discussions and to help in the development of a shared understanding of the MLE. |
|
MLE Diagramming report - Appendix on Requirements http://www.jiscinfonet.ac.uk/Resources/external-resources/MLE-Requirements.doc Following the workshop that explored the possibility of developing an overall description of a Managed Learning Environment (MLE) in a diagrammatic form, this set of possible requirements was produced as an appendix to the whole report. |
|
MLE Diagramming report - Summary http://www.jiscinfonet.ac.uk/Resources/external-resources/diagramrepsum A summary of the workshop held in the summer of 2002 to explore the possibility of developing an overall description of a Managed Learning Environment (MLE) in a diagrammatic form. |
|
Developing Object Orientated Software for the Macintosh N. Alger and J. Goldstein. Although the title mentions the Macintosh the first few chapters are applicable to any Object oriented type development. |
|
Developing Object Orientated Software for the Macintosh N. Alger and J. Goldstein. Although the title mentions the Macintosh the first few chapters are applicable to any Object oriented type development. |
|
A Framework for Information Architecture http://www.jiscinfonet.ac.uk/Resources/external-resources/A_framework_for_information_architecture With increasing size and complexity of the implementations of information systems, it is necessary to use some logical construct (or architecture) for defining and controlling the interfaces and the integration of all of the components of the system. This paper defines information systems architecture by creating a descriptive framework from disciplines quite independent of information systems, then by analogy specifies information systems architecture based upon the neutral, objective framework. Also, some preliminary conclusions about the implications of the resultant descriptive framework are drawn. The discussion is limited to architecture and does not include a strategic planning methodology. |
good practice and innovation
