1. MultiRole Course – Design & Process 2004/11/18 徐天送

2. Outline IMS LD Service MultiRole Course – Design & Process Conclusion

3. IMS LD Service Send Mail Conference Index Searching

4. Service - Conference (details)  Can read (listen/see) the information, and can contribute to the conference.  Have only reading rights; they may not contribute.  Be allowed to create new sub conferences and delete conferences he created.  Persons who have the right to control and change the contributions of participants before they are made visible to other participants or observers.

5. Open Source – ChipChat - 1

6. Open Source – ChipChat - 2

7. Open Source – ChipChat - 3

8. MultiRole Course – Design & Process LD Structure MultiRole Course Scenario Process Design

9. LD Structure – Act & Role-Part Act Role-part Activity- Structure Learning- Activity Role Learning- Activity Activity- Structure Support- Activity Support- Activity Role concurrent

10. 加減法課程 Service MultiRole Course Scenario John Mary Role: Class A Role: Class B 加法課程 加法 1 加法 2 Chat Room 減法課程 減法 1 減法 2 Chat Room Complete

11. Messages John Mary LoadCourse(role=classA) courseID LoadCourse(role=classB) Select(role=classB, selectedID=LA_Sub1) Select(role=classB, selectedID=LA_Sub2) Select(role=classB, selectedID=S_Chat) Select(role=classA, selectedID=LA_Add1) Select(role=classA, selectedID=LA_Add2) Select(role=classA, selectedID=S_Chat) Complete(role=classB) Complete(role=classA) Break(role=classB) Break(role=classA) Quit(role=classB) Quit(role=classA)

12. Process Process Design - 1 Class A Receive LoadCourse Class B Receive LoadCourse Flow 減法加法 There is no constraint to specify that two role-parts have to be started at the same time.

13. Process Process Design - 2 Class A Receive LoadCourse Class B Receive LoadCourse Flow Class AClass B Flow 減法加法 But this process make client wait for the reply message. Learner may confuse the views – it could be misunderstood as an error by learner.

14. Loading Mechanism 2. Tell the learner should wait for other participants John Mary Process 1. Join Course 2. Reply 3. Check Course Ready 4. isReady = false 7. [isReady] LoadCourse 5. Join Course 6. Reply Ready 3. The client periodically send message to process 3. Check Course Ready 4. isReady = true

15. Process Process Design - 3 There are still some problems in this. At first, the flow activity merely has fixed number of sub-activities. It means that we don’t have multiple persons to match one Role-Part. Class A Receive JoinCourse Class B Receive JoinCourse Flow Set CourseReady=true Class A Receive LoadCourse Class B Receive LoadCourse 減法 加法

16. Another Scenario Process John Kurt Mary A B A1 1.The Process have fixed number of sub-activities in the flow. 2.The activity block A has the same context with A1.

17. Process Design – 4 (conceptual) Main Process JohnKurt Mary AB Sub Process 加法 (John) Sub Process 加法 (Kurt) Sub Process 減法 (Mary)

18. Main Process Process Design – 4(detail) Class A Receive JoinCourse Class B Receive JoinCourse Flow Set CourseReady=true Class A Receive LoadCourse Class B Receive LoadCourse Sub Process 加法 Sub Process 減法 Reply Sub-Process BReply Sub-Process A Async Invoke

19. Sequence Diagram

20. Conclusion - 1 Completed acts are still left visible and accessible, but the interface should sharply distinguish them from the current act, and make it clear that they are only available for reference as part of the learner’s history.

21. Conclusion - 2 In runtime the time limit of the play overrules the time limit on act and that one on the role-parts. When-role-part-completed

22. LMS Service Design

23. Testing External Web Services Supported Services Repository LMS Services Domain Model Process Container Process Instance Course Sequencing Presentation Logic Client Message Mapping Message Sender View Browser Message Sequence LMS Behavior Functional Test Process Behavior