[AccessD] Requirements (was: I should be able to do this - resolved)

But if you are using Agile methodolgies, that requirement may not be identified until some 
distance down the track.    Building  Flexibility into your design is just as important and 
analysis and coding :-)


On 8 Dec 2011 at 7:47, Dan Waters wrote:

> Requirements are more important.  You can't build a good house with bad
> plans - no matter how good the builders are!
> 
> Dan
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark Simms
> Sent: Thursday, December 08, 2011 7:38 AM
> To: 'Access Developers discussion and problem solving'
> Subject: Re: [AccessD] I should be able to do this - resolved
> 
> Re: "......someone mentioned that the company uses 360-day years"
> 
> Oh boy, here we go with a fundamental issue that should have come out way
> back in the requirements definition.
> The best programmers in the world cannot overcome something like this.
> On the other hand, the best analysts cannot overcome bugs caused by crappy
> coding.
> 
> So what's more important: the analysis or the coding ?
> 
> 
> 
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>