The requirements were derived through sessions with school administrators and teachers. The goal of the sessions was to identify the key stakeholders, and their key requirements.
A number of functional requirements are already addressed through Google Apps Education Edition; the list below aims to highlight those that are not currently and are unlikely in the near future to be addressed by Google directly.
A distinction is made between school administrators (corporate interests) and school management (pedagogical interests).
- Students
- Ease of access: single username/password, Web/mobile access
- Continuity of access to my materials (learning portfolio)
- Access from home/library/etc.
- Consistent organisation structure for my information
- Teachers
- Ease of access: single username/password, Web/mobile access
- Visibility to their student’s materials
- Ability to set up and maintain a consistent information structure for students in my class
- Automation of admin tasks for documents (sharing, etc.)
- Some degree of control (co-ownership?) of my students' materials
-
- School Management ("pedagogy")
- Visibility to all student-generated materials
- Ability to control content visibility (public/school/individuals)
-
- School Administration ("corporate")
- Student identity managed by the SMS (single source)
- Access to all accounts and all school resources on Google Apps
- Minimal admin overheads in operating Google Apps
- Protection against students permanently deleting their own materials
-
- Parents & Caregivers
- Read-only visibility to my children’s work (same as workbooks, etc.)
- Ability to participate/collaborate online
| 
