Home Contact Us Feedback About Us

Frequently Asked Questions

General
Why is Powered™ so fast?
Can it really eliminate up to 95% of developer code?
What kind of application is Powered™ ideal for?
Can .NET be used to build applications with Powered™?

Architecture
Do developers need to know J2EE?

Infrastructure
Can I build my own infrastructure?

Methodology
What happens if I already have my own methodology?
What happens if I have already started or completed design?
Why should project teams be structured by business function?


General

Why is Powered™ so fast?
Powered™ has been completely optimised to ensure developers write the absolute minimum possible lines of code to implement any given business function. In some cases up to 95% of the code that would otherwise be required is eliminated. This reduction in code not only provides massive increases in efficiency during the construction phase, it has a ripple effect through the design and testing phases.

If code does not have to be written, it does not need to be designed OR tested. It’s that simple! Also, during the testing phase only 20% of time is spent writing and executing test plans. The reality is, the remaining 80% is spent documenting, discussing, resolving and retesting defects (regardless of what the project plan might show). Statistically, significantly less code translates to significantly less bugs.

Eliminating the majority of effort in the design, construction and testing phases provides increases in efficiency that would be impossible to achieve by simply tuning, restructuring or redefining the processes within these phases (the primary focus of most methodologies).
top

Can it really eliminate up to 95% of developer code?
Yes! Powered™ has been specifically designed to minimise the lines of code that needs to be written by developers. If you’re not convinced after reading the architecture and infrastructure sections you should take a look at the tutorial.
top

What kind of application is Powered™ ideal for?
Powered™ is ideal for enterprise strength, mission critical, transactional business systems. That is, core business applications that require users to store, retrieve and process large amounts of data. Furthermore, since Powered™ is a generic/technical framework used for custom development it is not limited to any specific business area.
top

Can .NET be used to build applications with Powered™?
Currently, Powered™ is only available for use on the J2EE platform. However, the Powered™ team intends on supporting .NET sometime in the near future. If you would like more information on this or would like to be kept informed about our progress, feel free to contact us.
top


Architecture

Do developers need to know J2EE?
No they don’t. The interface to developers is so simple and easy to use, that developers only need to have a basic understanding of object oriented programming and/or Java. The rest can be easily picked up in our training courses or by reading the developer reference materials provided with Powered™. But don't take our word for it, have a look at the tutorial and make up your own mind.
top


Infrastructure

Can I build my own infrastructure?
Of course the answer is ‘yes’ – but are you willing to risk it? Building a good infrastructure requires a significant amount of time and effort. It also requires a dedicated team with the right skills, experience and mind-set. At best, not having the time or expertise to do the job properly will result in a business solution that is expensive, buggy and costly to maintain. At worst, it will result in the failure of the project.
top


Methodology

What happens if I already have my own methodology?
The Powered™ framework is not dependent on the Powered™ methodology. If you already have a development methodology in place that you are happy with you can continue to use it successfully. However, we do recommend that you at least review the design and construction templates and standards supplied with Powered™. These have been specifically tailored to save you time and effort and can normally be easily adopted by the existing methodology.
top

What happens if I have already started or completed design?
Up until the start of construction you can still benefit from the Powered™ framework. But you will probably find that you have not been as efficient as you could have been during the design phase and that some of the design work produced is not required. In some cases, it may be beneficial to review the design deliverables in order to achieve the best possible outcome in the long run.
top

Why should project teams be structured by business function?
When building a business application, the focus of every team should be the business. This includes not only business analysts but also designers, developers and testers. In many projects, the development team is structured based on technical expertise rather than business area. This is largely due to the complexity and/or diversity of the technologies involved.

The problem with this approach is that business knowledge (the most important aspect of a business application) is fragmented across multiple teams. As a result, there is no team or individual with a good understanding of how a particular business process has been implemented. This significantly increases the complexity of a project because it:

  • increases the need for communication between teams
  • increases the chance that a particular business rule or function is “left out” because “I thought the other team was taking care of that”
  • increases the complexity of the development process as it introduces a “unit integration phase”
  • increases the complexity of the defect resolution process since defects need to be routed to the correct team. (a tester can easily tell you what business function he/she is testing, but not what technical component is responsible for the error)
top

 

 

 

 

 

 

 

 

 

 

 

[Intentionally Blank]