Difference between revisions of "Software architecture notes"
From Organic Design wiki
m |
|||
Line 1: | Line 1: | ||
+ | {{stub}} | ||
This document describes how existing technologies can be packaged to create a platform. The high-level conceptual development path for platform technology is described [[Platform Roadmap|here]]. We will describe our requirements and use cases in order to determine the correct components to use for various aspects. | This document describes how existing technologies can be packaged to create a platform. The high-level conceptual development path for platform technology is described [[Platform Roadmap|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 | *Groupware applications --> emails, contacts, calendars, tasks, projects | ||
Line 13: | Line 14: | ||
**Invoicing & reporting | **Invoicing & reporting | ||
**Book keeping | **Book keeping | ||
+ | *[[Physical network]] | ||
[[Category:platform]] | [[Category:platform]] |
Revision as of 22:20, 27 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?
- Personal portal and broadcast centre
- 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
- Physical network