|
Builder is a application constructor and automated deployment engine. Usng data from the creator web application, builder will analyze, construct and deploy a read-to-use web application to Linux, Windows or Mac OS. It supports most of the popular RDMS such as MySQL, Postgress, SQLLite, Oracle, MS SQL Server. Prototypes or Utility applications can imploy popular authentication systems such as Local Auth, Google, OAuth or LDAP with our without role based authorization. It even includes a mechanism to load context based test data. That's why we say "More than a code generator, it's an app generator."™ |
|
|
Utility applications are the life-blood of all corporations. The enterprise applications may get all the glory but utility applications, those little worker-bees that help the day-to-day operations, really run the show. In most if not all companies utility applications get implemented into less-than-ideal platforms. From spreadsheets to desktop databases, these one-off solutions carry a high-price and risk. Spreadsheets are easy to create but are non-colaborative and once released into the wild impossible to version control. End result, you have multiple versions with different data floating around in emails and on users desktops that can adversely affect your view of the very thing they are trying to represent. Desktop databases provide data interfaces to one person but now you have a single-point-of-failure. If that person who developed the database gets a new role in your organization, decides to leave, or simply goes on vacation, you have the same scenario you've spent gobs of money to prevent, your application is offline. Sure you can do a knowledge transfer, cross-train, or hope for the best, but that's extra time, money and risk you don't need. Utility applications constructed with Creator and Builder are web-based, funtional and cost-effective solutions that eliminate single-point-of-failure, are collaborative and version controlled. Utility applications are similar to prototypes but with the goal of providing a simple consistent web interface. Now everyone in a group can enter, view and output data from the same place without all the hassle associated with a full enterprise deployment. This gives you the ability to negotiate an SLA with your IT group that is less stringent than a core application but still give you the piece of mind knowing that you investment is protected. |
|
|
Every web application should start as a prototype. Let me say that again, EVERY web application should start as a prototype. Why? Even in a perfect scenario, with experienced Project Managers, Architects, Data-modelers, developers, testers and a willing and active user acceptance testing group, requirements are revised, or worse missed. Is every member of your team and A player? How much does their time cost you? Without a prototype application, at some point during the project development or implementation lifespan it becomes too costly to re-do part of all of a planned project. What you're left with is either an incomplete application or a forced solution based on business vs. IT compromise. Prototypes are not wasted effort. They serve as a liviing, breathing requirements document. Fast turnaround and visualization of business requirements for user evaluation can mean the difference between a failed project and a superstar web application for the business community. In short, prototypes save time and money by nailing the requirements before enterprise development begins. |
|
|
Creator is a web based design interface that feeds the building application to construct protyped or utility web applications. It is far more than a code-genereator allowing visualization and iterative design of applications by experienced and non-experienced users. The Creator and Builder components are built using Ruby and the Rails web framework along with a new SDLC (Software Development Life Cycle) called CORE Hall. The innerworkings of CORE Hall are based on AGILE SDLC with a some key differences. CORE Hall empasizies iterative design and a data-model centric approach. It uses Ruby and Rails conventions but takes them to a new level. The starting philosophy is that all applications are 90% identical as they are all based on some data-model and imploy user interaction, input and output. By normailzing those components, using the DRY (Don't repeat yourself) approach of code re-use, Creator streamlines the design approach and allow iterartions with user input to avoid requirement gaps or forced design on the user community. |
|
|