我说CMMI2.0之产品集成
1461
版权声明
我们非常重视原创文章,为尊重知识产权并避免潜在的版权问题,我们在此提供文章的摘要供您初步了解。如果您想要查阅更为详尽的内容,访问作者的公众号页面获取完整文章。
Product Integration (PI) Summary
Product Integration (PI) is the process of assembling different components into a larger part or a complete deliverable product. This Process Area (PA) includes activities related to the development of an integration strategy, preparation for integration, the integration process itself, post-integration verification and validation, and delivery.
Practice List Summary
- PI 1.1: Solutions are assembled and delivered to the customer, forming a deliverable product from different components.
- PI 2.1: An integration strategy is created, maintained, and followed, which covers integration frequency, methods, and order.
- PI 2.2: An integration environment is established and updated, including tools, hardware, simulators, and testing equipment.
- PI 2.3: Procedures and criteria for integrating solutions and components are developed and updated.
- PI 2.4: Prior to assembly, each component is confirmed to have been properly identified and to operate as per its requirements and design.
- PI 2.5: Assembled components are evaluated to ensure they conform to the solution's requirements and design.
- PI 2.6: Solutions and components are assembled according to the integration strategy, with a strong recommendation for continuous integration and automation.
- PI 3.1: Throughout the solution's lifecycle, interface or connection descriptions are reviewed and updated for coverage, completeness, and consistency.
- PI 3.2: Before assembly, component interfaces or connections are confirmed to comply with their descriptions.
- PI 3.3: Assembled components are evaluated for interface or connection compatibility, ensuring compatibility across various aspects like software, hardware, browsers, and data.
Layman's Explanation
The PI practices involve assembling and delivering a solution to the customer, developing an updated integration strategy and environment, and ensuring all parts work together seamlessly. This includes checking component readiness, evaluating assembled parts, and managing interfaces or connections over the product's entire lifecycle. Continuous integration and automated platforms are highly recommended. Interface management is crucial and involves stakeholder needs, transforming those needs into customer requirements, and ensuring interface or connection requirements are identified, developed, and kept updated.
麦哲思科技任甲林
麦哲思科技(北京)有限公司总经理 敏捷性能合弄模型评估师 认证的Scrum Master 认证的大规模敏捷顾问SPC CMMI高成熟度主任评估师 COSMIC MPC,IAC 成员,中国分部主席
还在用多套工具管项目?
一个平台搞定产品、项目、质量与效能,告别整合之苦,实现全流程闭环。
当下,就是现在。
现在不是过去,现在却是将来。
过去的不可能再回来,沉浸在过去,无论是成功,无论是失败,无论是悲伤,无论是喜悦,无论是庆幸,无论是后悔,历史都已经不可能更改。曾经的好事不会坐等而来,曾经的坏事也不会无缘无故的发生。前者之失,后者之师。历史的经验教训,能够指导现在、指导未来即可。
将来的事尚未发生,但将来是可以掌控的,有因必有果,善因结善果。因,是今天种下的,即使过去曾经做了恶因,从今天开始你种下善因,却可以弥补之
经验管理是依赖于管理者的经验判断,选择、实施各种措施以达成管理目标的管理方式。管理者的经验有丰富与匮乏的区别,经验也有其适用的范围,有时正确,有时又可能错误。正如我们去看中医大夫,有的大夫经验丰富,很容易就能对症下药,对症后见效很快,但是有时也看不准,如果不对症,则吃了3天后可以进行调整,如果调整仍然不到位,说明经验失效了,这个病不是这个大夫所能应对的。有的大夫经验不够,难以对症下药,下药后见效慢或者无效。中医看病也有其一套推理的规则,这套规则可以称为经验法则、启发式规则或统计推断,从A推理出
白皮书上线