Golden Orb Technologies Enterprise Application & Services Ecosystem
The Golden Orb Technologies (GOT) Enterprise Application & Services Ecosystem (EASE) has been created to enable explicit re-use of software components for highly flexible, high value and extendable enterprise solutions.
The Golden-Orb Meta-Framework can be considered to be both a product and a process.
Executive Summary
The Golden-Orb EASE can be considered to be both a product and a process. It is a total "end to end" solution delivery model encompassing the entire software development and asset management life cycle.
It is independent of contributing components and technologies. Individual software components and technologies are replaceable - with a key element being explicit methodologies for (re-useable software) asset utilisation, management and disposal.
GOT EASE = methodologies, business processes, re-useable software components (including industry specific Business Objects)
Business Benefits - ROI
GOT EASE = 70% of IT Strategy Core Components - Concentrate on 30% specific industry applications
Benefits - Openness, Speed, Flexibility, Control, Re-use
-
Open structure - open standards based with a focus on supporting business unit performance though flexible business functionality rather than technical boundaries between application layers.
-
Speed - enterprise architecture that allows the separation of concerns enabling architectural and application development to work in parallel.
-
Control and Flexibility - solutions adapt quickly to business needs and system changes by loosely coupling business logic from infrastructureReuse - solutions that allow for re-use of business components across applications and re-use of architecture across applications as well as re-use of development skills across projects.
-
Enables - Rapid prototyping and development so you can define your business model and processes.
Component based Development
Component based development describes the process of developing applications from software components. The advantages of component-based development can be illustrated by comparing it with more traditional once off development.
|
One off development |
Component based development |
| Predictability |
Low degree of predictability of delivery and resource effort |
High degree of predictability of delivery and resource effort |
| Speed / Cost |
Longer delivery time and resource effort |
Shorter overall delivery time and lower resource effort |
| Flexibility |
Hard to make flexible |
Highly flexible |
| Infrastructure |
Infrastructure difficulties most likely must be overcome. |
Component based means improved flexibility and less infrastructure issues |
| Testing |
Must test as a unit. Can only test once built |
Components are pre-tested, ready to go building blocks. |
| Integration |
Integration capabilities must be build |
Built for integration |
Component based development is therefore about the assembly and configuration of pre-built (and tested) components. It therefore provides a powerful and efficient development paradigm.
Separation of Concerns
A key principle in GOT EASE is the separation of concerns. This involves the design of patterns (processes) that deals with demarcating the concerns or issues in a problem space and tackling them as independently as possible. |