Abstract
The goal of this chapter is to give a flavour of a selection of tools that can support the various software engineering activities in the organization. Tools for project management, requirements management, configuration management, design and development, testing, and so on are considered. The organization will generally choose tools to support the process rather than choosing a process to support the tool.
Mature organizations will employ a structured approach to the introduction of new tools. First, the requirements for a new tool are specified and the options to satisfy the requirements are considered. These may include developing a tool internally; outsourcing the development of a tool to a third party supplier; or purchasing a tool off the shelf from a vendor.
Several candidate tools will be identified and considered prior to selection, and each candidate tool is evaluated to determine the extent to which it satisfies the specified requirements. An informed decision is then made and the proposed tool will be piloted prior to its deployment. Finally, the users are trained on the tool, and the tool is rolled out throughout the organization. Support is provided for a period post deployment.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Notes
- 1.
The list of tools discussed in this chapter is intended to give a flavour of what tools are available, and the inclusion of a particular tool is not intended as a recommendation of that tool. Similarly, the omission of a particular tool should not be interpreted as disapproval of that tool.
- 2.
That is, the process comes first then the tool rather than the other way around.
- 3.
SLOC includes delivered source lines of code created by project staff (excluding automated code generated and also code comments).
- 4.
The five scale drivers are factors contributing to duration and cost and they determine the exponent used in the Effort equation. Examples include team cohesion and process maturity.
- 5.
A good requirements process will enable high-quality requirements to be consistently produced, and the cost of poor quality is reduced as wastage and rework is minimized. The requirements are the foundation of the system and if they are incorrect then the delivered system will not be fit for purpose.
- 6.
Mercury is now part of HP.
Reference
Boehm B (1981) Software engineering economics. Prentice Hall, Englewood Cliffs
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2014 Springer International Publishing Switzerland
About this chapter
Cite this chapter
O’Regan, G. (2014). Software Engineering Tools . In: Introduction to Software Quality. Undergraduate Topics in Computer Science. Springer, Cham. https://doi.org/10.1007/978-3-319-06106-1_16
Download citation
DOI: https://doi.org/10.1007/978-3-319-06106-1_16
Published:
Publisher Name: Springer, Cham
Print ISBN: 978-3-319-06105-4
Online ISBN: 978-3-319-06106-1
eBook Packages: Computer ScienceComputer Science (R0)