Insights
Short, practical articles on systems and software engineering, safety-critical certification, and the engineering practices that keep aerospace and embedded programs on track.
The plans are where a programme commits to what it will do — and everything afterwards is judged against them. What each document is for, who reads it, and where the first audit finds the cracks.
Read article
Requirements in, proven products out, a control system running throughout — and the whole machine applied again at every level of the structure. How the engine actually works, and where teams break it.
Read articleCanada's defence spending is being deliberately routed to Canadian industry, and the ITB policy makes your certification readiness worth points on a prime's bid. Here is the machine behind the calls you are getting — and the three walls behind the opportunity.
Read articleNot paperwork, not project management, not the sum of the discipline engineers. The job is owning the system as a whole — and NASA's public-domain handbook is the best description of it ever written.
Read articleNo honest number exists — but the five things the number depends on are knowable, mostly controllable, and routinely ignored in the quotes teams are given.
Read articleRun this before you pay anyone for a gap analysis. Six lifecycle areas, twenty-seven questions you can answer from your own evidence, and what your pattern of answers actually means.
Read articleThe applicant owns the approval, the delegate speaks for the authority, and the supplier owns evidence but no approval. Getting the map straight tells you who to convince and whose signature closes an issue.
Read articleThe four reviews are scheduled engineering events, not exams. What each one samples, the thread-pull move every reviewer makes, and the failure patterns that repeat on programme after programme.
Read articleThe assessment chain that decides your software level, why software is assigned assurance rather than a failure rate, and the only legitimate way to change the answer.
Read articleDO-178C is the same document in Canada. The authority, the regulation, the delegation model and the route to recognition abroad are not — and almost nothing published explains them.
Read articleWhat each level means, where yours comes from, and what genuinely changes as you move up — including the step that costs more than the one everybody worries about.
Read articleWhat the standard actually requires, who decides your software level, what you have to produce, and where programmes lose time. Written for engineers meeting DO-178C for the first time.
Read articleAnnouncing a new section of nubit.ca for short, practical notes on systems engineering, safety-critical software, and certification — from the team that does the work.
Read article
