TESTniques Incorporated

Skip Navigation Links
Home
Test SystemsExpand Test Systems
J1939Expand J1939
EmbeddedExpand Embedded
SAC B52Expand SAC B52
White PapersExpand White Papers
Phone:
763 441 8296







Working With TESTniques

Why Hire a Consultant?

Experience  I've been involved with all phases: Concept, Specification, Design, Test, Deployment, and Support

Focus  I am focused on your project, period.

Expertise  I've been using CVI and LabVIEW for over 20 years, doing embedded development just as long 


Projects Start With an Idea

Projects always start with an idea or vision.  That idea might be detailed in specification, it might be a itemized list of major design objectives and a sketch of the screens, or it might be a few notes on the back of an envelope (really!).  I'm comfortable with any approach.
With some of customers I have open purchase orders and just do work as requested.   That is a level of trust few integrators enjoy.

There is no charge for evaluating your project and writing a proposal.

Setup a Budget

I generally bill on time and material.  When we start a project, I make an estimate of complexity and estimate a budget.  I treat the budget as a not to exceed number.  As development proceeds I track hourly time and budget.  I keep the customer fully informed of progress by detailed invoices and progress meetings.

Issue a Purchase Order

After TESTniques receives a purchase order development begins.

Build a Prototype

The next step is to build a prototype.  This usually builds the essential screens and user interface objects.  I try to work out the buttonology i.e. what happens when and what events are tied to what buttons.  The prototype allows the user have a feel for what the final project will be and helps greatly to get the developer and customer on the same page.

Devil is in the Details

The real work is in the details.  Each of the events in the prototype gets filled in with robust code, background tasks are filled in, error handling is built.
Items that are technically high risk are solved first.  I don't see much value in delaying risk mitigation.  Once a solution is found, it is demonstrated to the customer for approval.

Test, Test and Test

I can test the system to a limited degree.  The real testers and experts are the end users.  I am always surprised by that things users will do or attempt to do.  I'd never thought of that!  Let your people operate the system.  Give it a rigorous test drive.  During this stage keep detailed notes for code improvement.

Defect Reduction

Defect reduction is polite way of saying that there can be 1000 items correct with the system but the one thing wrong you'll hear about.  Once it I hear about it can be corrected.

 

Copyright TESTniques Inc. 2000-2017