Defining the base features of Anvil v1.0
There are a lot of great resources on the Internet about building software. One of my favorite insights happens to be from the 37 Signals blog. And that is that great software should be simple and intuitive, and can be built with small teams. Taken directly from their website:
We believe software is too complex. Too many features, too many buttons, too much to learn.
Amen.
So today I want to talk about the features that will be in Anvil, at least for version 1. While sitting in in Starbucks enjoying a Chai Latte, I have recorded a screencast on my TabletPC of me creating the first version of the functionality mindmap that I will use during the project. This will be used as the base when I start to schedule things and monitor the progress of the development.
From that mindmap, I will build some use case scenarios that I will later use in the threat model. I will have those done tonight or tomorrow. I also plan to work on deciding what technology I will use, and what the topology will look like. Chances are, tomorrow I will screencast the drawing and explanation of the technology mindmap.
Anvil Functionality Mindmap Screencast [Flash ~12MB]