|
|
|
|
|
 |
| Guidelines for Authoring a Technology Description | 
|
|
[Top] [Prev] [Next] [Bottom]
Guidelines for Authoring a Technology Description
The purpose of this document is to provide guidance to those writing
technology descriptions for the Software Technology Roadmap. It
provides background information about the document and guides authors through
the development and review processes for technology descriptions.
1 Introduction
The Software Technology Roadmap (STR) is a reference document
containing the latest information, in the form of technology descriptions, on
approximately 63 software technologies. The STR is of interest to anyone
building or maintaining systems. For more information about the background and
audience of the STR, please see Appendix A.
The purpose of a technology description is to
Each technology description also provides reference(s) to literature,
indications of the current maturity of the technology, and cross references to
related technologies.
Technology descriptions are not meant to be comprehensive--each description
should provide the reader with enough knowledge to decide whether to
investigate the technology further, to find out where to go for more
information, and to know what questions to ask in gathering more
information.
Typically, technology descriptions range in size from six to eight pages,
depending on the amount of information available or the maturity of the
technology.
For other examples of technology descriptions, please review the hard copy
document (CMU/SEI-97-HB-001) or visit the STR Web site.
The Web site always has the most recent
version of the technology descriptions.
[Top] [Prev] [Next] [Bottom]
The Software
Engineering Institute (SEI) is a federally funded research and
development center sponsored by the U.S. Department of Defense
and operated by Carnegie Mellon University.
Copyright
2007
by Carnegie Mellon University
Terms of Use
URL: http://www.sei.cmu.edu/str/feedback/guide/guide.ch01.html
Last Modified: 11 January 2007
|
|
|
