Existing System Analysis

Systems must evolve to meet changing needs both in terms of features and scale. Having an experienced 3rd party analyze, document, and report recommendations prior to launching the next major phase of your project or product can be invaluable. GRID I/O can help identify bottlenecks, limitations, and vulnerabilities of your current system. GRID I/O follows the technologies and trends within the broader software industry and can help make strategic recommendations in terms of architecture, technology selection, and testing.

Project management

Good software starts with requirements, but not every project can be completely flushed out prior to writing the first line of code. GRID I/O can analyze the customer’s needs and suggest a workflow that best suits your project, whether that be waterfall or a more iterative agile approach. GRID I/O provides project transparency by making source control visible to client using a platform like Github. Project planning, issue tracking, and source control is all exposed and managed in one location.

software implementation

GRID I/O works collaboratively with the company’s engineering team to reach the end goal of a robust system that meet specifications. GRID I/O applies best practices for the targeted language, platform, and environment so that the end product is consistent and maintainable.

quality assurance testing

GRID I/O typically implements multiple forms of positive and negative testing and to provide broad coverage and confidence in the systems we create. GRID I/O typically implements multiple forms of positive and negative testing and to provide broad coverage and confidence in the systems we create.
Positive testing involves making individual assertions about what the software should do under certain conditions. It is typically paired with metrics and tools like code coverage to identify areas lacking tests. GRID I/O has deep experience writing test suites and plans of various types.

• GRID I/O considers unit testing to be the foundational QA technique of software development.  Small “units” of code are tested for correct operation by making assertions about the codes expected behavior.  This simple idea can take years to master, as it is frequently infeasible to test all possible inputs and outputs.  GRID I/O can help you identify the areas of your system most amenable to unit testing, and where you should focus your efforts.

• Integration testing involves running an entire application and testing its external inputs and outputs. The most common example is testing a REST interface or web service using a mock client. It is an essential type of testing to ensure that the various parts of your application work together as whole.

• Continuous integration is the practice of integrating code into a common repository, automatically building the software, and executing the test suites whenever a change is made. GRID I/O uses CI for all of our projects as a means to provide transparency and metrics to our customers. Customers can monitor and track various metrics about the software being written.

Negative testing involves exposing the program to a large number of unexpected, random, or malformed inputs and verifying that it can gracefully discard, log, or trap errors. This testing is typically used for security purposes, but has large benefits.  Fuzzing is the primary methodology used for negative testing.
GRID I/O has years of experience building fuzzers and using various open source tools. We even sell a fuzzing platform called Aegis for standardized protocols.