Guidelines for writing Specifications ELEC 421. Word Use in Engineering Specifications Traditionalist: Obligation: shall Permission: may Revisionist:

Slides:



Advertisements
Similar presentations
Improving Readability with Style and Design
Advertisements

3 levels: Foundation, Standard, Advanced Language B Spanish Criteria.
Guide to Computer Forensics and Investigations Fourth Edition
AuthorAID Workshop on Proposal Writing Rwanda June 2011.
Introduction to Software Engineering Dr. Basem Alkazemi
At the end of this lesson you will be able to:
Writing Skills Improvement Guide Dr. Zubair A. Baig Computer Engineering Department KFUPM, Dhahran.
Introduction to Software Engineering
Software Engineering CSE470: Requirements Analysis 1 Requirements Analysis Defining the WHAT.
Computer Engineering 294 R. Smith Writing Skills 03/ Breaking Old Habits Generally we follow old habits. There are hundreds of rules to learn. –
Memos Objectives Differences Among Memos, Letters, and Criteria for Writing Successful Memos Process Criteria for Effective Technical Writing.
Cracking the English Test. General Hints Do the questions in order, leaving the tougher rhetorical questions for the end. If you’re having trouble with.
Writing Reports, Proposals, and Technical Documents By Laurie A. Pinkert.
Assessing Reading Meeting Year 5 Expectations
Chapter seven A word’s worth.
Proofreading & Revising
Writing Tips for Evaluators: 10 Principles for Clearer Communication Presented by: Joy Quill C. J. Quill & Associates, Inc. EERS 2008 Copyright 2008 C.
MECHANICS OF WRITING C.RAGHAVA RAO.
Requirements Analysis
TIPS TO “ROCK” THE TEST ACTAAP Writing Two Types of Writing on EOC Responses to reading Open Response Questions Responses to writing Topics.
WRITTEN ABILITY TEST(WAT) GUIDE An initiative of MPRC, IIM Kashipur.
Chapter 6. Writing for Your Readers © 2013 by Bedford/St. Martin's1 Understand eight typical patterns of organization: chronological spatial general to.
STEPS TO SUCCESSFUL WRITING!. The writing process consists of strategies that will help you proceed from idea or purpose to the final statement.
EDU 600: Educational Research Methods and Techniques How to Write so Readers Will Understand You Rachel Brown-Chidsey, Ph.D., NCSP Associate Professor.
Software Requirements Engineering CSE 305 Lecture-2.
Getting the Language Right ITSW 1410 Presentation Media Software Instructor: Glenda H. Easter.
Drafting and Revising Effective Sentences Chapter 11 Presented By Blake O'Hare Chris McClune.
Report Format and Scientific Writing. What is Scientific Writing? Clear, simple, well ordered No embellishments, not an English paper Written for appropriate.
Becoming a Better Writer LET I. Introduction Writing is one of the acts or processes used to exchange ideas. Your writing must be simple, readable, and.
OneM2M-REQ R03 Proposed simple guidelines for writing use cases and requirements Group Name: oneM2M WG1 / WG2 Source: Joerg Swetina (NEC), Ataru.
Writing the “Results” & “Discussion” sections Awatif Alam Professor Community Medicine Medical College/ KSU.
UML Use Case Diagramming Guidelines. What is UML? The Unified Modeling Language (UML) is a standard language for specifying, visualizing, constructing,
Proofreading Week 12 ( ) Peiling Hsia. Contents: Proofreading guideline Revising for Cohesion Common errors of writing a paper.
Some Tips about Writing Technical Papers Michael R. Lyu September 9, 2003.
Communication for Managers Guidelines for Effective Writing Write strategically Write logically and coherently Use formatting devices and color effectively.
BBI 2412 Writing for Academic Purposes PJJ Semester 2 – 2011/ /13/20151.
Crim B50 Criminal Justice Report Writing Bakersfield College Charles L. Feer, JD, MPA.
Unit 1 Activity 2B Communication Barriers Report
“See everything, overlook a great deal, correct a little.” work of “Grammar Across the Disciplines LC" presented by Katrina ArndtJohn Travers Russ Coward.
C ELEBRATION OF L EARNING ! 6+1 Writing Traits. W HAT ARE THE 6+1 W RITING T RAITS ? Guidelines that create consistent expectations for what good writing.
BBI 2412 Writing for Academic Purposes PJJ Semester 2 – 2012/ /3/20151.
Chapter Six Improving Readability with Style and Design McGraw-Hill/Irwin Copyright © 2014 by The McGraw-Hill Companies, Inc. All rights reserved.
Quick Punctuation Guide
Unit 8 Syntax. Syntax Syntax deals with rules for combining words into sentences, as well as with relationship between elements in one sentence Basic.
Improving Readability with Style and Design
Written Presentations of Technical Subject Writing Guide vs. Term paper Writing style: specifics Editing Refereeing.
Topic 4 - Database Design Unit 1 – Database Analysis and Design Advanced Higher Information Systems St Kentigern’s Academy.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
Instructor Availability AIM address: EleBranch Office Hours: Mondays & Thursdays 9:00 p.m. to 10:00 p.m. And by appointment.
Developing Business Practice –302BUS Writing Successfully for your Studies and in Business Unit: 3 Knowledgecast: 1.
Requirements Analysis
31 Ways to Flavor a Composition. Consider the audience.
Software Engineering, COMP201 Slide 1 Software Requirements BY M D ACHARYA Dept of Computer Science.
What is a report? A written statement prepared for... the benefit of others describing... what has happened or a state of affairs, normally based on...
S TEP 5 - E DITING The next stage in the writing process is called “editing”. The purpose of editing is to apply the standards of written English to your.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 6 Slide 1 Software Requirements (utvalgte foiler fra Kap 6 og 7 i Sommerville)
Copyright © 2011 Pearson Education, Inc. publishing as Prentice HallChapter Completing Business Messages.
1 January 31, Documenting Software William Cohen NCSU CSC 591W January 31, 2008.
INFORMATION FOR PARENTS AUTUMN 2014 SPELLING, PUNCTUATION AND GRAMMAR.
Copyright © 2017 Pearson Education, Inc.. Excellence in Business Communication Chapter 6 Completing Business Messages Copyright © 2017 Pearson Education,
Just because you wrote it doesn’t mean you’re finished!
Writing Requirements Lecture # 23.
Report Writing Three phases of report writing Exploratory phase (MAPS)
Language Paper targets
Just because you wrote it doesn’t mean you’re finished!
Communication Skills for Engineers
Tips for AP Exam!.
Communication Skills for Engineers
The SAT Writing and Language Test
TECHNICAL REPORTS WRITING
Presentation transcript:

Guidelines for writing Specifications ELEC 421

Word Use in Engineering Specifications Traditionalist: Obligation: shall Permission: may Revisionist: Obligation: must Permission: will Minimalist: Using the imperative (command) form of the verb with implicitly assumed subject.

6C Rule Clearly written (unambiguous) Coherent and well-organized (format) Complete (no omissions) Concise (no unnecessary words) Consistent (terminology, accuracy, drawings, constraints and needs) Correct (both technical & grammatical)

Jargon The specialized language used by experts in a particular discipline Makes communication more efficient among knowledgeable people Define terms in the text where they are first used for the benefits of all stakeholders

Acronyms Analogous to jargon Well-recognized and accept as a part of the language SCUBA (self-contained underwater breathing apparatus) RADAR (radio detection and ranging) Use acronyms judiciously and define them when they are first mentioned

Nominalizations A technique for changing a verb into a noun by adding a suffix Avoid its usage to shorten the text for conciseness and readability Repetitive use of normalizations makes the processing of writing more difficult. Text is harder to read when verbs are nominalized repeatedly.

Noun Stacks Use of a stack of nouns as an adjective to describe another noun For ease of reading, limit noun stacks to three or fewer nouns Noun stack: Aircraft wing-body junction vortex generation Revision: vortex generation at the wing-body junction of an aircraft

Long Sentences Sentence length should be guided by the complexity of the idea being described Avoid run-on (fused) sentences (i.e., containing more than one independent clause) Use connecting words to relate shorter sentences

Unforgivable Grammatical Errors Subject-verb agreement Fragments Run-on Sentences

Dr. Peeples’ Comments Use present tense unless explaining some sequence of events Clear & Precise Language. No marketing spin allowed Simple, direct, & Concise Consistent naming of functions and components throughout the spec.

Dr. Peeples’ Comments No “hanging” illustrations (i.e., figures or tables) that are just there and never discussed, explained, or even referred to for clarity Don’t specify brand names (Fluke, HP..) unless absolutely required to use a particular brand or model number As complete as possible

Reminder The specifications is written to describe the technical details of the project Formal project proposal concentrates more on marketing aspect