Living Progress - The Class Master - Desktop Wireframe Challenge

Welcome to Living Progress - The Class Master - Desktop Wireframe Challenge!

This project aims at creating wireframes for an application that aims at providing real-time attendance data/information for accurate decision making. This will enable education policy makers to understand the plight of the school going children who are missing classes so that they come up with feasible solutions to remediate the issues.

We are looking for wireframe (axure) solutions based on requirements from our client. We’re also looking to the community to come up with interesting ideas for the workflow - we’re absolutely open to creative solutions!

At the end of this wireframe challenge, we are looking to have a complete solution for the user experience and flow of the application.

This challenge is part of the HPE Living Progress Challenge Blitz Program (Secure top placements in the leaderboard to grab addiitional cash prizes)
 

Round 1

Initial Wireframe Concepts of the below scenarios for checkpoint review.
Common Functionality for All Users:
01 Dashboard
02 View Reports

A. Head Teacher:
03 Registering Teachers

B. Ministry Officials:
Reports 

C. Administrator:
04 Setup/Register Schools
05  School List

Any additional features or screens that will help explain your idea.

Round 2

Final Wireframe Concepts for all given requirements with any checkpoint feedback implemented.
Any additional features or screens that will help explain your idea.

The process of tracking daily attendance at the national and county government level in Kenya has been quite a challenge. This has always been highlighted as a pain point when the national examinations results are released every year. In spite of this challenge, the government is obligated to ensure that all children of school going age attend classes on a regular basis.

Current Problem:
Problem of absenteeism is prevalent amongst pupils in nursery and primary schools in the remote parts of Kenya. If we don’t arrest this issue on a timely basis then the number of school drop outs will definitely increase and eventually will have a lost generation.

Currently teachers record pupils’ attendance information on physical sheets which are filed at the school, there is no automated system in place at the moment.. Therefore this information is not readily accessible to the policy makers.

Solution; The Class Master:
Client is proposing a solution that leverages on data collection and analysis to capture school attendance information on a daily basis. A summary of daily attendance information and the common reasons for absenteeism is uploaded by the teachers through a mobile phone via a USSD code. The data is instantly received on the HP Helion Cloud and it is aggregated for the different sub-counties, counties and at the national government level in predefined formats. Infographics, dashboards and reports are then designed for different stakeholders involved directly in the management of education. This will help in understanding the challenges that are experienced in these educational institutions so as to enable policy makers devise better policies that enhances quality learning and education outcomes.

Wireframe Expectations:
- You must create traditional wireframe call-outs and notes
- Provide us with your interaction and click-path thoughts and suggestions
- The application must be very easy to use and intuitive. Keep that in mind when create your solution for the layout and flow information.

Suggested Screens:
Below are some of the screens that we suggest based on the above concept, feel free to expand on your concepts..

Teachers:
We don’t need a design for this user, but these users play a major part in submitting attendance data:
- The teachers will submit summaries of attendance data and reasons for absenteeism via a USSD code. USSD was preferred so as to make the solution universal since most of the
teachers in remote areas do not have access to smart phones. 
- The simple mobile phone can also keep charge for a couple of days as some of the schools in rural areas do not have.

Common Functionality for All Users:
01 Dashboard:
- This can show the list of statistics or trends in the absenteeism that’s captured on a daily basis
- We are looking for your thoughts on what needs to be shown in the dashboard for different types of users (Head teachers, Ministry Official and Administrator).

02 View Reports: 
Provide options to view report on school attendance, they should be able to view different metrics in the report - for example:
- - - The number of boys and girls absent from school 
- - - Rise in the school attendance rates.
- - - Months/Days of the week/Terms/Years where absenteeism rates will be high.
- - - The common reasons for absenteeism

User Specific Functionality:
A. Head Teacher:
Head teachers will see a basic dashboard with attendance metrics for the classes in their schools along with reasons for absenteeism trends.

03 Registering Teachers:
- Head Teacher will be responsible for registering teachers into this application.
- They should able to view all the field details mentioned below for each of the teacher.
- How should we display the list of teachers in the school..they should be able to view the profile of the teachers. 
- We need to provide option to deactivate teachers.

Profile Information:
The admin application will contain the following information about teachers/tutors:
- Teacher Name: character varying (200) NOT NULL
- Registration Number: character varying (150) (# provided by the Ministry of Education)
- ID No.: character varying (150) (National Identity Number - like SSN in US)
- School ID: Unique Identifier (drop-down with list of schools)
- Admin Unit: Unique Identifier (drop-down with list of counties or other administrative units)
- Status (This just indicates if this record is active / inactive or deleted, default value should be "Active")
- Employer ID: Unique Identifier (Teachers may be employed nationally, at county level, or locally -- teacher type by reporting structure) 

B. Ministry Officials:
Ministry officials will see reports across multiple schools/ classrooms

Reports: 
In addition to list of above reports mentioned in “point 02”, they will be able to view below reports as well:
- Comparative analysis for different regions.

C. Administrator
The admin is responsible for onboarding and setting up schools/ teachers

04 Setup/Register Schools:
- They will help setup/register schools into this application..
- We need to show the list of already registered schools along with their absenteeism statistics?
- Provide options to remove, edit a school.

As part of the registration process administrators will enter the following information about the school:
- Code: character varying(150)
- School Name: character varying(250), NOT NULL
- Base Admin Unit: unique identifier, NOT NULL
- School Status (Values: Public, Private)
- Gender
- Day Boarding Status: character varying(50)
- Date Started: date
- Latitude: character varying(150) - Longitude: character varying(150)
- Status (This just indicates if this record is active / inactive or deleted)
- School Level: unique identifier, NOT NULL (Values: Nursery, Primary)

05  School List:
- Administrators will need a list view of schools so they can navigate into each and review basic information about the schools.  
- Administrators should be able to navigate from the list to a school edit form which will be basically the same as the school registration listed above.

06 Registering Teachers:
- This provides same functionality as the head teacher

07 Manage Users:
- They will have the ability to add and delete users.
- Looking for your thoughts on how this can be shown.

08 Design Reports:
- Provide the ability to drill down into a detailed view (National > Counties > Sub-counties > Ward > School).
- Only 3 reasons for absence (School fees, Sickness and Unknown) per administrative unit, reasons separate by Gender in the USSD App.
- Come up with thoughts on what metrics need to be shown to allow them to generate below reports. We are looking for below reports to be included in your wireframes, client has provided few sample reports to help you get started - looking forward to your thoughts on how better these can be designed/presented.

D. System Administrator
09 System Configuration:
- System administrators need a way of maintaining basic configuration information about school systems, administrators, teachers, and students.  Please create a screen which allow administrators to maintain the following lists of values in the app:
- - Administrative Units:  This is a hierarchy of Counties (in Kenya), Subcounties (parent is counties), and Wards  (parent is subcounties or counties)
- - Absenteeism Reasons (these are maintained in association with a particular county) - for example:  School Fees, Sickness, Unknown
- - Administrator Level (Ward Educational Admin, Sub-county Educational Admin, County Educational Admin, Country Educational Admin)
- - Terms - Values are “Term 1”, “Term 2”, and “Term 3”
- - Academic Year - 2016, 2017, 2018, etc.

- System Administrators will assign the appropriate level for the Administrator users.  This will control their access to data within their hierarchy - County, Subcounty, Ward, or School.

Sample Reports:
Please take a look at the sample reports for reference (Attached to the challenge)
- Provide a way for the users to absenteeism report at different levels of administrative units: National, Counties, Sub-counties, Ward, School, so provide appropriate options to enable them to drill-down to detailed view.
- They should be able to view all the nursery / primary schools at different levels of hierarchy and drill down to more detailed views!
- They should be able to generate a report that helps them view the absenteeism report for a specific nursery school or a primary school.
- Would it be good to provide option to generate a comparison report between schools?
- How can they view or compare the absenteeism for a single county or multiple counties at a time..?
- We need a way for the user to view a absenteeism reason's summary report for a specific nursery school or a primary school, do you think we can allow user to select multiple schools to see a comparison?
- Provide a way for the user to dive into the details that shows girl absenteeism trend line analysis and allow a year range to be selected.
- Absenteeism Reasons setup County level for Preschool schools
- Absenteeism Reasons setup County level for Primary Schools
- Nursery Schools managed at County Level
- Primary Schools managed at National Level

Terminologies
Teachers
Schools
Academic Year

Terms:
We typically have 3 terms in nursery and primary (1st Term, 2nd Term, 3rd Term)

Class:
Nursery Classes have 3 academic years: Baby, Middle, Final Class
Primary Classes have 8 academic years i.e from class 1 - 8  (1st Grade in US not Kenya!)

New to axure RP, get started right-away!!
Here are some quick tutorials to help you get started http://www.axure.com/support

Target Audience:
Teachers, Head Teachers, Ministry Officials

Judging Criteria:
Your submission will be judged on the following criteria:
- User experience
- Completeness and accuracy of the areas of functionality and content
- How well your wireframes provide a consistent user flow and clear information architecture for the application

Submission & Source Files:
Preview Image
Create your preview image as one (1) 1024x1024 JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.

Submission File
Generated HTML files with all the requested contest requirements stated above.

Source Files
Wireframes should be built in axure. The resulting files should have generated HTML files. Also, all the content must be listed and the pages are linked together to show page flow.

Final Fixes
As part of the Final Fix phase, you may be asked to remove, update, or change some features of the wireframe.