Quality - The Real Thing

Software can be small or large, complex or simple, fault tolerant or home entertaiment, but in either case it MUST be high-quality. Most companies work in the model, when Quality*Cost*Time = constant. In other words, the faster and cheaper you want project to be done, the lower the Quality will be. If you want better Quality it will be longer and/or will cost you much more.

With TackleSoft it is another story. We pay special attention to product quality and perform testing and quality assurance throughout the whole process. When software system is ready according to requirements, TackleSoft begins extensive testing to ensure that product is stable, reliable and ready for end-user. Deployment includes installation package preparation, source code and documentation delivery. TackleSoft also provides free technical support for 3 months after developed software product was deployed.

TackleSoft members' skills are very different, experience in programming vary from 2 years to 12 years. There are C++ experts and Visual Basic gurus, talented web designers and algorithm creators, scrupulous database administrators and future predicting system architects. But the most valuable phenomenon in TackleSoft is how all these people are working together, building extraordinary software solutions. Additional advantage of the team is agile learning, which tends to be even more important than current knowledge in our continuously changing world.

Whether you need to solve specific issue in your ongoing project or build new system from the very beginning, TackleSoft is able to establish suitable environment and lead the project through the whole process. Experience of the team makes it possible to coexist with in-house development, software outsourcing and other environments.

Which plan fits your schedule best? Get answer at
TackleSoft Web Site

"... when Quality*Cost*Time = constant. In other words, the faster and cheaper you want project to be done, the lower the Quality will be ..."

I don't understand your equation, if 'Cost' and 'Time' decreases the 'Quality' must increase in order to remain constant the multiplication output.(!?!) 'Quality' is directly proportional(but not neccesarly) with 'Cost' and 'Time' so it can't be multiplication between them but division.

Thanks for your notice, this was a sort of typo. Actually, I used to measure things like SCO per KLOC, bugs per requirement, etc, i.e somewhat reciprocal to Quality. So the correct forumla would be of course Time*Cost/Quality = const
Speaking about the formulas, I'd also add Size (or Scope) to this expression, but I wanted to keep it simple. COCOMOII provides good rule of thumb for measuring efforts, however it is more of waterfall-process-oriented estimation techinque.

Have a nice day.