Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
Another 'tool' for the BAs to blag and fool around. Just got my head around MagicDraw, probably suitable for 7-10 year olds. what's wrong with Visio etc? It wouldn't be so bad if the person that did the nice drawing understood the process, but 9/10 they don't. Am I right or not?
1. The first Google result for Dynamic Object Oriented Requirements System isn't actually the company that makes it but a company that sells services related to it, implying total fail in their ability to market themselves on the web
2. Their actual website for this product is a load of jargon-laden blurb and "reports" that seem to just be a load of management-speak pseudo-knowledge garbage
3. Surely object orientation is related to software implementation strategies, not Requirements Management. I for one can take a set of requirements and implement them using spaghetti code, procedural code, or object oriented code (and probably all three ) - the requirements have nothing to do with the implementation strategy.
Or am I missing the point, and this is yet another attempt to take a term that has meaning in an actual software development context, and misapply it to some tedious management process, so that the managers can delude themselves into believing that they are somehow "cutting edge" rather than a bunch of dreary unimaginative people whose job is not so much to do anything interesting as to, well, manage the interesting stuff?
(And yes, I am being excessively cynical for the sake of being annoying, before anybody takes me too seriously. It's still true, though.)
Comment