framework

Software Architecture And Full Use Of Standards To Ensure Compatibility

Companies are looking to be ever competitive and stay well ahead of the competition. The Compliance Integrity has mastered this by staying on top of the latest technology trends, and has been using these to deliver Intelligent Business Solutions. In the late 1990's, The Compliance Integrity was the first software provider to implement full light-web solutions for the retail industry. Today, with the seventh version of The Compliance Integrity Suite, namely i3v7, The Compliance Integrity is maintaining its position ahead of the market, by providing portlet-based architecture, which is fully developed using HTML5 for compatibility and designed for mobility (access via Smart Phones, PDA's, Tablet PC's, …). Introducing industry best practices to the architecture and infrastructure of our solutions demonstrates our conscious efforts to ensure our products and services are compliant with our client's IT policy.

All The Compliance Integrity Solutions support n-tier, multi-browser (Microsoft IE, Mozilla Firefox, Chrome, Opera, Safari) web applications based on Model View Controller 2 using Struts as a framework. The core of this architecture is Spring, a full-stack Java/JEE application framework. It delivers significant benefits to our applications and reduces development efforts while improving test coverage and quality. We use the iBATIS data mapper framework to map classes to SQL statements using an XML descriptor. With iBATIS we can map any database to any object model.

client tier icon

Client Tier

The Compliance Integrity has years of experience in leveraging all the possible functions offered by browsers like JSON, JQuery, AngularJS,DOM, XML, JavaScript, XML-HTTP, thus offering to business users, rich interfaces that are required to perform complex business processes. The latest versions of the The Compliance Integrity Suite are fully HTML5-based and flash-free in order to ensure full compatibility with browsers and mobility.

presentation tier icon

Presentation Tier

This tier is based on Apache Struts; a framework for MVC2 Web Application development, it has become an integral part of our infrastructure software. In order to have a better maintenance facility, we separate the view (JSP/JavaScript) from the model (Java) by managing these two parts with a controller (Mainly Servlet).

business tier icon

Business Tier

This layer uses POJO's (Plain Old Java Objects). With POJO's, the Spring framework acts as a lightweight container providing optimum performance.

integration tier icon

Integration Tier

This tier is supported by iBATIS SQL Maps, which provides a very simple and flexible means of moving data between our Java objects and a Relational Database. This Data Mapper framework helps to significantly reduce the amount of Java code that is normally needed to access a relational database, thus optimizing performance again.




Integration: Open Architecture To Allow Any Kind Of Communication. The Compliance Integrity provides various mechanisms for importing and exporting information: Interface tables, XML messages, File exchanges, Web service calls. All these mechanisms can be used by the EAI (Enterprise Application Integration) tier tools.
The Compliance Integrity framework

Infrastructure

The The Compliance Integrity Suite is a classical Java Web application relying on a database server, a Java application server, and an optional HTTP front-end. The application is accessed through a browser connected to the HTTP front-end or the application server through a TCP/IP LAN.

Scale The Environment To Your Needs

Both, the 'database server' and 'application server' make up what we call the "environment". Depending on the purpose of the environment (i.e. demonstration, mission critical application,), the relevant components can be installed on a single hardware up to a set of highly redundant servers. Scalability can be achieved vertically (high-end servers with lots of resources), or horizontally (multiple clustered mid-sized servers). Deciding on the infrastructure depends on the importance of the application, budget, maturity and type of existing infrastructure, and cultural factors (like the influence of a dominant IT supplier).

Sizing Methodology

When it comes to hardware sizing, various approaches can be taken: sizing according to similarities, start small and grow big over time, and timely estimates of the target architecture.

When sizing according to similarities, choose a similar existing running application for reference of hardware size, functionalities, data volume and user base. This exercise gives you a very rough estimate of what may be needed for a new project.

Some customers prefer to start small and add relative hardware when required. It is easier to add an additional application server to a server farm made of entry/mid-range standardized servers.

In some cases, the client requests an accurate configuration by our team. To certify that the hardware will meet stated performance criteria, a benchmark is conducted on a hardware configuration relatively close to the client's chosen solution.

Standard Application Environments

This environment is often managed by The Compliance Integrity' staff, where application patches are installed and tested before delivery to the client, and can be located either at The Compliance Integrity' premises or at the client's site.

An environment used by The Compliance Integrity and the client to test the newly received application, modules, and patches.

An environment used by The Compliance Integrity and the client to test the inbound/outbound interfaces (data consumed by the The Compliance Integrity Suite and data exported by the The Compliance Integrity Suite).

Depending on the project organization, the training of the client's employees is either done on a functional testing environment or on a dedicated environment.

This is a mirror image of the production environment (i.e. in terms of connectivity for the interfaces, scheduling of the batches, software versions, etc.).

This is the "live" environment typically used by end-users. Clustering technology can be used for reliability purposes. Alternatively, the pre-production environment could act as a backup.

A separate environment is often located at a site away from the client's geographical data center location. The disaster recovery environment is used as a fallback in case of catastrophic problems at the production site. The technology used here is to keep the disaster recovery site synchronized with the production environment. The time needed to switch from one site to the other largely depends on the severity of the issues related to the system and on the available budget. Integral IT resources are designated for maintaining multiple environments required for a project's progress.




Data Import and Export services can also be done ad-hoc or scheduled. The The Compliance Integrity Integration suite also manages format mapping, transcoding and default values generation.

  Data Architecture

The request for speed and agility are the major components of the growing data movement. Therefore, The Compliance Integrity data model is used to define the business requirements that support and correlate with the different lines of business’ processes and incorporate them within the corresponding enterprise architecture. It represents a better communication between business and technical people, using agile techniques that concentrate on understanding the different services features and processes. The Compliance Integrity data modeling techniques (entity-relationship and dimensional) organize data elements by meaningful business objects, which increases application development speediness along with improving data quality and accuracy. By adopting The Compliance Integrity database strategy, our clients will be controlling the expenses resulting from the data duplication and missing integrity; which will lead to lower costs and leveraging new innovations’ investments, driving to a competitive advantage in terms of agility and time to market.

As we move into today’s data-driven values, it is important to understand that our data model architecture represents the single version of the truth across the enterprise management systems; where the data is analyzed and then structures, allowing immediate access for both business analysts and data scientists. It is an on-demand tuned infrastructure, permitting the manipulation and handling of large datasets at a rapid rate. It evolves over time, allowing a dynamic expansion and scalability. The way the data is structured and architected, helps the data to be integrated, governed, organized and completed in a cleansed unique repository. This will constitute the base for the Data Science Workspace, where the Big Data Warehouse for decisional reporting is fully governed and trusted. The Compliance Integrity information modeling provides a single point of accountability for data governance. Offering the feature to enrich and augment data to support efficient and agile analytics systems. It enforces the data governance policies and data security, where the enterprise repository is maintained based on standard architecture rules and data insights.