Embedded Software Course Notes On-Line

I'm just wrapping up my first semester teaching a new course on embedded system software. It covers code quality, safety, and security. Below is table of lecture handouts.

NOTE: there is an update here:
     https://users.ece.cmu.edu/~koopman/lectures/index.html#642
which includes newer course notes and quite a few YouTube videos of these lectures.
You should use that URL instead of this blog post, but I've left this post as-is for Fall 2017.

18-642 Embedded System Software Engineering
Prof. Philip Koopman, Carnegie Mellon University, Fall 2017


SlidesTopics
1Course IntroductionSoftware is eating the world; embedded applications and markets; bad code is a problem; coding is 0% of software; truths and management misconceptions
2Software Development ProcessesWaterfall; swiss cheese model; lessons learned in software; V model; design vs. code; agile methods; agile for embedded
3Global VariablesGlobal vs. static variables; avoiding and removing globals
4Spaghetti CodeMcCabe Cyclomatic Complexity (MCC); SCC; Spaghetti Factor (SF)
5Unit TestingBlack box testing; white box testing; unit testing strategies; MCDC coverage; unit testing frameworks (cunit)
6Modal Code/StatechartsStatechart elements; statechart example; statechart implementation
7Peer ReviewsEffective code quality practices, peer review efficiency and effectiveness; Fagan inspections; rules for peer review; review report; perspective-based reviews; review checklist; case study; economics of peer review
8Code Style/HumansMaking code easy to read; good code hygiene; avoiding premature optimization; coding style
9Code Style/LanguagePitfalls and problems with C; language use guidelines and analysis tools; using language wisely (strong typing); Mars Climate Orbiter; deviations & legacy code
10Testing QualitySmoke testing, exploratory testing; methodical test coverage; types of testing; testing philosophy; coverage; testing resources
11RequirementsAriane 5 flight 501; rules for good requirements; problematic requirements; extra-functional requirements; requirements approaches; ambiguity
12System-Level TestFirst bug story; effective test plans; testing won't find all bugs; F-22 Raptor date line bug; bug farms; risks of bad software
13SW ArchitectureHigh Level Design (HLD); boxes and arrows; sequence diagrams (SD); statechart to SD relationship; 2011 Health Plan chart
14Integration TestingIntegration test approaches; tracing integration tests to SDs; network message testing; using SDs to generate unit tests
15TraceabilityTraceability across the V; examples; best practices
16SQA isn't testingSQA elements; audits; SQA as coaching staff; cost of defect fixes over project cycle
17Lifecycle CMA400M crash; version control; configuration management; long lifecycles
18MaintenanceBug fix cycle; bug prioritization; maintenance as a large cost driver; technical debt
19Process Key MetricsTester to developer ratio; code productivity; peer review effectiveness
33Date Time ManagementKeeping time; time terminology; clock synchronization; time zones; DST; local time; sunrise/sunset; mobility and time; date line; GMT/UTC; leap years; leap seconds; time rollovers; Zune leap year bug; internationalization.
21Floating Point PitfallsFloating point formats; special values; NaN and robots; roundoff errors; Patriot Missile mishap
23Stack OverflowStack overflow mechanics; memory corruption; stack sentinels; static analysis; memory protection; avoid recursion
25Race ConditionsTherac 25; race condition example; disabling interrupts; mutex; blocking time; priority inversion; priority inheritance; Mars Pathfinder
27Data IntegritySources of faults; soft errors; Hamming distance; parity; mirroring; SECDED; checksum; CRC
20Safety+Security OverviewChallenges of embedded code; it only takes one line of bad code; problems with large scale production; your products live or die by their software; considering the worst case; designing for safety; security matters; industrial controls as targets; designing for security; testing isn't enough
Fiat Chrysler jeep hack; Ford Mytouch update; Toyota UA code quality; Heartbleed; Nest thermostats; Honda UA recall; Samsung keyboard bug; hospital infusion pumps; LIFX smart lightbulbs; German steel mill hack; Ukraine power hack; SCADA attack data; Shodan; traffic light control vulnerability; hydroelectric plant vulnerability; zero-day shopping list
22DependabilityDependability; availability; Windows 2000 server crash; reliability; serial and parallel reliability; example reliability calculation; other aspects of dependability
24Critical SystemsSafety critical vs. mission critical; worst case and safety; HVAC malfunction hazard; Safety Integrity Levels (SIL); Bhopal; IEC 61508; fleet exposure
26Safety PlanSafety plan elements; functional safety approaches; hazards & risks; safety goals & safety requirements; FMEA; FTA; safety case (GSN)
28Safety RequirementsIdentifying safety-related requirements; safety envelope; Doer/Checker pattern
29Single Points of FailureFault containment regions (FCR); Toyota UA single point failure; multi-channel pattern; monitor pattern; safety gate pattern; correlated & accumulated faults
30SIL IsolationIsolating different SILs, mixed-SIL interference sources; mitigating cross-SIL interference; isolation and security; CarShark hack
31Redundancy ManagementBellingham WA gasoline pipeline mishap; redundancy for availability; redundancy for fault detection; Ariane 5 Flight 501; fail operational; triplex modular redundancy (TMR) 2-of-3 pattern; dual 2-of-2 pattern; high-SIL Doer/Checker pattern; diagnostic effectiveness and proof tests
32Safety Architecture PatternsSupplemental lecture with more detail on patterns: low SIL; self-diagnosis; partitioning; fail operational; voting; fail silent; dual 2-of-2; Ariane 5 Flight 501; fail silent patterns (low, high, mixed SIL); high availability mixed SIL pattern
34Security PlanSecurity plan elements; Target Attack; security requirements; threats; vulnerabilities; mitigation; validation
35CryptographyConfusion & diffusion; Caesar cipher; frequency analysis; Enigma; Lorenz & Colossus; DES; AES; public key cryptography; secure hashing; digital signatures; certificates; PKI; encrypting vs. signing for firmware update
36Security ThreatsStuxnet; attack motivation; attacker threat levels; DirectTV piracy; operational environment; porous firewalls; Davis Besse incident; BlueSniper rifle; integrity; authentication; secrecy; privacy; LG Smart TV privacy; DoS/DDos; feature activation; St. Jude pacemaker recall
37Security VulnerabilitiesExploit vs. attack; Kettle spambot; weak passwords; master passwords; crypto key length; Mirai botnet attack; crypto mistakes; LIFX revisited; CarShark revisited; chip peels; hidden functionality; counterfeit systems; cloud connected devices; embedded-specific attacks
38Security Mitigation ValidationPassword strength; storing passwords & salt/pepper/key stretching; Adobe password hack; least privilege; Jeep firewall hack; secure update; secure boot; encryption vs. signing revisited; penetration testing; code analysis; other security approaches; rubber hose attack
39Security PitfallsKonami code; security via obscurity; hotel lock USB hack; Kerckhoff's principle; hospital WPA setup hack; DECSS; Lodz tram attack; proper use of cryptography; zero day exploits; security snake oil; realities of in-system firewalls; aircraft infotainment and firewalls; zombie road sign hack

Note that in Spring 2018 these are likely to be updated, so if want to see the latest also check the main course page:  https://www.ece.cmu.edu/~ece642/   For other lectures and copyright notes, please see my general lecture notes & video page: https://users.ece.cmu.edu/~koopman/lectures/index.html


Highly Autonomous Vehicle Validation

Here are the slides from my TechAD talk today.


Highly Autonomous Vehicle Validation from Philip Koopman

Highly Autonomous Vehicle Validation: it's more than just road testing!
- Why a billion miles of testing might not be enough to ensure self-driving car safety.
- Why it's important to distinguish testing for requirements validation vs. testing for implementation validation.
- Why machine learning is the hard part of mapping autonomy validation to ISO 26262

Need For Speed Rivals PC Car Racing Game

Need For Speed Rivals PC Car Racing Game








Need for Speed Rivals is a racing video game set in an open world environment. Developed by Swedish and British developers Ghost Games and Ghost Games UK and developer Criterion Games, this is the twentieth installment in the long-running Need for Speed series.

Rivals feature a rapturous gameplay bearing some resemblance to the earlier Hot Pursuit, with exotic cars and high-speed police chases. Players take on the role of a Racer or a Cop, with each side of the law offering its own set of challenges, risks, and rewards. Rivals feature eleven upgradeable gadgets such as EMPs, shockwaves and the ability to call in roadblocks. The game takes place in a fictional location known as Review County. It’s an open world and features over 100 miles (160 km) of open road, larger than that of 2012’s Need for Speed Most Wanted, but on the same size as Criterion’s Hot Pursuit. The open world features a similar set-up to Most Wanted, with several jumps, speed traps, and unlockable cars, as well as shortcuts that are not shown on the map.
Rivals feature a full career progression for both Cop and Racer. When playing as a Cop, there are three types of career that can be followed – patrol, enforcer, and undercover. Progression is by means of Speedlists for Racer and Assignments for Cop, which are sets of objectives which involve dangerous driving, maneuvers, and race standings. When the player completes a set of objectives, the player levels up and unlocks items, and is presented with another set of objectives to choose from. The Autolog system, a competition-between-friends system developed by Criterion for Hot Pursuit and since used in other titles in the Need for Speed series, factors into the progression system, comparing how quickly the player complete an Assignment or Speedlist to other players’ times and posts them to a Speed Wall for local and global leaderboards.
Rivals feature a new social system called the AllDrive, which allow players to seamlessly transition from playing alone to playing with friends, described as “destroying the line between single player and multiplayer”. This allows players to in engage co-op gameplay as well as play against each other. The game also features a dynamic weather system, which makes “the world feel alive in a much bigger sense than any other Need for Speed game.”
Rivals also take on some gameplay styles of earlier Underground titles in the franchise with cues on aesthetic vehicle personalization, as paint jobs, decals, rims and license plates and liveries can be modified, as well as vehicle performance, and various Pursuit Tech gadgets. With the exception of the Aston Martin Vanquish, other vehicles are only available in either racer or police variant. Ferrari officially returns to the franchise in full form for the first time in eleven years since Hot Pursuit 2 in 2002 (although they’ve appeared in 2009’s Shift as Xbox 360-exclusive downloadable content) with the F12berlinetta, 458 Spider, 458 Italia, FF, Enzo, and 599 GTO being the Ferrari vehicles featured.




















SWAT 4 PC Game Free Download Full Action PC Game

SWAT 4 PC Game Free Download Full Action PC Game










SWAT 4 is a tactical first-person shooter video game developed by Irrational Games and published by Muhammad Niaz Games on FEB 16, 2014. SWAT 4 uses the concept of authorized and unauthorized use of weapons. Most situations require the officers to give the suspect a warning to give them the chance to surrender. Shooting without warning is considered unauthorized use of force or deadly force, depending on whether the player kills the suspect. A non-compliant suspect that does not point his weapon at another person may not be lawfully shot. A single unauthorized use of force deducts 5 points, while deadly force deducts 10 points in addition to the loss of score because of not taking suspects alive. Shooting without warning is allowed if the suspect is pointing their weapon at a hostage or a SWAT team member or if they open fire. Suspect reactions to warnings differ some may attempt to hide and set up an ambush, some immediately surrender, others will flee and some will open fire. Some suspects may also pretend to surrender and open fire or run. If a hostage is killed, the mission is automatically deemed a failure.The characters in SWAT 4 are easily injured. Even though all members of the element are equipped with armor, they can be incapacitated quickly. If the player is incapacitated, then the mission ends in failure. Lightly wounded players suffer gameplay penalties depending on injury locations. Leg injuries result in a limp, and arm injuries result in loss of accuracy.
































System= Pentium IV CPU 1.4 GHz
RAM= 512 MB
Size= 780.1 MB
Video Memeory= 64 MB
OS= Windows 98 ME 2000 XP Vista 7 and Windows 8




Adobe premiere pro cc free download full register

Adobe premiere pro cc free download full register





Adobe Premier pro cc free download. This guide will be straightforward and brief on how you cant activate Adobe Premiere Pro CC for free. Activating Adobe product with crack is very safe, not that Activating with an Adobe Premiere Pro serial key is not good... Unless you want to get silly notification updates, using Adobe Premiere Pro crack will automatically block does update and giving you access to your Adobe product even if your trial period is over, Now a guide to install activate your Adobe product with our Adobe pro keygen.




  • Intel Core2 Duo or AMD Phenom II processor with 64-bit support.
  • Microsoft Windows 7 with Service Pack 1 (64-bit) or Windows 8 (64-bit)
  • 4 GB of RAM (8 GB recommended)
  • 4GB of available hard- disk space for installation, additional free space  required during installation ( can not removable flash storage devices)
  • 1 280 x 800 display with OpenGL 2.0- compatible graphics card
  • Windows 7 with Service Pack 1, Windows 8, and windows 8.1