【24h】

Track 4 background and purpose

机译:跟踪4的背景和目的

获取原文
获取原文并翻译 | 示例

摘要

Track 4 (Ada in Practice) was instituted as part of TRI-Ada '89 because few formal paper submissions had dealt with lessons learned from actual Ada usage in real-world, for-profit projects. The success of Track 4 sessions at TRI-Ada '89 led to continuation this year. The purpose of Track 4 is in-depth presentation of Ada development efforts from the perspective of systems engineering, software engineering, design, compiler implementations, tool capabilities/deficiencies, personnel, and policy decisions/rationale. The focus is on aggregate project decisions, tradeoffs, and rationale. Track 4 also differs from other conference sessions in that each presentation is 90 minutes long and extensive audience interaction is a part of each session.

rn

The Track 4 concept acknowledges that the current "system" for writing and clearing papers may place obstacles in the way of obtaining papers which are reflective of real experience. For example,rn

personnel in front-line positions on critical programs are generally too busy to generate formal papers;

rn

the DoD/contractor approval cycle must be complied with, and

rn

companies must deal with the issue of competition sensitivity when putting activities and decisions into a formally written paper.

rn

rn

Rather than describing programs, Track 4 presentations focus very strongly on alternatives/rationale for design decisions; in other words, the "why," not the "what." Track 4 presentations are selected based on the degree to which they contain specific rationale for decisions on the following subjects:rn

Difficulties encountered

rn

Substantive technical issues

rn

Quantitative system data

rn

Hardware architecture

rn

Software architecture

rn

Tradeoffs among hardware, systems software and applications software

rn

System size and complexity determination

rn

Compilerand tool problems

rn

Usefulness of management techniques

rn

Why Ada was beneficialot beneficial

rn

What would be done differently next time

rn

rn

Each Track 4 presentation is the result of cooperative effort between the selected project and a member of the TRI-Ada '90 staff known as a rapporteur. The rapporteur works with the project over a period of months to:rn

optimize the presentation's targeting of the criteria for these high-potential sessions,

rn

insure the potential for audience interaction,

rn

and moderate the session at the conference

rn

rn

The success of Track 4 sessions is, in no small part, due to the work of the rapporteurs; their efforts are hereby acknowledged.

机译:

第4轨(实践中的Ada)是TRI-Ada '89的一部分,因为很少有正式的论文提交来处理从现实世界中以营利为目的的项目中从Ada的实际使用中吸取的教训。今年在TRI-Ada '89上举办的Track 4会议取得了成功。专题4的目的是从系统工程,软件工程,设计,编译器实施,工具功能/不足,人员和政策决策/合理性的角度深入介绍Ada开发工作。重点是总的项目决策,权衡和基本原理。轨道4与其他会议会议的不同之处还在于,每个演示文稿的时长为90分钟,并且每次会议的一部分都是广泛的观众互动。 rn

轨道4的概念承认当前的书写和清除“系统”论文可能会阻碍获取真实经验的论文。例如,关键程序前线位置的 rn

人员通常太忙而无法生成正式文件; rn

DoD /承包商 rn

公司必须遵守批准周期,并且在将活动和决定写入正式书面文件时必须处理竞争敏感性问题。 rn

rn

Track 4演示不是针对描述程序,而是非常侧重于设计决策的替代方案/合理性。换句话说,“为什么”,而不是“什么”。选择第4条演示文稿的方式是根据它们在以下主题上做出决策的具体依据的程度: rn

遇到的困难 rn

实质性技术问题 rn

定量系统数据 rn

硬件体系结构 rn < P>软件体系结构 rn

硬件,系统软件和应用软件之间的权衡 rn

系统大小和复杂度确定 rn

Compilerand工具问题 rn

管理技术的实用性 rn

为什么Ada有利/无益 rn

下次会做些什么 rn

rn

第4步的每个演示文稿都是所选项目与TRI-Ada '90职员(即报告员)之间共同努力的结果。报告员在几个月的时间内与该项目合作,以: rn

优化演示文稿针对这些高潜力会议的标准, rn < P>确保观众互动的潜力 rn

并主持会议会议 rn

rn

第4场会议的成功在很大程度上要归功于报告员的工作;特此感谢他们的努力。

著录项

相似文献

  • 外文文献
  • 中文文献
  • 专利
获取原文

客服邮箱:kefu@zhangqiaokeyan.com

京公网安备:11010802029741号 ICP备案号:京ICP备15016152号-6 六维联合信息科技 (北京) 有限公司©版权所有
  • 客服微信

  • 服务号