www.j3s.us
Home  Projects  Services  SeaPort-e  About J3S  Employment  Contact Us 
SATE- Why use SATE in your project?

The SATE approach

  • Drives the developed system validation to capabilities envelope instead of performance specification
  • Avoids custom hardware and hardwired software test implementation
  • Forces a comprehensive performance specification
  • Mandates that requirements be configuration managed like hardware and software
  • Requires a data editor and publisher
  • Motivates a standard test document architecture
Flow down of requirements

A true flow-down of requirements results in the following:

  • System specifications generated from requirements rather than point solution creep from a design back into requirements
  • A requirements driven, performance based architecture
  • Consistent, re-usable requirements specifications
Agile System

An agile system results in test equipment that is:

  • Capable of absorbing requirements changes without breaking validation and configuration management
  • Capable of adapting to tested system changes during development without added cost
  • Capable of absorbing requirements changes without breaking validation and configuration management
  • Capable of conforming to changes in requirements post development with modest cost
  • Capable of absorbing requirements changes without breaking validation and configuration management

SGML/XML standards allow manageable, simplified data formatting effort, allows single root source for specification and execution, and allows change of performance without change in hardware or software configuration

Modular software design allows isolation of damage due to code modification, allows parallel S/W development, and minimizes modification & testing effort

Software tools (libraries) for hardware controllers and tools like CORBA, MPI, PVM, etc. make truly standardized interfaces possible, minimizes time & cost to exchange hardware

Employing SATE innovations
  • Allows parallel development of test equipment and system under test without cost and schedule risk due to redesign of test equipment when hardware changes. It also the start of equipment development while waiting for external designs and specifications to mature.
  • Allows changes to operational performance without changing hardware or software, configuration or reduced operational availability due to modification and revalidation.
  • Requires proper documentation of performance specifications and configuration management of the specification documentation.
 

Copyright © 2000 - 2014, J3S, Inc. All Rights Reserved.