Experts in the art of firmware

Our Values

USA Firmware Value's StatementR.PACT with our Employees, Customers and Partners

We hire and reward employees that exemplify these R.PACT traits in their daily work:

• RESPECT: We treat all our employees, partners and customers with ample respect for them as members of the human family.

• PASSION: We hire people who are passionate about their work. We are mostly passionate about our role in the betterment of the human condition.

• AFFABLE: We are positive, good natured and pleasant with all our colleagues, clients, partners and fellow employees.

• COMMUNICATION: The USA Firmware Team is committed to keeping lines of communication wide open at all times. This is a critical element to every healthy business relationship.

• TRUST: We build relationships based upon trust. The more trust we can establish between one another, the better will be our relationships, attitudes, performance and efficiencies.

Our Process

• ASSESS & CONSULT: • Analyze the problem. Assess and consult on what

engineering will be required.

• REQUIREMENTS & SPECIFICATIONS: • Determine what features and functions you need.

Communicate this in an SRS (System Requirement Specification) document.

• FEASIBILITY STUDY: • Are the project and product requirements and

specifications feasible? Mitigate risks.

• DESIGN & DEVELOPMENT: • Design a solution by using the right mix of skill sets

and talents. Manage and communicate with client team.

• TESTING: • Robust testing using well established processes &

procedures.

Assess & Consult

• Assess• What are you trying to accomplish?• What regulatory and standards do

you need to comply with?• What assumptions need to be

questioned?• What have you not considered that

you should? • Consult

• Consult on engineering feasibility.• Create an initial set of questions

for the client to consider.• Propose an initial set of

technologies, processes and procedures required to insure success.

Requirements &Specifications

• Requirements• What features and functions

are MVP (minimum viable product)?

• What are you ‘nice to have’ requirements?

• Are the product requirements reasonable? Traceable? Consistent?

• Specifications• What will be implemented to

meet the requirements?• How will the product perform?• What technologies will be used

to meet the requirements?

Feasibility Study

• Schedule• Schedule risks• Long lead items• Critical path analysis

• Scope• Proof of concept• Risk mitigation

• Cost• Product Cost• R&D Cost• Tooling Costs• NRE Costs

Design & Development

• Concept Design• Preliminary Design• Detailed Design • Unit Testing• Prototypes• Integration• Pilots• Code Freeze• Revision Control

Testing

• Verification• Test Procedures• Testing Specifications• Verify traceability• Defect tracking• Static Analysis• Complexity Analysis

• Validation• Use Cases• Testing Requirements• End user validation

Experts in the art of firmware.