|
Four weeks into the second semester (of three) of my final degree 'year' and a slight element of panic is beginning to set in. Out of the four modules I'm taking this year, three are fine. The fourth, though, is proving to be something of a problem. All it is, is a software project - we've been provided with a set of requirements and asked to implement a system that covers them. It's not anything we've not done a number of times before, and always with reults that I've been more than happy with. This time around, the requirements specification is astonishingly poorly written, with a complete lack of any communication with client or end users and, instead, a page and a half of purely technical information that not only appears to contradict itself on a number of occasions but also confuses the reader by using terms that pop up once with no definition and then uses entirely different terms for exactly the same things (without mentioning that they're exactly the same things, natch). The reason for all this is painfully bloody obvious; the module leader has based it on a project that she's acutally carried out in the past and is writing it from the piont of view of someone who's already completed it, has no need for explanation of any depth and fails to understand that people coming to this project fresh need more to go on than someone who's spent months implementing it in a real-world situation. Put simply, if I attempted to hand in a documented requirements specification as flawed as this I'd automatically fail the module. I could fucking scream. Instead, I present for your pleasure our group development blog, wherein I'm attempting to get these problems across without getting kicked off the module. And yes, I did only start it an hour ago. |
Losing the fight against mediocrity for the last few years. | ||
|
|||
|
|||