|
|
|
How We Do It > KnowledgeFrame Methodology > Our
Framework for Reuse
The Business Case for Software Reuse
|
|
|
Database Designs
- logical and physical models
- covering most business
domains
- extensible and flexible
- designs to support the most
demanding availability, scalability
and security needs
|
|
|
|
|
Rule Frameworks
- presentation, data quality, security, process (workflow)
- rule automations; completely data driven, no new code required
|
|
|
|
|
| Example: KnowledgeFrame
Business Rule Engine |
|
In the KnowledgeFrame business rule engine many common rule patterns are fully automated.
Rules are separated from the presentation logic and data.
Rules are attached to:
- ROLES, e.g. customer, vendor, salesperson, clerk, manager
- The TYPE of business object, the BUSINESS FUNCTION being performed,
the STATE of the Business Object, the PROJECT or even the LOCATION
the function is being performed for, and the triggering EVENT
|
|
|
The bottom lines ($$$):
Rules are either fully automated or written once.
Developers are protected from data complexities.
|
|
|
Runtime Infrastructure
- J2EE, optimization (cache), Integration
- extensible application components
- production ready (tested!) code
- use inheritance to extend or override methods
|
|
|
|
|
| Example: KnowledgeFrame
User Interface Engine |
|
A KnowledgeFrame user
interface is completely dynamic. It is
driven by rules expressed in data.
- No code for query,
insert, update, delete and no servlet
or JDBC code
- Implements best
practice designs for the UI
- Single
record, multi-record, master-detail,
TABs…
- Familiar consistent
paradigms
- Advanced functions
built In
- Multi-select,
duplicate, sort, export to
excel…..
- “First cut” application
is usable and productive (without
writing code)
|
|
|
The bottom line ($$$):
Developers focus on the business requirements and not the technology.
|
|
|
Copyright © T4Bi. Email: contact@t4bi.com
|
|
|
|
|
