计算机专业英语第六章

1、Unit Six Documenting Your Work,Contents,Persuading others Listening To learn to persuade others; To comment source codes properly; To read and write source code documentation; To reply and forward e-mails; To learn how to draft planning proposals.,6.1 Persuading others,A. Culture tips Listen to the

2、audio and answer these questions: When you want to interrupt someone, the best time is _. A. in the middle of a sentence B. after he/she finishes his/her speech C. between sentences,C,Which of the following is the most effective way to convey your meaning? _ A. words B. intonation C. body language O

3、ccasional differences of opinions between a boss and a subordinate are a sign of _ in American companies. A. a good working relationship B. an intense relationship C. a bad relationship,6.1 Persuading others,C,A,B. Group discussions: persuading others 1.Read the two dialogs between co-workers and te

4、ll which one is better, the left or the right. 2.Listen to the conversation, the project team is discussing hiring new programmers.,6.1 Persuading others,6.1 Persuading others,B. Group discussions: persuading others Sentence patterns Learn to use these expressions to Strongly agree; Agree; Partly ag

5、ree; Disagree; Strongly disagree; Interrupt.,6.1 Persuading others,C. Exercises Dictation 1. Some Tips for Persuading Others,1. admit to a minor weakness 2. stating the strengths 3. I can be trusted 4. acts against their own self-interest 5. build credibility 6. the opinion of others 7. For instance

6、,8. on the other hand 9. making a positive statement 10. more credible 11. The more similar 12. the more powerful 13. make informed decisions,6.1 Persuading others,C. Exercises Dictation 2. Conversation between colleagues,1. efficient and reliable 2. I feel sure 3. I agree with you 4. on the other h

7、and,5. asks for 6. charges far less 7. youve got a point 8. according to,6.1 Persuading others,Oral practice,YOU,Mr. Johnson,Show your understanding.,I dont think we can move into the Japanese market at this time. Wed better improve and increase our share of the market here in China.,Try to interrup

8、t.,The potential market in Japan is no doubt huge, but,Show agreement.,Just let me finish what I was saying, please.,Show your understanding.,but, before we move into the Japanese market we should strengthen our market share here in China.,What were you trying to say just now?,I believe our success

9、in China can bring us a much more reliable reputation than just setting up branches in Japan. What do you think? Do you agree with me?,I was trying to remind you that our rival, AAA Company, has already set up several branches in Japan. It has already begun to establish its reputation there.,Complet

10、ely disagree, insist on moving into Japanese market now.,A. Discussing code documenting conventions Annie Jefferson, Sam Carter, and Michael Zhang are receiving a training program offered by the R Single-Line Comments; Trailing Comments; Out Comments.,6.3 Source code documentation,Please connect the

11、 following names with their main conventions.,the first letter of all words capitalized,Variables,Class files and header files,Functions,Classes,the first letter of all words capitalized except for the first one,reflects the content of the file,more than eight characters with a mix of upper cases an

12、d lower cases,6.3 Source code documentation,C source file,C/C+ header file,C+ inline function file,Interface Description language,Resource Script,Java source file,C+ source file,6.3 Source code documentation,Fill in the following table.,4.Translations. a)A good name for a routine clearly describes e

13、verything the routine does. b)Special care should be given to the naming of header files because of potential conflicts between modules. c)When applicable, all source documentation should be in a format compatible with the generic formatting defined by the original programming language. d)Block comm

14、ents are used to provide descriptions of files, methods, data structures and algorithms.,一个好的例程名能明确地描述该例程的功能。,注意头文件的命名以避免模块间潜在的冲突。,在可应用的时候，所有源文档的格式应适当地与原始程序语言定义的通用格式兼容。,块注释用来说明文件、方法、数据结构和算法。,6.3 Source code documentation,e)Short comments can appear on a single line indented to the level of the code

15、that follows. f)Very short comments can appear on the same line as the code they describe, but should be shifted far enough to separate them from the statements. g)The information provided by documentation comments delivers very important messages to other developers and users. h)Documentation comme

16、nts, specially in Java, describe the classes, interfaces, constructors, methods, and fields.,短注释可以出现在单一一行，缩进位置与其后的代码相同。,若注释非常短，可与代码同行，但要空出足够的间距。,文档注释向其他开发人员和用户传递非常重要的信息。,文档注释，特别是在Java语言中，说明类、接口、构造函数、成员方法和成员变量。,6.3 Source code documentation,The five types of documentation comments, as mentioned in th

17、e article, are listed below. Try to use as few words as possible to describe them. Copyright information: Module comments: Revision history: Code specification: Source documentation:,provides the copyright and licensing information of the code.,6.3 Source code documentation,indicates where the reade

18、r can find the sources of the information.,contains enough information about the programmers destination.,records the history of changes in the source files.,describes the classes, interfaces, constructors, methods, and fields.,6.4 E-mail & technical writing,A. Replying or forwarding e-mails properl

19、y Key points: Every message other than spam or junk mail deserves a reply. Give your final answer in your reply. Respond as soon as possible. When replying, include enough of the original message to provide a context. When replying or forwarding a message, minimize the original one. Distinguish betw

20、een text quoted from the original message and your reply. Know where your reply or forward will end up.,6.4 E-mail & technical writing,A. Replying or forwarding e-mails properly Key points: Reply to e-mails with one-word answers or questions. Forward e-mails unless you have the permission of the aut

21、hor. Forward forwarded messages to your friends and co-workers. Use “Reply To All” when you are replying to just one sender.,B. E-mails about software documentation Assignments:,Gather examples of e-mail replies and forwarded e-mails. Are they properly written in terms of layout, tone, and professio

22、nalism? Write a letter to a colleague about copyright comments.,6.4 E-mail & technical writing,C. Guide to technical writing Drafting planning proposals: Use appropriate format and supplements. Write a concrete and specific title. Begin with a clear introduction. Develop a plain and understandable b

23、ody. Design your planning proposal to reflect your attention to detail. Focus on one specific subject and one purpose. Identify all problems readers themselves might not recognize. Provide concrete and specific information. Use visuals whenever possible. End with a comprehensive summary.,6.4 E-mail & technical writing,D. Technical writing exercises Locate a planning proposal from your library or company. Does the proposal conform to the above guidelin