The application I'm building is a membership system used to manage and engage members of a group or organization. Key features it has are:
- Flexible design enabling use by a variety of audiences.
- Easy to use, familiar user interface.
- Enable distributed management of data.
- Enough features to provide a compelling reason to use it.
My wife is the administrative assistant for our church and when she took over the position she inherited a variety of "data sources" - a church directory consisting of names, addresses, telephone numbers and email addresses in an MS Word document, other assorted membership lists in their own MS Word documents, Excel spreadsheets used to track attendance and an Outlook Express address book used for email communication. Our situation is more common than you may realize even in today's electronic age. Non-profits operate on very low (or no!) budgets and volunteers who donate some time and effort. What started out for us as small organized lists has grown over time to become unmanageable and even outdated. Information has to be manually synchronized across multiple documents and inevitably things get missed and forgotten.
Here are the posts which document this journey:
- Introduction (this post)
- Overall Design
- Data Layer
- Business Module
- Work Items
- Deployment Packaging