MOT Analysis (C,D of Project Theme 1)

MOT Analysis (c,d of project theme 1): Domain model (conceptual layer) and Goal and Constraints model (lesson layer) Analysis

Instructions:  Please address the issues below in two short reports, each of min. half a page (max. 1 page).  Make this report of question-answer type.  Please note that for each question asked (or issue raised) you have to only take into consideration the existing conceptual – and lesson layer implemented in MOT, and the user model and adaptation model that you have designed yourself. Please try to be critical, but constructive.  Also add (and answer) for each point of view (i.e., table) a question of your own.

Table 1. Goal point of view (data representation & manipulation) evaluation Collaboratio - What are the good points? n - What are the problems? Suggestions for solving them? How did you try and more authors solve them? collaborating at a course; Completeness - What is the (perceived) connectivity degree? Should there be more looking at connections (more types), or less? What would this possible extra given goal connections be? What should be deleted (e.g., is superfluous)? (e.g., URD), - What is the perceived percentage of completeness? I.e., What is the LAOS two expressivity? (how much can be represented with the system – e.g., layer counterexamples) Adaptivity - How much adaptivity to the design goal is perceived? - Can the desired grain size (for concepts & lessons) be appreciated/ achieved? - Can the desired relations be represented? - Would you want extended adaptation rules (grouping together the functionality of more than one IF-THEN rule)? If yes, what kind of rules do you have in mind? Design range - How much more can be achieved in this way as compared to the linear model?

Table 2. USI point of view evaluation Ease of use - information display (e.g., on screen at one time), information order, distance of search (depth); - minor issues: color scheme, ease of access, ease of installation Robustness - parallelism (data overlap), security, recovery Complexity - some ideas on possible reduction of this complexity; of interface