<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Requirements on Artur Rios Lab</title><link>https://lab.artur-rios.tech/tags/requirements/</link><description>Recent content in Requirements on Artur Rios Lab</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 21 Oct 2026 17:30:00 +0000</lastBuildDate><atom:link href="https://lab.artur-rios.tech/tags/requirements/index.xml" rel="self" type="application/rss+xml"/><item><title>How I Start a Project From Scratch</title><link>https://lab.artur-rios.tech/engineering/starting-a-project-from-scratch/</link><pubDate>Wed, 21 Oct 2026 17:30:00 +0000</pubDate><guid>https://lab.artur-rios.tech/engineering/starting-a-project-from-scratch/</guid><description>&lt;p&gt;Every project on this site starts the same way. Not with code, but with a&#10;document, because the cheapest place to find a mistake is in a sentence, before&#10;anything has been built on top of it. This is the roadmap I follow, from the&#10;first idea to a system that is ready to use:&lt;/p&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;Create a brainstorm document for the project, with ideas about its nature,&#10;its implementation and the technologies to use.&lt;/li&gt;&#10;&lt;li&gt;Refine the brainstorm into four initial documents: Project Overview,&#10;Technology Stack, Workflow and Business Rules.&lt;/li&gt;&#10;&lt;li&gt;Formalise them into a Vision Document, a System Requirements Document and a&#10;Use Case Specification Document.&lt;/li&gt;&#10;&lt;li&gt;Review the documents, improve them, and review them again until they match&#10;what the project is meant to be.&lt;/li&gt;&#10;&lt;li&gt;Create GitHub issues for the initial scaffold and infrastructure.&lt;/li&gt;&#10;&lt;li&gt;Create a GitHub issue for each use case, linked to a GitHub Project and to an&#10;MVP milestone.&lt;/li&gt;&#10;&lt;li&gt;Implement the initial scaffold and infrastructure.&lt;/li&gt;&#10;&lt;li&gt;Implement one use case after another, including unit and functional tests.&lt;/li&gt;&#10;&lt;li&gt;For each use case, run the tests and fix until all of them pass, and only&#10;then move on to the next one.&lt;/li&gt;&#10;&lt;li&gt;Run a final test of the full functionality and fix any issue found,&#10;repeating until the system is ready.&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;p&gt;The ten steps fall into four phases:&lt;/p&gt;</description></item></channel></rss>