Reviewed by

格式：pdf
大小：250.22 KB
文档页数：4

下载文档原格式

/ 4

软件产品开发计划四篇

软件产品开发计划四篇篇一：产品开发计划项目号：项目名称：编制人：部门：日期：1内容简介1.1文档目的这部分要描述文档的目的，应该指明读者。

1.2文档范围<描述项目计划的范围，明确文档涉及的各项内容>简要描述本计划需要在该产品项目中完成的工作活动及其工作目标、项目采用的生命周期、项目交付物、相关人员的角色和职责、主要里程碑、进度计划、质量计划、配置管理计划、风险计划等。

2项目概况简要描述本项目的类型（新产品/改进/维护类）、项目的目的、范围、目标（例如：项目的市场定位，产品需求等）。

3项目组织结构PDT组织结构图PDT及系统分析与设计组成员建议，产品开发成员建议在决策评审点前与适当的PRB成员及相关资源部门经理对这些列表进行沟通的结果描述项目的组织结构，建议采用图表的表示方式。

也可参考下例：下表定义了项目成员的角色和职责。

●在审核之前项目经理需指定所有文档和代码的审核人。

●对于各个角色的职责定义可根据项目实际情况进行补充。

●下表内容应当至少在项目的每个阶段结束时进行更新。

对于项目阶段中/ 阶段间发生的组织结构的变化，项目经理应当通过邮件周知所有相关人员，然后更新项目计划。

表4 项目的组织结构4项目依赖关系分析5.1 项目关键路径分析及保障措施在本节中，分析影响项目进度的关键步骤/环节、关键因素，并提出保障措施5.2 项目依赖关系分析在本节中，说明项目的内部依赖关系(如：开发测试工具、人力资源等)和对外部的依赖（如项目之间、与客户之间的技术、资源等方面）。

可用依赖性列表、活动网络图的方法描述。

列出所有影响项目计划的假设因素(相对于已知的因素)。

如果这些假设因素有误，或者没有利用到假设因素，或者假设因素发生变化都会使项目受到影响。

另外还要描述项目对外部因素的依赖关系，例如，如项目作为整个大系统的一部分，需要其他部分提供接口定义或者PDT提供正在开发的仿真性能测试工具以代替实际环境测试等等>请参考下例：表1 项目依赖关系5.3 项目关键成功因素5.3 技术方法和工具在本节中，描述对产品项目进行需求分析、设计、实现、测试、文档写作、发布、修改、或维护过程中采用的开发方法、组织结构和其他标记、工具、技术和方法。

美国会计准则中文版01 收入确认-reviewed by Cathy-ok

1-1. 会计定义概述只有当收入实现时或者收入可以实现并能取得相关利益时才能予以确认。

一般情况下，只有当以下条件同时得到满足时才可确认收入：(SAB No. 101 & 104):1.有说服力的证据表明销售约定存在；2.货物已经交付或者劳务已经提供；3.卖方向买方提供的商品价格是固定的或者是可以确定的；4.可以合理确信能够收到货款。

有些收入约定包含有多个销售商品或提供服务的活动。

在一般情况下，企业应该在交易完成时确认收入，并根据可能收不回来的金额按适当比例计提坏帐准备。

但若买方拥有退回货物的权利时，卖方只能按照一定的标准确认销售收入。

供应商可能会偶尔地或持续地给予其顾客各种各样的优惠（促销），诸如：折扣、礼券、回扣、"免费"的产品或服务等（紧急问题工作组01－9《卖方给予买方回报的会计处理》）。

顾客可以是直接的，也可以是间接的。

例如，供应商销售货物给分销商，分销商再将该货物销售给零售商。

紧急问题工作组01－9还涵盖了制造商给零售商或分销商的顾客促销奖励，诸如：折扣、礼券、回扣、"免费"的产品或服务以及各项其他安排如展位费、协作广告等。

当销售退回权利存在时的收入确认当顾客有销售退回权时，卖方应该按估计的退回金额减少收入和销售成本的确认，并且要相应预提销售退回所产生的成本和费用。

企业可能允许顾客在销售以后的某一段时间内通过退货而取得退款、信贷、调换产品等。

在这种情况下，商品的所有权实质上并未转移给买方，因此，销售并没有完成，收入一般也就不能确认。

当然，当以下条件同时满足时，即使存在销售退回，企业也可以在销售时便确认收入：1.卖方给买方的销售价格在销售发生时实质上是固定的或者是可确定的；2.买方已经支付了货款或者有义务支付货款给卖方，且该义务并不取决于买方是否将所买商品重新卖出；3.买方支付价款给卖方的义务不会因货物被盗、损失或者毁损而改变；4.交易对于买方具有实质性经济意义（而非是卖方出于确认销售收入的目的而发生的形式上的交易）；5.卖方没有任何义务帮助买方将货物重新卖出；6.退货的金额可以被可靠的估计。

请相关团队审查英语作文

请相关团队审查英语作文---。

Request for Review of English Essays by Relevant Teams。

In the modern educational landscape, the importance of effective communication in English cannot be overstated. As students strive to master this global language, the role of feedback from experts and relevant teams becomes indispensable. This essay aims to discuss the significanceof having essays reviewed by relevant teams and thebenefits it offers to students.First and foremost, having English essays reviewed by relevant teams ensures the quality and accuracy of the content. English is a language with numerous intricacies, including grammar rules, vocabulary usage, and sentence structure. A slight mistake in any of these areas can significantly impact the overall meaning and clarity of an essay. By submitting essays for review, students canreceive valuable feedback from experts who possess a deep understanding of the language. This feedback helps students identify and correct errors, thereby improving the overall quality of their writing.Furthermore, reviewing essays with relevant teams promotes continuous learning and growth. Each essay review session offers students an opportunity to learn new concepts, techniques, and strategies for effective communication in English. By engaging with experts and receiving constructive criticism, students can expand their knowledge base, enhance their writing skills, and develop a more profound appreciation for the English language.In addition to improving the quality of writing, having essays reviewed by relevant teams also prepares studentsfor real-world communication scenarios. In today'sglobalized world, English is often used as a medium of communication in various professional and academic settings. By receiving feedback from experts, students can learn to communicate more effectively, articulate their thoughts clearly, and convey their ideas persuasively. This not onlyboosts their confidence but also equips them with the necessary skills to succeed in their future endeavors.Moreover, reviewing essays with relevant teams fosters a culture of collaboration and mutual support among students. Instead of viewing feedback as criticism, students learn to see it as an opportunity for growth and improvement. By working closely with experts and peers, students can exchange ideas, share experiences, and learn from each other's strengths and weaknesses. This collaborative approach to learning promotes a supportive and inclusive learning environment where students feel valued, respected, and motivated to excel.Lastly, having English essays reviewed by relevant teams enhances the credibility and recognition of students' work. When students receive positive feedback and endorsements from experts, it validates their efforts and achievements, boosting their self-esteem and confidence. Furthermore, showcasing reviewed and refined essays in portfolios, applications, or publications can significantly enhance students' academic and professional profiles,making them stand out in a competitive landscape.In conclusion, having English essays reviewed by relevant teams offers numerous benefits to students, including improving the quality of writing, promoting continuous learning and growth, preparing for real-world communication scenarios, fostering collaboration and mutual support, and enhancing credibility and recognition. As students continue to strive for excellence in mastering the English language, the role of feedback from experts and relevant teams remains crucial in guiding, supporting, and empowering them to achieve their academic and professional goals. Therefore, it is essential for educational institutions, teachers, and students to recognize the importance of this collaborative approach to learning and to embrace it wholeheartedly.---。

装运前验货报告(中英文版)

从未包装产品
中抽样数
Sample from not packed quantity
2.做工质量WORKMANSHIP：
次品描述Defect Description:
致命Critical
主要Major
次要Minor
-
-
次品总计Actual Findings：
最大允许次品数Maximum Allowed：
数据测量/现场测试
Data Measurement / On-site Testing
包装Packing
箱麦/标贴Shipping Mark/Label
最终结论
OVERALL CONCLUSION
合格，可以安排出货CONFORMED
不合格，需返工并接受重新验货NOT CONFORMED
待讨论后决定是否出货PENDINGfor customer’s decision
最终随机检验Final Random Inspection
验货日期Inspection Date
验货地点Inspection Location
验货结论INSPECTION CONCLUSION：
数量Quantity Available
颜色/款式/材料Style/Material/Color
做工质量Workmanship
验货主管确认：日期Date：
1.验货数量INSPECTION QUANTITY
订单号Order No.
款号Item No.
条形码UPC Code
数量Quantity
箱数
Carton
总计Total
验货标准：采用标准,单次抽样一般检验水平Ⅱ级Inspectionstandard:,Single sampling plan for normal inspectionlevelⅡ

项目管理主要表格

签字：日期：
10-项目总结表
项目总结表
Project Overviews
一、项目基本情况Project Basic Info.
项目名称Project name：
项目编号project code：
制作人Prepared by
审核人reviewed by：
项目负责人project leader：?
制作日期data：
审核人reviewed by：
项目负责人project leader：?
制作日期data：
二、当前任务状态（简要描述任务进展情况）
关键任务
状态指示
状态描述
三、本周期内的主要活动（对本周期内的主要交付物进行总结）
四、下一汇报周期内的活动计划（描述活动需要与项目计划和WBS相对应）
五、财务状况
六、上期遗留问题的处理（说明上一个汇报周期内问题的处理意见和处理结果）
制作日期data：
二、历史变更记录（按时间顺序记录项目以往的每一次变更情况）
序号
变更时间
涉及项目任务
变更要点
变更理由
申请人
审批人
三、请求变更信息
受影响的基准计划
1、进度计划
2、费用计划
3、资源计划
是否需要成本/进度影响分析：
对成本的影响
对进度的影响
对资源的影响
申请人签字
申请日期
五、审批结果
审批意见：
四、发放材料（列出会议讨论的所有项目资料）
五、发言记录（记录发言人的观点、意见和建议）
六、会议决议（说明会议结论）
七、会议纪要发放范围
08-项目状态报告表
项目状态报告表
一、项目基本情况Project Basic Info.

项目管理一整套表单中英文版

成员姓名
Name
项目角色
Project Role
所在部门

职责
Reponsibility
项目起止日期
Data
工作量Time
联系电话
Tel No.
主管经理
Supervisor
签字signature：
日期date：
项目赞助人Sponsor
项目经理projectmanager
02项目策划/任务书（Project Plan/Charter）
2.Projectobjectives(includingtimelimit , costobjectives, deliverablesandbriefdescriptionoftheirfeatures)
三、项目里程碑计划（包含里程碑的时间和成果）III.Project milestones ( includingtimelimit and deliverablesof
制作人preparedby：
审核人reviewedby：
项目经理projectmanager：
制作日期data：
二、项目沟通计划II.Project Communication Plan
利益干系人stakeholders
所需信息
Info needed
describe themain projectassumptions and the ?
六、项目主要利益干系人（包括高管、客户、职能部门主管、供应商、项目赞助人、项目经理、项目组成员等
干系人）
姓名name
类别（加下拉菜单）
部门
职务
03WBS表
ProjectWBS
一、项目基本情况I. Project Basic Info

客户投诉改善报告(中英文模板)

3.此款产品要求的材质决定了表面会有细微凹点的存在，无法避免。
拟定Prepared By：
审核Reviewed By：
完成日期Completed Date：
5.永久性纠正措施(Discipline5.PermanentCorrectiveActions)
1.增加全检工位对产品外观进行全检。
2.正常目视情况下，将可视的亮点、凹点、凸点等外观不良挑出。
3.将此次客户投诉作成品质履历，培训相关生产人员和品管人员，在后续生产与检验过程中注意管控此不良问题
拟定Prepared By：
审核Reviewed By：
完成日期Completed Da
8.客户确认及评价(Discipline8.Customersatisfactiondegree)
XXXX有限公司
品质异常8D报告
产品名称（PartName)
投诉类型（ReaForCA)
□头
客户(Customer)
总数量（OccurredQty)
/
供应厂商（Supplier)
提出日期（DateRaised)
2017
部门(Dept)：
品质
市场/PMC
生产
工程
采购
其他
姓名(Name)：
2.问题描述(Discipline2.ProblemDescription)
logo客户在显微镜下观察有明显的凹坑。
拟定Prepared By：
审核Reviewed By：
完成日期Completed Date：
3.临时纠正措施(Discipline3.ImmediateContainmentActions)
1、排查库存、在制品，对其进行全检，将正常目视能看见的凹点挑出，OK后才可出货。

美国会计准则中文版06 养老金核算-reviewed by Cathy-ok

6-1 会计定义概述养老金计划是为职工提供福利以应对某些潜在事件，如退休、死亡、残疾、或者失业的发生。

该计划大体上可以分为“确定给付计划”及“确定缴费计划”。

两者的区别在于前者日后可以获得确定的补偿而后者平常按确定的金额缴费。

就是说，“确定给付计划”提供给参加者确定的利益，而“确定缴费计划”向每个参加者提供一个账户，并且对缴费金额和方法作了相应的规定。

确定给付计划企业对“确定给付计划”的会计核算目标有两个：（a）将养老金计划相关支出在职工服务期间计入经营费用，（b）支付养老金时同时减少相关的负债和资产。

为了减少养老金费用在财务报表中的变动幅度，企业往往将养老金支出在日后一定期间摊销，而不是一次确认为费用。

养老金费用包括年金损益、施行财务会计准则公告第87号“雇主对养老金的会计核算”的规定时预计的净资产和负债以及在养老计划实施和修改之前员工因工作而享受到的相关福利。

因此每年用于“确定给付计划”的费用包含以下几个方面：1．服务成本；2．预计给付义务的利息费用；3．该计划相关资产的实际收益；4．前期未确认服务成本的摊销；5．未确认损失及收益的摊销；6．首次采用财务会计准则公告第87号时未确认的养老金计划相关资产和负债的分摊。

由于财务会计准则公告第87号对于分期摊销的规定，很难确切对一个企业资产负债表中的预提养老金费用或待摊销养老金费用进行定义。

如果企业在采用财务会计准则公告第87号之后未修改养老金计划，并且此前所有的养老金计划相关的资产及负债均已确认，此时，报表中的预提养老金费用或待摊养老金费用则反映该计划的实际状况。

也就是说，待摊养老金费用表示相对于经营状况多付的养老金费用，而预提养老金费用则表示相对于经营状况尚未付足的养老金费用。

如果企业实行财务会计准则公告第87号，当养老金计划结算或者发生了缩减的情况，企业应记录未确认的收益和损失、前期服务费用以及由此引起的净资产或负债。

养老金计划结算以后，企业就解除了对养老金所负担的义务。

B W基础概念详解

Sales
Time_key Unit_key Currency
文件名 (File Name): 创建人 (Prepared By): 审核人(Reviewed By): 第 19 页
Week Month Year
SAP’s extended Star Schema
文件名 (File Name): 创建人 (Prepared By): 审核人(Reviewed By):
数据上载 − 源系统（Source System） − 信息包（ InfoPackage） − 持续分段传输区域 (PSA) − 数据传输处理（DTP） − 信息源（Info source)
文件名 (File Name): 创建人 (Prepared By): 审核人(Reviewed By):
第 11 页
信息提供者（InfoProviders)
InfoProviders 提供信息的物理或虚拟对象。用于出报表和分析包括infocube /DSO /infoSet /MutiProvider
文件名 (File Name): 创建人 (Prepared By): 审核人(Reviewed By):
文件名 (File Name): 创建人 (Prepared By): 审核人(Reviewed By):
第3页
信息对象（InfoObjects）
• • • •
信息对象是BW的核心组成部分,最小的组织单位信息对象是其它信息模型的基础，如DSO/InfoCube，也可以做另一个信息对象的属性
信息对象必须可以放在一个信息对象目录下
大部分重要的信息对象拥有主数据, 文本, 层次表. 主数据的信息对象也可以做二维表 (例如：列出所有客户的报表)

工艺验证方案模板

Verification department (department):验证科室（部门）：Verify completion date:验证完成日期：Validity:有效期：Index 目录1.Purpose目的 (5)2.Scope范围 (5)3.Responsibility职责 (5)3.1 AAA responsibilities AAA的职责 (5)3.2 XXX responsibilities XXX的职责 (6)4.Regulation and Guidance 法规和指南 (8)5.Abbreviations缩略语 (9)6.Protocol Description方案说明 (11)7.Product And Process Description产品和工艺描述 (14)7.1 Product specification (14)7.2 Drug approval No. (14)7.3 Standard Followed: (14)7.4 Raw Materials and Adjuvants原辅料情况 (14)7.5 Process description: (16)7.6 Process Recipe工艺处方： (21)7.7 List of Production Plants生产车间一览 (26)7.8 List of Production Equipment 生产设备一览 (29)7.9 Process Flow Diagram 工艺流程图 (33)7.10 CPP Identification CPP确认 (34)7.11 Validation Plan验证计划 (49)8.Validation prerequisite验证先决条件 (51)8.1 Personal Identification人员确认 (51)8.2 Process Documentation Verification 生产文件确认 (51)8.3 Training Verification 培训确认 (52)8.4 System and Equipment Instruments Calibration Verification 系统和设备仪表校验确认.. 528.5 System and Equipment Instruments Calibration Verification 生产相关验证状态确认 (53)8.6 Test Instruments Calibration Verification 测试仪器和仪表校验确认 (53)8.7 Testing Method Validation Verification检验方法验证的确认 (54)8.8 Raw Material and Excipient Verification原辅料确认 (54)9.Sampling Plan and Evaluation Criteria取样计划及评估标准 (56)10.Sample Coding Method样品编码原则 (70)11.Process Validation Test Execution 工艺验证执行 (72)11.1 Liquid Preparation 液体配制 (72)11.2 Cell Resurrection and Passage细胞复苏及传代 (74)11.3 Harvest liquid test 收获液检测 (81)11.4 Clarification Filtration Efficacy Test 澄清过滤效果检测 (83)11.5 UF Concentration 1 Efficacy Test超滤浓缩1效果检测 (83)11.6 Ammonium sulfate precipitation efficacy test 硫酸铵沉淀效果检测 (84)11.7 Potassium bromide extraction efficacy test 溴化钾提取效果检测 (85)11.8 First density gradient centrifugation efficacy test 一次密度梯度离心效果检测 (86)11.9 Second density gradient centrifugation efficacy test 二次密度梯度离心效果检测 (87)11.10 UF Concentration 2 Efficacy Test 超滤浓缩2效果检测 (88)11.11 Chromatography purification product test 层析纯化产物检测 (90)12.Bulk Determination原液检验 (92)13.Process Validation Summarization工艺验证总结 (93)14.PV Report工艺验证报告 (94)14.1 Process Validation Report 工艺验证报告 (94)14.2 Process Validation Analysis and Evaluation 工艺验证分析与评价 (94)15.Requirements on Execution Records 执行记录要求 (95)16.Deviation Handling 偏差处理 (95)17.Change Handling 变更处理 (95)18.Test Form测试表 (96)表格1 缩略语 (9)表格2原辅料质量标准表 (11)表格3物料消耗表1 (21)表格4物料消耗表2 (21)表格5所用液体配料表 (22)表格6生产车间一览表 (26)表格7主要生产设备一览表 (29)表格8工艺风险分析表 (33)表格9工艺时间表 (49)表格10取样计划表 (56)表格11样品编码原则 (70)表格12配液取样检测信息表 (72)表格13复苏和传代取样表 (74)表格14复苏和传代样品编码 (80)表格15收获液标准 (81)表格16澄清过滤标准 (83)表格17超滤浓缩1标准 (83)表格18硫酸铵沉淀标准 (85)表格19溴化钾提取标准 (86)表格20一次密度梯度离心标准 (87)表格21二次密度梯度离心标准 (88)表格22超滤浓缩2标准 (89)表格23纯化产物标准 (90)表格24原液标准 (92)表格25测试表列表 (96)1. Purpose目的This purpose of this process validation is to provide documented evidence to show that the combination of the personnel, materials, equipment, methods, environmental conditions and the other related utilities XXX Co., LTD (XXX) can ensure the consistent production of products conforming to the enterprise internal standards and the national standards, and the processes are reliable and conforming to the GMP requirements. The process validation and the test results are to be documented based on this validation protocol.本工艺验证用于提供文件化的证据，证明XXX疫苗一室生产XXX原液的人员、材料、设备、方法、环境条件以及其它有关公用设施的组合可以始终如一的生产出符合企业内控标准及国家法定标准的产品，工艺稳定可靠，符合GMP要求，工艺验证的过程和检查的结果将按照该验证方案进行记录。

1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。

3. D e r i v a t i o n a l b r e a k d o w n
Sproat's MORL~r rules are divided into two main subgroups: ME,,code, which are (morpho)phonological mappings, and Mspell, which are "autonomous spelling rules" or rules reflecting the conventions of the orthography itself. As the rules are regular, they can simply be composed together, and the result can be encoded as a finite-state transducer and applied bidirectionally.
MORL--*P ~ MEncode o MSpel I
This distinction is easy to defend. Mspell covers phenomena such as the conventions for representing phonologically long vowels in Dutch orthography, and parallel examples in other orthographies are easy to find. Sproat then makes another, less-obvious, distinction, splitting up Mspell, so that aspellrnap is a mapping, encoded as a finite-state transducer, but MSpellconstrain encoded is as a regular-language filter. Again, the two subsystems are regular and are composed together.
In the current academic world, derivational approaches to phonology are out of fashion, overshadowed by Optimality Theory (Prince and Smolensky 1993) and other mono-stratal models. The Two-Level finite-state model of computational morphology (Koskenniemi 1983) also eschews derivation. Nevertheless, a grelogy and morphology continues to be done with derivational cascades of rewrite rules, which Johnson (1972) and Kaplan and Kay (1994) showed to be only
464
Book Reviews finite-state in power. Computational linguists from this tradition have challenged OT (Karttunen 1998; Gerdemann and van Noord 2000), assuming that as long as linguists stay within finite-state power, they can construct their grammars flatly or derivationally as they find most convenient and perspicuous. The interesting contribution of Sproat to this ongoing debate is his argument that the derivation has explanatory power, modeling "orthographical depth." In this model, English orthography reflects a fairly deep ORL, Russian a shallower one, Belarusian a level slightly shallower than Russian, Spanish quite shallow, and so on. Sproat's claim that his derivations are regular is testable and potentially disprovable; he is forthright in discussing challenges and apparent counterexamples. The second claim, that an orthography always represents a consistent level of representation, and not sometimes one level and sometimes another, is a stronger claim, especially given the messy history of borrowing and adapting scripts. Scripts, as Sproat himself points out, are contingent "artifacts" or technologies, not something inherently human like phonology. He argues credibly, however, that a viable everyday writing system must bear a "sensible relationship" to the language it represents, that we can expect a natural pressure in the direction of consistency.
Computational Linguistics
Volume 27, Number 3
A Computational Theory of Writing Systems Richard Sproat
(AT&T Laboratories) Cambridge University Press (Studies in natural language processing, edited by Branimir Boguraev), 2000, xviii+236 pp; hardbound, ISBN 0-521-66340-7, $59.95
Mspell =MSpellma p o Id(Mspellco.st~.,~i,,)
As composition is defined only for transducers, the composition must technically involve the identity relation on the filter as shown. The examples of MSpellco,,s,rai involve alternate representations that appear in comn plementary distribution in the surface orthography. In Malagasy, the vowel / i / is represented as either (i) or (y), with (i) occurring only in nonfinal position and (y) occurring only at the end of words. If MEncode contains the rule
2. Derivational geometry
Sproat provides very little in the way of an introduction to writing systems; after pointing the reader to reliable sources, he jumps boldly into his model of reading devices. The geometry of his model is traditional derivational phonology, involving a mapping through various levels from an underlying representation U to the surface phonology. Sproat makes two major claims: 1. . Consistency: Every orthography corresponds to a single Orthographically Relevant Level (ORL) in the derivation; and Regularity: MOaL~r, the mapping from the ORL to F, the spelling itself, is regular.
Reviewed by Kenneth R. Beesley Xerox Research Centre Europe
1. Introduction
Interest in the history, theory, and classification of writing systems has never been higher, and the last decade saw the publication of several worthy books on the subject, including the formidable one by Daniels and Bright (1996). At the same time, under the Unicode initiative, there has been solid progress in the definition of and, finally, the implementation of standards for computer encoding and rendering of scripts used around the world. However, the implications of this multi-lingual revolution for computational linguistics beyond the level of word-processing have not been well explored, and Richard Sproat's book A Computational Theory of Writing Systems is a welcome contribution. In particular, Sproat's observations and theories are motivated and tested by years of work at AT&T on text-to-speech systems. This is not the first or the last time that the rigor of computational application, and the massive practical testing that it allows, will come back to shape theory.