LOGO

产品中心

/
/
-->
/
Product Requirements Engineering
1/1
浏览量:
1000

Product Requirements Engineering

需求的价值并不在于确定相关需求,而在于通过其推动产品开发流程。 Teamcenter 为各种下游功能/特性/产品架构分配需求,同时生成报告、文档和仪表板对需求流程加以管理。 您可以通过熟悉的 Microsoft Office 应用程序(包括 Microsoft Word 和 Excel)直接创建、查看和编辑需求。 借助生命周期集成需求,可在整个产品生命周期内实现“开始集成,保持集成”的开发流程。
1
产品描述

Requirements engineering drives compliant product development

1

Product Requirements Engineering

需求设计事关重大。 需求定义了客户会购买的产品,但仅仅管理需求并不足以打造完善的产品。 您需要通过将需求与产品生命周期相关联来设计需求,这样每个人都可以根据一组正确的已配置需求来制定产品决策。

Teamcenter® 产品生命周期管理 (PLM) 确定各种需求并为各种下游功能/特性/产品架构分配需求,同时生成报告、文档和仪表板对需求流程加以管理。 您可以通过熟悉的 Microsoft® Office 应用程序(包括 Microsoft Word 和 Excel®)直接创建、查看和编辑需求。 Teamcenter 将产品诉求与项目计划相关联,并使用正确的测试、相关证据、历史记录等信息确认和验证 (V&V) 需求。  这种源自 V&V 的需求设计反馈循环提供经验教训并推动产品开发的合规性,确保您可以在整个产品生命周期中“开始集成,保持集成”,确保为您的客户提供合适的产品。

Requirements engineering doesn't simply capture requirements, but it connects requirements with every product decision in the lifecycle. Learn more below.

Report & Specification Generation

借助 Teamcenter 报告功能,您可以快速创建标准需求报告和仪表板视图并生成相应的规格。 可以生成和使用有关需求、可跟踪性、验证、变化、状态、影响分析等方面的报告,以便您全面了解产品开发流程。 报告还可以通过有意义的方式将内容整合在一起。 例如,您可以请求报告显示分配给您的所有需求,以及当前版本的截止日期。

1
1

Requirements Capture & Authoring

借助 Teamcenter Requirements Management 工具,您可通过需求采集和重用功能在整个产品生命周期中融入相应的需求。  需求与标准产品管理流程(包括更改、工作流程等)相关联,并且包含在标准报告和仪表板中,从而使这些需求成为标准管理实践的一部分。  从各种来源采集需求,这些来源包括 Word 文档、PDF 文件、Excel 电子表格、数据交换文件(如 RIF)和其他格式。

Verification & Validation

Teamcenter Requirements 的核实和验证功能将通过捕获核实和验证结果,并将这些结果与要求进行关联同时支持重点测试来实现对要求的闭环管理。 使用 Teamcenter Requirements Management 时,要求已包含在闭环流程中,其中要求与它们的核实和验证 (V&V) 方式紧密关联。 由于 Teamcenter 也包含测试和验证管理,要求也可与验证它们的测试案例紧密关联。

1
1

Apply product configuration to requirements

Because requirements are an integral part of Teamcenter®, requirements can participate in all aspects of your controlled product development process; requirements are subject to the same product lifecycle processes, configurations, variants, change, workflows, access controls, and other standard practices.  For example, setting your product configuration also configures the requirements that apply to that particular version/variant of your product.

Requirements Allocation & Tracelinking

Because requirements are managed in Teamcenter®, they can also link to all aspects of the product definition including: specifications, other requirements, Bill of Materials, program/project tasks, test cases, 1D and 3D models, manufacturing processes, and more.  This brings X-ray vision impact visibility allowing you to see change propagation in ways never before possible.  For example, a warranty issue could trigger a requirement change which in turn could impact/flow to a part, to a test case, to a test set configuration, to manufacturing processes, a PKI target, resources, and more.

1
1

Requirements change

In Teamcenter, requirements can participate in standard change management practices either as a requirement change process or included in product level changes.   So, requirement changes no longer have to be managed separately but can be included with global product change planning/management—no more working from stale requirements after a product change.

Integrate Requirements across PLM and ALM

Cross-domain requirements traceability is a key component of successful product development and the Polarion ALM-Teamcenter interoperability provides the cross-domain requirements traceability that enables product development organizations to successfully develop mechanical and software-driven electronic systems. Providing you with a clearer definition of how software is related to specific product functions you can derive software requirements from product requirements and then to validate that the software developed fulfills both the software and product requirements.

 
未找到相应参数组,请于后台属性模板中添加
暂时没有内容信息显示
请先在网站后台添加数据记录。
暂时没有内容信息显示
请先在网站后台添加数据记录。
搜索
搜索