首页> 外文会议>Innovate integrate amp; invigorate >Systems Engineering MegaPractices - Identification, Assessment and Redundancy By Object Analysis and Modeling
【24h】

Systems Engineering MegaPractices - Identification, Assessment and Redundancy By Object Analysis and Modeling

机译:系统工程实践-通过对象分析和建模进行识别,评估和冗余

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

摘要

What happens when practices and disciplines overlap? - Wasted efforts, turf battles, redefinition of lifecycle models based on different management, engineering, manufacturing, finance, maintenance and support viewpoints. In short, a proliferation of the 'way we do things around here'.rnSystems engineering has become a set of complex processes that are difficult to implement and improve. Too often, either sub processes are developed for lower tier Integrated Product Team performance or for large enterprise level practices which are promoted as 'Best Practices' (Heibler 1998). Most often, the linkage at different levels of abstraction is very difficult to see, much less apply. These are difficult to implement for management of larger and smaller projects. Also many projects in an enterprise are at different stages of development, which makes process improvement across the organization difficult to assess and implement.rnLifecycle 'Practices' and 'Standards' are generated as panaceas for good systems engineering and are evidenced as:rn1. Systems integration,rn2. Systems design,rn3. Systems validation,rn4. Software engineering,rn5. Design to Cost (DTC),rn6. Design for Manufacture and Assembly (DFMA),rn7. Cost as an independent variable (CAIV),rn8. Affordability,rn9. Quality Function Deployment (QFD),rn10. Supply Chain Management,rn11. Robust Design,rn12. Risk management,rn13. Requirements management,rn14. Time-to-market, andrn15. Just-in-Time ManufacturingrnThe purpose of this paper is to show how a set of capability improvement models (SW-CMM 1995, SECM-EIA731 1998, CMMI 2000, ISO 9001 1994, ISO 15504 1998) and process definition standards (IEEE1220 1998, EIA-632 1998, ISO 15288 2000, and ISO12207 1995) can be used to test these megapractices for commonality and redundancy.rnObject oriented (OO) techniques are be used to: 1) identify the validity of megaprocesses, 2) determine which processes belong to megapractices and are common throughout the chosen set, and 3) assist assessors and process improvement practitioners in selection and optimization of best set of practices for the top level enterprise down to team level performance. Conclusions from this analysis are:rn1. Systems Integration includes Design Reviews,rnIntegrated Schedules, and Integrated Planningrn2. CAIV includes Trade Studies, Requirements,rnRisk, Cost, Performance (TPMs), and Decision Makingrn3. Software Development is a large subset ofrnSystems Integration in software-intensive systems.
机译:当实践和学科重叠时会发生什么? -根据不同的管理,工程,制造,财务,维护和支持观点,浪费精力,争夺地盘,重新定义生命周期模型。简而言之,“我们在这里做事的方式”的泛滥。系统工程已变成一组难以实施和改进的复杂过程。很多时候,要么开发子流程来实现较低级别的集成产品团队绩效,要么开发大型企业级实践,这些实践被推广为“最佳实践”(Heibler 1998)。通常,很难看到不同抽象级别的链接,更不用说了。这些对于大型项目和小型项目的管理都很难实现。此外,企业中的许多项目处于不同的开发阶段,这使得整个组织的流程改进难以评估和实施。rn生命周期“实践”和“标准”是良好系统工程的灵丹妙药,并被证明为:rn1。系统集成,rn2。系统设计,RN3。系统验证,rn4。软件工程,rn5。设计成本(DTC),rn6。制造和装配设计(DFMA),rn7。成本作为自变量(CAIV),rn8。可负担性,rn9。质量功能部署(QFD),rn10。供应链管理,rn11。稳健的设计,rn12。风险管理,rn13。需求管理,rn14。上市时间,和rn15。即时制造rn本文旨在展示一套能力改进模型(SW-CMM 1995,SECM-EIA731 1998,CMMI 2000,ISO 9001 1994,ISO 15504 1998)和过程定义标准(IEEE1220 1998, EIA-632 1998,ISO 15288 2000和ISO12207 1995)可用于测试这些大实践的通用性和冗余性。面向对象(OO)技术用于:1)识别大过程的有效性,2)确定哪些过程属于3)协助评估人员和过程改进从业人员为顶层企业(直至团队绩效)选择和优化最佳实践集。分析得出的结论为:系统集成包括设计评审,集成计划表和集成计划。 CAIV包括贸易研究,需求,风险,成本,绩效(TPM)和决策制定3。软件开发是软件密集型系统中系统集成的很大子集。

著录项

相似文献

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

客服邮箱:kefu@zhangqiaokeyan.com

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

  • 服务号