Software design document

The Software Design Document serves as a bridge between what the user wants the software to do, and what the developers need to program.

We are using Scrum development practices which focus on delivering something to the users every two weeks, and documenting our code using tests rather than a traditional Software Design Document (SDD).

The software design is documented on the fly and across time in our Issue Tracker. Each issue represents a user story or a feature, or a bug. The Issue tracker and our milestones are the best place to get an idea of what the software is designed to do, what it does now, and what it will do.

• Screencast on Top-down Architecture

• Deliverables and Milestones

• Features and Bugs

• Module Docs

• Specifications written as Jasmine Tests