IEEE Software Special Issue: Development Tools: Difference between revisions

From Istlab
Jump to navigationJump to search
← Older editNewer edit →
Content deleted Content added
Shelsen (talk | contribs)
31 edits
Dds (talk | contribs)
449 edits
→Summary: Format and spelling
Line 2: Line 2:
Software development tools have become an indispensable part of the modern
Software development tools have become an indispensable part of the modern
software development process. They are required to manage software complexity,
software development process. They are required to manage software complexity,
global team coordination, legacy software maintainance, software migration,
global team coordination, legacy software maintenance, software migration,
agile software development, localization, etc. Such tools address virtually all
agile software development, localization, etc. Such tools address virtually all
aspects of the software development lifecycle and are used to
aspects of the software development lifecycle and are used to
* improve the quality of produced software (e.g. profilers, automated test environments,
* 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.)
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)
* ease the process of producing code (e.g. intelissense editors and sophisticated IDEs)
* increase the reliability and maintainabilty of software under construction
* increase the reliability and maintainability of software under construction (e.g. version control systems, continuous build integration, reproducible night builds, etc.)
(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 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)
* improve customer communication and feedback (e.g. customer issue management and handling)
* manage and synchronise documentation (e.g. documentation generators)
* manage and synchronize documentation (e.g. documentation generators)
* track quality changes over the development lifecycle (e.g. automated performance measurements)
* 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)
* improve the ability to maintain released products (e.g. lifecycle management tools, remote debugging)
* etc.


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


== Co-editors ==
== Co-editors ==

Revision as of 13:45, 8 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
  • Microsoft guy?

Possible contributors

Interesting tools

  • JMX
  • FindBugs
  • JAZZ (see [1])
Retrieved from "https://istlab.dmst.aueb.gr/wiki/index.php?title=IEEE_Software_Special_Issue:_Development_Tools&oldid=2018"