Why ASP?
For example, let's say your organization uses an accounting software package. That software is likely running off of a server located in your building. Which means someone had to purchase the server and the software, install the software, maintain the server and the software, set up user accounts, process and maintain data, etc.

... Under an ASP model these responsibilities and costs are transferred to us.

The Process
Software is often measured by what it can accomplish, or more importantly, what it cannot accomplish. Most of the time the technology exists to serve the needs of the user. Human error is the typical cause of software shortcomings. Market demands and rushed production schedules can decrease the time spent in planning the functionality of the software. Industry experts may not be involved in the development of the product's requirements and functionality. Assumptions made regarding user needs can be left unverified.

We believe these issues should be resolved in our Discovery Phase before the first line of code is written. Following extensive industry research and market studies, we identify every detail of the product's anticipated functionality. We invite industry experts to review the ideas behind the product and share their views or concerns. We then hold focus groups with the people who might eventually use our product. We test whatever assumptions we have made and look for ways to improve or revise our product.

In our Evaluation Phase we determine not only if the concept can be built, but also should it be built. Can we build the product using existing technologies and meet the needs of the user? Is there a need in the market for a product of this kind, or do we anticipate a future need for this product?

We begin to give the product life during the Design Phase . Our front-end design team begins testing concepts, layouts, usability, fonts, colors, platform and browser compatibility, while our back-end design team starts creating the database structures and relationships.

 
During the Design Phase we begin Usability Testing. The best software products are designed with the end user in mind. If the end user has difficulties using a product or if a product is not intuitive to their needs, they will stop using the product. Keeping the user in mind during the Design Phase is paramount to our software's success.

There is little to no turning back by the time we reach the Full Production Phase . By now we have documentation outlining exactly what the product will and will not do. Even small changes during this phase can be 5 times as expensive to complete as compared to being addressed in The Discovery, Evaluation or Design Phases.

During the Full Production Phase we conduct Unit Tests. By dissecting the product into small sections "units" we can run tests to ensure proper functionality, confirm production schedule markers, and catch small variances before they become system-wide problems.

System Testing is the next logical step from Unit Testing. One test group takes a general look at the product to make sure all the systems function properly. Another group is sent in with the purpose of trying to break the system. An often unappreciated job, we actually reward testers for identifying faults in the product. While there is no such thing as a flawless software product, we endeavor to come as close to perfection as possible.

The final phase in our development cycle is the Future Upgrades Phase . Before the product is out the door, we are busy prioritizing the next generation of system functionality. Combined with continual customer feedback, future upgrades ensure the peak performance of our products.