| |
 |
|
RELATED LINKS / DOCUMENTS
|
 BriteWorks™ Studio
- Absolutely NO CODING Required
- The main input to BriteWorks™ is a data model or database. If a database already exists, all the user has to do is define a connection to the database and BriteWorks™ handles the rest.
- Metadata is automatically generated from the user database.
- Users may 'enrich' the metadata with their own database rules
- Drag & Drop of templates and data is all that is required to create sophisticated user interfaces.
- Wizards and fill-in-the-blanks guide the user and remove any necessity to learn syntax.
- Events show the user where to include business rules
- Actions help the user define any business logic
- At any stage, the user may 'run' their designs in the studio or do this in a browser or runner, without code compilation.
- No code is ever written or generated!
- Design Once, Run Everywhere
- Any applications created through BriteWorks™ will work in multiple environments:
- Web - our web interface runs under JSF and AJAX. The looks is Web 2.0 / RIA (Rich Internet Application) with an enhanced user experience.
- Desktop - this is rich client interface running under java / JRE. Data and business rules run on the server, however certain syntactical validation such as date controls, numeric vs. text etc. run under the client machine
- Mobile - we support J2ME, Symbian and Windows. Special templates are provided for mobile phones, however, the same windows/applications that run on the web and in client/server will also run on mobile devices. Mobiles applications can run in on-line and off-line mode with database synchronization.
- Database Tool & Metadata Enrichment
- The database tool allows users to connect to any database and change tables, columns and other properties. This is a single interface into multiple databases, which eliminates the need to learn syntax for each specific database.
- Once the database is complete and metadata is generated from it, users can add more properties such as display name, editable, auditable etc.
- Run / Execute in Design
- Any interface, business rule or other resource can be tested within the studio environment. This eliminates the need for the user to get out of the studio to test.
- Having said that, the user may also launch the runner or any browser to test.
- Going from Design to Run, is as simple and instantaneous as clicking a button.
- No code is generated, no compilation is required - it is a simple toggle.
- Debugging, Step through Execution
- When business rules are not working as they should, users can go into 'debug' mode and step through each action that has been created.
- Input and output values can be seen.
- Action parameters can be viewed and changed
- The user may progress one step at a time, step into functions or skip steps
- Template Management
- BriteWorks™ comes with a series of predefined templates (user interfaces / artefacts).
- Users drag and drop these templates, along with the data they would like to work with and the user interface is automatically created.
- These templates can be copied, modified and saved as new templates.
- The newly created templates can be modified in the following areas:
- Interface - layout of controls / components - manually adjusted
- Theme - select any theme and modify it for this template
- Behaviour - what should happen when a button is clicked etc.
- Database - what should happen for basic database actions
- Other - master child interfaces, gaps between controls etc.
- Once saved, these templates can be used as any other template
- On each execution of these templates any of the parameters may be changed.
- Handles Presentation Layer, DB Layer, Business Object Layer, SQL etc.
- User interfaces created in BriteWorks™ are ready to use. The developer need not think about any of the standard tiers such as data, business object etc. as these are part and parcel of BriteWorks™.
- Even SQL knowledge is not required. The user defines what data to read or manipulate through actions (described below).
- Business Rules at DB and Window Levels
- Business rules in BriteWorks™ can be defined at two levels. The first is at the database level, where certain conditions can be defined on attributes (fields) and they apply in whatever window or interface they are used in.
- Business rules at window level allow users to define their rules in a more controlled manner, applied to certain interfaces only.
- Business rules at window level are created through the use of actions (described below)
- Functions, Events, Actions
- Actions are the primary means by which business rules are defined.
- This is the main mechanism by which BriteWorks™ eliminates CODING.
- Actions are grouped into areas such as Database actions, Interface actions, Loops, Conditions etc.
- Most, if not all the actions required for general business scenarios are covered in BriteWorks™.
- Actions can be grouped together into a function and used thereafter through the 'Execute Function' action.
- If an action is missing, customers have three options:
- If the action is generic, they could request BriteSoft™ to introduce the new action into the tool. Actions are typically quick to implement and don't affect the rest of the system.
- If they have the know-how, they could create an action using java and through an API provided by BriteWorks™, introduce this action into the tool, alongside other actions.
- An alternative is to use external code which can be 'plugged-in' and used in BriteWorks™ like any other action.
NOTE: As a general rule of thumb, BriteWorks™ continues to add to and enhance actions according to industry requirements as well as general BriteWorks™ upgrades.
- Controls/Components, Properties
- BriteWorks™ comes with a predefined set of controls or components.
- These are thought to be adequate for most applications, however, BriteSoft™ continually enhances and adds to these set of controls.
- Each component has a predefined set of properties such as colour, font, default value, etc.
- If users are able to, they may create their own controls and through an API provided by BriteWorks™, can import their controls into the studio.
- Theme Management
- Users can define any number of themes which can then be called either in the studio or in the runtime in order to change the look and feel of a window or application.
- Themes allow users to define colours for any of the components / controls that are used in BriteWorks™.
- On the web, CSS (Cascading Style Sheets) are used to achieve the same objective.
- Help Tool
- Any level of help can be defined by the developer for an application.
- Colours, images etc. can be included in the help panel.
- Language Tool
- Users may define any language to be used in an application.
- Even user defined language can be specified and labels can be translated to anything the user requires, such as local colloquial slang or technical terms.
- In the runtime, the language can be changed dynamically.
- The language tool is context sensitive, in that it recognizes left to right and right to left languages and displays the interfaces accordingly.
- Full Scale Reporting
- BriteWorks™ is fully integrated with an industry standard reporting tool called iReports.
- The structure of the data that is used in iReports is exactly the same as that used in BriteWorks™
- The added advantage of using this tool is that any data that is restricted on users interfaces due to security set in the application will also be restricted in the reports. If the user cannot see it on the screen, then they cannot see it on paper. Using an external reporting tool would not provide this unique feature.
- Scheduling / Batch Engine
- Any action or set of actions (functions) that are defined in BriteWorks™ can be executed base on an event, a time interval or other predefined conditions.
- This eliminates the need for a user to manually trigger an action or a series of actions, instead those same actions can be executed overnight, at a specific time or on a recurring basis.
- Team Development
- Allows teams of developers to work together on a single project.
- They may check-out any resources, take them away from the server, update them when they return and check-in when their tasks are completed.
- Work spaces are created on an individual's desktop or laptop to allow them to work with an application.
- No database or other third party tools / software need be installed on the development machine.
- Users may also have a work space on the server, whereby they can modify the system directly on the server.
- Self-Documenting Feature
- A picture says a thousand words.
- All actions / business rules in BriteWorks™ have an automatic diagram generation feature.
- At any time, if a user is maintaining a system, it is easier to view a set of actions as a flow diagram rather than a tree or sequential set of instructions.
- This way, documentation of the system is always current, is in an understandable format and can be extracted and printed or inserted into a document.
- Any to any DB Conversion
- This is a very useful tool that allows BriteWorks™ applications to be migrated from one type of database to any other.
- BriteWorks™ itself uses this feature in order to allow development on multiple platforms and database, however, users may also decide to change either their development platform or production platform to a different database and this tools will help them achieve this easily. Currently there aren't too many tools in the market that allow such migration with ease.
- Layout Management allows users to define layouts based on roles
- Depending on the task that is being performed by the user, this is a very useful feature which allows developers to save different views. These views typically have panes and panels associated with the task that is being performed. For instance, a 'design view' might have controls/components, actions and events.
- Migration & Auto-Deployment
- Auto-Deployment allows customers using BriteWorks™ to deploy applications easily. A package is created from within BriteWorks™ studio which can then be taken to the target environment and installed.
- Migration allows users to incrementally migrate changes to an application from one environment to the other. A typical example of this is when developers migrate certain resources from development to test or from test to production.
- Services
- Web Services can be easily consumed within BriteWorks™.
- An initial URL is provided and thereafter, web services can be dragged and dropped as any other action.
- Alert Services are used to send messaged back and forth between client machines (designers) and servers for actions such as save, locking etc.
- Messaging Services equates to the Enterprise Message Bus (EMS) and used for application integration.
- Messaging services such as SONIC, JMS and Active MQ etc. have been tested
- Email Services allows users to define Email profiles which can then be used in actions to send emails with any desired data and text.
- Transaction Management
- Multiple database transactions can be grouped and if one action fails, then the whole set of actions would be rolled back
- Transactions management can happen not only within one database, but across multiple, heterogeneous databases.
|
|
|
Copyright © BriteSoft Corporation, 2008. All Rights Reserved
|
|
|
|
