Subj : Re: Tools for software-developement To : comp.programming From : Christof =?iso-8859-1?Q?K=F6hler?= Date : Sat Oct 08 2005 02:41 am Jonathan Bartlett schrieb: > Christof Köhler wrote: > > > - corporate planning and scheduling (e.g. resource planing ERP) > > I've never seen any such thing used successfully. Sure there can occur problems by using such Software but i guess in an professional development-team they will be found. For example also to see, if an additional employee is needed. > > - development (incl. IDE and VCS) > > cvs > emacs > make > > > - groupware for (team-) internal communication and todo-list > > bugzill > sourceforge > > > - quality management (e.g. bugtracking, issuetracking, tech. > > documentation) > > same as above > documentation - > javadoc > DocBook > quality management - > JUnit (I believe the generic product is called nUnit) > > > - external relations (customer and partner relationship CRM etc.) > > I usually use people for this. Then they are plugged into the groupware > system. > > > As far as i found out it seams to be quite common to use a combination > > of different tools to fulfil the above points. I don't know but i demur that the above mentioned tools work well together in any combination. Perhaps you could suggest a combination that works fine or fulfills major parts of the demands of a programmer-team? Combinations of tools in an software development-team is what i'm looking for. > Schedules are essentially meaningless for development. Perhaps scheduling is not the most important part of what i wanted to describe. The planning in general and dividing up the development process into parts and tangible tasks. I think this could be done and is being done by (or better: with help of) softwaretools. Of course it is not easy to find a solution for all tasks in a software company / team. For quality assurance it could be useful and especially if you want to get a quality certificate. You will need a well organized and documented workflow. Thanks for your help, Chris .