<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>NASA</title>	<link>http://tc.eserver.org/publisher/NASA</link>
	<description>A listing of works published by NASA in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>NASA</title>
		<link>http://tc.eserver.org/dir/NASA</link>
	</image>
	<item>
		<title>Criteria for Focused Data Collection</title>
		<link>http://tc.eserver.org/27491.html</link>
		<guid>http://tc.eserver.org/27491.html</guid>
		<description>The objective of this task is to propose and validate a mechanism whereby projects can identify their needs for software measurement data and focus their data collection activities using a minimum standardized set of software measures. The purpose of this strategy is to evolve a process that will enable NASA projects to tailor with their data collection activities to their unique needs for effective management control indicators, but also encourages consistent data collection that will facilitate statistical analysis across NASA domains.</description>
	</item>
	<item>
		<title>Writing Effective Requirements Specifications</title>
		<link>http://tc.eserver.org/27450.html</link>
		<guid>http://tc.eserver.org/27450.html</guid>
		<description>The Goddard Space Flight Center&apos;s (GSFC) Software Assurance Technology Center (SATC) has developed an early life cycle tool for assessing requirements that are specified in natural language. The Automated Requirements Measurement (ARM) tool was used to analyze more than 50 NASA System/Software Requirements Specification (SRS) documents. ARM reports were used to focus human analysis on specific aspects of the documentation practices exhibited by these documents. Several significant weaknesses were identified. This paper identifies the underlying problems that produce these deficiencies and recommends methods that can be used to prevent such problems.</description>
	</item>
	<item>
		<title>The Goddard Library: Writing and Presenting</title>
		<link>http://tc.eserver.org/18411.html</link>
		<guid>http://tc.eserver.org/18411.html</guid>
		<description>This Subject Guide is intended to provide pointers to references and information resources which should be helpful to anyone involved in writing scientific journal articles and papers, technical reports, or other technical documentation, or in preparing conference presentations and poster sessions. </description>
	</item>
	<item>
		<title>NASA Guide to Grammar, Punctuation, and Capitalization:  A Handbook for Technical Writers and Editors</title>
		<link>http://tc.eserver.org/14189.html</link>
		<guid>http://tc.eserver.org/14189.html</guid>
		<description>This publication is directed toward professional writers, editors, and proofreaders. Those whose profession lies in other areas (for example, research or management), but who have occasion to write or review others&apos; writing will also find this information useful. By carefully studying the examples and revisions to these examples, you can discern most of the techniques in my editing &apos;bag of tricks&apos;; I hope that you editors will find these of particular interest.</description>
	</item>
	<atom:link href="http://tc.eserver.org/publisher/NASA.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>