IEEE P1603 reviewer’s guideline Wolfgang Roethig, WG chair.

Slides:

Advertisements

Similar presentations

Doc.: IEEE /0564r0 Submission May 2014 Marc Emmelmann, SelfSlide 1 Results of LB 201 on TGai D2.0 Date: Authors:

Advertisements

Jump to first page ©2003, Darby Dickerson. License given for educational use. Cite & Source Steps and Strategies.

The Systems Analysis Toolkit

Chapter 12 – Strategies for Effective Written Reports

McGraw-Hill/Irwin © 2009 The McGraw-Hill Companies, All Rights Reserved.

Lecture 7 Loose Ends. Quality Both the experimental plan and final report must be professional quality! Nothing should be hand written! Correct grammar.

IMS Systems Analysis and Design Communication and Documentation: Additional Notes on Written Reports.

Technical Writing II Acknowledgement: –This lecture notes are based on many on-line documents. –I would like to thank these authors who make the documents.

Editing, Peer-Reviewing and Team-Writing Editing isn’t a cosmetic process. It’s a thinking process. Richard Rhodes, author Making of the Atomic Bomb.

CSE Information Systems 1 Communication and Documentation: Additional Notes on Written Reports.

CSE Information Systems 1 Communication and Documentation: Additional Notes on Written Reports.

Basic Scientific Writing in English Lecture 3 Professor Ralph Kirby Faculty of Life Sciences Extension 7323 Room B322.

Systems Analysis & Design Sixth Edition Systems Analysis & Design Sixth Edition Toolkit Part 1.

Grant Proposal Preparation Topic Hypotheses Subject Organization Evaluation Searching for articles.

Human Services Practicum

Slide #1 Writing Winning Proposals. Slide #2 Agenda  Overview  Writing Tips  Comments, Suggestions, Questions  Upcoming Seminars.

Writing Reports Ian McCrum Material from

Business Memo purpose of writer needs of reader Memos solve problems

An Introduction to Content Management. By the end of the session you will be able to... Explain what a content management system is Apply the principles.

Writing Across the Curriculum Collins’ Writing. To develop successful, life-long writers, students must have: Opportunities to: write in many environments.

 Jennifer Sadowski & Kaati Schreier May 30, 2012.

To navigate the slide presentation, use the navigation bar on the left OR use your right and left arrow keys. Move your mouse over the key terms throughout.

Differences and similarities with informal and formal reports

Chapter 13– Strategies for Effective Oral Presentations The goal of the presentation is to communicate, clearly and concisely, the results and implications.

EE LECTURE 4 REPORT STRUCTURE AND COMPONENTS Electrical Engineering Dept King Saud University.

COMP 465W Software Engineering Fall Components of the Course The three main components of this course are: The study of software engineering as.

Business Correspondence: Letters, Memos, and s

NETIQUETTE GUIDELINES FOR DISTANCE EDUCATION COURSES.

What is Peer Editing? A peer is someone your own age. Editing means making suggestions, comments, compliments, and changes to writing.  Peer editing.

Report Writing. Table of contents Your report should include a table of contents if longer than about 5-10 pages. This allows the reader to quickly find.

Being an Effective Peer Reviewer Barbara Gastel, MD, MPH Texas A&M University

 You will be editing a research paper.  During each step in this process, it is important that you follow the directions accurately.  Please make sure.

Ian F. C. Smith Writing a Conference Paper. 2 Disclaimer This is mostly opinion. Suggestions are incomplete. There are other strategies.

DMD Senior Design Projects CIS 497 Joseph T. Kider Jr.

ECOS Information Session Draft EPA Quality Documents February 13, 2013 Presented by EPA Quality Staff, Office of Environmental Information For meeting.

Organizing Your Information Chapter 7. Chapter 7 Contents Understanding Three Principles for Organizing Technical Information Using Basic Organizational.

Written Presentations of Technical Subject Writing Guide vs. Term paper Writing style: specifics Editing Refereeing.

To be completed Your proposal  Your House style  Your site plan  Page plans (a draft layout for each of your five pages)  A design mock-up -  All.

3 Steps to Peer Editing There are three important steps to remember when you are peer editing another student’s writing. Step 1 – Compliments Step 2 –

1 Technical Communication A Reader-Centred Approach First Canadian Edition Paul V. Anderson Kerry Surman

ERROR CORRECTION. How to respond calm calm consistent consistent brief brief and respectful and respectful.

Internet Safety Guidelines for Using the Internet By: Mrs. Aquilino.

Technical Writing: An Editor’s Perspective Michael K. Lindell Hazard Reduction & Recovery Center Texas A&M University.

The Writing Process USING THE STRATEGIES OF EXPERIENCED WRITERS COPYRIGHT LISA MCNEILLEY, 2010.

Workshop Overview What is a report? Sections of a report Report-Writing Tips.

Sub Committee 6 Ballot resolution Summary June 2012 Mike Briggs.

By: Wilmer Arellano FIU Summer Overview s Introduction to Proposal Style General Recommendations ▫Section Headings ▫References Title Page.

Copyright © 2015 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior written consent of McGraw-Hill Education.

Creating a Great Presentation Jody Student February 1, 2006.

Doc.: IEEE /xxxxr0 Submission July 2007 Terry Cole, AMDSlide Common Editorial Comment Resolution Process Date: Authors:

Doc.: IEEE /320R0 Submission May 2003 Terry Cole, AMDSlide SDL Amendments Terry Cole, AMD WG Technical Editor.

REPORT STYLE. A reader of a successful report should: Understand it without effort. Accept the facts, findings, conclusions and recommendations. Decide.

Minutes Document March 2006 Terry Cole, AMDSlide Editor’s Best Practices Terry Cole, AMD WG Technical Editor & Simon Barber, Devicescape.

Systems Analysis & Design 7 th Edition Systems Analysis & Design 7 th Edition Toolkit 1.

How to get a paper published Derek Eamus Department of Environmental Sciences.

Fall CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Senior Design Lecture 7 Functional specifications Technical meetings.

Learning Outcome 01 : Be able to design interactive products Unit R005: Creating an interactive product using multimedia components Cambridge Nationals.

Doc.: IEEE a Submission Sept 2004 Tom Siep, TMS Assoicates, LLCSlide 1 Project: IEEE P Working Group for Wireless Personal.

Skilled performances look easy and effortless

Document Development Cycle

Report Writing Three phases of report writing Exploratory phase (MAPS)

Editor’s Guideline Version 1.0

HUM 102 Report Writing Skills

IETF68 Mini-BOF MIB-Doctor-Sponsored MIB Document Templates

A01 DESIGN To be completed Your proposal  Your House style 

Procedural review of initial WG ballot on P802.1CF

Paper Expectations PSY 475.

Design Report Submit one report per sub-team

THE TECHNICAL WRITING PROCESS

Planning, Composing & Revising

Presentation transcript:

IEEE P1603 reviewer’s guideline Wolfgang Roethig, WG chair

Please review the IEEE P1603 document for the following criteria Clarity Contents Completeness Consistency Practicality Organization Style

Clarity Is the contents understandable? Does the section/subsection describe what the title says? If not, should the title be changed or the section/subsection be rewritten? Feel free to ask questions for clarification Don’t assume that someone else (with more expertise on the subject?) will understand if you don’t

Contents Does the proposed contents fulfill a purpose? Is the proposed contents acceptable? If not, please state the reasons and draft alternative proposal – be brief

Completeness Is a section complete in itself? Are appropriate references given to other sections/subsections or to external documents? If information is missing, is it found in other sections/subsections? – please identify Feel free to draft a proposal that fills the blanks

Consistency Are there any contradictions within a section/subsection? Are there any contradictions between sections/subsections? Propose resolutions for apparent contradictions

Practicality Is the proposed contents practical for new implementations? Is the proposed contents compatible with existing implementations? Are changes with respect to previous versions justified? Give practical examples, if there are issues

Organization Are the topics presented in an appropriate order? Do the topics of a section/subsection belong together? Are topics that belong together found in the same section/subsection? Feel free to propose an alternative organization

Style Simplicity: any suggestions to shorten a 300 page document are welcome Tables and figures are as important as text Check for correct and concise terminology No need to report typos and grammar in detail: this is the responsibility of the technical editor

How to give feedback to is Break it into several s if subject is long Please refer to version, page and line numbers Direct editing of source text by reviewer should be exception, not rule

Thanks for your time and effort to review the IEEE P1603 document