<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Reqi</title>
	<atom:link href="https://reqi.io/articles/feed" rel="self" type="application/rss+xml" />
	<link>https://reqi.io/articles</link>
	<description>Reqi Systems Engineering Articles</description>
	<lastBuildDate>Tue, 23 Jun 2026 13:36:11 +0000</lastBuildDate>
	<language>en-AU</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0</generator>

<image>
	<url>https://reqi.io/articles/wp-content/uploads/2023/08/logo-sm.png</url>
	<title>Reqi</title>
	<link>https://reqi.io/articles</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Requirements Baseline in Systems Engineering</title>
		<link>https://reqi.io/articles/requirements-baseline-in-systems-engineering</link>
					<comments>https://reqi.io/articles/requirements-baseline-in-systems-engineering#respond</comments>
		
		<dc:creator><![CDATA[Mike Wayne]]></dc:creator>
		<pubDate>Tue, 23 Jun 2026 08:00:00 +0000</pubDate>
				<category><![CDATA[Requirements]]></category>
		<guid isPermaLink="false">https://reqi.io/articles/?p=2120</guid>

					<description><![CDATA[At some point a project has to stop arguing about what the requirements are and agree: this is the set we are building. That agreed, frozen snapshot is the baseline. A requirements baseline is a formally reviewed and agreed set of requirements that becomes the reference point for design, development, and change control. Without a...]]></description>
		
					<wfw:commentRss>https://reqi.io/articles/requirements-baseline-in-systems-engineering/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>SMART Requirements: Specific, Measurable, Attainable, Relevant, and Time-Bound</title>
		<link>https://reqi.io/articles/smart-requirements</link>
					<comments>https://reqi.io/articles/smart-requirements#respond</comments>
		
		<dc:creator><![CDATA[Mike Wayne]]></dc:creator>
		<pubDate>Tue, 23 Jun 2026 08:00:00 +0000</pubDate>
				<category><![CDATA[Requirements]]></category>
		<guid isPermaLink="false">https://reqi.io/wordpress/smart-requirements/</guid>

					<description><![CDATA[&#8220;The system should be user-friendly&#8221; is not a requirement &#8212; it is a wish wearing a requirement&#8217;s clothes. You cannot build it, test it, or prove you met it. SMART requirements fix that by demanding every requirement be Specific, Measurable, Achievable, Relevant, and Time-bound &#8212; five tests that turn a vague hope into something an...]]></description>
		
					<wfw:commentRss>https://reqi.io/articles/smart-requirements/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Unravelling Reliability, Maintainability, and Availability (RAM)</title>
		<link>https://reqi.io/articles/reliability-maintainability-availability-ram</link>
					<comments>https://reqi.io/articles/reliability-maintainability-availability-ram#respond</comments>
		
		<dc:creator><![CDATA[Mike Wayne]]></dc:creator>
		<pubDate>Tue, 23 Jun 2026 08:00:00 +0000</pubDate>
				<category><![CDATA[RAMS]]></category>
		<guid isPermaLink="false">https://reqi.io/wordpress/reliability-maintainability-availability-ram/</guid>

					<description><![CDATA[Two machines do the same job. One runs for years; the other is in the workshop every other week. Same function, wildly different value &#8212; and the difference has a name. RAM stands for Reliability, Availability, and Maintainability: the three properties that decide whether a system can be depended on over its working life. Reliability...]]></description>
		
					<wfw:commentRss>https://reqi.io/articles/reliability-maintainability-availability-ram/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Understanding the Differences Between Functional and Non-functional Requirements</title>
		<link>https://reqi.io/articles/functional-and-non-functional-requirements</link>
					<comments>https://reqi.io/articles/functional-and-non-functional-requirements#respond</comments>
		
		<dc:creator><![CDATA[Mike Wayne]]></dc:creator>
		<pubDate>Tue, 23 Jun 2026 08:00:00 +0000</pubDate>
				<category><![CDATA[Requirements]]></category>
		<guid isPermaLink="false">https://reqi.io/wordpress/functional-and-non-functional-requirements/</guid>

					<description><![CDATA[Here is a system that passed every test and still failed. It did exactly what the spec said &#8212; calculated the right numbers, returned the right answers &#8212; and was unusable, because it took eleven seconds to respond and fell over under ten users. Every functional requirement was met. The non-functional ones were never written...]]></description>
		
					<wfw:commentRss>https://reqi.io/articles/functional-and-non-functional-requirements/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Digital Twins in Systems Engineering: A Digital Revolution</title>
		<link>https://reqi.io/articles/digital-twins-in-systems-engineering</link>
					<comments>https://reqi.io/articles/digital-twins-in-systems-engineering#respond</comments>
		
		<dc:creator><![CDATA[Mike Wayne]]></dc:creator>
		<pubDate>Tue, 23 Jun 2026 08:00:00 +0000</pubDate>
				<category><![CDATA[Systems Engineering]]></category>
		<guid isPermaLink="false">https://reqi.io/wordpress/digital-twins-with-systems-engineering-digital-future/</guid>

					<description><![CDATA[Imagine a living copy of a jet engine that runs inside a computer at the same time as the real one &#8212; same wear, same temperatures, same stresses, updated second by second from sensors on the actual machine. That copy is a digital twin. A digital twin is a dynamic virtual model of a physical...]]></description>
		
					<wfw:commentRss>https://reqi.io/articles/digital-twins-in-systems-engineering/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>SysML v1 vs SysML v2: What Changed and Should You Switch?</title>
		<link>https://reqi.io/articles/sysml-v1-vs-sysml-v2</link>
					<comments>https://reqi.io/articles/sysml-v1-vs-sysml-v2#respond</comments>
		
		<dc:creator><![CDATA[Mike Wayne]]></dc:creator>
		<pubDate>Sun, 21 Jun 2026 09:00:00 +0000</pubDate>
				<category><![CDATA[Model Based System Engineering (MBSE)]]></category>
		<category><![CDATA[Systems Engineering]]></category>
		<guid isPermaLink="false">https://reqi.io/articles/?p=2625</guid>

					<description><![CDATA[Every MBSE team is now asking the same question: do we move to SysML&#160;v2, and if so, when? It is a fair thing to wrestle with &#8212; SysML v1 has two decades of tooling, training and existing models behind it, while SysML v2 is a clean-sheet redesign. The short answer: v2 is more precise, more...]]></description>
		
					<wfw:commentRss>https://reqi.io/articles/sysml-v1-vs-sysml-v2/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>SysML v2: What&#8217;s New and Why It Matters</title>
		<link>https://reqi.io/articles/sysml-v2-whats-new-and-why-it-matters</link>
					<comments>https://reqi.io/articles/sysml-v2-whats-new-and-why-it-matters#respond</comments>
		
		<dc:creator><![CDATA[Mike Wayne]]></dc:creator>
		<pubDate>Sun, 14 Jun 2026 09:00:00 +0000</pubDate>
				<category><![CDATA[Model Based System Engineering (MBSE)]]></category>
		<category><![CDATA[Systems Engineering]]></category>
		<guid isPermaLink="false">https://reqi.io/articles/?p=2622</guid>

					<description><![CDATA[For twenty years, model-based systems engineering ran on SysML&#160;v1 &#8212; a language that was, honestly, a profile bolted onto UML: a software notation pressed into service for whole systems. It worked, but it creaked. SysML&#160;v2 is the ground-up rebuild &#8212; a systems modelling language with its own formal foundation, a first-class textual notation alongside the...]]></description>
		
					<wfw:commentRss>https://reqi.io/articles/sysml-v2-whats-new-and-why-it-matters/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Configuration Management Explained: Process, Roles &#038; Real-World Examples</title>
		<link>https://reqi.io/articles/what-is-configuration-management</link>
					<comments>https://reqi.io/articles/what-is-configuration-management#respond</comments>
		
		<dc:creator><![CDATA[Mike Wayne]]></dc:creator>
		<pubDate>Sun, 07 Jun 2026 06:00:00 +0000</pubDate>
				<category><![CDATA[Systems Engineering]]></category>
		<guid isPermaLink="false">https://reqi.io/articles/?p=1277</guid>

					<description><![CDATA[Configuration management, minus the jargon: what it is, the five core CM activities, who does the work, why it matters, and the real-world failures (Knight Capital, Mars Climate Orbiter, ERTMS) that prove the point.]]></description>
		
					<wfw:commentRss>https://reqi.io/articles/what-is-configuration-management/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>What Is Systems Engineering V Model?</title>
		<link>https://reqi.io/articles/what-is-systems-engineering-v-model</link>
					<comments>https://reqi.io/articles/what-is-systems-engineering-v-model#respond</comments>
		
		<dc:creator><![CDATA[Mike Wayne]]></dc:creator>
		<pubDate>Sun, 31 May 2026 06:00:00 +0000</pubDate>
				<category><![CDATA[Terms]]></category>
		<guid isPermaLink="false">https://reqi.io/articles/?p=1297</guid>

					<description><![CDATA[A clear guide to the systems engineering V-model: how the V lifecycle links requirements and design to testing, verification and validation — plus how to read the V model diagram.]]></description>
		
					<wfw:commentRss>https://reqi.io/articles/what-is-systems-engineering-v-model/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Drawing System Architecture: Visual &#038; AI-Native Update to Reqi</title>
		<link>https://reqi.io/articles/drawing-system-architecture-visual-ai-native-update-to-reqi</link>
					<comments>https://reqi.io/articles/drawing-system-architecture-visual-ai-native-update-to-reqi#respond</comments>
		
		<dc:creator><![CDATA[Mike Wayne]]></dc:creator>
		<pubDate>Sun, 10 May 2026 00:39:19 +0000</pubDate>
				<category><![CDATA[Systems Engineering]]></category>
		<guid isPermaLink="false">https://reqi.io/articles/?p=2415</guid>

					<description><![CDATA[A look at the new system architecture canvas, the requirements drill-down, and the AI tools that have been quietly built around an INCOSE backbone. What the Visual Architecture Update Adds Capability What it means for you AI-native diagramming Describe the system and let reqi draft the architecture Connected to requirements Diagrams link to the requirements...]]></description>
		
					<wfw:commentRss>https://reqi.io/articles/drawing-system-architecture-visual-ai-native-update-to-reqi/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
