Part of the Allyn & Bacon series in technical communication, Writing Software Documentation features a step-by-step strategy to writing and describing procedures.
This task-oriented book is designed to support both college students taking a course and professionals working in the field. Teaching apparatus includes complete programs for students to work on and a full set of project tracking forms, as well as a broad range of examples including Windows-style pages and screens and award-winning examples from STC competitions.
"Sobre este título" puede pertenecer a otra edición de este libro.
Descripción Prentice Hall. Estado de conservación: New. Brand New. Nº de ref. de la librería 0321103289
Descripción Pearson. PAPERBACK. Estado de conservación: New. 0321103289 New. Looks like an interesting title, learn more! We provide domestic tracking upon request. We provide personalized customer service and want you to have a great experience purchasing from us. 100% satisfaction guaranteed and thank you for your consideration. Nº de ref. de la librería S-0321103289
Descripción Longman, 2002. Paperback. Estado de conservación: New. book. Nº de ref. de la librería 0321103289
Descripción Longman Pub Group, 2002. Paperback. Estado de conservación: Brand New. 2nd edition. 468 pages. 9.50x6.00x1.00 inches. In Stock. Nº de ref. de la librería zk0321103289
Descripción Longman, 2002. Estado de conservación: New. Brand new! Please provide a physical shipping address. Nº de ref. de la librería 9780321103284
Descripción Pearson, 2002. Paperback. Estado de conservación: New. Nº de ref. de la librería P110321103289
Descripción Longman, 2002. Estado de conservación: New. Brand New, Unread Copy in Perfect Condition. A+ Customer Service! Summary: Each chapter begins with "Examples," and "Guidelines," and concludes "Glossary," "Checklist," and "Practice/Problem Solving" .1. Understanding Task Orientation. 1. Emphasize Problem-Solving. 2. Provide Task-Oriented Organization. 3. Encourage User Control of Information. 4. Orient Pages Semantically. 5. Facilitate Both Routine and Complex Tasks. 6. Design for Users. 7. Facilitate Communication Tasks. 8. Conducting Usability Tests. 9. Support Cognitive Processing.Discussion. The Principles of Software Documentation. A Definition of Task Orientation. The Theory Behind Task Orientation. Tutorial Documentation. Procedural Documentation. Reference Documentation. The Processes of Software Documentation. I. The Forms of Software Documentation. 2. Writing to TeachTutorials. 1. Identify User Actions You Need to Support. 2. State Objectives as Real-World Performance. 3. Choose the Right Type of Tutorial. 4. Present Skills in a Logical, Cumulative Structure. 5. Offer Highly Specific Instructions. 6. Give Practice and Feedback at Each Skill Level. 7. Test Your Tutorial.Discussion. Designing Tutorials. Tutorial Users Need Special Care. The Elaborative Approach. The Minimalist Approach.3. Writing to GuideProcedures. 1. Relate the Task to Meaningful Workplace Activities. 2. Determine How Much Information Your User Needs. 3. Choose the Appropriate Procedural Format. 4. Follow a Rhythm of Exposition. 5. Test All Procedures for Accuracy.Discussion. What Constitutes a Procedure? How Does a Procedure Work?4. Writing to SupportReference. 1. Choose the Right Form of Reference. 2. Decide What to Include. 3. Establish Pattern. 4. Organize the Reference Section. 5. Show How to Use the Reference Information.Discussion. Understanding the Reference User. Understanding a Reference Entry. II. The Process of Software Documentation. 5. Analyzing Your Users. 1. Choose Users Carefully. 2. Anticipate Transfer of Learning: Study Before and After Tasks. 3. Research Professional Behaviors. 4. Write User Cases. 5. Plan Interviews Carefully. 6. Involve Users in All Phases of the Project. 7. Identify Document Goals. 8. Tie the User Analysis to Documentation Features.Discussion What Does Use Mean? What You Want to Know About Users. Tasks the User Will Perform with the Program. The User's Informational Needs. The User's Work Motivations. Range of Computer Experience: Novice, Experienced, Expert. Extent of Knowledge of Subject Matter of the Program. The Workplace Environment: User Communities. Users' Learning Preferences. Usage Patterns: Regular, Casual, Intermittent.6. Planning and Writing Your Documents. 1. Start the Project. 2. Design the Documents. 3. Perform the User Analysis. 4. Plan the Documentation Project. 5. Write the Alpha Draft. 6. Conduct Reviews and Tests. 7. Revise and Edit. 8. Write a Final Draft. 9. Conduct a Field Evaluation.Discussion. Team Structures. Kinds of Development Documents. Processes. The Documentation Plan. Reviewing the Documentation Plan. An Outline for a Documentation Plan.7. Getting Useful Reviews. 1. Review the Document Objectives from the Documentation Plan. 2. Determine the Type of Review Needed. 3. Establish a Review Schedule. 4. Plan the Reviews. 5. Write a Cover Letter with Questions for Reviewers. 6. Prepare Feedback Materials for Reviewers.Discussion. Reviewing Differs from Testing. Reviewing Differs from Editing. The Purpose of Reviews. Reviewing t. Nº de ref. de la librería ABE_book_new_0321103289