To help you enhance your writing, we present four useful tips based on commonly found errors. You can place the next few points right into practice!

為了幫助大家編寫方案，我們根據普遍發(fā)現(xiàn)的問題向大家推送了4條有用的技巧，供大家參考。

1. Have detailed Design Specifications. 

有具體的設計規(guī)范

Design Specifications should precisely detail how Requirements will be met. Since they are the most technical of all of the documents, it is critical that material is placed in a logical manner. Using a template will help set the stage for Design Specifications that are functional and streamlined.

設計規(guī)范應該清晰明確要求是如何被滿足的。技術資料是整個文件最技術性的問題，應以合理的方式列出。使用一個模板有助于為滿足設計規(guī)范創(chuàng)造條件。

2. Figure out how many times your protocols will be executed.

算出你的方案將被使用多少次

The number of times you expect your protocol to be used should dictate how much time you should spend on making it efficient to executive. If the protocols will be executed numerously, take extra time to make them as efficient and effective as possible.

你的方案預計被使用的次數將決定你在其生效被執(zhí)行前需要消耗的時間。如果該方案將會被無限次數的使用，可以花費多點時間以使其盡可能的有效和有用。

3.  Avoid sloppy errors in test cases and get familiar with who is using your protocol.

在測試案例中避免提供錯誤，并且了解你的方案將是被誰使用的

Who is going to be using your system? If it is someone not as familiar with your system, consider writing better procedures with more instructions. If you find a mistake in your reusable protocol or template, take time to correct it in the template before the text, in case it appears again the next time it is run.

誰將使用你的系統(tǒng)？如果是一些不是很熟悉你的系統(tǒng)的人，應考慮寫入帶有更多指導說明的程序。如果你在你的方案模板中發(fā)現(xiàn)一個錯誤，花點時間去糾正它，以免它在下次使用時再次出現(xiàn)。

4.  Cut down on excessively long procedures.

減少過長的程序

Optimally, procedures shouldn’t be more than 5 sentences. If your steps are lengthy, break them up into 2-3 smaller steps.

程序最好不要超過5句。如果你的步驟太長，將他們分成2-3個小步驟。