33
Technical Writing Examples Plus A Few Tips

Technical Writing Examples Plus A Few Tips

  • Upload
    yanni

  • View
    28

  • Download
    0

Embed Size (px)

DESCRIPTION

Technical Writing Examples Plus A Few Tips. What is wrong? H ow to rewrite?. Before. - PowerPoint PPT Presentation

Citation preview

Page 1: Technical Writing Examples Plus A Few Tips

Technical Writing ExamplesPlus A Few Tips

Page 2: Technical Writing Examples Plus A Few Tips

What is wrong?How to rewrite?

Page 3: Technical Writing Examples Plus A Few Tips

BeforeThe volume of information has been rapidly increasing in the past few decades. While computer technology has played a significant role in encouraging the information growth, the latter has also had a great impact on the evolution of computer technology in processing data through the years. Historically, many different kinds of databases have been developed to handle information, including the early hierarchical and network models, the relational model, as well as the latest object-oriented and deductive databases. However, no matter how much these databases have improved, they still have their deficiencies. Much information is in textual format. This unstructured style of data, in contrast to the old structured record format data, cannot be managed properly by the traditional database models. Furthermore, since so much information is available, storage and indexing are not the only problems. We need to ensure that relevant information can be obtained upon querying the database.

Page 4: Technical Writing Examples Plus A Few Tips

After

Much information is textual. This unstructured data cannot be managed properly by traditional database models. Furthermore, storage and indexing are not the only problems. We need to ensure that relevant information can be obtained upon querying.

Page 5: Technical Writing Examples Plus A Few Tips

Before

As each value is passed to the server, the “heart” of the system, it is checked to see whether it is in the appropriate range.

Page 6: Technical Writing Examples Plus A Few Tips

After

Each value passed to the server is checked to see whether it is in the appropriate range.

Page 7: Technical Writing Examples Plus A Few Tips

Before

Tree structures can be utilized for dynamic storage of terms.

Page 8: Technical Writing Examples Plus A Few Tips

After

Terms can be stored in dynamic tree structures.

Page 9: Technical Writing Examples Plus A Few Tips

Before

The following theorem can now be proved.

Page 10: Technical Writing Examples Plus A Few Tips

After

We can now prove the following theorem.

Page 11: Technical Writing Examples Plus A Few Tips

Before

The authentication process and update activities are the responsibility of the database manager module.

Page 12: Technical Writing Examples Plus A Few Tips

After

Authentication and updating are the database manager’s responsibility.

Page 13: Technical Writing Examples Plus A Few Tips

Before

This language has more “power” than the functional form.

Page 14: Technical Writing Examples Plus A Few Tips

After

This language allows simpler expression of queries than does the functional form.

Page 15: Technical Writing Examples Plus A Few Tips

Before

In SIMD, the same instructions are applied simultaneously to multiple data sets, whereas in MIMD different data sets are processed with different instructions.

Page 16: Technical Writing Examples Plus A Few Tips

After

In SIMD, multiple data sets are processed simultaneously by the same instructions, whereas in MIMD multiple data sets are processed simultaneously by different instructions.

Page 17: Technical Writing Examples Plus A Few Tips

Before

A static model is appropriate because each item is written once and read often.

Page 18: Technical Writing Examples Plus A Few Tips

After

A static model is appropriate because each item is only written once but is read often.

Page 19: Technical Writing Examples Plus A Few Tips

Before

Type inference derives information about programs.

Page 20: Technical Writing Examples Plus A Few Tips

After

Type inference proves that programs obey the language typing rules.

Page 21: Technical Writing Examples Plus A Few Tips

Before

We are planning to consider possible options for extending our results.

Page 22: Technical Writing Examples Plus A Few Tips

After

We are considering how to extend our results.

Page 23: Technical Writing Examples Plus A Few Tips

Before

is a conditional dependency.1 np q q

Page 24: Technical Writing Examples Plus A Few Tips

After

The dependency is conditional.

1 np q q

Page 25: Technical Writing Examples Plus A Few Tips

Before

For each , , is positive. ix 1 i n ix

Page 26: Technical Writing Examples Plus A Few Tips

After

Each , where , is positive.ix 1 i n

Page 27: Technical Writing Examples Plus A Few Tips

Before

(Within pseudocode on strings …)

For1. Set 2. Set

1 i s

c s i

1c cA A

Page 28: Technical Writing Examples Plus A Few Tips

After

For each character c in string s, increment Ac.

Page 29: Technical Writing Examples Plus A Few Tips

Other tips

Page 30: Technical Writing Examples Plus A Few Tips

Beware of analogies

Writing a program is like building a model with connector blocks.

Page 31: Technical Writing Examples Plus A Few Tips

Open strongThis paper does not describe a general algorithm for transactions.

General-purpose transaction algorithms guarantee freedom from deadlock but can be inefficient. In this paper we describe a new transaction algorithm that is particularly efficient for a special case, the class of linear queries.

We describe a new transaction algorithm that is particularly efficient for linear queries. While general-purpose transaction algorithms guarantee freedom from deadlock, they can be inefficient. So, we focus on a common special case.

Page 32: Technical Writing Examples Plus A Few Tips

Be consistent

Style, terminology, variable names, ordering of list items, numbering 1-2-3 vs. a-b-c, fonts, indentation, …

Page 33: Technical Writing Examples Plus A Few Tips

Credits

• Most examples taken/adapted from “Writing for Computer Science”, by Justin Zobel (2nd ed.), 2004

• Some taken/adapted from a document by the CMU SCS Research Documents Group, 1989.