I'm currently doing a project seminar at Augsburg Uni on software re-engineering and have been talking about development and testing tools etc.
We've covered UML development tools for doing the specifications, code generators and development environments and I'm currently going over testing techniques. I've covered the sort of tools that we used to use at Capgemini, but thought it would be interesting if the students got an insight into how a software house / open source project is run. What tools and methods are used at SUSE/Novell to capture requirements and produce the specifications? (We've covered the likes of Requisite Pro, Rational Rose, Rational Software Architect etc. which were used on large projects, but obviously as they run into 10's of thousands for licensing, I guess you'll use something different.) Do you use any code generators or is the code 100% hand rolled? If so, what tools do you use? What standards and tools do you use internally for testing SUSE before releasing it for public testing, I guess you use Bugzilla throughout for tracking problems? What testing suite do you use to automate the testing procedures internally. How thorough is your test documentation? The problem I find at the Uni is that most of the professors are very academic and expound about theoretical techniques etc. which aren't used in industry, and while I've been showing the students what is used on the consultancy side for producing bespoke applications for clients, I thought it would be interesting if I could give them a perspective inside a software house like SUSE and anyone in the community who wants to respond with what specification and testing tools they use, please feel free to chip in. Information also on the size of the testing lab etc would also be useful. Dave -- "I got to go figure," the tenant said. "We all got to figure. There's some way to stop this. It's not like lightning or earthquakes. We've got a bad thing made by men, and by God that's something we can change." - The Grapes of Wrath, by John Steinbeck --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
