Introduction to Embedded Software Development

1. Introduction to Embedded Software Development He Zongjian hezongjian@msn.com 13816533720

2. Learning by doing • Project • Source code server • Progress control • MSF • Speech • Microsoft MSF expert • ICOP -- CTO

3. Windows ChallengE • Reference web site: • http://www.windowschallenge.com/

4. FAQ Resources • http://bbs.tongji.net • Teacher Assistant: • t-lsong@microsoft.com

5. Brief Introduction • An elective course of Embedded Computing • 3-credit course, 3 hours per week. • Has been available for 2 years, over 260 students have taken this course.

6. Goals • make the student understand the characteristics of embedded system and embedded software • understand the features and architecture of Windows CE, especially the differences from other embedded operating systems. • know how to customize the OS and how to develop applications and device drivers. • give the students more practice via one or two projects.

7. Achievement • Students show great interests in this course. • More than 200 undergraduate students and over 20 graduate students have selected this course. • It has largest attendance among all the elective courses

8. Achievement (continued) • Windows CE club is set et up. Now, more than 150 members have joined the club. • Huaheng Cup Software development Competition • Microsoft internship program

9. Differences from Windows Programming • Application Development • API，MFC • Development Tools • Common Application • Networking， database • Application Development • Device Driver Development • OS Design • Windows CE Kernel Architecture

10. Two teaching methods in SSE 03 • Traditional way >= 50% • Learning by doing <= 50%

11. Course Agenda • Embedded System(2) • Embedded Operating System(2) • Introduction to Windows CE (2) • Application Development (6) • Windows CE OS Development (6) • Windows CE System Architecture(4) • Driver Development (4) • BSP Development & Other Topics (4) • Summary and Case study : (2) • vehicle electronic • Lab Course (16)

12. Learning by doing • CMU Learning by Doing + the situation of China + the involvement of software industry • Use large-scale applied or virtual software projects • Organize students like software company members • Organize teaching courses like real software developing process

13. Learning by doing (Contd.) • 20% teaching, 80% projects • Teachers give the key points to students; students learn knowledge by self-study and doing projects. Teacher works as consultants. • The grading criterion is whether students can finish software projects on schedule and on demand.

14. Sources of projects • 1. Consider whether Microsoft can provide some detailed project requirements, the projects can be virtual or real. Students can be grouped and “bid” for the projects. • 2. Students can be organized to join “Microsoft Windows Embedded Student ChallengE” competition. • 3. Some internal embedded projects in school.

15. Training of engineering experience • During the whole projects, we want to focus on training the engineering attainment of students. Not only lies in the usage of CASE tools, but also in the management of software process. From the initial business plan to analysis and design, coding and testing, product release and so on. All of these should be strictly according to the process of software companies.

16. Responsibility of the teacher • Provide fundamental course introduction and introduction to tools and technologies. • Help students to build the develop environment and tools (code management, bug management) • assort with project process (coding, testing and communication) • Provide technical support (solving problems in projects) and so on…

17. How students get knowledge • 1. The teacher’s necessary explanation. • 2. Self-learning. This is the main approach of getting knowledge. • 3. Communications between students.

18. Organization of the students • Divided into several groups. Each students can act as a specific role, such as：Architect，Program Manager，Developer，Test and so on. • Each student takes his own responsibility and finishes the program together. • In order to let students experience different roles, we can perhaps put one student in different groups and let him / her act as different roles.

19. Phaseof the projects • Divide the project into several phases. For example, writing business planning, project designing, software developing, testing and software release. • At the beginning of each phase, teachers or experts from enterprise can tell the students the tasks of this phase and important things. At the end of each phase, teachers or experts should review the results to see whether they can pass. If the result passes, they can go to next phase, or else, they should redo or modify it.

20. How to grade • Students are divided into several groups. For each group, we give the members the same result. • We treat each group as a unit so that team working can be trained.

21. Future vision • We would like to make this course and this teaching mode as a brand and this brand can have certain effect in software industry. • We may give the students a “Learning by doing” certification, so that students who take part in this course can have more advantages in job hunting.

22. Course Selection if in agenda select it else goto Mrs. Ji xuelian’s office before 20th end if

23. Reference Web site • http://msdn.microsoft.com/library/en-us/dnanchor/html/mobileembedded.asp?frame=true • http://www.palmheart.net/ • http://www.wince.com.tw/ • http://www.csdn.net/ • http://bbs.yesky.com/

24. Reference Newsgroup • microsoft.public.windowsce.app.development • microsoft.public.windowsce.embedded • microsoft.public.windowsce.embedded.vc • microsoft.public.windowsce.platbuilder • microsoft.public.windowsce.targeted.device • microsoft.public.windowsce.update