ESC Boston offers integration-and-test track
Systems integration and test will be the focus of a Thursday, September 29, track at the Embedded Systems Conference Boston. The track will feature four 75-minute sessions on software certification, a C test harness for embedded systems, model-based testing, and scenario testing.
Shan Bhattacharya, a field application engineer at LDRA, will begin the track at 9:30 a.m. with a session titled “A Practitioner’s Guide to Critical Software Certification.” He will provide technical tips and techniques for developing critical software in compliance with DO-178B/C, IEC 61508, CENELEC, ISO 26262, and FDA guidelines. He will highlight the processes, procedures, and tools used to achieve critical software certification, and he will use practical examples, to remove the mystery and confusion surrounding development, verification, configuration management, and quality assurance. This session is aimed at software engineers and engineering managers interested in learning about developing and certifying critical software and at systems engineers interested in learning about the interface between systems and software in a critical environment.
Niall Cooling, a director at Feabhas Ltd., will present an 11 a.m. session titled “Unity: A Lightweight C Test Harness for Embedded Systems.” Cooling will note that one of the key benefits of the Agile movement is moving the test activity from test-after-construction (TAC) to test-before-construction (TBC). In support of that movement, he will describe Unity, an open-source lightweight test harness that can be used for in-target testing of an embedded C application. The class will explain how Unity works, how to integrate into your environment, and how to use it.
Kicking off the afternoon portion of the track at 1 p.m., Dr. Bruce Powel Douglass, chief evangelist at IBM, will present a session on model-based testing. He will note that one of the primary difficulties continuously facing developers is assuring that the design, and the implemented code, is correct-that the delivered system correctly implements the system requirements. He will describe how to assure that a design is correct in object-based or object-oriented systems, particularly those employing use-case, sequence diagrams, and statecharts to capture requirements. He will also discuss how to effectively transition from the specification of requirements into the design and testing phases with continuous, on-going testing that ensures that the evolving design always meets the desired requirements using the UML Testing Profile.
James Grenning, president of Renaissance Software Consulting, will present the track’s final session, “Scenario Testing With Executable Use Cases in C,” at 2:30 p.m. He will note that manually testing embedded software leads to great expense and inconsistent results, and he will explain how attendees can use FitNesse to test execution scenarios of the their embedded software. He will describe tests are repeatable and consistent and that can act as a form of executable specification. He will also explain how to structure designs to be testable, how to take over a clock to deal with periodic and timed events, and how to intercept events to and from the hardware and operating system. He will provide examples that are mainly in C but fully applicable to C++.
See related posts:
Theresa commented:
This article achieved excalty what I wanted it to achieve.
Bonner commented:
And I thought I was the sensible one. Thanks for setitng me straight.
