<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Le Vie, Donald S., Jr</title>	<link>http://tc.eserver.org/authors/Le_Vie,_Donald_S.,_Jr</link>
	<description>A bibliography of works by Le Vie, Donald S., Jr 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>Le Vie, Donald S., Jr</title>
		<link>http://tc.eserver.org/dir/Le_Vie,_Donald_S.,_Jr</link>
	</image>
	<item>
		<title>Writing Software Requirements Specifications</title>
		<link>http://tc.eserver.org/27447.html</link>
		<guid>http://tc.eserver.org/27447.html</guid>
		<description> For technical writers who haven&apos;t had the experience of designing software requirements specifications (SRSs, also known as software functional specifications or system specifications) templates or even writing SRSs, they might assume that being given the opportunity to do so is either a reward or punishment for something they did (or failed to do) on a previous project. Actually, SRSs are ideal projects for technical writers to be involved with because they lay out the foundation for the development of a new product and for the types of user documentation and media that will be required later in the project development life cycle. It also doesn&apos;t hurt that you&apos;d be playing a visible role in contributing to the success of the project.</description>
	</item>
	<item>
		<title>Developing a Project Life Cycle for Technical Publications</title>
		<link>http://tc.eserver.org/23643.html</link>
		<guid>http://tc.eserver.org/23643.html</guid>
		<description>Having a technical publications project life cycle (pLC) that parallels an organization&apos;s product life cycle (PLC) greatly facilitates its adoption by engineering or development organizations. A technical publications project life cycle&#xD;relates major documentation project management&#xD;strategies, tasks, and deliverables to the same model used&#xD;by technical organizations to control product development&#xD;in an efficient and cost-effective manner. Some technical&#xD;organizations perceive the documentation development&#xD;process as being “intrusive” into the product development&#xD;process, particularly during the Implementation Phase of&#xD;the PLC. Communicating a technical publications pLC to&#xD;these organizations early in the PLC eliminates this&#xD;misperception.</description>
	</item>
	<item>
		<title>Contracting: Flat Fee or Hourly Rates?</title>
		<link>http://tc.eserver.org/15101.html</link>
		<guid>http://tc.eserver.org/15101.html</guid>
		<description>Recommends that technical writers working as independent contractors quote flat fees for projects instead of hourly rates. The article offers tips on preparing portfolios and conducting client interviews.</description>
	</item>
	<item>
		<title>Documentation Metrics: What Do You Really Want to Measure?</title>
		<link>http://tc.eserver.org/15117.html</link>
		<guid>http://tc.eserver.org/15117.html</guid>
		<description>Examines several metrics--systems for measuring production and production standards--to determine their value to technical communicators.  He argues that qualitative metrics are more meaningful than quantitative ones.</description>
	</item>
	<item>
		<title>Internet Technology and Intellectual Property</title>
		<link>http://tc.eserver.org/15147.html</link>
		<guid>http://tc.eserver.org/15147.html</guid>
		<description>This article outlines the complex legal environment surrounding the Internet, copyright law, and intellectual property. </description>
	</item>
	<item>
		<title>Resumes: You Can&apos;t Escape</title>
		<link>http://tc.eserver.org/15185.html</link>
		<guid>http://tc.eserver.org/15185.html</guid>
		<description>Lists ten common mistakes in resumes and ten suggestions for improvement based on his experience as a hiring manager. The article includes a sidebar on how to write effective cover letters.</description>
	</item>
	<item>
		<title>What&apos;s the Value of Technical Communication?</title>
		<link>http://tc.eserver.org/14964.html</link>
		<guid>http://tc.eserver.org/14964.html</guid>
		<description>Unlike many other professions, our work products rarely stand by themselves. The work product of an engineering team may be a new pager or PDA; the work product of a development team may be a general-market software application. Data sheets, programmers reference manuals, and microprocessor design guides don&apos;t have their own standalone markets. They are designed and produced specifically for supporting standalone products. Their value, therefore, lies in how well they serve as a conduit for transferring and translating knowledge about the product to customers or end users according to their requirements.</description>
	</item>
	<item>
		<title>An eCommerce Primer for Technical Communicators</title>
		<link>http://tc.eserver.org/13293.html</link>
		<guid>http://tc.eserver.org/13293.html</guid>
		<description>The burgeoning eCommerce industry has redefined not only traditional business processes, but the technology required to impart them. Roles are being created or redefined, where programmers, systems analysts, and engineers now have to have almost as much knowledge of business process development as they do of their technical specialty. The same can be said for technical communicators. Technical communicators involved in eCommerce today need to have an understanding of the major issues involved in eCommerce. This paper&#xD;addresses five of these major eCommerce areas: the&#xD;statistics behind eCommerce issues, eCommerce&#xD;infrastructure providers, managed electronic commerce,&#xD;business object technology, and data mining.&#xD;</description>
	</item>
	<item>
		<title>Understanding Data Flow Diagrams</title>
		<link>http://tc.eserver.org/13204.html</link>
		<guid>http://tc.eserver.org/13204.html</guid>
		<description>Data flow diagrams (DFDs) reveal relationships among and between the various components in a program or system.</description>
	</item>
	<item>
		<title>Using JavaScript to Develop Interactive Self-Assessments</title>
		<link>http://tc.eserver.org/13172.html</link>
		<guid>http://tc.eserver.org/13172.html</guid>
		<description>Interactive self-assessments are effective tools for a&#xD;variety of audiences; from determining one’s Myers-&#xD;Briggs Type Indicator (MBTI) or personality&#xD;characteristics to self-scoring quizzes of all types for&#xD;online training. Many Web sites contain such selfassessments&#xD;that help customers select from among other&#xD;offerings the type of product or service that meets their&#xD;requirements. The strategic design and development of&#xD;interactive self-assessments can also help steer customers&#xD;to your specific product line or service, or even help them&#xD;make the decision to buy or award a contract. This paper&#xD;looks at the effectiveness of self-assessments as a business&#xD;tool and the use of JavaScript for supporting the&#xD;interactive elements.&#xD;</description>
	</item>
	<item>
		<title>Writing Killer eCommerce/IT Proposals that Win New Business</title>
		<link>http://tc.eserver.org/13157.html</link>
		<guid>http://tc.eserver.org/13157.html</guid>
		<description>Winning new eCommerce/IT business depends on many&#xD;factors, not the least of which is a requirements-focused,&#xD;bloat-free proposal that prospects and customers will&#xD;read. But to get to that point, proposal development must&#xD;be tied to a business development process that will guide&#xD;a qualified opportunity toward becoming a business&#xD;proposal, and ultimately, a sustainable or repeatable&#xD;business deal. Before committing resources to proposal&#xD;development, a Needs Analysis/Return on Investment&#xD;(ROI) study (billable service) for the prospect or&#xD;customer should be necessary. Such a study not only&#xD;shows the prospect how well your organization knows its&#xD;business, it helps steer a prospect to your organization’s&#xD;process. The Needs Analysis/ROI study results provide a&#xD;head start on proposal development, where the proposal&#xD;turnaround time can be as short as one day.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Le_Vie,_Donald_S.,_Jr.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>