OK, the very next thing I intend to do is expand the range of the product a little. For months I've been primarily responsible for attendance-taking in the church; collecting the sign-in sheets, checking for visitors, trying to make sure they're followed up with appropriately. So this is an obvious extension piece for this software; a way to track attendance and followups. I'll think some more about the design of this, but it's similar in many ways to what I've already stated - data entry screens, a data store, and reports, so hopefully there will be some opportunities for refactoring here. Also, requirements for security are a lot less stringent - the data that is kept is names, dates, addresses and phone numbers, rather than social security numbers and income. So it's a bit easier to put together.
So right now, we're looking at three main pieces of the application: benevolence; attendance; and updating (wonder if I can come up with a word that means "updating" that ends in "ence", that would be cool). For ease of updates, we'll split these out into several assemblies:
- A stub. This will be the launcher application. It will be very simple and hopefully will allow us to update the other pieces very simply.
- A Benevolence assembly.
- An Attendance assembly.
- An Updates assembly.
- A Persistence assembly. This will handle the interface to the data store. Now I really need another word for "Updateance"!
Next step: We'll throw a few screens together and see how they look.
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.