May 10 Design UoStrath managing course info


Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • System will provide two main functionalities: First one is related to class and course design stage during which designer needs to provide class or course details by filling in appropriate forms. System will therefore provide online forms repository where users will be able to fill in class or course details and store them within the system. To ensure high quality of class or course design, a designer should comply with pedagogical design guidelines and for this purpose system will provide easy and instant access to design guidelines and examples of good design. Design of a class or course is usually a collaborative work therefore system will facilitate cooperation by providing features such as forms versioning, draft versions, online discussion boards, email alerts. Second main functionality is related to what happens after class or course proposal is submitted for approval and this involves class or course to be reviewed and approved by various committees and institutional departments (e.g. faculty committee, senate, library, disability service, resource allocation and planning). System will therefore act as an approval workflow management and tracking tool and will provide such features as: online access given for committee members to view submitted proposals Class / course proposal workflow state management which may be changed by various events triggered by various people at various workflow stages (e.g. Senate may approve class proposal which in effect will change class proposal’s state from “Being reviewed” to “Approved”) assigning tasks to committee members, automatic timers, email alerts, Logging messages related to proposal’s approval / review decisions in a form of online discussion which may be viewed by class designer Workflow routing dependant on decisions being made (e.g. approve decision will route proposal to the next step but “reject – sent back to re-design” will re-route proposal to the designer
  • May 10 Design UoStrath managing course info

    1. 1. Managing Course Information PiP Project
    2. 2. Drivers <ul><li>top issues faced </li></ul><ul><ul><li>Tracking and Auditing </li></ul></ul><ul><ul><li>Compliance monitoring </li></ul></ul><ul><ul><li>Supporting the translation of University policies into actual designs </li></ul></ul><ul><ul><li>Risk management and portfolio management </li></ul></ul><ul><ul><li>Marketing </li></ul></ul>
    3. 3. Issues and Bottlenecks Completing forms creates a teachable moment
    4. 4. Issues and Bottlenecks
    5. 5. Different Perspectives <ul><li>I don't need that information (so why do we collect it) </li></ul><ul><li>I can't see the point of that information (ditto) </li></ul><ul><li>I need this information but there is nowhere for me to put it (so I put it somewhere else) </li></ul><ul><li>I don't have that information (yet) so I won't enter anything </li></ul><ul><li>The process is too onerous (see above) </li></ul><ul><li>We ought to collect more information about X </li></ul>
    6. 6. That boil down to <ul><li>Get the right information in </li></ul><ul><ul><li>By the right people </li></ul></ul><ul><ul><li>At the right time </li></ul></ul><ul><li>Make it accessible </li></ul><ul><ul><li>To the right people </li></ul></ul><ul><ul><li>At the right time </li></ul></ul><ul><li>Flag </li></ul><ul><ul><li>Its position in the approval process </li></ul></ul><ul><ul><li>What needs to happen next </li></ul></ul>
    7. 7. System Users
    8. 8. Squaring the Circle
    9. 9. System Functionality <ul><li>Online, standardised class/course descriptor forms </li></ul><ul><li>Single proposals repository </li></ul><ul><li>Pedagogical support content available during design </li></ul><ul><li>Forms versioning, discussion boards, email alerts </li></ul><ul><li>Proposals workflow state management and tracking </li></ul><ul><li>View submitted proposals, record decisions made </li></ul><ul><li>Assigning workflow tasks, automatic timers, email alerts </li></ul><ul><li>Logging messages related to approval / review decisions </li></ul><ul><li>Attaching documents from meetings </li></ul><ul><li>Workflow routing depending on decisions made </li></ul>
    10. 10. Some principles <ul><li>Unified not Homogenised </li></ul><ul><ul><li>Add and refine </li></ul></ul><ul><ul><li>Hide what is out of scope </li></ul></ul><ul><li>Roles-based perspectives </li></ul><ul><li>Make as much visible as possible </li></ul><ul><li>Single source data </li></ul><ul><ul><li>Hold only what needs to be held </li></ul></ul><ul><ul><li>Hold a complete record </li></ul></ul>
    11. 11. Different Questions <ul><li>Form filling as a catalyst for design </li></ul><ul><li>Just-in-time support </li></ul><ul><li>Option lists </li></ul><ul><li>Fine granularity </li></ul><ul><li>Questions that challenge (designers) </li></ul>
    12. 12. Current Work understanding and articulating their own requirements