You are currently viewing Affirm Project Planning:  Agile and FDD

Affirm Project Planning: Agile and FDD

Part 2 of 5 of the Affirm series

The Affirm Project will use FDD (Feature-Driven Development) to produce an app to deliver quotations associated with keywords. FDD is an Agile methodology; see Smartsheets for the basics and LucidChart for details.

FDD Process

I will use the five-step process of FDD, albeit in abbreviated form:

  1. Develop the overall model
  2. Build a features list
  3. Plan by feature
  4. Design by feature
  5. Build by feature

Overall Model

The domain model used in FDD is not standardized in its form; a Google search shows images of models in various sloppy and rigorous diagrams.

My simplified version includes a user story:

“A visitor to the web app can submit selected keywords and receive quotations back that match those keywords.”

Affirm is a small enough project the domain model is straightforward:

As a supplement, here are the use cases:

Simple Use Cases

Features

  1. The user can select a keyword and submit the request
  2. On submission, the keyword is matched up with one or more references
  3. On submission, the quotations matching the given keywords and references are returned
  4. The admin can add or remove keywords
  5. The admin can add or remove references associated with keywords

Next

In the next part of this series on the Affirm project, I will cover the plan and design for the first feature listed above.

CR Johnson

As a software engineer with over a decade of experience working for Fortune 50 companies developing software for Windows, the web, and a few interplanetary spacecraft, she's programmed in a plethora of languages including the C#/ASP.NET stack and, recently, Rails. She has tweaked more CSS files than she can count and geeks out a little on data and SQL databases. In her spare time she works on her first novel and enjoys bicycling and dark chocolate.