Features

Below is a summary of the features included in the Powered™ Framework. It should give you a feeling for the breadth and depth of the framework. However, a number of the features are quite sophisticated and difficult to explain at such a high level. Please feel free to contact us if you would like to learn more about any of these features.

Architecture

• Simple
  • no unecessary components or layers
• Hidden from Developers
  • developers are only exposed to 2 types of components
  • no need to to learn or understand the details of the architecture
  • no need to be experienced or trained in J2EE (EJBs, Servlets or JSPs)
• Completely Business Object Centric
  • ensures that developers are 100% focused on solving business rather than technical problems
  • eliminates the dependency on the underlying technology, future proofing the solution
• Flexible
  • supports web and fat client development
  • supports 2 tier and/or 3 tier architecture (modes)

Infrastructure

• True Framework Approach to Infrastructure
  • eliminates up to 95% of design/code
  • infrastructure takes control of the application
  • eliminates the need to design/code all technical logic
  • developer focuses on business problems
• Completely Automated Persistence
  • no data access logic (no SQL, EJB QL, or any other variant)
  • no need to write query/search logic (even complex searches)
  • no need to write/generate or maintain long winded deployment descriptors
  • supports lazy and selective retrieval
  • automatic and custom ID generation & pooling
  • database independent
• Sophisticated GUI Management
  • components are 100% reusable between Web and Fat Client
  • easy to create simple through to the most complicated forms (only a few lines of code)
  • no object or field mapping logic required; even the most complex object graphs are automatically mapped to the most complex forms
  • no passing business object between form components (panels)
  • no business logic is required on forms (not even field names/types/sizes, validation, security, interaction rules, drop list data sources, etc...)
  • automatically invokes selective retrieves for performance (form data is loaded incrementally)
  • ensures consistency across the application
• Full Object Graph Management
  • management of complex object graphs
  • handles uni-directional and bi-directional relationships
  • graph level caching; handles multiple references to the same object
  • object graph operations (functions which operate on entire object graph)
  • automatic business object based validation
  • no need for "special" business objects (e.g. header or master objects); "all objects are created equal"
• Security
• implemented completely by the infrastructure; no need to write any code
• business object based
• data configurable rules
• Other Features
  • business object caching; client and server side (mult-tier)
  • pessimistic concurrency
  • business object auditing; configuration only required

Methodology

• Design
  • Design Standards
  • Functional Design Template
  • Technical Design Template
• Construction
• Coding Standards
• Developer’s Guide
• Unit Test Standards
• Unit Test Checklist & Template

• Pulse – Project Tracking System

• Analysis
  • Analysis Standards
  • Use-Case Template
• Testing
  • System Test Standards
  • System Test Checklist & Template
  • User Acceptance Test Standards
  • User Acceptance Test Checklist & Template