Aviarc® socializes enterprise app development™.

Aviarc DrawingBoard changes the way organizations unlock the creativity of their people.

It allows a team of people to work together to create powerful software solutions, starting from an intuitive visualization tool without any risk of lost in translation as things progress.

Aviarc® not only provides a level of productivity that has never been possible before, it does so without compromising what can be created; unlike other offerings, it isn't constrained by being forms, template or convention based. It's a whole new paradigm that changes the entire software lifecycle forever.

Aviarc DrawingBoard means you can conceive just how a new software system or automated process should look, feel, behave and interact with everything and everyone. It happens much more quickly, cooperatively and intuitively than any other way. It is easier to understand and feel confident about.

Aviarc® is beyond agile, building from abstraction to detail without wasted code and effort.

With the Aviarc® paradigm, the "requirements" are replaced by an evolving application that looks and feels real because it is real, forming the process, interactions and structure of the application, leaving no ambiguity to fog up the construction process.

Leveraging stakeholders throughout the design and development process assures buy-in with the results being guaranteed and traceable.

Being highly collaborative means the business users can (via the browser) interact with the evolving application on a continuous basis by dropping "PINS" on the working application (providing instant feedback).

Unlike traditional process automation tools, Aviarc® does not force you to work step by step through a particular process.

This is because often things can be different. It might be that the process doesn’t exist, it may be a new line of business for example, and needs to be invented from scratch. Understanding and capturing the current process using DrawingBoard is the right place to start, with the opportunity to keep on testing whether things can be done more efficiently and capturing good ideas along the way.

A typical Aviarc® project might evolve as follows:

1. A short workshop to agree the project aim, team and conditions such as budget, deadlines, business imperatives.
2. Business and IT work together to capture the existing process and/or new ideas with the Aviarc DrawingBoard. These are linked together in a way that makes sense to everyone and everyone understands.
3. From this an outline automated process is very quickly created (a lot of this happens automatically in the Drawingboard). People interact and share by seeing what the computer screens will look like, how the business process will flow and how everything will work in the finished system.
4. Detail and the IT technical bits are "plumbed in" via the Aviarc® process to any existing computer systems and information that you want to use in the new process. Also at this time any bits of detail not automatically generated by Aviarc DrawingBoard are put together. Again, the team gets to check that the automated process is doing what they need it to do.
5. The application begins to be used for real. The documentation is already part of the Aviarc® application context and is on the DrawingBoard. Everything seems to happen where you can see it, on the computer, not in screeds of requirements paperwork and manuals, or expensive consultants.