Browse Prior Art Database

Automation Test Solution for Embedded Software

IP.com Disclosure Number: IPCOM000185731D
Original Publication Date: 2009-Jul-01
Included in the Prior Art Database: 2009-Aug-25
Document File: 44 page(s) / 1M

Publishing Venue

Motorola

Related People

Hew, Chun Fung: AUTHOR [+2]

Abstract

In a business world that constantly pushes the boundary of improving lead time to market without compromising product quality, software testing for embedded software has become the attention of the discussion. In response to such demanding expectation, the establishment of a test organization that carries the qualities to provide efficient and effective test service is inevitable. For the test organization to rise to the occasion to meet the demand, there are many aspects to consider. In this presentation, we will focus on one such key aspect that of automation test solution that provides uncompromised product test service. The core of the presentation emphasizes on the challenges faced in providing quality automation test solution for embedded software, the requirements and expectations of a realistic automation test system, the approach used to derive the solution, and the benefits of the solution. Attending will benefit those eager to learn a structured approach to develop a robust yet easy-to-maintain automation test solution for embedded software without investing a huge sum of resources into it.

This text was extracted from a Microsoft PowerPoint presentation.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 24% of the total text.

Slide 1 of 44

Automation Test Solution for Embedded Software

By CF Hew

Updated on: Jul 14, 2009

Notes

1


Slide 2 of 44

Agenda

History & Background of the Radio Communication Business

Challenges in Embedded Software Testing

Requirements & Expectations of a Realistic Solution

Approach Used to Derive the Solution

Benefits & Lessons Learned

Notes

2


Slide 3 of 44

History & Background of Motorola Radio Communication Business

Notes

3


Slide 4 of 44

Brief History of Radio Communication Business in Motorola

In 1930, Galvin Manufacturing Corporation introduced the Motorola radio, one of the first commercially successful car radios

In 1943 Galvin Manufacturing Corporation (later Motorola) designed the world's first FM portable two-way radio, the SCR300 backpack model, for the U.S. Army Signal Corps

A Motorola radio transponder relayed the first words from the moon to Earth in July 1969, from Apollo 11

[This slide contains 3 pictures or other non-text objects]

Notes

4


Slide 5 of 44

Brief History of Radio Communication Business

Introduced in 1999, Motorola's iDEN i1000plus handset was the world's first to combine a digital phone, two-way radio, alphanumeric pager, Internet microbrowser, email, fax and two-way messaging

Motorola introduced the APX family of Project 25 multi-band two-way radios in 2008. Designed with first responder input, APX radios work in the 700/800 MHz and VHF bands, and have custom-designed microphones, integrated GPS, and text messaging

[This slide contains 2 pictures or other non-text objects]

Notes

5


Slide 6 of 44

Observations

Why do I want to take the effort to share with you about some brief history of our products – to boast about our legacy?

     

Time

Complexity

The complexity of the radio communication products has increased significantly from years to years

   

Time

Time-to-market

 

Lead time-to-market to produce a new product has shorten significantly to meet the demanding market and competitions

Notes

6


Slide 7 of 44

Observations

Software involvement in product design has accelerated from a totally-no-involvement state in the 30’s to today’s software-defined-product stage

In conclusion, a robust and comprehensive software test system needs to be put in place to meet today’s challenges

[This slide contains 1 picture or other non-text object]

Notes

7


Slide 8 of 44

Background & Understanding

What need considerations when testing embedded software of a radio communication device?

At least two fundamental aspects to consider,

Who interact with the embedded software?

What kinds of interactions are they?

[This slide contains 3 pictures or other non-text objects]

Notes

8


Slide 9 of 44

Who Interact with the Embedded Software?

Trunking System Team:

  Interact with network system

Manufacturing Counterpart:

  Flashing, tuning and programming

Product Dealers:

  Customize software settings

End Users:

  Prod...