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