IEEE Software Special Issue: Development Tools: Difference between revisions

From Istlab
Jump to navigationJump to search
Newer edit →
Content deleted Content added
Dds (talk | contribs)
449 edits
New page
 
Shelsen (talk | contribs)
31 edits
Line 1: Line 1:
== Summary ==
== Summary ==
Software development tools have become an indispensable part of the modern
The issue will address software development tools from the two perspectives: problems and tasks. From the problem perspective the issue will examine how particular tools can be used to address modern software development challenges. Such challenges include software complexity, utilizing multi-core processors, coordination in global teams, dealing with legacy software, compliance, agile software development, and localization. Task-oriented articles will examine advances and trends in specific areas, compare specific tools and approaches, or present an in-depth description of a particular tool. Examples of tool categories that task-oriented articles can address include: editors, compilers, debuggers, build managers, bug trackers, version control management systems, static analyzers, profilers, documentation generators, and integrated development environments. The issue will focus on practical articles whose claims are backed up by working software or empirical evidence.
software development process. They are required to manage software complexity,
global team coordination, legacy software maintainance, 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 maintainabilty 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 synchronise 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)
* etc.


The special issue on "software development infrastructure" sollicits 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 emperical evidence.


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

Revision as of 16:23, 30 April 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 maintainance, 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 maintainabilty 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 synchronise 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)
  • etc.

The special issue on "software development infrastructure" sollicits 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 emperical evidence.

Co-editors

  • Diomidis Spinellis
  • Simon Helsen
  • Microsoft guy?

Possible contributors

Interesting tools

  • JMX
  • FindBugs
Retrieved from "https://istlab.dmst.aueb.gr/wiki/index.php?title=IEEE_Software_Special_Issue:_Development_Tools&oldid=2013"