软件产品线集成技术研究
|
摘要
随着软件产品线的集成产品开发模式被越来越多的软件开发组织所采用，软件集成技术的应用越来越引起人们的关注。集成包括了将小组工作结果集成到子系统，及将子系统集成为完整系统等不同级别、不同阶段的开发活动。进行集成的目的，在于得到可靠的软件构造版本。
美国卡耐基·梅隆大学软件工程研究所于20世纪90年代末提出了软件产品线实践框架(PLP)，在PLP产品开发关键实践中，软件系统集成(SSI)是一个关键活动。对于产品比较多、依赖关系比较复杂的产品线，为实现产品集成的正确性、完整性、一致性、稳定性和可测试性，需要提供面向软件产品线的集成技术的整体解决方案。
本文基于ERP产品线SSI的实践，提出集成技术框架(ITF)。ITF提供了SSI相关的集成技术、方法和过程等方面的综合支撑，并可以将其有机地结合起来，可以根据特定软件产品线的特点，或集成技术、工具等方面的最新进展，对框架进行裁剪、扩展，并基于ITF建立适合软件产品线需要的SSI过程和工具平台。
集成技术框架(ITF)包括了集成依据、集成前提、集成事实、集成规则、集成结论等五个关键组成部分。可以采用知识库的方式，实例化ITF并将ITF中五个关键组成部分有机组织起来，形成集成知识库(IKB)，可以通过对集成事实和集成规则的匹配，及集成前提和集成规则的推导，选择与构造工具适应的构造脚本模板，最后自动生成构造脚本。本文结合ERP软件的一个典型应用场景，即商业批发企业的物流过程，对其产品线工程和产品线SSI技术的应用进行实践，并基于ITF开发一套适用于ERP产品线集成的集成支撑工具。
More and more organizations begin to adopt the software product line approach for developing systems, and they are realizing the importance of the integration techniques. Integration is done at several levels and stages of the software development lifecycles: integrating the work of a team working in the same implementation subsystem, and integrating subsystems into a complete system. The goal of integration is to produce a qualified build.
In the late 1990's, the Carnegie Mellon Software Engineering Institute (SEI) launched a technical initiative, the Product Line Practice Initiative, to help facilitate and accelerate the transition to sound software engineering practices using a product line approach. Software System Integration (SSI) is one of key practice areas described in the Framework for Software Product Line Practice (PLP) which was published by the SEI. A product line oriented total solution is needed to keep the correctness, completeness, consistentency, stability and testability of the system integration, especially to those large product lines with complex dependency releations.
This thesis synthesizes the practices in an ERP Product Line, and presents the concept of the Integration Technique Framework (ITF). The Integration Technique Framework provides integration techniques infrastructures to the SSI activities, and can be tailored to satisfy the requirements of specific product line, or be extended to adopt the recent developments in the integration techniques and tools.
ITF involves five essential components: (1) Integration References, (2) Integration Premises, (3) Integration Facts, (4) Integration Rules, and (5) Integration Consequences. The knowledgebase approach can be used to instantiate the ITF and organize these components into the Integration KnowledgeBase (IKB). Experts can use IKB to match Integration Facts with Integration Rules, reason about Integration Premises and Integration Rules, and finally create the build scripts automatically.
This thesis summarizes the practices in an ERP software product line, and provides a
美国卡耐基·梅隆大学软件工程研究所于20世纪90年代末提出了软件产品线实践框架(PLP)，在PLP产品开发关键实践中，软件系统集成(SSI)是一个关键活动。对于产品比较多、依赖关系比较复杂的产品线，为实现产品集成的正确性、完整性、一致性、稳定性和可测试性，需要提供面向软件产品线的集成技术的整体解决方案。
本文基于ERP产品线SSI的实践，提出集成技术框架(ITF)。ITF提供了SSI相关的集成技术、方法和过程等方面的综合支撑，并可以将其有机地结合起来，可以根据特定软件产品线的特点，或集成技术、工具等方面的最新进展，对框架进行裁剪、扩展，并基于ITF建立适合软件产品线需要的SSI过程和工具平台。
集成技术框架(ITF)包括了集成依据、集成前提、集成事实、集成规则、集成结论等五个关键组成部分。可以采用知识库的方式，实例化ITF并将ITF中五个关键组成部分有机组织起来，形成集成知识库(IKB)，可以通过对集成事实和集成规则的匹配，及集成前提和集成规则的推导，选择与构造工具适应的构造脚本模板，最后自动生成构造脚本。本文结合ERP软件的一个典型应用场景，即商业批发企业的物流过程，对其产品线工程和产品线SSI技术的应用进行实践，并基于ITF开发一套适用于ERP产品线集成的集成支撑工具。
More and more organizations begin to adopt the software product line approach for developing systems, and they are realizing the importance of the integration techniques. Integration is done at several levels and stages of the software development lifecycles: integrating the work of a team working in the same implementation subsystem, and integrating subsystems into a complete system. The goal of integration is to produce a qualified build.
In the late 1990's, the Carnegie Mellon Software Engineering Institute (SEI) launched a technical initiative, the Product Line Practice Initiative, to help facilitate and accelerate the transition to sound software engineering practices using a product line approach. Software System Integration (SSI) is one of key practice areas described in the Framework for Software Product Line Practice (PLP) which was published by the SEI. A product line oriented total solution is needed to keep the correctness, completeness, consistentency, stability and testability of the system integration, especially to those large product lines with complex dependency releations.
This thesis synthesizes the practices in an ERP Product Line, and presents the concept of the Integration Technique Framework (ITF). The Integration Technique Framework provides integration techniques infrastructures to the SSI activities, and can be tailored to satisfy the requirements of specific product line, or be extended to adopt the recent developments in the integration techniques and tools.
ITF involves five essential components: (1) Integration References, (2) Integration Premises, (3) Integration Facts, (4) Integration Rules, and (5) Integration Consequences. The knowledgebase approach can be used to instantiate the ITF and organize these components into the Integration KnowledgeBase (IKB). Experts can use IKB to match Integration Facts with Integration Rules, reason about Integration Premises and Integration Rules, and finally create the build scripts automatically.
This thesis summarizes the practices in an ERP software product line, and provides a
引文
[1] Rational. Rational unified process (version 2003) [CD]. IBM Corp, 2003-06.
[2] Mark C Paulk, Bill Curtis, Mary Beth Chrissis, Charles V Weber. Capability maturity model for software, version 1.1 [EB/OL]. http://www.sei.cmu.edu/publications/documents/93.reports/93.tr.024.html, 2005-11-30.
[3] James Withey. Investment analysis of software assets for product lines [EB/OL]. http://www.sei.cmu.edu/publications/documents/96.reports/96.tr.010.html, 2005-02-22.
[4] Martin Fowler, Matthew Foemmel. Continuous Integration [CD]. ThoughtWorks, 2002
[5] David L. Parnas. On the Design and Development of Program Families [J]. IEEE Transactions on Software Engineering, 1976, SE-2.
[6] Kyo C. Kang, Sholom G. Cohen, James A. Hess, William E. Novak, A. Spencer Peterson. Feature-Oriented Domain Analysis (FODA) Feasibility Study [EB/OL]. http://www.sei.cmu.edu/publications/dociunents/90.reports/90.tr.021.html, 2005-2-22.
[7] Will Tracz, Lou Coglianese. Domain-Specific Software Architecture Engineering Process Guidelines (Version 2.1) [M]. IBM Corp, 1994.
[8] Ruben Prieto-Diaz. Domain Analysis: An Introduction [J]. Software Engineering Notes, 1990,15(2).
[9] Paul C. Clements, Linda M. Northrop. A Framework for Software Product Line Practice Version 2.0 [EB/OL]. http://www.sei.cmu.edu/productlines/framework. htmL 2005-01-25.
[10] Paul C Clements, Linda M Northrop. A framework for software product line practice version 4.2 [EB/OL]. http://www.sei.cmu.edu/productlines/framework.html, 2005-01-25.
[11] Sholom Cohen. Product Line State of the Practice Report [EB/OL]. http://www.sei .cmu .edu/publications/documents/02 .reports/02tn017 .html, 2005-9-29.
[12] Doug McIlroy. Mass produced software components [C]. //Software engineering concepts and techniques, 1968 NATO conference on software engineering. New York, 1969.
[13] F. Bachmann, L. Bass, C. Buhman, S. Comella-Dorda, F. Long, J. Robert, R. Seacord, K. Wallnau. Volume II: Technical Concepts of Component-Based Software Engineering [EB/OL]. http://www.sei.cmu.edu/publications/documents/00.reports/00tr008.html, 2005-9-29.
[14] John Foreman, Kimberly Brune, Patricia McMillan, Robert Rosenstein. Software Technology Review [EB/OL]. CMU/SEI, 1997-7.
[15] Frederick Hayes-Roth. Architecture-Based Acquisition and Development of Software, Guidelines and Recommendations from the ARPA DSSA Program [DB/OL]. Teknowledge Federal System, 1994-2.
[16] ANSI/IEEE Std 1471-2000, IEEE Recommended Practice for Architectural Description of Software-Intensive Systems -Description [S]. 2000-10.
[17] K Czarnecki, U Eisenecker. Generative programming [M]. New York: Addison-Wesley, 2000.
[18] 董乃文．软件产品线中BOM和工艺路线技术的应用[J]．山东师范大学学报(自然科学版)，2006年第2期．
[19] ANSI/IEEE Std 610.12-1990, IEEE Standard Glossary of Software Engineering Terminology [S]. 1991-2.
[20] C. Burrows, G. W. George, Susan Dart. Configuration Management [M]. Ovum Ltd., 1996.
[21] Kurt C Wallnau. Volume Ⅲ: A technology for predictable assembly from certifiable components [EB/OL]. http://www.sei.cmu.edu/publications/documents/03.reports /03tr009.html, 2005-09-29.
[22] 董乃文．“软件产品线中的项目组织和管理Project Management and Organization in the Software Product Line”[C]．//第二届中国项目管理国际会议论文集．北京，2004-5．
[23] John D. McGregor. Preparing for automated derivation of products in a software product line [EB/OL]. http://www.sei.cmu.edu/publications/documents/05.reports /05tr017.html, 2006-02-15.
[2] Mark C Paulk, Bill Curtis, Mary Beth Chrissis, Charles V Weber. Capability maturity model for software, version 1.1 [EB/OL]. http://www.sei.cmu.edu/publications/documents/93.reports/93.tr.024.html, 2005-11-30.
[3] James Withey. Investment analysis of software assets for product lines [EB/OL]. http://www.sei.cmu.edu/publications/documents/96.reports/96.tr.010.html, 2005-02-22.
[4] Martin Fowler, Matthew Foemmel. Continuous Integration [CD]. ThoughtWorks, 2002
[5] David L. Parnas. On the Design and Development of Program Families [J]. IEEE Transactions on Software Engineering, 1976, SE-2.
[6] Kyo C. Kang, Sholom G. Cohen, James A. Hess, William E. Novak, A. Spencer Peterson. Feature-Oriented Domain Analysis (FODA) Feasibility Study [EB/OL]. http://www.sei.cmu.edu/publications/dociunents/90.reports/90.tr.021.html, 2005-2-22.
[7] Will Tracz, Lou Coglianese. Domain-Specific Software Architecture Engineering Process Guidelines (Version 2.1) [M]. IBM Corp, 1994.
[8] Ruben Prieto-Diaz. Domain Analysis: An Introduction [J]. Software Engineering Notes, 1990,15(2).
[9] Paul C. Clements, Linda M. Northrop. A Framework for Software Product Line Practice Version 2.0 [EB/OL]. http://www.sei.cmu.edu/productlines/framework. htmL 2005-01-25.
[10] Paul C Clements, Linda M Northrop. A framework for software product line practice version 4.2 [EB/OL]. http://www.sei.cmu.edu/productlines/framework.html, 2005-01-25.
[11] Sholom Cohen. Product Line State of the Practice Report [EB/OL]. http://www.sei .cmu .edu/publications/documents/02 .reports/02tn017 .html, 2005-9-29.
[12] Doug McIlroy. Mass produced software components [C]. //Software engineering concepts and techniques, 1968 NATO conference on software engineering. New York, 1969.
[13] F. Bachmann, L. Bass, C. Buhman, S. Comella-Dorda, F. Long, J. Robert, R. Seacord, K. Wallnau. Volume II: Technical Concepts of Component-Based Software Engineering [EB/OL]. http://www.sei.cmu.edu/publications/documents/00.reports/00tr008.html, 2005-9-29.
[14] John Foreman, Kimberly Brune, Patricia McMillan, Robert Rosenstein. Software Technology Review [EB/OL]. CMU/SEI, 1997-7.
[15] Frederick Hayes-Roth. Architecture-Based Acquisition and Development of Software, Guidelines and Recommendations from the ARPA DSSA Program [DB/OL]. Teknowledge Federal System, 1994-2.
[16] ANSI/IEEE Std 1471-2000, IEEE Recommended Practice for Architectural Description of Software-Intensive Systems -Description [S]. 2000-10.
[17] K Czarnecki, U Eisenecker. Generative programming [M]. New York: Addison-Wesley, 2000.
[18] 董乃文．软件产品线中BOM和工艺路线技术的应用[J]．山东师范大学学报(自然科学版)，2006年第2期．
[19] ANSI/IEEE Std 610.12-1990, IEEE Standard Glossary of Software Engineering Terminology [S]. 1991-2.
[20] C. Burrows, G. W. George, Susan Dart. Configuration Management [M]. Ovum Ltd., 1996.
[21] Kurt C Wallnau. Volume Ⅲ: A technology for predictable assembly from certifiable components [EB/OL]. http://www.sei.cmu.edu/publications/documents/03.reports /03tr009.html, 2005-09-29.
[22] 董乃文．“软件产品线中的项目组织和管理Project Management and Organization in the Software Product Line”[C]．//第二届中国项目管理国际会议论文集．北京，2004-5．
[23] John D. McGregor. Preparing for automated derivation of products in a software product line [EB/OL]. http://www.sei.cmu.edu/publications/documents/05.reports /05tr017.html, 2006-02-15.