Architecture design is a complex process. It embodies best practice and acknowledged wisdom presenting a set of services, standards, design concepts, components and configurations that guide the development of applications and their architectures.

In addition to this application architecture must be suited to its specific business purpose and that purpose may change with time along with the resources available to you. The task of designing the reliable application architecture can be eased by the architectural framework tools and components.

Technology Infrastructure is the core of any enterprise. Making calculated investments in your infrastructure can create business opportunity and drive success; conversely, a poorly structured or managed infrastructure can impede your ability to remain competitive.

Elite.NET is an architectural framework that enables PIE Systems to deliver solutions in a multi-tier environment quickly and effectively. It also ensures that the majority of our time is spent on addressing your business problem(s) and minimizes the time required for building supporting components (aka plumbing). This naturally means that we can develop systems with less effort, lower cost, and faster.

Other benefits include:

• Clearly define the structure of the existing system
• Reduce the number and complexity of the interfaces between the components, improving the ease of:
• Component upgrade
• Component exchange
• Component development and maintenance
• Code re-use
• Set out the strategy for future developments
• Significantly reduce development time and hence improve time to market
• Improve quality of delivery through re-use and building of a common knowledge

Elite.NET is an application architectural framework based on sound architectural design patterns.

Elite.NET - Architecture significantly reduces development time through re-use of existing components both bespoke and off the shelf and it allows the development team to focus in developing business requirements and not the "plumbing".

• It is based on standard layered architectural design patterns
• XML is the primary data transformation type across boundaries
• All Business and Meta-Objects are XML based
• XML meta-objects are used to define schemas, transformation and processing rules between all layers: Data layer to/from Business Entities to/from the presentation layer
• Web services and pre-built components (med to large grain) are used to facilitate re-use

By selecting a core set of components that we consistently work with to deliver this framework in multiple client environments is where the true advantage is made.

The following is an example of the framework as it would be implemented in a Microsoft .NET environment. The red boxes are areas in which we have existing components, re-usable code, or take advantage of off the shelf software. As you can see, by using this approach, the primary development activity is spent developing business logic (blue-green) that directly benefits your organization.

Back    Next