nGenera Community - nGenera Reference Architecture

« nGenera Apps Team Attack Plan - July 2008 | Home | Radiohead again leaves us thinking: Did they just do that? »

nGenera Reference Architecture
belongs to Apps Team

, Architecture Review Team

by Brittain on Jul 14, 2008 - 07:21 PM read 1832 times

Last updated: 11/12/2008.

Here's my business view of the nGenera Platform Reference Architecture and corresponding product landscape. This document scopes the elements included in the nGenera Platform and depicts their rough ownership:

There's a few talking points for both views:

First, we deliberately avoid the traditional stacked representation so often seen. In actuality, as an SOA, the RA functions more peer-to-peer than layered. This permits additional flexibility, reusability, and integrateability. Also, we deliver our user experience through composite apps built on this SOA core.
Second, we explicitly represent the four product domains we play in - nGen Customer, nGen Leadership, nGen Sales, and nGen Talent. This reinforces the principle that we are a solution provider and not an ESB or similar pure play horizontal technology.
Third, we convey that we're an open, heterogeneous system. This applies across all levels of granularity - interoperability with third party SaaS applications, cloud services, and open source components.
Last, we represent the leverage created by reusing application data stores and nGenera's "soft assets" throughout the RA and it's dependent applications.

Version with working notes: reference_architecture.vsd

Drill in version on the services layers: reference_architecture_expanded.vsd

Last published, simplified graphic: