--- MJ Ray markj@cloaked.freeserve.co.uk wrote:
David Freeman david_freeman@rocketmail.com writes:
I never got around to ripping it a part. The problems are
- Based on assumptions a) People are honest
Have to pretty much try this. Having some sort of deposits may be a good move, but who holds them?
In a per-to-peer system? good question, in a centralised system? the librarian.
b) People will notice books have gone astray
Send out "please confirm your borrowing" emails and email the maintainers or this list if people don't answer?
Might work.
c) People will return books
Same as a, surely?
Yes but from a different angle.
In that case you haven't modelled the system properly. You can't
start
programming till you have a decent enough idea of how it will work. incedentally I will have a modell created by mondays IRC.
It seems this model is slipping further and further back...
Well I decided to enjoy the weather yesterday and then goto the pub, and as it will start to rain in a mo, I will do it ASAP.
There needs to be a dead line for collection and for loans, but you would have modelled this in the functional requirements.
Unless we discuss this thing, how do we find these things out? I don't believe any initial model will get all of these things right first time.
Nor do I, this is why we will have an iterative development process.
And what are assumptions?
Assumptions are beliefs which you accept as truths in order to build a logical system. They cannot be proved, but they are used to prove other results. I would have thought you'd know that, having used the word so freely...
So basically you are using one incomplete system for prove another incomplete system? An assumption is object with no evidence of fact backing it up which is used to help prove one system. And as such they are the mother of all f*** ups.
Thanks
D
-- MJR
__________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/