Schedules（进度）
A key part（关键部分） of a softwareproduct is its schedule. As a project grows in size and complexity, with manypieces and many people contributing to the product（构建产品）, itbecomes necessary to have some mechanism（一些机制） to track itsprogress（跟踪进度）. This could range from simple task lists（将一些任务列表） toGantt charts（甘特图）to detailed tracking（用来详细跟踪） of every minutetask with project management software.（中文就是根据项目管理软件，将分离的任务列表绘制成甘特图来详细跟踪每一个分钟的任务情况）
The goals of scheduling are to know whichwork has been completed, how much work is still left to do, and when it willall be finished.
SoftwareDesign Documents （软件设计文档）
One common misconception（误解） is thatwhen a programmer creates a program, he simply sits down and starts writingcode. That may happen in some small, informal（非正式、不正规的） softwareshops, but for anything other than the smallest programs（但是除去这些极小的软件）,there must be a design process to plan out how the software will be written.Think about this book, which required an outline（大纲） before the firstwords were typed（想想这本书，在第一个字写之前需要先列好大纲）, or a building, which has blueprints drawn before the firstconcrete is poured（或者建筑物，在混凝土被浇筑之前要先绘制好蓝图）. The same planning should happen with software.
（注意：这里的which有的人翻译成哪些，这里不是疑问句，是非限制性定语从句，表示指前一句所说的事物）
The documents that programmers create vary greatly（不同的文档）depending on the company（根据不同公司）, the project, and the team, but their purpose is to plan andorganize the code that is to be written.
Here is a list of a few common softwaredesign documents:几个常用的文档
Architecture（概要设计说明书）. A documentthat describes the overall（全部） design of the software, including descriptions of all the majorpieces and how they interact with each other.
Data Flow Diagram（数据流程图）. Aformalized （正式的）diagram that shows how data moves through a program. It's sometimes referred to as（被称为） abubble chart（气泡图）because it's drawn by using circles and lines.
State Transition Diagram（状态转移图）.Another formalized diagram that breaks the software into basic states, orconditions, and shows the means for moving from one state to the next.
Flowchart（流程图）. Thetraditional means（传统方法） for pictorially（绘画） describing a program's logic. Flowcharting isn't very populartoday, but when it's used, writing the program code from a detailed flowchartis a very simple process.
Commented Code（注释）. There'san old saying that you may write code once, but it will be read by someone atleast 10 times. Properly embedding（嵌入） useful commentsin the software code itself is extremely important, so that programmersassigned（被派去维护代码的程序员） to maintain the code can more easily figure out what it does and how.
| 欢迎光临 51Testing软件测试论坛 (http://bbs.51testing.com/) | Powered by Discuz! X3.2 |