COURSE SYLLABUS Course Title: Course No: Level: Semester: Classroom: Meeting: Course Prereq: Textbook: Embedded Software

Construction & Testing SWE 3843 & SWE 6843, Section 001 Undergraduate & Graduate Spring 2008 J131 MW 06:00p to 7:15p Programming skills in C/C++ or JAVA, Simulation, CS 4243/5243 (OS concepts) Testing Embedded Software, by Bart Broekman and Edwin Notenboom, Pearson/Addison-Wesley (UK), ISBN: 0-321-15986-1 Further reading: (follow citations at end of each chapter)

Teacher: Dr. Patrick O. Bobbie, Professor Office Hrs / Ph: J386, 678-915-4284 Mon, Wed: 10:00am 12:00pm Email: pbobbie@spsu.edu Website: http://cse.spsu.edu/pbobbie Course Coverage: A. (Revised) Catalog description This project-oriented course focuses on the use of embedded software (ES) development paradigms for generating ES-specific testing processes. Topics include component-based (unit) development and testing; a mapping of embedded software (characteristics) into testing techniques (measures) in the context of the (embedded) software lifecycle, infrastructure (environment/tools), techniques (approaches), and testing organization (people); and methods for classifying ES for selecting suitable testing contexts; and the impact or constraints due to the embedded operating systems, hardware, memory, tools, and related protocols. B. Course Focus The course content addresses such issues as: Fundamentals of testing; the TEmb (testing embedded system) methodology; the multiple V-model; the LITO (Lifecyle, Infrastructure, Techniques, and Organization) framework, which encompasses variants of the Vmodel, planning and levels of testing; standard testing techniques; testing environments and tools; and testing teams and required skills. C. Course Project: The course includes a project that focuses on developing a testing suite and/or a case-study of an embedded system, considering its design, implementation, testing, and simulation/deployment. Program Outcomes: 1. Student will be able to identify key component parts of an ES, differentiating the ES itself from the environment it controls, its interfaces, and the component testing and integration of the parts 2. Students will be able to integrate into the testing process various OS, hardware, timing, and programming language considerations or characteristics 3. Students will be able to develop suites of testing processes for ES-specific applications using the TEmb methodology 4. Students will be able to evaluate or validate their capabilities via realistic semester projects

COURSE SCHEDULE:
Meeting 1 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 4/23/08
31.

32. 33.

Date Part Chp Coverage Focus____________ 1/14/08 I 1/2 Fundamentals/TEmb Method 1/16/08 1/2 Fundamentals/TEmb Method 1/21/08 MLK Holiday No classes 1/23/08 II 3/4 The V-Model/Test Planning 1/28/08 Project discussion Init Phases Assigned 1/30/08 Project design (teams) 2/04/08 3/4 The V-Model/Test Planning 2/06/08 5/6 Testing: Developer vs Team 2/11/08 5/6 Testing: Developer vs Team 2/13/08 Exam 1 On 1 - 6 2/18/08 III 7/8 Risk-based Strategy/Reviews 2/20/08 7/8 Risk-based Strategy/Reviews 2/25/08 9/10 Inspection/Safety Analysis 2/27/08 11 Test Design Techniques 3/03/08 11 Test Design Techniques 3/05/08 Project discussion Init Phases due, [Next Set Assigned] 3/10/08 Spring Break No classes 3/12/08 Spring Break No classes 3/17/08 11/12 Test Design Techniques/Checklists 3/19/08 12 Checklists 3/24/08 Exam 2 On 7 - 12 3/26/08 IV 13 Testing Environments / Tools 3/31/08 13/14 Testing Environments / Tools 4/02/08 15 (exam 2 due take home) Automated Testing 4/04/08 15/16 Automated Testing/Mixed Signals 4/09/08 no class (Compile Test Suite Study Appx E) Mixed Signals 4/11/08 V 17 Testing Organization (People) 4/16/08 17 Testing Organization (People) 4/18/08 E.1 E.9 Testing Suite, Sample Project Completion 4/25/08 Proj Presentations & Discussion [All Phases & Reports due] 4/30/08 Review & Finals On 13 17 5/05-05/09 Finals Week

COURSE LOAD DESCRIPTION and POLICIES: Term Project: There will be a semester project. The phases will encompass developing a testing suite (following the TEmb methodology) for testing phases of an embedded software system analysis, design, prototyping, testing levels, full development, and deployment. The design and implementation techniques will be drawn from the principles and knowledge, which the students have gathered in the course of the semester. The success of this project will certainly reinforce the knowledge and understanding of strategies for testing embedded software systems, and the departure from or overlaps with conventional software systems. Academic Responsibility: You are to work alone, or in designated groups, on all assigned tasks. You are encouraged to consult with other students on assignments. However, any submitted work must be yours. Any form of copying or plagiarizing from current or past students work will result in disciplinary action and automatic F grade for an entire group, or students involved.

Additional Requirements: Each student is expected to be in attendance every class period. The textbook is required and each student must have a copy during class time. Each chapter, or coverage sections, should be read BEFORE each lecture. Assignment due dates must be adhered to. Each assignment will cover concepts/principles that will be discussed in the weeks following its assigned date. The course project (simulation) will be done in groups to allow team-oriented reasoning, design, and development. Any form of copying or plagiarizing from past or current students project code or report will result in disciplinary action and automatic F grade for an entire group, or student(s), involved.

In case of illness, emergencies, etc., students are required to call (or leave a message) on my voice mail or call the main office and leave a written message at 678-915-3571. This must be done before the class takes place, not afterthe-fact. Attendance: Attendance is required for all classes. Grades: The course grade will be distributed as follows: Semester project (All phases, including final report) 1st & 2nd Exams Final exam 40% 40% (20% each) 20%

NOTES: "Students with disabilities who believe that they may need accommodations in this class are encouraged to contact the counselor working with disabilities at (678) 915-7226 as soon as possible to better ensure that such accommodations are implemented in a timely fashion." "If you are majoring in Computer Science and have questions about your schedule or you are having registration problems, please contact the CS Student Services office located at J 393 or call (678) 915-3571 and ask for an appointment."