Presentation on theme: "ICS 139W Critical Writing on Information Technology"— Presentation transcript:
1ICS 139W Critical Writing on Information Technology Lecture 1Emily NavarroDuplication of course material for any commercial purpose without the explicit written permission of the professor is prohibited
4Course BasicsCourse: ICS 139W – Critical Writing on Information TechnologyProfessor: Emily NavarroTA: Scott GodfreyLecture: T Th 5-6:20pm, ICS 180Discussion: W 9-9:50 (ICS 259), 10-10:50 (DBH 1423) (attend one per week)Some weeks: required activitiesSome weeks: informal consultation hourCourse Website: html
5Course Basics (II) Office hours Questions and announcements Emily: before or after lecture, by appointmentScott: before or after discussion, by appointmentQuestions and announcementsor in classClass listCourse materialsEnglish dictionary and thesaurusA writing guide (see UCI Writing Center resources)I’ll use class list to respond, you can use it too for general questionswriting guide: spelling, grammar, verb tenses, numbers, etc.
6Course GoalsTo give you the opportunity to focus on writing in your specific academic discipline (CS)To help you become comfortable writing technical documents for a variety of audiencesTo help you become comfortable with giving presentationsIn your CS career you may have to write manuals, conference papers, journal papers, white papers, memos, executive summaries, even s can be critical
7Grading Writing Assignments: "Writing Instructions:" 10%"Influencing Policy:” 15%"Changing the System Introductory Tutorial:" 15%"Changing the System Proposal:" 20%“Changing the System Promo Piece:” 5%Resumé and cover letter: 5%Two or three smaller in-class exercises: 10%Class attendance and participation, including three or four oral presentations: 20%Really good reason for absence, let me know beforehandNo exams
8Writing Assignment Requirements Submission mechanicsSubmit a hard copy at the BEGINNING of classALSO submit an electronic copy via EEE DropboxIntermediate versionsshould be as good as you can make themcount for 1/3 of your grade on the assignmentmust include marked copies of all earlier versionsboth instructor marks and peer editing marksrefers to paper submission onlyFor most assignments, you will turn in more than one versionOther 2/3=final draft
9Writing Assignment Requirements (II) PlagiarismDON’T DO IT!Plagiarism = presenting someone else’s work as your ownCite any resources from which you pull information“Two or more” rule of thumbAll assignments are checked thoroughly for plagiarismPlagiarism consequencesFail the courseOffense recorded with Student AffairsAny time you use two or more words in a row that you did not think up yourself, use quotation marks and indicate where they came fromPlagiarism checked through manual and automated checkersCan affect financial aid, graduation, eligibility for honors, etc.
10Writing Assignment Requirements (III) Grammatical/spelling mechanicsA good command of English syntax, spelling, and punctuation is assumedCourse focuses on content, organization, audience, and styleWe will not mark every grammatical error on your assignmentsBut they can lower your gradeIf you need help with this, the UCI Writing Center has many resourcesTalk about non-native English speakersAlways leave time for a slow careful read-through before the deadline
11Spelling/Grammar Checkers Spell check will not fined words witch are miss used butt spelled rite!Marketing are bad for brand big and small. You Know What I am Saying? It is no wondering that advertisings are bad for company in America, Chicago and Germany. ... McDonald's and Coca Cola are good brand. ... Gates do good marketing job in Microsoft.Do not rely on it. Simply a first step.
12Spelling/Grammar Checkers Spell check will not fined words witch are miss used butt spelled rite!Marketing are bad for brand big and small. You Know What I am Saying? It is no wondering that advertisings are bad for company in America, Chicago and Germany. ... McDonald's and Coca Cola are good brand. ... Gates do good marketing job in Microsoft.Do not rely on it. Simply a first step.Passes MS Word’s grammar checker!
13Writing Assignment Requirements (IV) Counting words and pagesone page = one standard, double-spaced typewritten page; ~300 words, point fontTypography: All papers must beTypewrittenDouble-spacedExcept forInfluencing Policy letter final versionChange proposal cover letterTypewritten except for in-class
14Writing Assignment Requirements (V) BindingSmaller assignments: one staple in upper left cornerLarger assignments (that include previous drafts): one large paper clip or purse clipInclude your name on each pieceFor more details see “Writing Assignment Requirements” linked off the class Website
16Basic IdeaExamine some software system you are familiar with from a variety of perspectives:Introducing new users to the systemProposing changes to the systemPromoting the changed system to its usersYou will create documents and oral presentations for each of these purposesFocus on the different audiencesand how your writing/presenting needs to be tailored to each
17Stage I – Choosing a System Can be conventional application software or a Website with complex navigation/interaction/functionalityAudience: our classDeliverables:4/3: to ScottName the systemDescribe it if unfamiliarSketch out the changes you are proposing4/10: 1-2 minute oral presentation in lectureBased on feedback from ScottClass may or may not know about the SW, may have suggestions about the changes you propose
18Stage II – Introduction for Novices Write an introduction to the system for novices3-4 pagesHigh-level description of the system, its capabilities, tasks it performsInclude any necessary background informationDo not include tedious minor detailsE.g., which keys to press, which menu items to chooseAudience: novicesDeliverables:4/16: First draft4/17 or 4/21: 2-minute oral version of introduction4/23: Final version
19Stage III – Proposal for Change Write a proposal for changing the system5-6 pages plus a single-page cover letterAddress the proposal to whoever is in charge of making the changes happenProduce a proposal that is actually “sendable” to this personAudience: decision-makersDeliverables:4/24: First draft for joint editing in class + presentation slides5/1: Revision of proposal and slides based on joint editing5/15, 5/20, 5/22: Final oral proposal for change (~4 min.)5/20: Final written version + final presentation slidesdecision makers know about the software, but need to be convinced of the usefulness and feasibility of the changes
20Stage IV – Promotion for Users Prepare a one-page promotion piece announcing, describing, and promoting your change to current usersFlyer, brochure, memo, Web page, etc.Can be relatively informalAudience: current users of the systemDeliverables:5/29: Draft for editing in class6/3: Final version + 2- minute presentationknow what it does now but need to know what the changes mean
21Suggestions/Advice Choose software that you know/care about Be mindful of your audienceUse graphics effectivelyCite your sources of informationFor oral portions, do not simply read from a scriptSeek advice from usOral presentation graded on preparedness (not speaking style, nervousness, etc.)Graphics don’t count towards page countCitation format not crucial, just be consistentoral presentations: can have notes, but speak naturally (maintain formality)
23Basic Idea The premise The assignment We are used to writing instructions for computersWriting instructions for human execution requires a different set of skillsThe assignmentBuild some object using Legos, Tinkertoys, etc.Premade “kits” not allowedWrite a manual for building your object using only words (no pictures)Build each other’s objects in class using only the written manualSystem must have more than one type of object that can be combined in more than one wayComputers interpret language reliably, humans don’t; programming langugaes are simple and unambiguous
24Due Dates4/9Disassembled components of your object and three copies of a good draft of your manualYou will build each others’ objects in class and make suggestions for improvements to each others’ manuals4/15Final revision of your manualDisassembled components
25Suggestions and Hints Start your manual with a list of components Consider describing your object in terms of modulesUse organizational guides in your manuale.g., section headers, table of contents
26Next Time Discussion (tomorrow) Lecture (Thursday) Consultation hour for “Changing System” and “Writing Instructions” assignmentsLecture (Thursday)In-class writing sample“Easy” topic~300 wordsYou may bring a dictionary or other reference work on paperStrive for perfect mechanics, grammar, usage, clarity, organizationBring a pencil or two
27Next, Next Time Lecture (Tuesday) Read the two papers on PowerPoint available on the course WebsiteYou will write about them in class