Reasonable Development Time
Question, what do you think is a reasonable development time from design to production of a Windows service that reads in a text file, parses data from it, creates a new table in a SQL Database with a time stamp for generations of data and stores that the parsed data in there. Finds the last generation and runs a comparison between the two and creates an action list of all adds, updates, and deletes, the writes that data to SQL Server and then constructs a flat file output of it. There are logging and e-mail pieces that are mostly reuse code. There is also a manager app to control and schedule this service that is mostly reuse code. Just a guestimate if that came across your desk for everything, design, implimentation, test. Trying to decide if I am way off on my estimate as my boss tends to think.
Re: Reasonable Development Time
All I know is that your boss is gonna want it sooner, and you're gonna want more time :D
Re: Reasonable Development Time
Depends on some stuff but I'd say 4-6 hours as a conservative estimate.
Re: Reasonable Development Time
What was your estimate?
I say 4 hours depending on the parsing, code reuse, and testing. Graff has a good estimate too.
Re: Reasonable Development Time
If I had a spec sheet that everybody had agreed upon, I would say that a day would cover it.
Re: Reasonable Development Time
I always make an estimate and then double it. My managers are technophobes though :D.