After spending numerous years using and getting frustrated by industrial technologies, I came up with a set-like object model, which started as a hobby, and which, compared to today’s object models, defines a much more abstract and powerful model. This is the PowerObject model, built on set theory concepts and procedures, including high level set theory topics.
Brillien, as a PowerObject implementation, has grown to a product. This document helps to fully understand Brillien as a working system, therefore no details are included on its mathematical background. The concept model of Brillien can shift the basics of corporate application planning and development to a whole new level by developing into a complete, working system. It does not aim to replace or compete with the standard EE technologies, or to create a new framework; Brillien is a simply an interesting architecture, still under development, that might enable a different development perspective, and hopefully a more efficient way of development as well.With the increasing size and structure depth of issues being modeled, there is a directly proportional demand for a more abstract and sophisticated architecture.
Given that the Java language and the SDK built around it is a structure based on consistency and logic to model the world around us and define its main elements, it is an excellent basis for constructing more complex models. Corporate systems consist of more abstract components than a set of objects and packets, and are mainly workflow-based. Brillien offers an architecture that satisfies this demand. Acting as the main tool, it supports the flows and provides necessary tools for modeling components the flow consist of. The main tool also handles functional dependencies, so it is safe to say Brillien is not another workflow engine; but rather a corporate application development tool that, by reducing the significance of modeling issues and inconveniences, is able to map the logical system formed during the requirement analysis and make it a functioning one. Without History, that is, the crippling constraint of backwards compatibility, the system can truly shine in its simplicity, smooth, and delicate finesse.
Development started in March, 2008, and in the first phase (until August) only basic concepts and modeling definitions took place. There was a strong emphasis on creating a tool suitable for expectations. After many case studies, a stable and evolved concept system was born with a slightly different attitude and increased usability, offering a likeable platform to develop EE-level applications.
The first public release of Brillien was published under BSD license. We use it for awhile now with pleasure, and hope that you will find this architecture exciting and useful. So, any feedback is much appreciated. Please browse to: www.brillien.org