DRAFT - Portlets Splits and Review

[srenault-meeds]

Rationale

Using the Meeds Layout Manager hilights the fact that some portlets need to be reviewed:

• Some needs indeed to be splitted for better apps management in pages: rewards or reputations portlets in overview page can be splitted indeed

1. Functional Requirements

Top User Stories

1. Split of portlets

• split portlet My Reputation to two different portlets: userBadges & userKudos
• split portlet My Reward to two different portlets: userRewards & pinnedPerks
• split portlet ProfileStats to tow different portlets: userNetwork & userActivity

2. Review of portlets

Ability to change list sorting of some portlets

• Enable for admin or publisher of the platform to change settings of the pinnedPerks, challengeOverview, programsOverview
• So the user can choose wich perks to list: last created, last updated, manually -> then select from a suggestor

contributionOverview & userActivity

• When activity during the last period, provide an access to achievement list of the user (drawer)
• Period equals to the period set for rewarding

Impacts

Gamification

Notifications

Analytics

Unified Search

2. Technical Requirements

Expected Volume & Performance

Security

Extensibility

Configurability

Upgradability

Existing Features

Feature Flags

Property Name	Default Value	Target Audience	Functional Behaviour

Other Non Functional Requirements

3. Impacts

Documentation

Training

4. Software Architecture

Security

Access

• GUI
• API

Services & processing

• Ex: Scheduled Jobs

Data and persistence

• Macro data model
• Persistence layer
• Use of caches

  Clustering

Multitenancy

Integrations

Migration strategy

5. Annexes

• Reasoning that explain the technical choices
• Impacts
• References