Requirements analysis in software development

Requirement analysis

By on January 14, 2013

Before you build a complex system — it is best to ensure the task is understood well. It is better than having to redo it later. For this we use a number of techniques, from early prototyping to detailed specifications with screen designs and algorithm descriptions.


Using Google services (Wave, Docs) in daily QA process

By on March 11, 2010

Using Google services (Wave, Docs) in daily QA processThere are many organizational difficulties facing small to medium Software Quality Assurance (QA) teams. Because of this, we welcome any help to simplify this work and make assignment, communication and reporting more reliable. Tools are not the silver bullet, yet with a responsible team the right tools can make a lot of difference. Read on to see how we started using Google’s toolkit (namely, Google Wave and Google Docs) in our daily QA and general development practices, as described by Dmitriy Boltovskiy, our QA team lead.


Pricing, estimation: How NOT to

By on July 31, 2009

Last December, we decided to redesign our website, and, due to lack of resources, wanted to hire and external shop to do it for us. After the requirement discussions and resulting budget calculation, we decided to design and implement our website ourselves. Yet some lessons were learned, which I would like to share below.