The Student Room Group
Reply 1
well since you're doing the project to meet the needs of the end user - it would be rather surprising if they were vastly different!

IMO the project objective will go into more specific detail than the user requirements

e.g. user requirement - to reduce errors to under 1%

whereas that might translate into project objectives to do calculations automatically and have decent validation rules

there should be what almost seems like repitation throughout the project - you have what the system needs to do, then you plan HOW you'll achieve it in design, test that it does it in testing, show how you did it in system maintenance, and evaluate it in evaluation. If you don't then you may well lose marks
Reply 2
Avatar for kjr
kjr
OP
right, thanks. :smile:
so if, for example, in user requirements i say that the user needs a way to communicate with other users, in objectives i say that the system must contain private messaging service. right?


P.S.

Also, the part 'Analysis data dictionary'. How can i possibly knnow what kind of data i will need to deal with if i haven't started design yet?
It seems my whole analysis is simply wrong :s-smilie:

Latest

Trending

Trending