Embedded Systems, Risk and Two IT Business Models
Course foundations: what embedded software is, why physical effects change engineering, and how product and service business models frame the work.
Read notes →
Teaching / Course
Embedded Software Engineering
Fifteen consecutive sessions, from embedded-engineering foundations to customer discovery, team presentations, qualification, pricing models, detailed delivery planning and the full project estimate. Previously approved notes remain protected.
01.09.2026 → 03.11.202615 sessionsfrozen 28.09.2026
Course map
Dated modules trace the course from embedded-system foundations through delivery, commercial engineering, requirements and architecture.
15 sessions · Jira, hiring and kick-off (forecast)
MODULE 01FOUNDATIONSEmbedded constraints, risk and business models
MODULE 02TEAM & DELIVERYPeople, roles and the physical delivery chain
MODULE 03MARKET & CUSTOMERVisibility, trust, leads and formal pre-sale
MODULE 04COMMERCIAL ENGINEERINGStandards, proposal structure, estimates and pricing
MODULE 05REQUIREMENTS & ARCHITECTUREDiscovery, traceability and system decomposition
MODULE 06DEVELOPMENT, V&V & RELEASEPlanned: implementation, integration, test, release and feedback
Lecture archive
Each published session keeps its date, frozen notes and raw transcript.
01 · FOUNDATIONS1 Published
02 · TEAM & DELIVERY1 Published
03 · MARKET & CUSTOMER2 Published
04 · COMMERCIAL ENGINEERING1 Published
05 · REQUIREMENTS & ARCHITECTURE1 Published
06 · DEVELOPMENT, V&V & RELEASEPlanned
—Planned
Traceable timeline
Traceable timeline
The course history is chronological and append-only after the 28 September reconstruction.
Published sessions
Published sessions
Engineering Team and the Physical Delivery Chain
Firmware, hardware and mechanics form the core; architecture, management, procurement and manufacturing make the three streams work as one system.
Read notes →
From an Unknown Company to a Lead
Trust, referrals, public evidence, technical champions and events create the conditions for a potential customer to start a real conversation.
Read notes →
From Lead to Formal Pre-Sale
Initial and technical follow-ups turn interest into structured information exchange: RFI, RFQ, course-local RFC and the first Proposal baseline.
Read notes →
Proposal, Standards and Commercial Model
Reference documents, conformity constraints, V&V, resources and pricing models turn a technical idea into a proposal that can actually be negotiated.
Read notes →
From Contract to Requirements and First Architecture
The course crosses from pre-sale into delivery: staffing lead time, discovery, business decomposition, user needs, system requirements and the first architecture sketch.
Read notes →
Preparing an Engineering Company for Industry Engagement
A technical company must communicate its competence: consistent visual identity, credible business cards, working digital contacts and a focused, verifiable engineering one-pager.
Read notes →
Workshop: Business Artifact Review and Engineering Proposal
Review real student artifacts, map engineering responsibilities and study a technical proposal from requirements and high-level architecture to PoC, MVP, verification and delivery.
Read notes →
Industry Exhibition Simulation: From Contact to Engineering Project
An interactive exhibition simulation turns first contact into a qualified lead, a follow-up meeting and an engineering delivery plan, while testing vendor/buyer roles and business boundaries.
Read notes →
From Exhibition Contact to Technical Discovery: Follow-up, Team and Presentation
Post-conference reporting, follow-up invitations, meeting team, interactive client presentation and the transition to technical discovery. Read notes →
Negotiating After the First Contact: Discovery, Partnership and Project Transition
Customer meeting role-play: tailored presentation, team roles, discovery questions, RFI, delivery planning and IP rights.
Read notes →
The Expert Meeting, RFI/RFC/RFQ and the Proposal: From Company Talk to a Project
Second follow-up with experts, meeting roles, RFI, RFC and the proposal, how much to disclose, versioning, RFQ and team estimates.
Read notes →
A Way of Work for the Customer: Phases, Gates and Pricing Models
Phases with gates, the cone of uncertainty, Fixed Price versus Time & Material, capped T&M and combined models.
Read notes →
HARA for the PoC, a Hybrid Contract and the First Epic Plan
HARA for the PoC, FP for in-house engineering and T&M for vendors, assembly levels and a 29-step EPIC 1 plan with gates.
Read notes →
Gantt Chart, Risks, Team Cost and the Full Project Estimate
Gantt, PERT, risks and Monte Carlo, team cost, price by phase and full timing for a cell with CV+AI, Jetson and ROS 2.
Read notes →