<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Assignments-Springs on SDL: Software Development Lab</title><link>https://sdl-56e997.gitlab.io/assignments-spring/</link><description>Recent content in Assignments-Springs on SDL: Software Development Lab</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://sdl-56e997.gitlab.io/assignments-spring/index.xml" rel="self" type="application/rss+xml"/><item><title/><link>https://sdl-56e997.gitlab.io/assignments-spring/1-bdd-intro/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sdl-56e997.gitlab.io/assignments-spring/1-bdd-intro/</guid><description>&lt;h1 id="assignment-1-bdd-introduction"&gt;Assignment 1: BDD Introduction&lt;/h1&gt;
&lt;h2 id="motivation-software-development-challenges"&gt;Motivation: Software Development Challenges&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;If it ain&amp;rsquo;t tested, it&amp;rsquo;s broke.&lt;/strong&gt; This is a quote from an avionics
testing engineer. Testing cannot prove software works, but its almost
certain that untested software does &lt;em&gt;not&lt;/em&gt; work. The typical solution is do
a bit of manual testing after writing code, but these tests are not
repeatable. Written tests are slightly better, but too expensive to
re-execute often. They do little to improve stability. But you probably
have a lot of experience with software working today but not
tomorrow. Errors always creep in. It critical to establish a thorough,
automated test environment early in the project, and clients are unlikely
to find systems without tests to be useful or maintainable.&lt;/p&gt;</description></item><item><title/><link>https://sdl-56e997.gitlab.io/assignments-spring/2-bdd-implementation/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sdl-56e997.gitlab.io/assignments-spring/2-bdd-implementation/</guid><description>&lt;h1 id="adding-bdd-to-your-sdl-project"&gt;Adding BDD to your SDL project&lt;/h1&gt;
&lt;p&gt;This assignment will give you experience with applying automated behavior-driven
development (BDD) to your SDL project. It assumes that you have
successfully completed the &lt;a href="../1-bdd-intro"&gt;BDD introduction&lt;/a&gt; assignment
and quiz.&lt;/p&gt;</description></item><item><title/><link>https://sdl-56e997.gitlab.io/assignments-spring/3-project-video/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sdl-56e997.gitlab.io/assignments-spring/3-project-video/</guid><description>&lt;h1 id="assignment-3-knowledge-transfer-video"&gt;Assignment 3: Knowledge Transfer Video&lt;/h1&gt;
&lt;h2 id="assignment-project-knowledge-transfer-video"&gt;Assignment: Project Knowledge Transfer Video&lt;/h2&gt;
&lt;p&gt;This assignment is due Friday May 8, 2026 at 11:59 PM. NO LATE SUBMISSIONS WILL BE ACCEPTED. NO EXCEPTIONS.&lt;/p&gt;
&lt;h2 id="objective"&gt;Objective&lt;/h2&gt;
&lt;p&gt;The purpose of this assignment is to create a professional, high-quality
video that documents your team’s project for future student groups. This
video should serve as both a showcase of your work and a practical
onboarding resource that helps others understand, set up, and extend your
project.&lt;/p&gt;</description></item><item><title/><link>https://sdl-56e997.gitlab.io/assignments-spring/abet-seso2p4-testing/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sdl-56e997.gitlab.io/assignments-spring/abet-seso2p4-testing/</guid><description>&lt;h1 id="documenting-meaningful-test-suites"&gt;Documenting Meaningful Test Suites&lt;/h1&gt;
&lt;p&gt;Include title information: A title for the assignment, your name, the
date, and the course code (e.g., SWE3720).&lt;/p&gt;
&lt;p&gt;Provide a link to a file with a suite of tests you wrote that is available on the main branch.  (This means that you must perform a merge to main with at
least that test if it is not already on the main branch.)&lt;/p&gt;</description></item><item><title/><link>https://sdl-56e997.gitlab.io/assignments-spring/abet-seso3p4-documentation/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sdl-56e997.gitlab.io/assignments-spring/abet-seso3p4-documentation/</guid><description>&lt;h1 id="individual-assignment-writing-documentation"&gt;Individual Assignment: Writing Documentation&lt;/h1&gt;
&lt;p&gt;Each student will write documentation.&lt;/p&gt;
&lt;p&gt;Ideally, this will be planned during Sprint 4, but could carry over into
Sprint 5 for individual students if other activities take priority.&lt;/p&gt;</description></item></channel></rss>