R. Recio, Claudia A. Salzberg, J. Palm, Carol Machuca
{"title":"在IO需求过程中利用协作技术","authors":"R. Recio, Claudia A. Salzberg, J. Palm, Carol Machuca","doi":"10.1109/RE.2008.62","DOIUrl":null,"url":null,"abstract":"The process of clearly defining a strategic roadmap that anticipates and sets industry directions depends on requirements input from a diverse set of folks and disciplines. The input spans several key factors: customer, market and application workloads and requirements; basic and derivative technology trends; competitor directions; business model innovations; applicable new and substitute technologies; riskanalysis; and the team’s capabilities. To perform this level of analysis requires dynamic collaboration by a diverse group of thought leaders, as well as input from the wider community that will share the responsibility for carrying out the mission from start through release and into field support. When the influx of feedback and ideas is not limited or restricted, more perspectives and backgrounds can be leveraged to make the more comprehensive predictions and fine tuning that are required of a cohesive strategic roadmap. In many cases this type of process will not lead to consensus, in which case the thought leader(s) must weigh the factors and make a decision. This paper will provide an overview of the teams involved in creating IBM’s Systems IO and DataCenter Networking (DCN) technologies and products. It will describe the roles each team plays in turning requirements into products. A key part of this processis the IO Technical Community (IOTC), which provides a collaboration medium that spans all ofthese teams. It will also describe the technologies and methods used by these teams. It ends with a summary of the keys to leveraging an active technical community in turning requirements into products.","PeriodicalId":340621,"journal":{"name":"2008 16th IEEE International Requirements Engineering Conference","volume":"2 9","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2008-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":"{\"title\":\"Leveraging Collaborative Technologies in the IO Requirements Process\",\"authors\":\"R. Recio, Claudia A. Salzberg, J. Palm, Carol Machuca\",\"doi\":\"10.1109/RE.2008.62\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"The process of clearly defining a strategic roadmap that anticipates and sets industry directions depends on requirements input from a diverse set of folks and disciplines. The input spans several key factors: customer, market and application workloads and requirements; basic and derivative technology trends; competitor directions; business model innovations; applicable new and substitute technologies; riskanalysis; and the team’s capabilities. To perform this level of analysis requires dynamic collaboration by a diverse group of thought leaders, as well as input from the wider community that will share the responsibility for carrying out the mission from start through release and into field support. When the influx of feedback and ideas is not limited or restricted, more perspectives and backgrounds can be leveraged to make the more comprehensive predictions and fine tuning that are required of a cohesive strategic roadmap. In many cases this type of process will not lead to consensus, in which case the thought leader(s) must weigh the factors and make a decision. This paper will provide an overview of the teams involved in creating IBM’s Systems IO and DataCenter Networking (DCN) technologies and products. It will describe the roles each team plays in turning requirements into products. A key part of this processis the IO Technical Community (IOTC), which provides a collaboration medium that spans all ofthese teams. It will also describe the technologies and methods used by these teams. It ends with a summary of the keys to leveraging an active technical community in turning requirements into products.\",\"PeriodicalId\":340621,\"journal\":{\"name\":\"2008 16th IEEE International Requirements Engineering Conference\",\"volume\":\"2 9\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2008-09-08\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"0\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2008 16th IEEE International Requirements Engineering Conference\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/RE.2008.62\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2008 16th IEEE International Requirements Engineering Conference","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/RE.2008.62","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 0
摘要
明确定义预测和设置行业方向的战略路线图的过程取决于来自不同人员和规程的需求输入。输入涉及几个关键因素:客户、市场和应用程序工作负载和需求;基础和衍生技术趋势;竞争对手的方向;商业模式创新;适用的新技术和替代技术;riskanalysis;以及团队的能力。要执行这种级别的分析,需要不同思想领袖群体的动态协作,以及来自更广泛的社区的投入,这些社区将分担从开始到发布到现场支持的执行任务的责任。当反馈和想法的涌入不受限制时,可以利用更多的观点和背景来做出更全面的预测和微调,这是一个有凝聚力的战略路线图所需要的。在许多情况下,这种类型的过程不会导致共识,在这种情况下,思想领袖必须权衡各种因素并做出决定。本文将概述参与创建IBM Systems IO和数据中心网络(DataCenter Networking, DCN)技术和产品的团队。它将描述每个团队在将需求转化为产品时所扮演的角色。这个过程的一个关键部分是IO技术社区(IOTC),它提供了一个跨越所有这些团队的协作媒介。它还将描述这些团队使用的技术和方法。最后总结了利用活跃的技术社区将需求转化为产品的关键。
Leveraging Collaborative Technologies in the IO Requirements Process
The process of clearly defining a strategic roadmap that anticipates and sets industry directions depends on requirements input from a diverse set of folks and disciplines. The input spans several key factors: customer, market and application workloads and requirements; basic and derivative technology trends; competitor directions; business model innovations; applicable new and substitute technologies; riskanalysis; and the team’s capabilities. To perform this level of analysis requires dynamic collaboration by a diverse group of thought leaders, as well as input from the wider community that will share the responsibility for carrying out the mission from start through release and into field support. When the influx of feedback and ideas is not limited or restricted, more perspectives and backgrounds can be leveraged to make the more comprehensive predictions and fine tuning that are required of a cohesive strategic roadmap. In many cases this type of process will not lead to consensus, in which case the thought leader(s) must weigh the factors and make a decision. This paper will provide an overview of the teams involved in creating IBM’s Systems IO and DataCenter Networking (DCN) technologies and products. It will describe the roles each team plays in turning requirements into products. A key part of this processis the IO Technical Community (IOTC), which provides a collaboration medium that spans all ofthese teams. It will also describe the technologies and methods used by these teams. It ends with a summary of the keys to leveraging an active technical community in turning requirements into products.