Changeset 13175 for main/waeup.kofa/trunk/README.txt
- Timestamp:
- 17 Jul 2015, 03:35:16 (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
main/waeup.kofa/trunk/README.txt
r13174 r13175 9 9 about WAeUP. The system controls all kinds of application and 10 10 student registration processes at large schools and universities in 11 Nigeria. It is a generic system which can be deployed by and is11 Nigeria. It is a generic system which can be deployed by, and is 12 12 useful to most universities, colleges or schools wordlwide. 13 13 14 Kofa is really an allrounder. The best way to briefly describe Kofa, 15 is to explain what Kofa can *not* do for you, rather than trying to 16 describe all the features in just a few words. Kofa is primarily not 17 an e-learning system, although, it has some basic content management 18 features which can be used by lecturers to disseminate course 19 material. Kofa is also not a scheduler which generates lesson plans 20 or timetables for lecturers or students. Although students register 21 their courses with Kofa and can see or print course lists for each 22 academic session, so far, courses do not contain information, when 23 or where they take place. However, due to the modular design of Kofa, 24 a scheduler or room planner could be easily added. 14 Kofa is really an allrounder. The best way to briefly describe its functionality, is to explain what the software can *not* do for you, rather than trying to describe all its features in just a few words. Kofa is primarily not an e-learning system, although, it has some basic content management features which can be used by lecturers to disseminate course material. Kofa is also not a scheduler which generates lesson plans or timetables for lecturers or students. Although students register their courses with Kofa and can see or print course lists for each academic session, so far, courses do not contain information, when or where they take place. However, due to the modular design of Kofa, a scheduler or room planner could be easily added. 25 15 26 Kofa is divided into sections. To each section belongs afolder in16 Kofa is divided into sections. Each section has its own folder in 27 17 Kofa's :ref:`object database <object_database>`. When starting Kofa 28 18 in debug mode:: … … 41 31 42 32 43 Each of these subfolders in the root folder of the database belongs 44 to such a section. The section structure can be figured as follows:: 33 The section/folder structure can be figured as follows:: 45 34 46 35 root (Database Root)
Note: See TracChangeset for help on using the changeset viewer.