Difference between revisions of "Software architecture notes"
From Organic Design wiki
m |
(re-org a bit) |
||
| Line 2: | Line 2: | ||
*Groupware applications --> emails, contacts, calendars, tasks, projects | *Groupware applications --> emails, contacts, calendars, tasks, projects | ||
*Global accounts and synching via robot framework - OpenID? | *Global accounts and synching via robot framework - OpenID? | ||
| − | * | + | *CMS |
| − | * | + | **Content (procedures, roles, etc.) |
| − | + | **Ontology portals structure | |
| − | *Content (procedures, roles, etc.) | + | **Records, forms & queries |
| − | *Organisational setup (forms) and org. templates | + | **Organisational setup (forms) and org. templates |
*E-commerce | *E-commerce | ||
| + | **Payment methods/merchant accounts | ||
**Accounts management | **Accounts management | ||
| − | **Invoicing | + | **Invoicing & reporting |
**Book keeping | **Book keeping | ||
[[Category:platform]] | [[Category:platform]] | ||
Revision as of 05:34, 23 September 2010
This document describes how existing technologies can be packaged to create a platform. The high-level conceptual development path for platform technology is described here. We will describe our requirements and use cases in order to determine the correct components to use for various aspects.
- Groupware applications --> emails, contacts, calendars, tasks, projects
- Global accounts and synching via robot framework - OpenID?
- CMS
- Content (procedures, roles, etc.)
- Ontology portals structure
- Records, forms & queries
- Organisational setup (forms) and org. templates
- E-commerce
- Payment methods/merchant accounts
- Accounts management
- Invoicing & reporting
- Book keeping
