Programming Tools
Programming tools consist in programs or applications that we use for elaborating, maintaining, debugging and support other programs and applications. Since they come in many forms and address different issues in the software development process, we tried to make a guiding list of what our team generally uses:
1. Project Guidance
Definition & role
There are numerous tools that make the project guidance simpler, clearer and more transparent. Such tools we use are: Microsoft Team Foundation Server, Microsoft Project, mind mapping software like FreeMind, UML architecturing and design tools like Sparx Enterprise Architect or Rational Rose, issue-tracking systems like Mantis, Bugzilla, GLPI, configuration management and version control systems like Perforce, SVN, Microsoft Team Foundation Server and others.
Codespring added value
At Codespring, we are trying to use the same project management tools within all teams, so that we are able to share experience and best practice. In addition our team has developed specific project management tools simplifying the project controlling process and respecting our QMS (quality management system).
2. Architecture Design
Architecture design is the problem-solving phase of the software development process, where the system architects understand and model the client’s demands. Creating an architecture design needs an important experience in the software development, an architectural view, and a wide vision over technologies, algorithms and implementation issues. The architecture design has also to reveal list of modules, functionality of modules, interface relationship, dependencies, database tables, architecture diagrams, technology details and so on.
Passionate about software development, the architecture design phase is the one we really can add value on. Talented and extremely skilled technical engineers run into a race to deliver best software architecture designs. Not to mention that we will always guide you through the selection of different architecture designs by highlighting the pros and cons of each proposed architecture.
3. Testing
Testing is an important part of the software development process. It insures that bugs and inconsistencies are early recognized at this stage. It verifies that the software has been correctly built. Testing may be done at different levels: unit testing, integration testing, system testing, user acceptance testing. Thus the dynamic testing process is completed and eventually all potential errors or deviations are being solved. For these operations we can use internal testing teams, sourced testers and users’ staff – the personnel that will effectively work with the software.
From our experience, testing at all levels is a mandatory phase, even if sometimes, due to time and budget constraints we are tempted to make only the unit, the integration and the system testing. Codespring recommendation is that it is always cheaper to prevent than to correct after the product has been delivered. We add value by foreseeing and preventing potential issues before deploying.
4. Bug tracking
5. Version Handling
6. Other tools
FxCop is a free static code analysis tool from Microsoft that checks .NET managed code assemblies for conformance to Microsoft’s .NET Framework Design Guidelines. Unlike the lint programming tool for the C programming language, FxCop analyzes the compiled object code, not the original source code. It uses CIL parsing, and call-graph analysis to inspect assemblies for more than 200 different possible coding standards violations in the following areas:
- Correctness
- Library design
- Internationalization and Localization
- Naming conventions
- Performance
- Security
FxCop provides a tool to help developers to follow our company’s coding standards. FxCop does code analysis to check whether the new code is compliant with the coding standards and naming conventions followed by this company. FxCop will ensure that the specified rules are used in the source code.
