Running IDE Projects
I have always been less than enthusiastic about using integrated development environments (IDEs). I saw them as very specific applications that:
Recently however I have started using Eclipse for occasional work (I can use it for Java, C++ and Perl) and I have been working with a customer who uses Borland JBuilder. I can see some virtue in such tools, indeed for todays complex environments (i.e. .NET and J2EE) they would appaer to be essential. However pitfalls still lurk to trap the unwary. Here are my some observations:
- Hide too much necessary detail from the developer and deny the level of control and understanding often required in anything other than toy systems development
- Encouraging sloppy programming practice because too much just happened under the hood
Of course some of these issues need to be addressed even wothout and IDE. However in my experience and IDE makes a lot of assumptions and without making some explicit descisions it is easy to get caught.
- Development teams that use IDE's need a common
- IDE standard operating environment (SOE) that documents:
- Which IDE's will be supported
- How such tools will be set up in a consistent fashion. This
affects such things as
- Names and locations
- Hierarchy of settings (projects vs. user vs. installation)
- Project library management standards e.g.
- A consistent CLASSPATH in Java that is used by all developers
- Link edit options in other languages
- Software Configuration Management (SCM) approach
- Needs a common directory set and file naming
- Re-factoring needs to be addressed (how does one manage re-factoring in an environment with enforced changed control?)
- Should IDE specific files (e.g. project files) be placed under SCM control?
- Specific for Serena Dimensions configuration management tool
- One workset per IDE project
- IDE Project directory to included in workset directory structure
- A documented approach for the management of shared code and libraries across multiple projects. Who is responsible for
- Identifying change
- Implementing changes
- Accepting and migrating changes into projects
- Building software for test and release environments
- Software build must be done via a scripting process.
- Some IDE's support this (e.g. JBuilder uses the -build
- Others will required the creation of Ant, make scripts or the use of similar tools.
- Some IDE's will assist the in the generation of the make or Ant script
- Builds must be done on configuration managed environment, not on developers PCs.