IEEE Software Special Issue: Development Tools: Difference between revisions

From Istlab
Jump to navigationJump to search
Content deleted Content added
Dds (talk | contribs)
Dds (talk | contribs)
→Co-editors: Add Arthur Ryman
Line 24: Line 24:
* Diomidis Spinellis
* Diomidis Spinellis
* Simon Helsen
* Simon Helsen
* Arthur Ryman
* K. Rustan M. Leino?


== Possible contributors ==
== Possible contributors ==

Revision as of 21:43, 14 May 2007

Summary

Software development tools have become an indispensable part of the modern software development process. They are required to manage software complexity, global team coordination, legacy software maintenance, software migration, agile software development, localization, etc. Such tools address virtually all aspects of the software development lifecycle and are used to

  • improve the quality of produced software (e.g. profilers, automated test environments, bug finders, debuggers, etc.)
  • automate the software production process (e.g. compilers, program generators, GUI creation tools, wizards, etc.)
  • ease the process of producing code (e.g. intelissense editors and sophisticated IDEs)
  • increase the reliability and maintainability of software under construction (e.g. version control systems, continuous build integration, reproducible night builds, etc.)
  • improve communication inside development teams (e.g. requirement, feature, and bug tracking; WIKI's)
  • improve customer communication and feedback (e.g. customer issue management and handling)
  • manage and synchronize documentation (e.g. documentation generators)
  • track quality changes over the development lifecycle (e.g. automated performance measurements)
  • improve the ability to maintain released products (e.g. lifecycle management tools, remote debugging)

The special issue on "software development infrastructure" solicits papers, which describe how tools can generally improve the software development lifecycle process. Articles may address specific trends; compare existing tools and approaches; or provide an in-depth analysis of the benefits and drawbacks of a particular tool. Articles should be backed by working software or empirical evidence.

Co-editors

  • Diomidis Spinellis
  • Simon Helsen
  • Arthur Ryman

Possible contributors

Reviewers

  • Markus Voelter [1]

Interesting tools

  • JMX
  • FindBugs
  • JAZZ (see [2])