BriteWorks operates on the principle of “What, not How.” BriteWorks provides a direct mapping of the requirements model – the “WHAT”- to the application model. This results in a high level of transparency while eliminating errors and tedious steps.
Programming languages have no constructs that map to requirements and must go through a series of transformations – the “HOW” – that distort the
requirements to fit the software.
BriteWorks provides the infrastructure, so developers can focus on the business functionality and avoid the menial task of coding that drowns the development effort.
The Brite architecture suite is based on industry standards and utilises many of the features in the java stack such as J2ME, J2SE, J2EE, Midlets, Tomcat, MySQL (or any other RDBMS), JSF, Ajax etc.
The solution architecture is depicted in the diagram below:
The following diagram shows how BriteOptimizer fits into the BriteWorks and Java framework:
An example of the deployment architecture in a clustered environment is as follows:
The BriteOptimizer solution provides an excellent return on investment platform. The following are some of the points that can be considered for ROI:
Business applications, as diverse and unique as they may seem, share many similarities that are almost universally required in enterprise class applications.
These requirements are operational features, known as ‘aspects’ that must be distributed across functional features.
Because of this cross-cutting, implementations of aspects become tangled with
the implementation of functional features, making maintenance difficult.
BriteWorks provides these system functions as services that are automatically invoked without any additional effort.
Authentication/Authorization
Access control in BriteWorks is based on a rule-base of authorization options. Authorization rules can quickly define in a coarse-grained way which users may perform which actions on which objects and they have a global scope.
Audit
BriteWorks provides the crosscutting function of auditing transactions at a high level of granularity. Authorization rules also govern how the auditing is performed. You have control over specifying what types of events, actions are audited and also audit by named user or by role.
Internationalization/Localization
BriteWorks is designed from the ground up to support multilingual and multicurrency deployment. It supports double-byte characters and is compliant with Asian and East European languages.
Web Services
Web Services are provided natively within BriteWorks. Developers are shielded from the intricacies of WSDL and a web service is treated as just another data source to be consumed by BriteWorks.