On this week we focused on defining the scope, purpose, and objectives of our project. These are the results:

Badges are our main feature. They are the reason this project is built. A badge has the following properties:

  • Information: data related on what the badge owner did, when was it granted, etc.
  • Categories: tags such as “sports”, “health”, “altruism”, etc.
  • Expiracy date: this expiracy is on being granted, not on being owned.
  • States: a badge can have different values (eg. a badge for number of owned badges, which can change from 10, 20, 50, 100, etc).
  • Number of uses: it can be granted to a limited number of people.

We also defined the following roles:

  • User:  a common student/teacher. Can win badges. Has permission to request a badge.
  • Badge admin: a common student/teacher. Has permission to grant a badge.
  • Super admin: controls all the system.

Badges can be of the following types:

  • Automatic: triggered by system properties/events, such as years in the system, number of badges, etc.
  • Event: limited time badges, which can be delivered by two ways: QR/code or geolocation.
  • Direct grant: a badge admin can give a badge to a custom user (via email).

The idea of this application is not that users have a social network with a feed: there are many of these (Facebook, Twitter, Reddit, Instagram, etc). And to be honest, as a student I don’t really see myself using this as a content source. The main purpose is for the students to have a shareable profile as a CV.

The other important delivery is our mockups. They are very simple, but they work.