ITE Platform Design

ITE Platform Design

Data is Platform concern – does not imply central, could be distributed – is managed according to a Master Data Management MDM strategy
Data use Patterns are Application concern – Applications should be modular, both commonly shared and local specific

1.

Platform Concerns are:

Master Data Management
Interoperability
Connectivity
Governance and Roles

Platform Pattern: Someone produces the data -> Someone observes the data

2.

Application Concerns are:
Local Data
Local Conditions
Local Rules

Application Pattern: Verify, Filter and Ruled use of Data

1.1

Patterns of Data Distribution

Publish Subscribe – distribute data
Point to Point – distribute computing
Request Reply – distribute platform (data and function)

1.2

Master Data Patterns and Platform resposnibilities

Collaborative – Event Management
Operational – Quality Management
Analytical – Life Cycle Management

Information service patterns, Part 4: Master Data Management architecture patterns
http://www.ibm.com/developerworks/data/library/techarticle/dm-0703sauter/

2.1

Data Warehousing is a Life Cycle Management function performed by Platform
BI – Business Intelligence is a Analytical application

3. Modules – http://www.slideshare.net/odino/soa-with-symfony2-confoo-2014-in-montreal-ca

3.1 Platform Modules (Super Patterns)

3.1.1 Domain Management Module
3.1.2 Builder Module
3.1.3 Master Data Management Module
3.1.4 System Status Module
3.1.5 Roles Module
3.1.6 Access Control Module
3.1.7 Data WareHouse Module [cubes, archives]
3.1.8 Topology Module (for distributed systems – where does the call go for that service – mini ESB)
3.1.9 Profile Module

3.2 Application Modules (Local Patterns)

3.2.1 CRUD on all Domain Entities
3.2.2 Dashboard Module
3.2.3 Reports Module
3.2.4 User Management Module
3.2.5 Single Signon Module

http://odino.org/why-we-choose-symfony2-over-any-other-php-framework/

Leave a Reply