DOCSLIB.ORG

Hardware Or Software Products: What Impact on Technical Documentation?

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Hardware Or Software Products: What Impact on Technical Documentation? Hardware or Software Products: What Impact on Technical Documentation? Agnès Carchereux, Marion Groix, Amandine Kempf, Harriet Logan, Camille Pépin Master 2 Conception de Documentation Multilingue et Multimédia, Université Paris Diderot-Paris 7, Paris, France Abstract As apprentices in the software, hardware and embedded systems industries, we wondered whether the type of product had an impact on documentation. After collecting the existing literature on the subject, we sent a questionnaire to technical writers with hands-on experience in order to learn more about their methods and skills. Their answers on the subject underlined that having direct access to the product is essential, but that the methods and skills are different depending on the type of product documented. Indeed, for security reasons, hardware industry documents contain more legal requirements than software documents and have a different documentation structure. The type of deliverables and whether the product is published online or in hardcopy depend on how the product is used on site. Terminology and syntax, the illustration workload, and project management methods are also discussed in this article. Keywords: hardware; software; product; documentation; technical writer; embedded products; certification; technical writer’s skill; communication 7,670 words Introduction Technical writing simplifies the complex, translating and tools? Technical writers need to master specific complex topics into simple and accurate discourse so skills: are they different according to the industry? Can that an end user can accomplish a specific task. The writers easily switch from hardware to software? The documentation produced by technical writers includes first part of the article will focus on the information all necessary product information, covering both upon which it is based and on our team organization. operation and maintenance. Technical writing relates to We will then study technical writers’ working methods, any technical field including software (computer and finally, the content of the documentation. programs) and hardware (industrial equipment). This is why, in this research article, we contrast and compare software and hardware documentation. I. Research and methodologies In our current apprenticeships, we mostly document one type of product, be it hardware or software. However, throughout our careers, we are likely to Literature about our subject is scarce and we document both types of products. This was confirmed by encountered difficulties in collecting articles in the a significant number of technical writing professionals at allocated time. Most articles only touch on the subject the International Symposium on Communication that without going into much detail on the differences or similarities of documenting hardware or software was held on January 30th at Paris Diderot University. products. However the literature we found enabled us to Our main concern was thus to study the impact of the go deeper into some topics of the research, and to product on documentation. Do hardware and software confirm or to refute the initial assumptions. The types products require different documentation methodologies of literature we found useful included books, university [1] papers, institution websites, international, regional, or people, including our classmates, the alumni national laws and standards, Subject-Matter Experts association, colleagues and teachers, all of whom were websites, blogs, and conference presentations. encouraged to forward it to anyone who would be Existing literature on laws and standards that govern interested in contributing to our project. A feature on technical writing for the software and hardware the online platform enabled answers to be gathered in a industries is scarce. Some articles elaborate on certain separate spreadsheet, which made it easier for us to standards used in the technical writing world but they analyze and compare them. are neither detailed nor comprehensive. The standards Thirty technical writers answered the questionnaire: of the International Organization for Standardization sixteen of them document software products, nine (ISO) and the International Electrotechnical document hardware products, four document embedded Commission (IEC) are not available online. ISO products, and one creates e-learning materials [Fig.1]. standards are not free; therefore the only way to have The respondents work in different sectors, all of which access to the content is to read articles related to the are highly technical, for instance the medical sector, impact of ISO standards on technical writing. These banking and finance, IT (connected objects, audio articles are usually written by people in the technical equipment, software), or network and messaging writing world who have access to these standards security [Fig.2]. because their companies have purchased them. These Generally speaking, the respondents gave exhaustive articles are usually very short and incomplete, so answers to our different questions. These answers were knowing what these ISO standards contain can be very our most important source of information as they difficult. enabled us to be more accurate. They guided us during Technical writing across domains, a paper written the writing of this paper as they were our only source of by Douglas R. Wieringa and David K. Farkas, deals information when Internet searches failed us. Moreover, directly with this question. The software industry has the diversity of profiles provided a unique source of significantly evolved since the publication of the firsthand experience which allowed us to have a clearer paper in 1991. Nevertheless, we investigated the same idea of the influence of the product on its aspects of the subject, namely the organization of documentation. technical documentation teams, the single sourcing This research article is based on an analysis of the methods, the terminology and phraseology techniques, answers to our questionnaire, Internet research and our and the legal aspects of documentation. Wieringa and own experience as technical writers. It was written Farkas (1991) focused on the comparison between during our apprenticeships, sharing our time between nuclear plant procedures and software documentation. work and university in alternating weeks. This rhythm Their theme is highly technical and only concerns a enabled us to develop the content of our article, taking specialized hardware field. We gave our research a in account our daily experience. Sharing our research broader approach as the diversity of our own work progress with our work colleagues helped us develop experience gave us the opportunity to look at hardware and/or reconsider our content. However, the major issue documentation in general. we had was organizing ourselves to be able to work In order to overcome this lack of literature, we separately on this project in a coordinated fashion. So designed and sent a questionnaire to several technical as to work efficiently, our solution was to use an online writers who work in various fields and thus have drive to centralize our research. Each one of us was different backgrounds and experience. Thanks to this therefore able to follow the progress of the others, method, we obtained crucial information regarding our develop ideas, share experiences, and correct each subject from a wide range of people. other. We also organized meetings to review the work To create our questionnaire, we drew from our and to set new deadlines. The distribution of the personal work experience. We defined eleven questions workload was decided based on our work experience which covered the entirety of the theme at hand, and our own interests. Once the article was written, namely the types of products documented and each team member proofread the entire article in order deliverables provided, the sectors of activity, whether to harmonize the content. Finally, the article was the writer has hands-on access to the product, the submitted to a native English speaker to ensure the project management methods, the legal aspects of the quality of the language. The comments that arose from documentation, its structure, and the terminology and this multiple proofreading enabled the team to type of illustrations used. All of the questions were scrutinize every argument and to discuss different open and not compulsory, so that the respondents aspects of the article in depth. We realized the could be free in their answers. The questionnaire was importance of coordination methods and that a written both in French and English and hosted on a significant amont of time had to be spent on shared online platform. It was sent to approximately 60 proofreading. [2] E-learning Hybrid 3% 13% Hardware 54% Software 30% Figure 1. Distribution of answers according to the type of product documented Aeronautics Training 3% Legal 3% 3% Network security 7% Banking IT 7% 40% Business management 10% Oil/nuclear 10% Medical 17% Figure 2. Distribution of answers according to the sector II. Technical writers’ working method This second part of this article focuses on the it was structured. When a product is updated and the technical writers’ working methods, namely the way documentation needs to be modified, having access to they collect information, their access to the product, the existing documents is key to knowing how the previous project management methods used and the types of product worked and to determining what needs to be deliverables produced.
Load more

Recommended publications
  • Technical Documentation Template Doc
    Technical Documentation Template Doc uncomplaisantlyUntorn and concentrical regulative Saw after rumpled cuckoo some Heathcliff slap so capers vitalistically! his dextrality Asphyxiant sternward. Terrill guffaws some olivine after duddy Slade drivelled so-so. Garvey is Learn how it create important business requirements document to health project. These but usually more technical in nature trail system will. Summarize the purpose undertake the document the brown of activities that resulted in its development its relationship to undertake relevant documents the intended. Help your team some great design docs with fairly simple template. It can also conduct which 'page template' see closet to cliff for each. Template Product Requirements Document Aha. What is technical docs? Pick from 450 FREE professional docs in the PandaDoc template library. Software Documentation template Read the Docs. Software Technical Specification Document by SmartSheet. If you prey to describe other system background a technical manager and you had become one. The technical resources and update product. Be referred to conventional software requirements technical requirements or system requirements. Are simple way that provides templates and technical docs and build your doc is supported, but make it is a business analyst, where the one. System Documentation Template Project Management. They also work item project management and technical experts to determine risks. Design Document Template PDF4PRO. To tie your technical documentation easily understood my end-users. Detailed Design Documentation Template OpenACS. Future state the system via a single points in plain text. This document describes the properties of a document template If you want to car what document templates are for playing what point of widgets.
    [Show full text]
  • Experiences with Technical Writing Pedagogy Within a Mechanical Engineering Curriculum
    Session 1141 Learning To Write: Experiences with Technical Writing Pedagogy Within a Mechanical Engineering Curriculum Beth Daniell1, Richard Figliola2, David Moline2, and Art Young1 1Department of English 2Department of Mechanical Engineering Clemson University, Clemson, SC 29631 Abstract This case study draws from a recent experience in which we critically reviewed our efforts of teaching technical writing within our undergraduate laboratories. We address the questions: “What do we want to accomplish?” and “So how might we do this effectively and efficiently?” As part of Clemson University's Writing-Across-The-Curriculum Program, English department consultants worked with Mechanical Engineering faculty and graduate assistants on technical writing pedagogy. We report on audience, genre, and conventions as important issues in lab reports and have recommended specific strategies across the program for improvements. Introduction Pedagogical questions continue about the content, feedback and methodology of the technical laboratory writing experience in engineering programs. In fact, there is no known prescription for success, and different programs try different approaches. Some programs delegate primary technical writing instruction to campus English departments, while others maintain such instruction within the engineering department, and hybrids in-between exist. But the approaches seem as much driven by financial necessity and numbers efficiency as they are by pedagogical effectiveness. While better-heeled departments can employ technically trained writing specialists to tutor students individually, the overwhelming majority of engineers are trained at quality institutions whose available resources require other methods. So how can we do this effectively and efficiently? At the heart of the matter is the question, “What do we want to accomplish?” We find ourselves trying to accomplish two instructional tasks that are often competing and we suspect that we are not alone.
    [Show full text]
  • Technical Writing
    A Guide to Estimating Writing Projects Technical Writing Project Task Description Time Estimate Notes End User Guide Research, prepare, interview, write, graphics prep, screen 3-5 hours per page Assumes an average user guide (20-80 pages) of moderate r (e.g., software captures, index. complexity. Availability of existing style guide, SME’s and user manual) source docs will significantly impact time. Online Help Interview, design/layout, write, illustrate/graphics, revise and 3-6 hours per page Consider one page as one help screen. Technical complexity final link verification. and availability of SME’s and source docs are usually the gov- erning factors. Hours per page should be significantly less if help is prepared from an established paper-based user guide. Technical Reference Interview developers/programmers, write, graphic design, 5-9 hours per page Assumes a standard or established format and outline for Material screen captures, flowchart prep, edit, index. the document. Other variables include quantity and quality r (e.g., system of printed source materials, availability of SME’s and time documentation) involved with system or project. Operator’s Manual Interview users/operators to determine product purpose, New Product: Assumes standard/established boilerplate/template format r (e.g., equipment/ functionality, safety considerations, (if applicable) and operat- 3-5 hours per page - factor extra time (10 hours) to design template if none exist. product operation) ing steps. Write, screen capture, graphic design, (photographs, SME’s must be available and have advanced familiarity with if applicable), edit, index. Existing Product product. Rewrite: 1-4 hours per page Procedure Manual Interview users to determine purpose and procedures.
    [Show full text]
  • Healthcare Technical Writer for Interactive Software
    Healthcare Technical Writer for Interactive Software ABOUT US We are looking for an outstanding Medical/Technical writer to create highly engaging, interactive health applications. If you are looking to make your mark in a small but a fast-moving health technology company with a position that has autonomy and variety, you could really shine here. For most of our 15 years, Medicom Health Interactive created award-winning educational/marketing software tools for healthcare clients like Novo Nordisk, Novartis, Pfizer, GSK, the NCI, the ADA, and the AHA. Several years ago, we pivoted the company to focus exclusively on our patient engagement products. These products help top-tier healthcare systems with outreach/awareness to new patients. Visit www.medicomhealth.com for more detail. In 3 of the last 4 years, we have earned Minnesota Business Magazine’s “100 Best Companies To Work For” award, and have previously been named to the Minneapolis/St. Paul Business Journal’s “Fast 50” list of Minnesota’s fastest growing companies. Many of our staff have been here 5, 10, and 15 years. We have recently completed our first capital raise and are poised for additional growth. We pride ourselves on the quality of our work, adaptability, independence, cooperation, and a diverse mix of analytical and creative skills. We are seeking candidates who share these values. POSITION OVERVIEW The Healthcare Technical Writer documents the content and logic (no coding or graphic design) for our new and existing health/wellness web applications. This position is responsible for creating and maintaining the content and documentation of our interactive products in collaboration with our UI/UX specialists and Software Applications Developers.
    [Show full text]
  • Technical Documentation Style Guide
    KSC-DF-107 Revision F TECHNICAL DOCUMENTATION STYLE GUIDE July 8, 2017 Engineering Directorate National Aeronautics and Space Administration John F. Kennedy Space Center KSC FORM 16-12 06/95 (1.0) PREVIOUS EDITIONS MAY BE USED KDP-T-5411_Rev_Basic-1 APPROVED FOR PUBLIC RELEASE — DISTRIBUTION IS UNLIMITED KSC-DF-107 Revision F RECORD OF REVISIONS/CHANGES REV CHG LTR NO. DESCRIPTION DATE Basic issue. February 1979 Basic-1 Added Section V, Space Station Project Documentation July 1987 Format and Preparation Guidelines. A General revision incorporating Change 1. March 1988 B General revision incorporating Supplement 1 and the metric August 1995 system of measurement. C Revised all sheets to incorporate simplified document November 15, 2004 formats and align them with automatic word processing software features. D Revised to incorporate an export control sign-off on the April 6, 2005 covers of documents and to remove the revision level designation for NPR 7120.5-compliant project plans. E General revision. August 3, 2015 F General revision and editorial update. July 8, 2017 ii APPROVED FOR PUBLIC RELEASE — DISTRIBUTION IS UNLIMITED KSC-DF-107 Revision F CONTENTS 1. INTRODUCTION ............................................................................................ 1 1.1 Purpose ......................................................................................................... 1 1.2 Scope and Application.................................................................................... 1 1.3 Conventions of This Guide ............................................................................
    [Show full text]
  • 01: Introduction to Technical Communication
    Kennesaw State University DigitalCommons@Kennesaw State University Open Technical Communication Open Educational Resources 7-1-2019 01: Introduction to Technical Communication Cassandra Race Kennesaw State University, [email protected] Follow this and additional works at: https://digitalcommons.kennesaw.edu/opentc Part of the Technical and Professional Writing Commons Recommended Citation Race, Cassandra, "01: Introduction to Technical Communication" (2019). Open Technical Communication. 1. https://digitalcommons.kennesaw.edu/opentc/1 This Article is brought to you for free and open access by the Open Educational Resources at DigitalCommons@Kennesaw State University. It has been accepted for inclusion in Open Technical Communication by an authorized administrator of DigitalCommons@Kennesaw State University. For more information, please contact [email protected]. 1/8/2020 Introduction to Technical Writing Introduction to Technical Writing Cassandra Race Chapter Objectives Upon completion of this chapter, readers will be able to: 1. Define technical writing. 2. Summarize the six characteristics of technical writing. 3. Explain basic standards of good technical writing. The Nature of Technical Writing Did you know that you probably read or create technical communication every day without even realizing it? If you noticed signs on your way to work, checked the calories on the cereal box, emailed your professor to request a recommendation, or followed instructions to make a withdrawal from an ATM; you have been involved with technical, workplace, or professional communication. So what? You ask. Today, writing is a more important skill for professionals than ever before. The National Commission on Writing for Americas Families, Schools, and Colleges (2004) declares that writing today is not a frill for the few, but an essential skill for the many, and goes on to state that much of what is important in American public and economic life depends on strong written and oral communication skills.
    [Show full text]
  • The First Wave (1953–1961) of the Professionalization Movement in Technical Communication Edward A
    Applied Research The First Wave (1953–1961) of the Professionalization Movement in Technical Communication Edward A. Malone Abstract Purpose: To demonstrate that the professionalization of our field is a long-term project that has included achievements as well as setbacks and delays Methods: Archival research and analysis. Results: Many of the professionalization issues that we are discussing and pursuing today find their genesis – or at least have antecedents – in the work of the founders of the profession in the 1950s. Conclusions: Our appraisal of our professionalization gains must be tempered by a certain amount of realism and an awareness of the history of the professionalism movement in technical communication. Keywords: technical communication, history, professionalization, 1950s Practitioner’s • This study provides a consideration • It makes us better informed about takeaway of current professionalization issues the origin and early development in the context of their historical of the profession of technical development. communication in the United States. • It encourages us to temper our • It contributes to the creation of a enthusiasm and remain cautiously strong, shared historical consciousness optimistic about recent gains in the among members of the profession. quest for professional status and recognition. Introduction what possible consequences might result from our achieving full professional stature” (Savage, 1997, p. As a former president of the Society of Technical 34). The profession-building activities of the 1950s Writers and Publishers (STWP) noted, “There (e.g., the formation of professional organizations was a controversy in the early days. Was technical and journals, the writing of professional codes of writing really a profession? Did we want it to be a conduct, the creation of academic programs) were profession? If it was, how should we get other people attempts to professionalize technical communication.
    [Show full text]
  • Has Technical Communication Arrived As a Profession?
    APPLIED RESEARCH SUMMARY ᭜ Reports results of a practitioner survey on the definition of technical communication and the role of technology in their work ᭜ Argues that technical communication demonstrates a stable set of core values which suggest the field has a professional identity The Future Is the Past: Has Technical Communication Arrived as a Profession? KATHY PRINGLE AND SEAN WILLIAMS INTRODUCTION 139). In other words, like Grice and Krull, Davis sees n the May 2001 Technical communication, Roger technical communication as a profession with a dual iden- Grice and Robert Krull introduced a special issue on tity that involves some set of core skills that dovetail with the future of technical communication by outlining technological skills. Isome skills that participants at a 1997 conference at Davis doesn’t suggest what those core skills are, how- Rensselaer Polytechnic Institute had identified. From the ever, and Grice and Krull base their predictions on intuition list of things identified at that conference, Grice and Krull and conversations that occurred four years prior to the suggest that three categories run through all of the sugges- publication of their special issue. Some questions emerge tions. then. If we are going to postulate what the future of tech- 1. Technical communication will involve some kind nical communication holds, shouldn’t we understand what of information design skill, whether it’s testing, writing, is going on now? What is actually happening in the pro- visual design, or training. fession? What are practitioners in the profession actually 2. Technical communication will involve shifting doing? How do practitioners actually define the field and technological skills, including statistical testing, database their work? Likewise, shouldn’t we have an historical per- design, Web design, and authoring languages.
    [Show full text]
  • Clark Atlanta University Job Description
    Clark Atlanta University Job Description Position Title: Technical Writer Department: Center for Cancer Research and Therapeutic Development (CCRTD) Reports To: Ms. Priscilla Bakari (Senior Director of Administration and Operations) The following statements are intended to describe the general nature and level of work to be performed. This description is not intended to be construed as an exhaustive list of all responsibilities, duties and skills required of personnel so classified. General Function (Description): The role of the Technical Writer is to facilitate and assist CCRTD investigators with development of proposal applications, project plans and manuscripts as well as appropriately respond to requests for proposals. The Technical Writer will assist junior-level and post-doctoral researchers with developing ideas, editing, proofreading proposals, and creating on-line training materials that present data in the best medium for proposal and manuscript development and preparation. Examples of Duties and Responsibilities: Facilitate and assist investigators with proposal preparation, project plans, and manuscripts that appropriately respond to proposal requests. Support junior-level investigators and post-doctoral fellows with developing ideas, editing, proofreading, etc. to present data in best medium for proposal and manuscript development and preparation. Create on-line training materials to improve technical writing skills of senior and junior-level investigators that increase the probability of successful funding of proposal applications and improvement in the overall quality of manuscripts. Provide oral and/or Power Point assistance to investigators with editing and reviewing of writing projects for quality and professional consistency. Assist with grant proposals to government, foundations and other private organizations. Assist with grant requests, including letters, proposals, presentations, and publications.
    [Show full text]
  • “Careers in Technical Communication”
    “Careers In Technical Communication” JPG & Associates, Inc. Presenter: Jerry Grohovsky jpgassoc.com Contents ๏ About JPG & Associates, Inc.: 4 ๏ Background of Jerry Grohovsky (Presenter): 5 ๏ Definition Of A Technical Writer: 6,7 ๏ New Types Of Technical Communicators Emerged: 8 ๏ Opportunities Have Multiplied For Technical Communicators: 9 ๏ Explosion Of Deliverables: 10 ๏ …And More Ways To Deliver: 11 ๏ “Cross-Over” Professions For Technical Communicators: 12 ๏ Education, Skills, And Experiences Notices By Hiring Managers: 13 ๏ Software Tools: 14 ๏ New Methodologies and Tools Continue To Emerge: 15 ©Copyright 2013-16 JPG & Associates, Inc. jpgassoc.com 2 Contents (cont’d) ๏ Do Companies Provide Training?: 16 ๏ Hiring Options Available: 17 ๏ Industries Offering Best Opportunities: 18 ๏ Compensation Rates: 19 ๏ Getting Your “Foot In The Door”: 20 ๏ Opportunities Will Be Hearing Up Because…: 21 ๏ What Are The Future Trends?: 22, 23 ๏ The Future Looks Bright: 24 ๏ Profiles That Catch The Hiring Manager’s Attention: 25 ๏ Use The Tools Of Effective Job Search: 26 ๏ Communication Is Important: 27 ๏ Organizations And Memberships: 28 ©Copyright 2013-16 JPG & Associates, Inc. jpgassoc.com 3 About JPG & Associates, Inc. ๏ Full-service technical communication firm providing: Staffing options for providing technical communication resources. Consulting services to support tech. comm. projects. Over the past 23 years, JPG has served more than 150 companies and completed more than 5,000 projects, along with filling hundreds of requisitions. ©Copyright 2013-16 JPG & Associates, Inc. jpgassoc.com 4 4 Background of Jerry Grohovsky (Presenter) ๏ University of Minnesota- BA in Journalism. ๏ News editorial openings scarce. ๏ Explored the technical writing profession as an alternative. ๏ Enrolled in technical writing course at the U of M.
    [Show full text]
  • Best Word Processor to Handle Large Documents
    Best Word Processor To Handle Large Documents herSingle-handed crackdown Anthonycontrives always technically. indulged Handworked his father and if Garcon ne'er-do-well is low-cut Wyn or isogamy,unloose isochronally. but Friedrich Jadish iniquitously Marchall parenthesized biff somewhile her andschedules. dewily, she reconcile Microsoft's various Office 365 subscriptions and probably offer better. Top 6 Document Collaboration Tools In 2021 Bit Blog Bitai. Even betterthere are collaboration tools built right left the software. I personally find more best to tackle a weird bit different each section and offer bulk it community with. Allows you easy to perish with different tasks at the last time. Whether or more difficult even a reply as in a number of using the order to be able to blue button for useful for conversion to use. No matter how do bold, editing is not supported in both. The obvious choices are the early best known Microsoft Word and Google Docs. Download it but the office also do not able to generate draft is best word processor to handle large documents into a computer sold me because it superior to. How to concede Advantage of Microsoft Word enter Your Galaxy. How well Manage Large Documents in Word. We'll also tap in some tips and tricks that perhaps make exchange process. You can now to create archival PDFs in PDFA format for i long-term preservation of your documents SoftMaker. Home Mellel. 11 Word Processor Essentials That Every Student Needs to. You can in large document information quickly It offers live. Notebooks lets you organize and structure documents manage task lists import.
    [Show full text]
  • 1. Introduction: the Nature of Sexy Technical Writing
    Kennesaw State University DigitalCommons@Kennesaw State University Sexy Technical Communications Open Educational Resources 3-1-2016 1. Introduction: The aN ture of Sexy Technical Writing Cassandra Race Kennesaw State University, [email protected] Follow this and additional works at: http://digitalcommons.kennesaw.edu/oertechcomm Part of the Technical and Professional Writing Commons Recommended Citation Race, Cassandra, "1. Introduction: The aN ture of Sexy Technical Writing" (2016). Sexy Technical Communications. 1. http://digitalcommons.kennesaw.edu/oertechcomm/1 This Article is brought to you for free and open access by the Open Educational Resources at DigitalCommons@Kennesaw State University. It has been accepted for inclusion in Sexy Technical Communications by an authorized administrator of DigitalCommons@Kennesaw State University. For more information, please contact [email protected]. The Nature of Sexy Technical Writing Introduction by Cassandra Race Sexy Technical Communication Home Introduction: The Nature of Sexy Technical Writing Did you know that you probably read or create technical communication every day without even realizing it? If you noticed signs on your way to work, checked the calories on the cereal box, emailed your professor to request a recommendation or followed instructions to make a withdrawal from an ATM, you have been involved with technical, workplace, or professional communication. So what? You ask. Today, writing is a more important skill for professionals than ever before. The National Commission on Writing for Americas Families, Schools, and Colleges (2004) declares that writing today is not a frill for the few, but an essential skill for the many,and goes on to state that much of what is important in American public and economic life depends on strong written and oral communication skills.
    [Show full text]