| Click on the links below to learn more |
|
| Component Applications |
| The solution is visualized as a set of independent applications that operate together to perform the customer's business processes. These applications are designed in a modular fashion so that it is possible to remove a particular application from the setup and replace it with another system providing similar functionality. |
|
| |
| Interface Driven |
We envisage that there may be existing legacy systems and hence it is important that these applications have the ability to communicate or do data transport in an existing IT landscape.
The applications implementing the 'interface driven' principle can also participate in global business processes, i.e. business processes that span multiple applications. In this case, the global business process will communicating with each application using services provided in that application's service interface.
When a particular application requires data or functionality from another application, it will access the same using the service interface. |
|
| |
| Web Enabled |
| Since the solution advocates synergy and collaboration between actors of a business process irrespective of their physical or geographical location, it is important to have thin client based architecture. This not only gives all the users a common look and feel, but, it also reduces the implementation to single deployment at centre. This essentially means access to Single System Deployment over the Intranet, Internet or Extranet. |
|
| |
| Open Source Based |
| The solution is based on open source products as much as possible to reduce the overall cost of the solution. At the same time, the architecture will allow for use of COTS products based on customer preferences and existing investments. |
|
| |
| Open Standards |
| The architecture adheres to non-proprietary standards since the system will be built from different open source components, thus ensuring interoperability between the components. This will also maximize pool of technical resources to support the system. |
|
| |
| Workflow |
| Every business process is made up of functional elements with the right set of access rights granted to roles involved and with pre-defined set of tasks to be done. A workflow automates this entire process, while allowing flexibility like ad-hoc routing, notifications, wait events, etc. The solution has strong workflow capabilities to handle both enterprise level business processes as well as process flows within a particular application. |
|
