Quality Control

We can provide following services that ensures delivery of high quality software.

Daily Build Process

Hive Studios sees daily build as one of most important things in software development process. Starting of daily build process is incorporated as option in ‘Starting a new project’ procedure that each team member must follow in order to start up a new project. If you prefer continuous integration environments we can quickly deploy CruiseControl.NET.

Here are some of the tools we use in daily build process:

• NUnit (http://www.nunit.org/)
• FxCop (http://www.gotdotnet.com/team/fxcop/)
• VSSDiff – shows difference between two labeled versions in Source Safe. (NAnt-contrib task)
• SourceMonitor – analyses source code for comment coverage, complexity and other metrics (http://www.campwoodsw.com/sm20.html)

After evaluation of NUnitForms (http://nunitforms.sourceforge.net/) and NUnitAsp (http://nunitasp.sourceforge.net/) we decided to unit test only middle tier components.

Automatic testing and reporting is incorporated in daily builds.

Test First

"Test First - Implementation Later" means that critical sections of code are implemented after unit tests.

Bug Management

Right now we are using customized SharePoint site in conjunction with Project Server 2003 to perform bug and project management. Since that solution generates large overhead to operations in small environment like Hive Studios, we have decided to develop custom solution that will cover task management, assignments, time reporting, budgeting, timesheet and bug management. Deployment of production version in Hive Studios is planned for late May/early June.

Coding Standards

Hive Studios is using coding standards derived from .Net Framework Coding Guidelines. Implementations of coding standards are partially enforced by FxCop tests.

Extreme Programming

Most of the time developers are working alone. When there is a complex task that should be done we are usually ‘pairing’ developers in order to produce higher level of code quality. All developers are encouraged to do a lot of code refactoring.

Evaluation of third party components

Each candidate component has to pass trough evaluation process before it is used in solution. Evaluation process consists of feature testing, documentation reviews and sample project implementation. Community support is also evaluated. We prefer to use tested, documented and widely accepted building blocks and frameworks.

Documentation

We can deliver following documentation in chm or html format for every solution. Samples are available upon request.

1. Administrator guides covers procedures for installation, configuration, securing and back-up and restore.
2. User guides
3. Application architecture and extensibility documentation
4. Class documentation (SDK) generated from XML code comments with NDoc (http://ndoc.sourceforge.net/)
5. UML diagrams

We can provide professional translation of user and admin documentation to English.