Difference between revisions of "Wishlist for architecture"

Revision as of 10:10, 12 September 2013

Listening to device reporter - 0.2 / 0.3 (Android)
Lifecycle manager and its relation to the service synthesizer tool.
Connecting semantic framework with the solution registry.
Mapping internal application users to GPII users. (Single sign on) - 0.3
Document directory structure on the wiki - 0.2
Document directory structure of the code
Conditional preferences (example Omnitor; change settings depending on which person you’re calling) - after actual device/environment reporter - 0.2/0.3
Supporting binary data
Proper device reporting - 0.2 / 0.3 (Android)
Common terms registry / listing
Snapshotting tool - 0.4 (start planning soon)
Security - 0.3 (or at least have a plan!)
Thin matchmaker (and transformer) / allowing web based applications and other apps more to use the common setting - 0.2
.INI settings handler 0.2 (needed for pilots)

Continue the model transformation work.
Get the pilots branch merged into master.
- Need to document clear JIRAs and wiki pages explaining each feature and the steps to test them.
Automated integration testing (building on Cloud4all Integration Tests and Cloud4all Pilot Scenario Tests).
Release GPII/Cloud4all v0.2

Android convergence.
A re-envisioned Security Gateway (Oauth 2.0 & UMA).
Web-based Flow Manager for web personalization.
Error handling and logging improvements. (See the thread from June 2013, the message from July and JIRA issue GPII-139.) The logs should make benchmarking of the matchmakers easier.
Preference editors (see User Preferences UX).
Settings snapshotter.
Conditions in preferences set (see Proposal for Declarative Preference Conditions).
Next generation Ontology Service.
Separate ‘GPII framework’ from universal repository and offer it as a reusable framework for building apps (‘Kettle’).
Unified Listing.
Common Terms Registry (see Registry - database planning and Registry - choice of database).

@@ Line 29: / Line 29: @@
 * A re-envisioned Security Gateway (Oauth 2.0 & UMA).
 * Web-based Flow Manager for web personalization.
-* Error handling and logging improvements.
+* Error handling and logging improvements. (See [http://lists.gpii.net/pipermail/architecture/2013-June/001052.html the thread from June 2013], [http://lists.gpii.net/pipermail/architecture/2013-July/001144.html the message from July] and [http://issues.gpii.net/browse/GPII-139 JIRA issue GPII-139].) The logs should make '''benchmarking of the matchmakers''' easier.
 * Preference editors (see [[User Preferences UX]]).
 * Settings snapshotter.