Slashdot is powered by your submissions, so send in your scoop


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).


+ - Software engineering, or should we compromise?

Submitted by
AccUser writes "I was recently engaged by a major logistics company to review a proprietary software system that had been developed over the past 5 years. The system had been developed in isolation to the industry, and contained a serious number of design flaws — basically, it was not fit for the company's future business plans. Having proposed a suitable solution to their problems, which has been accepted by the company, I am now faced with a contracted project manager who has no experience of software architecture or software engineering methodology, and who wants to compromise on the proposed solution in an effort to deliver a solution quicker and stay in his comfort zone. What would you do? Compromise, or stick to software engineering principals?"

What good is a ticket to the good life, if you can't find the entrance?