Software Design Process

Here is a quote from a presentation by Scott Ambler about agile delivery:

"Scaling factors such as team size, geographic distribution, regulatory compliance, technical complexity, domain complexity, organization distribution, or organizational complexity will affect the way that you organize your team and tailor your process."

If you wanted to give our process a name, it is very closely related to a combination of SWEBOK at a surface level and Scott Ambler's idea of fast, Agile Model Driven Development.

Like any good agile developer, we combined several methods that suited our needs at the time (and by time, we mean at the expense of how much free time we had across 4 graduate students on a 5 week project).

We tackled our project with the following methodology:

• Initial meet and requirements gathering
  • Which data providers to use
  • Language, design process
  • Story board UI design
• A very quick and dirty design of the framework -JBGE artifacts (Scott Ambler)
• Prototyping stage over
  • Yahoo API data provider
  • World Weather Online data provider
  • Implementation of Story board into UI
• Core design of framework
• Converting from prototypes to implementations of interfaces within framework
  • utilizing TDD for core and data provider implementations
  • utilizing story boards for ui implementations and beta testing for consistency
• Built and tested across MAC, Linux, and Windows 7 & 8

Something to note. Although we do have UML models in the repo, these were utilized post - source implementation. The UML diagrams are used as a replacement to index cards and white boarding that was done prior to implementation of version 1.0.