|Product Performed to Expectations:||3|
|Specifications were sufficient to design with:||5|
|Demo Software was of good quality:||3|
|Product was easy to use:||2|
|Support materials were available:||4|
|The price to performance ratio was good:||5|
|TotalScore:||22 / 60|
This course is probably best suited for established embedded system software engineers and senior year computer/computer science engineering students who really want to get an introduction into the guts of developing a product that includes an ARM processor. Most of the course is devoted to being an advertisement vehicle to ARM processor hierarchy.
To me, this course seems written by embedded system developers for embedded system developers. The lectures are terribly boring, the lectures lack the use of animation graphics and other structured learning education techniques to emphasize important points and concepts. The quizzes should be reinforcement to the important points of the lecture, I often felt it was a trivia quiz. The course lavished in the use of jargon and acronyms, which kept me confused.
My expectations for doing this RoadTest was to learn enough basic cellphone/ bluetooth interface to do very simple , but creative, robotics/IOT projects and use it to inspire 10-18 year olds at community exhibits, schools, and code classes my robotics club teaches at the library.
What I learned is the “simplified” bluetooth BLE interface is highly structured and very complex for a beginner, as well as the cornucopia of needed development tools: Nucleo STM and the Keil uvision IDE, mbed, Android, etc.
The labs are the best learning tool, and the best part of the course. However, the lab videos were out of date, and each lab had major roadblocks to overcome. It’s a shame because the course does have some good work invested in it, but the roadblocks destroyed my motivation and enthusiasm, and I had to dig deep to reluctantly push thru the course material.
Course roadblocks included big problems with licensing, getting them and expiring during the course, the lack of functionality with LITEware versions, fighting to get programs to work.
I spent significant hours every day and weekends mostly installing and setting up tools. I would prefer to use that time learning.
I would recommend to create make this course a 12 lesson course just from lessons 9-12 (throw away lesson10 lecture because its worthless), break lectures into smaller modules, where students can enjoy small successes and pick up terminology.
The lectures need to reinforce major points, include some humor, cartoons, CGI computer motion graphics (imagine that) , use TECHNOLOGY to teach and make the experience enjoyable. The labs need to be closely coordinated with the lectures.
Please please please – the first lesson should be the “getting started document” with COMPLETE instructions of EVERY software tool needed to complete the course and every frequently used URL. Each new lab introduced new software tools that need installed, which became a huge distraction. Please have any tool license be valid for at least 6 months. We had 8 weeks to do the course, but I may find time to refresh my learning after that 8 weeks. I could use the hardware later in an exhibit that would be great advertisement for ARM and this course.
I hope these honest and friendly feedbacks can help improve this course presentation to give justice to the important concepts and teachings it is trying to present.