基于需求特征的软件可信需求全生命周期管理研究
|
摘要
以通信、存储和计算为核心的信息基础设施已经渗透到政治、经济、军事、文化以及社会生活的各个层面,成为当代生产力发展和人类文明进步的强大动力。软件是信息基础设施的灵魂,随着人们对功能需求的不断增加,软件系统变得日趋庞大和难以驾驶,缺陷和漏洞难以避免,系统越来越脆弱,很多时候不以人们期望的方式工作,经常发生各种故障和失效,给用户带来损失,其原因直接或间接的与软件系统的可信需求相关,这就使得软件企业对可信需求的管理必须贯穿需求的整个生命周期。
可信需求是一种表示软件可信性的特殊的质量需求,由于它与功能需求存在本质的不同,使得软件企业在可信需求与功能需求的管理方法上存在较大的差别。目前,可信需求管理存在的主要问题之一是:缺乏基于可信需求特征对需求获取、选择、实现、变化管理等可信需求管理全生命周期内容的针对性研究。鉴于此,本文从管理学角度,基于可信需求的特征,研究可信需求的全生命周期管理问题,其主要研究工作包括:
①在阐述可信性问题产生、可信软件需求的分类、可信需求的内涵和可信需求特征的基础上,并根据可信需求管理的生命周期,给出了可信需求全生命周期管理框架及其实现方法选择。
②从知识管理角度,将可信需求获取看作知识在软件需求方和软件开发方两个知识主体间的流动,分析了基于知识流动的需求获取机理,并从双因素理论的视角,将影响需求获取过程中知识流动的各种因素归纳为保障因素和促进因素两大类,提出了基于知识流动的可信需求获取“双因素”模型,并指出知识流动的最终效果是由保障因素和促进因素共同决定的,只有把两者结合起来进行管理、控制,才能为可信需求获取过程中的知识流动带来较好的实施成效。
③将可信需求选择看作可信需求的优先实现顺序,基于复杂度约束,提出了一个可信需求选择优先级模型。基于可信需求本体对有向图进行扩展,建立了基于本体的可信需求模型;对设计结构矩阵进行扩展建立了可信活动DSM模型和可信影响度DSM模型;通过改进的搜索算法和灵敏度算法实现模型的转换。模型可以随可信需求的变化作动态变更,并实现可信需求的动态优先级排序,从而提高了可信需求选择的灵活性。
④将可信需求的实现看作可信级别的评定,提出了一个属性权重确定考虑专家群体和决策者主观偏好的可信需求实现评价模型和一种可自动实现可信级别评定的评价方法,能够兼容专家实数型、区间型和语言型等类型的属性权重赋值。发挥了专家群体和决策者在可信需求实现评价过程中的主观能动性,评价结果非常直观、方便并易于理解,能够应对由于专家评价习惯对属性权重赋值的数据类型差异,可操作性较强。
⑤将可信需求变化管理看作可信需求变化的影响分析,提出了一个基于流程的三阶段可信需求变化影响分析框架模型,以指导分析可信需求变化后的影响范围和程度;同时引入水波式、开花式和雪崩式等三种传播模式,用于分析可信需求变化影响呈现的模式,为可信需求变化的管理、控制、利用和评价提供了可靠的依据。
可信需求全生命周期管理研究是一个有重要管理意义的课题,期望通过本文的研究,提高软件企业的可信需求管理能力,降低可信软件开发的风险,提高可信软件产品质量,减少软件企业因可信软件需求管理问题带来的损失,促进我国可信软件产业的快速发展。
Based on the communication, storage and calculation the information infrastructure has penetrated into politics, economy, military, culture and all aspects of social life, and becomes the strong driving force of contemporary productivity development and human civilization progress. Software is the soul of information infrastructure, and as the increasing requirement what people have to function, software system is becoming increasingly large and obstreperous, and its loopholes and defects are unavoidable. Software system is more fragile, sometimes working by the way unexpected by people, and often happening various fault, which has influence to the trustworthy requirement of software system. This makes that the trustworthy requirement management for software company must run through the whole life cycle of requirement.
The trustworthy requirement is a special quality requirement to express the software trustworthiness, because of the difference between it and functional requirements, there exists a big difference between trustworthy requirement and function requirement. At present, one of the main problems existing in trustworthy requirement management: lacking the nichetargeting researches about the whole life cycle of requirement management for example the obtaining, selecting, implement and change management of trustworthy requirement. In view of this, from the angle of management, based on the characteristic of trustworthy requirement, this paper does research on the management problem of the whole lifecycle in trustworthy requirement, and its main research includes the following:
On the basis of expression the appearance of trustworthiness problem, the classification of trustworthy software requirement, and this paper brings out a management framework about the whole lifecycle of trustworthy requirement and the realization method selection based on requirements management lifecyle.
From the viewpoint of knowledge management, this paper looks on trustworthy requirement acquisition as knowledge flow between customer and software developer, and analyzes the mechanism of requirement acquisition based on knowledge flow. Also, from the perspective of the theory of double factors ,after this paper will summarize various factors which affected knowledge flow in the process of requirement acquisition into guarantee factors and promoting factor, the double factors model for requirement acquisition based knowledge flow is presented. The final result of knowledge flow is determined by guarantee factors and promote jointly. The two factors are combined to management and control so as to obtain the good implementation effect for knowledge flow.
After looking on trustworthy requirement selection as the priority order of requirement realization, based on complexity constraint, this paper provides a three phase model and method on priority sorting of trustworthy requirement selection. On the basis of trustworthy requirement ontology, to extend directed graph to establish trustworthy requirement ontology model based on the ontology as well as to extend designing structure matrix to establish trustworthy activity DSM model and trustworthy affected DSM model, also, to realize phase model conversion through improved search algorithm and sensitivity algorithm. With the change of trustworthy requirements the model can be auto-adjusted, and realize the dynamic priority sorting of trustworthy requirement so as to improve the flexibility of trustworthy requirement selection.
The realization of trustworthy requirement is considered trustworthiness level evaluation. Based on subjective preference of experts and decision-makers, a new method of determining attribute weights in multi-attribute group decision-making is presented. This method is also considered the subjective preference of experts on the attribute weights and of decision-makers on the importance awareness of the decision-making importance, and also can be compatible with main date types such as real number, interval number and language number. This method can exert subjective initiative of the expert group and decision-makers. The evaluation result is very intuitive, convenient and easy to understand. Also, this method can handle the difference of the attribute weights assignment data types because of expert evaluation habit.
The change management of trustworthy requirement is considered the impact analysis of trustworthy requirement change. This paper presents a three phase impact analysis framework model for trustworthy requirement change based on process so as to analyze the effect scope and the effect degree after changing the trustworthy requirement. At the same time, three typical propagation modes (ripple propagation, blossom propagation, avalanche propagation) are introduced to study trustworthy requirements change impact mode, and to provide a reliable basis of management, control, and evaluation of trustworthy requirements change.
The research on trustworthy requirement management is an important research topic. It’s expected that through the study, the software trustworthy requirement management ability can improved, the risk of trustworthy software development can reduced , trustworthy software product quality can improved, the loss can reduced because of trustworthy software requirements management problems, and the rapid development of the trustworthy software industry can promoted.
可信需求是一种表示软件可信性的特殊的质量需求,由于它与功能需求存在本质的不同,使得软件企业在可信需求与功能需求的管理方法上存在较大的差别。目前,可信需求管理存在的主要问题之一是:缺乏基于可信需求特征对需求获取、选择、实现、变化管理等可信需求管理全生命周期内容的针对性研究。鉴于此,本文从管理学角度,基于可信需求的特征,研究可信需求的全生命周期管理问题,其主要研究工作包括:
①在阐述可信性问题产生、可信软件需求的分类、可信需求的内涵和可信需求特征的基础上,并根据可信需求管理的生命周期,给出了可信需求全生命周期管理框架及其实现方法选择。
②从知识管理角度,将可信需求获取看作知识在软件需求方和软件开发方两个知识主体间的流动,分析了基于知识流动的需求获取机理,并从双因素理论的视角,将影响需求获取过程中知识流动的各种因素归纳为保障因素和促进因素两大类,提出了基于知识流动的可信需求获取“双因素”模型,并指出知识流动的最终效果是由保障因素和促进因素共同决定的,只有把两者结合起来进行管理、控制,才能为可信需求获取过程中的知识流动带来较好的实施成效。
③将可信需求选择看作可信需求的优先实现顺序,基于复杂度约束,提出了一个可信需求选择优先级模型。基于可信需求本体对有向图进行扩展,建立了基于本体的可信需求模型;对设计结构矩阵进行扩展建立了可信活动DSM模型和可信影响度DSM模型;通过改进的搜索算法和灵敏度算法实现模型的转换。模型可以随可信需求的变化作动态变更,并实现可信需求的动态优先级排序,从而提高了可信需求选择的灵活性。
④将可信需求的实现看作可信级别的评定,提出了一个属性权重确定考虑专家群体和决策者主观偏好的可信需求实现评价模型和一种可自动实现可信级别评定的评价方法,能够兼容专家实数型、区间型和语言型等类型的属性权重赋值。发挥了专家群体和决策者在可信需求实现评价过程中的主观能动性,评价结果非常直观、方便并易于理解,能够应对由于专家评价习惯对属性权重赋值的数据类型差异,可操作性较强。
⑤将可信需求变化管理看作可信需求变化的影响分析,提出了一个基于流程的三阶段可信需求变化影响分析框架模型,以指导分析可信需求变化后的影响范围和程度;同时引入水波式、开花式和雪崩式等三种传播模式,用于分析可信需求变化影响呈现的模式,为可信需求变化的管理、控制、利用和评价提供了可靠的依据。
可信需求全生命周期管理研究是一个有重要管理意义的课题,期望通过本文的研究,提高软件企业的可信需求管理能力,降低可信软件开发的风险,提高可信软件产品质量,减少软件企业因可信软件需求管理问题带来的损失,促进我国可信软件产业的快速发展。
Based on the communication, storage and calculation the information infrastructure has penetrated into politics, economy, military, culture and all aspects of social life, and becomes the strong driving force of contemporary productivity development and human civilization progress. Software is the soul of information infrastructure, and as the increasing requirement what people have to function, software system is becoming increasingly large and obstreperous, and its loopholes and defects are unavoidable. Software system is more fragile, sometimes working by the way unexpected by people, and often happening various fault, which has influence to the trustworthy requirement of software system. This makes that the trustworthy requirement management for software company must run through the whole life cycle of requirement.
The trustworthy requirement is a special quality requirement to express the software trustworthiness, because of the difference between it and functional requirements, there exists a big difference between trustworthy requirement and function requirement. At present, one of the main problems existing in trustworthy requirement management: lacking the nichetargeting researches about the whole life cycle of requirement management for example the obtaining, selecting, implement and change management of trustworthy requirement. In view of this, from the angle of management, based on the characteristic of trustworthy requirement, this paper does research on the management problem of the whole lifecycle in trustworthy requirement, and its main research includes the following:
On the basis of expression the appearance of trustworthiness problem, the classification of trustworthy software requirement, and this paper brings out a management framework about the whole lifecycle of trustworthy requirement and the realization method selection based on requirements management lifecyle.
From the viewpoint of knowledge management, this paper looks on trustworthy requirement acquisition as knowledge flow between customer and software developer, and analyzes the mechanism of requirement acquisition based on knowledge flow. Also, from the perspective of the theory of double factors ,after this paper will summarize various factors which affected knowledge flow in the process of requirement acquisition into guarantee factors and promoting factor, the double factors model for requirement acquisition based knowledge flow is presented. The final result of knowledge flow is determined by guarantee factors and promote jointly. The two factors are combined to management and control so as to obtain the good implementation effect for knowledge flow.
After looking on trustworthy requirement selection as the priority order of requirement realization, based on complexity constraint, this paper provides a three phase model and method on priority sorting of trustworthy requirement selection. On the basis of trustworthy requirement ontology, to extend directed graph to establish trustworthy requirement ontology model based on the ontology as well as to extend designing structure matrix to establish trustworthy activity DSM model and trustworthy affected DSM model, also, to realize phase model conversion through improved search algorithm and sensitivity algorithm. With the change of trustworthy requirements the model can be auto-adjusted, and realize the dynamic priority sorting of trustworthy requirement so as to improve the flexibility of trustworthy requirement selection.
The realization of trustworthy requirement is considered trustworthiness level evaluation. Based on subjective preference of experts and decision-makers, a new method of determining attribute weights in multi-attribute group decision-making is presented. This method is also considered the subjective preference of experts on the attribute weights and of decision-makers on the importance awareness of the decision-making importance, and also can be compatible with main date types such as real number, interval number and language number. This method can exert subjective initiative of the expert group and decision-makers. The evaluation result is very intuitive, convenient and easy to understand. Also, this method can handle the difference of the attribute weights assignment data types because of expert evaluation habit.
The change management of trustworthy requirement is considered the impact analysis of trustworthy requirement change. This paper presents a three phase impact analysis framework model for trustworthy requirement change based on process so as to analyze the effect scope and the effect degree after changing the trustworthy requirement. At the same time, three typical propagation modes (ripple propagation, blossom propagation, avalanche propagation) are introduced to study trustworthy requirements change impact mode, and to provide a reliable basis of management, control, and evaluation of trustworthy requirements change.
The research on trustworthy requirement management is an important research topic. It’s expected that through the study, the software trustworthy requirement management ability can improved, the risk of trustworthy software development can reduced , trustworthy software product quality can improved, the loss can reduced because of trustworthy software requirements management problems, and the rapid development of the trustworthy software industry can promoted.
引文
陈华友, 2004.多属性决策中基于离差最大化的组合赋权方法[J].系统工程与电子技术, 24(2): 194-197.
陈伟,夏建华. 2007.综合主、客观权重信息的最优组合赋权方法[J].数学的实践与认识, 31(1): 17-22.
程平,刘伟,陈艳. 2010.我国可信软件产业的发展现状与应对策略[J].科技进步与对策, 27(3): 51-54.
龚艳斌. 2008.基于方案偏好和部分权重信息的模糊多属性决策方法[J].控制与决策, 23(5): 507-510.
顾新,李久平,王维成. 2006.知识流动、知识链与知识链管理[J].软科学, 2(20): 10-13.
何睿,唐敦兵,薛建彬. 2008.基于设计结构矩阵的工程变更传播研究[J].计算机集成制造系统, 4(14): 656-660.
黄德毅,万江平. 2006.基于SECI的软件需求获取过程中知识转移模式研究[J].研究与发展管理, 27(11): 77-81.
黄蒙,舒风笛,李明树. 2006.一种风险驱动的迭代开发需求优先级排序方法[J].软件学报, 17(12): 2450-2460.
金芝, 2000.基于本体的需求自动获取[J].计算机学报, 5(23): 486-492.
李江,冯勤超. 2006.加性加权法在确定软件需求优先级中的应用[J].现代图书情报技术, (1):79-84.
李顺才,邹珊刚. 2003.知识流动机理的三维分析模式[J]. .研究与发展管理, 15(4): 39-44.
李薇,蒋绍忠. 2005.层次分析法(AHP)在ERP需求分析中的应用[J].技术经济与管理研究, (2): 23-25.
李未, 1999.网络环境下海量信息组织与处理的理论与方法研究[M]. G199903270
李晓明,孙林岩,汪应洛. 2005.基于知识管理的软件需求管理研究[J].研究与发展管理, 17(4): 28-32.
梁梁,熊立,王国华. 2005.王国华.一种群决策中专家客观权重的确定方法[J].系统工程与电子技术, 27(4): 652-655.
林正奎,杨德礼,杨红. 2006.软件开发系统六元结构模型及其复杂性研究[J].系统工程学报, 21(4): 368-374.
刘宏伟,和金生. 2003.“双因素”问题的理论分析[J].南开管理评论, 6(5): 30-35.
刘克,单志广,王戟等. 2008.“可信软件基础研究”重大研究计划综述[J].中国科学基金, (3): 138-151.
刘业政,徐德鹏,姜元春. 2007.多属性群决策中权重自适应调整的方法[J].系统工程与电子技术, 29(1): 45-48.
马永红,周荣喜,李振光. 2007.基于离差最大化的决策者权重的确定方法[J].东北化工大学学报, 34(2): 177-180.
那一沙,夏军. 2007.需求开发的知识转移模型研究[J].中国农机化, 5(53-55.
宋兴光,杨德礼. 2004.基于决策者偏好及赋权法一致性的组合赋权法[J].系统工程与电子技术, 36(9): 1226-1290.
宋兴光,周平. 2010.多属性群决策中决策者权重的确定方法[J].系统工程, 4(5): 84-89.
谭大鹏,霍国庆. 2006.企业知识转移的“双因素”分析[J].研究与发展管理, 12(8): 1-7.
万树平, 2009.区间型多属性决策的心态指标法[J].控制与决策, 24(1): 35-43.
汪应洛,李勖. 2002.知识的转移特性研究[J].系统工程理论与实践, 22(10): 8-11.
王怀民,刘旭东,郎波. 2009.软件可信分级规范[MS]. [EB/OL]http://www.trustie.com/, 2009/6/1-2009/6/12.
王莉,方澜,王方华等. 2007.网络环境下客户参与对产品开发绩效的影响研究-以我国软件企业为例[J].管理工程学报, 21(4): 95-101,135.
王明涛.. 1999.多指标综合评价中权数确定的离差、均方差决策方法[J].中国软科学, (8): 100-101.
王映辉,王立福,张世琨. 2006.一种软件需求变化追踪方法[J].电子学报, 8(34): 1428-1432.
王映辉,张世琨,刘瑜. 2004.基于可达矩阵的软件体系结构演化波及效应分析[J].软件学报, 15(8): 1107-1115.
魏勇,魏江,徐金发. 2004.企业知识平台整体结构:以某软件企业为例[J].研究与发展管理, 16(1): 49-56.
谢守美. 2009.知识生态系统知识流动的生态学分析[J].图书馆学研究, (5): 7-10.
熊健,陈英武,杨克巍. 2009.一种基于多属性群决策的需求优先级排序方法[J].系统工程理论与实践, 3(27): 79-83.
徐建锁,王正欧,李淑伟. 2003.基于知识链的管理[J].天津大学学报(社会科学版), 4(5): 133-136.
徐泽水,达庆利. 2003.区间数排序的可能度法及其应用[J].系统工程学报, 18(1): 67-70.
徐泽水, 2001.模糊互补判断矩阵排序的一种算法[J].系统工程学报, 16(4): 311-314.
徐泽水,. 2002.三角形模糊互补判断矩阵的一种排序方法[J].模糊系统与数学, 16(1): 47-50.
徐泽水, 2009.权重信息完全未知且对方案有偏好的多属性决策法[J].系统工程理论与实践, 23(12): 100-103.
杨崐,王二平. 2004.软件开发管理中的沟通与协调问题研究[J].中国管理科学, 12(3): 141-148.
杨善林,丁帅,付超. 2009.考虑信息源相关的软件可信性评估模型[J].中国管理科学, 17(6): 87-90.
殷国鹏,陈禹. 2009.企业知识整合活动对信息系统吸收的影响研究[J].科学学研究, 5(27): 750-758.
应洪斌,沈瑶. 2009.非正式网络中隐性知识传递的影响机制研究[J].科研管理, 7(30): 130-137.
郑志明,马世龙,李未. 2009a.软件可信性动力学特征及其演化复杂性[J].中国科学F辑:信息科学, 39(9): 946-950.
郑志明,马世龙,李未. 2009b.软件可信复杂性及其动力学统计分析方法[J].中国科学F辑:信息科学, 39(10): 1050-1054.
周晓东,项保华. 2003.企业知识内部转移:模式、影响因素与机制分析[J].南开管理评论, (5): 7-10.
周欣, 2003.面向对象软件变化影响分析技术研究.北京大学,北京.
A. S, N. M. 1998. The domain theory for requirements engineering [J]. IEEE Transactions on Software Engineering, 3(8): 760-773.
A.Ulrich, H.Hallal, A.Petrenko, 2002. Verifying Trustworthiness Requirements in Distributed Systems with Formal Log-file Analysis. In: Proc. Of the 36th Hawaii International Conference on System Sciences (HICSS’03). 1977/11/01 ed. IEEE Computer Society Press.
Abdelmoez W, Shereshevsky M, Gunnalan R, et al., 2004. Software Architectures Change Propagation Tool (SACPT). 20th Ieee International Conference on Software Maintenance, Proceedings.
Acha V, Davies A, Hobday M, et al. 2004. Exploring the capital goods economy: complex product systems in the UK [J]. Industrial and Corporate Change, 13(3): 505-529.
Amirat A, Laskri M, Khammaci T. 2008. Modularization of crosscutting concerns in requirements engineering [J]. International Arab Journal of Information Technology, 5(2): 120-125.
Baxter I D, Pidgeon C W, 1997. Software change through design maintenance. International Conference on Software Maintenance, Proceedings.
Berander P, Svahnberg M. 2009. Evaluating two ways of calculating priorities in requirements hierarchies - An experiment on hierarchical cumulative voting [J]. Journal of Systems and Software, 82(5): 836-850.
Bjornson F O, Dingsoyr T. 2008. Knowledge management in software engineering: A systematic review of studied concepts, findings and research methods used [J]. Information and Software Technology, 50(11): 1055-1068.
Blanes D, Insfran E, Abrahao S, 2009. Requirements Engineering in the Development ofMulti-Agent Systems: A Systematic Review. Intelligent Data Engineering and Automated Learning, Proceedings.
Bohner S A. 1996. Impact analysis in the software change process: A year 2000 perspective [J]. International Conference on Software Maintenance, Proceedings, 42-51,373.
Bohner S A, 2002. Software change impacts - An evolving perspective. International Conference on Software Maintenance, Proceedings.
Borga G, Castelli S, Costa S D, et al. 2008. A prototype system for monitoring information demand and data availability [J]. Urban and Regional Data Management, 333-343,523.
Breech B, Danalis A, Shindo S, et al., 2004. Online impact analysis via dynamic compilation technology. 20th Ieee International Conference on Software Maintenance, Proceedings.
Browning T R. 2001. Applying the design structure matrix to system decomposition and integration problems: A review and new directions [J]. Ieee Transactions on Engineering Management, 48(3): 292-306.
Cao Y, Bai Y, Chen H, et al., 2009. Machining Parameter Optimal Selection for Blades of Aviation Engine Based on CBR and Database. Cutting-Edge Research Topics on Multiple Criteria Decision Making, Proceedings.
Caplinskas A. 2009. Requirements Elicitation in the Context of Enterprise Engineering: A Vision Driven Approach [J]. Informatica, 20(3): 343-368.
Cardoso E C S, Almeida J P A, Guizzardi G. 2009. Requirements Engineering Based on Business Process Models: A Case Study [J]. 2009 13th Enterprise Distributed Object Computing Conference Workshops (Edocw 2009), 320-327,359.
Carlshamre P, Sandahl K, Lindvall M, et al., 2000. An industrial survey of requirements interdependencies in software product release planning. Fifth Ieee International Symposium on Requirements Engineering, Proceedings.
Chan C W. 2004. From knowledge modeling to ontology construction [J]. International Journal of Software Engineering and Knowledge Engineering, 14(6): 603-624.
Chao B, Zhu X, Li Q A, et al., 2006. Reliability management in software requirement analysis. 2006 IEEE International Conference on Management of Innovation and Technology, Vols 1 and 2, Proceedings.
Chau K W. 2007. An ontology-based knowledge management system for flow and water quality modeling [J]. Advances in Engineering Software, 38(3): 172-181.
Chen C H , Ling S F , W C. 2003. Project scheduling for collaborative product development using DSM [J]. International Journal of Project Management, 21(4): 291-299.
Chen C Y, She C W, Tang J D, 2007. An object-based, attribute-oriented approach for softwarechange impact analysis. 2007 Ieee International Conference on Industrial Engineering and Engineering Management.
Chen H G, Jiang J J, Klein G, et al. 2009. Reducing software requirement perception gaps through coordination mechanisms [J]. Journal of Systems and Software, 82(4): 650-655.
Chen Z Z, Pooley R. 2009. Rediscovering Zachman Framework using Ontology from a Requirement Engineering Perspective [J]. 2009 Ieee 33rd International Computer Software and Applications Conference, Vols 1 and 2, 676-681,1234.
Chu W C C, 2008. Retrospect of Taiwan's Software Industry and issues of Software Maintenance and Evolution. 2008 Ieee International Conference on Software Maintenance.
Chung L, Nixon B A, Yu E. 2000. Non-functional requirements in software engineering [M]. Boston: Kluwer Academic
Corbin R D, Dunbar C B, Zhu Q. 2007. A three-tier knowledge management scheme for software engineering support and innovation [J]. Journal of Systems and Software, 80(9): 1494-1505.
Cote M A, Suryn W, Georgiadou E. 2007. In search for a widely applicable and accepted software quality model for software quality engineering [J]. Software Quality Journal, 15(4): 401-416.
Dam K H, Winikoff M, Padgham L, 2006. An agent-oriented approach to change propagation in software evolution. 2006 Australian Software Engineering Conference, Proceedings.
Davies A. 1999. Innovation and competitiveness in complex product systems: The case of mobile phone systems [J]. Europe and Developing Countries in the Globalised Information Economy, 9(107-125,245.
Deng Z H, Peng L Q. 2008. Knowledge map and knowledge flow of supply Chain [J]. Industry Cluster and Meta-Studies, 721-726,953.
Donald E. Harter, Mayuram S. Krishnan, Slaughter S A. 2000. Effects of Process Maturity on Quality, Cycle Time, and Effort in Software Product Development [J]. Management Science, 46(451-466.
Dubois E, Mouratidis H. 2010. Guest editorial: security requirements engineering: past, present and future [J]. Requirements Engineering, 15(1): 1-5.
Eckert C M, Zanker W, Clarkson P J. 2001. Aspects of a better understanding of changes [J]. Design Applications in Industry and Education, 147-154,483.
English K W, Bloebaum C L. 2008. Visual Dependency Structure Matrix for Multidisciplinary Design Optimization Tradeoff Studies [J]. Journal of Aerospace Computing Information and Communication, 5(9): 274-297.
Ethiraj S K. 2007. Allocation of inventive effort in complex product systems [J]. Strategic Management Journal, 28(6): 563-584.
Evelyn J. Barry, Chris F. Kemerer, Slaughter S A. 2006. Environmental Volatility, Development Decisions, and Software Volatility: A Longitudinal Analysis [J]. Management Science, 52(448-464.
Feng W F, Zhu W J, Feng G L, et al. 2009. Dominant Modeling of Implicit Construction Knowledge Based on Ontology [C]. Proceedings of 2009 International Conference of Management Science and Information System, Vols 1-4, 371-375,1848.
Fred B, Schneider, M S. 1999. Building Trustworthy Systems: Lessons from the PTN and Internet [J]. IEEE Internet Computing, 11(4): 53-61.
Fu W, Jia L M, Zhang Y, et al. 2005. Research on software requirement analysis method based on five-key elements arrange [C]. SERP '05: Proceedings of the 2005 International Conference on Software Engineering Research and Practice, Vols 1 and 2, 442-447,953.
Garzas J, Piattini M. 2007. An ontology for understanding and applying object-oriented design knowledge [J]. International Journal of Software Engineering and Knowledge Engineering, 17(3): 407-421.
Gendreau O, Robillard P N, 2009. Exploring Knowledge Flow in Software Project Development [C]. International Conference on Information, Process, and Knowledge Management: Eknow 2009, Proceedings.
Germani M, Mengoni M, Raffaeli R. 2006. Design Structure Matrix Used as Knowledge Capture Method for Product Configuration [C]. 9th International Design Conference - Design 2006, Vols 1 and 2, 36): 253-262,1574.
Gokpinar B, Hopp W J, Iravani S M R. 2010. The Impact of Misalignment of Organizational Structure and Product Architecture on Quality in Complex Product Development [J]. Management Science, 56(3): 468-484.
Gorschek T, Davis a M. 2008. Requirements engineering: In search of the dependent variables [J]. Information and Software Technology, 50(1-2): 67-75.
Gottgtroy P, 2007. Ontology Driven Knowledge Discovery Process: a proposal to integrate Ontology Engineering and KDD [M].
Gu X, Li J P, Wang W C, 2005. Knowledge chain & knowledge chain management based on knowledge flow among organizations [C]. Proceedings of the 11th International Conference on Industrial Engineering and Engineering Management.
Guo J M, Wang Y L, 2008. Context modeling for knowledge flow [C]. Proceedings of the 2008 Ieee International Conference on Information Reuse and Integration.
Guo L T, Guo X F. 2009. Connectivity of the Mycielskian of a digraph [J]. Applied Mathematics Letters, 22(10): 1622-1625.
Hashim K, Khairuddin N N, 2009. A Framework for Software Requirements Engineering [C]. Sepads'09: Proceedings of the 8th Wseas International Conference on Recent Advances in Software Engineering, Parallel and Distributed Systems.
Hassan a E, Holt M C, 2004. Predicting change propagation in software systems [C]. 20th Ieee International Conference on Software Maintenance, Proceedings.
Hasselbring W, Reussner R. 2006. Toward trustworthy software systems [J]. Computer, 39(4): 91-92.
Helo P T. 2006. Product configuration analysis with design structure matrix [J]. Industrial Management & Data Systems, 106(7): 997-1011.
Hogan H. 2007. Building trustworthy software [J]. Control Engineering, 54(7): 78-81.
Hou H, Song Q B, Hou H, et al. 2009. The Research of BPM Software Trustworthy Evaluation Model (based on AHP and group decision-making in linguistic scale) [C]. Proceedings of the First International Workshop on Education Technology and Computer Science, Vol Iii, 815-823,1083.
Hu J, Liao W H, Dai Y, et al. 2006. Study on ontology-based modeling technologies for the construction machinery conceptual design knowledge management [J]. Advances in Machining & Manufacturing Technology Viii, 315-316(361-365.
Huang G. 2008. Detecting and Resolving Undesired Component Interactions by Runtime Software Architecture [J]. Feature Interactions in Software and Communication Systems Ix, 188-192,217.
ISO, 1985a. ISO/IEC 9126-1 Software Engineering-Software Product Quality(Part 3):Internal Metrics.
ISO, 1985b. ISO/IEC 9126-1 Software Engineering-Software Product Quality(Part I):Quality Model.
Jarratt T, Eckert C, Clarkson P J, et al., 2002. Product architecture and the propagation of engineering change [C]. DESIGN 2002: Proceedings of the 7th International Design Conference.
Karlsson J, 1996. Software requirements prioritizing [C]. Proceedings of the Second International Conference on Requirements Engineering.
Karlsson L, Dahstedt a G, Regnell B, et al. 2007. Requirements engineering challenges in market-driven software development - An interview study with practitioners [J]. Information and Software Technology, 49(6): 588-604.
Kassab M, Ormandjieva O, Daneva M, 2008. A traceability metamodel for change management of non-functional requirements [C]. Sera 2008: 6th Acis International Conference on SoftwareEngineering Research, Management and Applications, Proceedings.
Kilsup Lee, Lee S J, 2005. A software product evaluation process for supporting the component based development Software Engineering Research [C].The third ACIS International Conference on Software Engineering Research.
Ko J G, Hu S J. 2008. Balancing of manufacturing systems with complex configurations for delayed product differentiation [J]. International Journal of Production Research, 46(15): 4285-4308.
Kohring G A. 2009. Complex Dependencies in Large Software Systems [J]. Advances in Complex Systems, 12(6): 565-581.
Konrad S, Gall M, 2008. Requirements Engineering in the Development of Large-Scale Systems [C]. Proceedings of the 16th Ieee International Requirements Engineering Conference.
Lamantia M J, Cai Y F, Maccormack a D, et al. 2008. Analyzing the evolution of large-scale software systems using design structure matrices and design rule theory: Two exploratory cases [C]. Seventh Working Ieee/Ifip Conference on Software Architecture, Proceedings, 83-92,336.
Li Y H, Song Y D. 2008. An adaptive and trustworthy software testing framework on the grid [J]. Journal of Supercomputing, 46(2): 124-138.
Lin J J Y, Lin Y S. 2008. Research and Development of a CMMI-Compliant Requirement Management System for Software Engineering [J]. Computer Supported Cooperative Work in Design Iv, 5236(76-86,676.
Lin J X, Fox M S, Bilgic T. 1996. A requirement ontology for engineering design [J]. Advances in Concurrent Engineering: Ce96, 96(343-351,450.
Ling L, Hu Y J, Wang X L, et al. 2007. An ontology-based method for knowledge integration in a collaborative design environment [C]. International Journal of Advanced Manufacturing Technology, 34(9-10): 843-856.
Litt J, Simon D L, Meyer C, et al. 2000. NASA Aviation Safety Program Aircraft Engine Health Management Data Mining Tools roadmap [J]. Data Mining and Knowledge Discovery: Theory, Tools, and Technology Ii, 4057(292-298,428.
Liu X Q, Sun Y, Veera C S, et al. 2006. Priority assessment of software process requirements from multiple perspectives [J]. Journal of Systems and Software, 79(11): 1649-1660.
Liu Z, Huang L. 2008. Research on process-oriented enterprise knowledge modeling and integration management based on ontology [J]. Research and Practical Issues of Enterprise Information Systems 254(349-357,806.
Lockledge J C, Salustri F A. 2001. Design communication using a variation of the design structure matrix [J]. Design Management - Process and Information Issues, 27-34,635.
M. S. Krishnan, C. H. Kriebel, Sunder Kekre, et al. 2000. An Empirical Analysis of Productivity and Quality in Software Products [J]. Management Science, 745-759.
Maccormack A, Rusnak J, Baldwin C Y. 2006. Exploring the structure of complex software designs: An empirical study of open source and proprietary code [J]. Management Science, 52(7): 1015-1030.
Malik H, Hassan a E. 2008a. Supporting Software Evolution Using Adaptive Change Propagation Heuristics [C]. 2008 Ieee International Conference on Software Maintenance, 177-186,483.
Malik H, Hassan a E, 2008b. Supporting Software Evolution Using Adaptive Change Propagation Heuristics [C]. 2008 Ieee International Conference on Software Maintenance.
Marc A, Witold S , Y C. 2005. The evolution path for industrial software quality evaluation methods applying ISO/IEC 9126:2001 quality model: example of MITRE's sqae method [J]. Software Quality Journal, 3(14): 17-30.
March S T, Allen G N. 2009. Challenges in Requirements Engineering: A Research Agenda for Conceptual Modeling [J]. Design Requirements Engineering: A Ten-Year Perspective, 14(157-165,495.
Matulevicius R, Sindre G. 2006. Requirements engineering tool evaluation approach [J]. Advances in Information Systems Development, 695-706,1052.
Mclean J. 2006. Trustworthy Software: Why we need it, Why we don't have it, How we can get it [C]. 30th Annual International Computer Software and Applications Conference, Vol 1, Regular Papers/Panels, Proceedings, 32-33,540.
Miguel A, Languna, M J M. 2003. Docflow: workflow based requirements elicitation [J]. Information and Software Technology, 45(2): 357-369.
Mirarab S, Hassouna A, Tahvildari L, 2007. Using Bayesian belief networks to predict change propagation in software systems [C]. Icpc 2007: 15th IEEE International Conference on Program Comprehension, Proceedings.
Moon D H, Choi M S. 2003. Development of sensitivity analysis algorithm for a straight-line beam structure by the transfer stiffness coefficient method [C]. Jsme International Journal Series C-Mechanical Systems Machine Elements and Manufacturing, 46(1): 138-144.
Mu K D, Jin Z, Zowghi D. 2008. A Priority-Based Negotiations Approach for Handling Inconsistencies in Multi-Perspective Software Requirements [J]. Journal of Systems Science & Complexity, 21(4): 574-596.
Myers C R. 2003. Software systems as complex networks: Structure, function, and evolvability of software collaboration graphs [J]. Physical Review E, 68(4): -.
Pavon J, Garijo F, Gomez-Sanz J. 2008. Complex systems and agent-oriented software engineering[J]. Engineering Environment-Mediated Multi-Agent Systems, 5049(3-16,295.
Penzenstadler B, Sikora E, Pohl K. 2009. A Requirements Reference Model for Model-Based Requirements Engineering in the Automotive Domain [J]. Requirements Engineering: Foundation for Software Quality, 5512(212-217,255.
Port D, Boehm B, Klappholz D, 2008. Nancy R. Mead: Making requirements prioritization a priority [C]. 21st Conference on Software Engineering Education and Training, Proceedings.
Qian Y J, Goh T N, 2007. Development projects scheduling and Design Structure Matrix. 2007 Ieee International Conference on Industrial Engineering and Engineering Management, Vols 1-4.
Rajiv D. Banker, Gordon B. Davis, Slaughter S A. 1998. Software Development Practices, Software Complexity, and Software Maintenance Performance: A Field Study [J]. Management Science, 44(433-450.
Rashid A, Cottenier T, Greenwood P, et al. 2010. Aspect-Oriented Software Development in Practice: Tales from AOSD-Europe [J]. Computer, 43(2): 19-26.
Ruhe G, Greer D. 2003. Quantitative studies in software release planning under risk and resource constraints [C]. 2003 International Symposium on Empirical Software Engineering, Proceedings, 262-271,336.
Ryan K, Karlsson J, 1997. Prioritizing software requirements in an industrial setting [C]. Proceedings of the 1997 International Conference on Software Engineering.
Saleh K, Habil M. 2007. The security requirements behavior model for trustworthy software [C]. 2008 International Mcetech Conference on E-Technologies, Proceedings, 235-238,262.
Shaik I, Abdelmoez W, Gunnalan R, et al., 2006a. Change propagation for assessing design quality of software architectures [C]. 5th Working IEEE/IFIP Conference on Software Architecture, Proceedings.
Shaik I, Abdelmoez W, Gunnalan R, et al., 2006b. Using change propagation probabilities to assess quality attributes of software architectures [C]. 2006 Ieee International Conference on Computer Systems and Applications, Vols 1-3.
Sharareh Afsharian, Marco Giacomobono, Inverardi P, 2008. A Framework for Software Project Estimation Based on COSMIC, DSM and Rework Characterization. In CfPart BIPI’08. 1983/03/30 ed., Germany.
Solemon B, Sahibuddin S, Ghani a a A, 2009. Requirements Engineering Problems and Practices in Software Companies: An Industrial Survey [C]. Advances in Software Engineering, Proceedings.
Song X P, Sherman W, Hwong B, et al., 2009. Requirements Engineering Needs in a Solution and Infrastructure Improvement Project [C]. 2009 IEEE 33rd International Computer Software andApplications Conference,.
Sosa M E, Eppinger S D, Rowles C M. 2004. The misalignment of product architecture and organizational structure in complex product development [J]. Management Science, 50(12): 1674-1689.
Steffen Becker, Marko Boskovic, Dhama A. 2006. Trustworthy Software Systems: A Discussion of Basic Concepts and Terminology [J]. ACM SIGSOFT Software Engineering Notes, 11(31): 1-18.
Sutcliffe A, N M. 1998. The domain theory for requirements engineering [J]. Ieee Transactions on Software Engineering, 3(8): 760-773.
Tahmoush D, Lofland L. 2009. A Prototype National Emergency Deployment System [C]. 2009 IEEE Conference on Technologies for Homeland Security, 323-330,695.
Tran T, Js S, 1995. Quality function deployment (QFD): An effective technique for requirements acquisition and reuse [C]. In: Proc. Of the 2nd IEEE Software Engineering Standards Symp. Los Alamitos: IEEE Computer Society Press.
Trudel S, Lavoie J M, Pare M C, et al. 2006. PEM: The small company-dedicated software process quality evaluation method combining CMMISM and ISO/IEC 14598 [J]. Software Quality Journal, 14(1): 7-23.
Uzuegbunam I S. 2005. Managing collaborative new product development of complex software systems: Mythical man-month re-visited [C]. 2005 IEEE International Engineering Management Conference, Vols 1 and 2, 494-498,922.
Venkatasubramanian V. 2005. Prognostic and diagnostic monitoring of complex systems for product lifecycle management: Challenges and opportunities [J]. Computers & Chemical Engineering, 29(6): 1253-1263.
Wang C H, Chu W C, Wang F J. 2005. Providing a behavioral and static formal model to elicit the functional software requirement [C]. Proceedings of the 2005 IEEE International Conference on Information Reuse and Integration, 44-49,606.
Wang T S, Zhong D M, 2008. Research on the Avionic Software Quality Evaluation Based on the Wsr Methodology [C]. Dasc: 2008 Ieee/Aiaa 27th Digital Avionics Systems Conference.
Wang Z Y, Ding S T, Ding L, et al., 2009. Analysis of Micro Aviation Piston Engine Coolant System for Airworthiness [C]. Proceedings of 2009 International Symposium on Aircraft Airworthiness.
Wieringa R, Maiden N, Mead N, et al. 2006. Requirements engineering paper classification and evaluation criteria: a proposal and a discussion [J]. Requirements Engineering, 11(1): 102-107.
Xiong W, Wang X T, Wu Z X. 2008. Study of a customer satisfaction-oriented model for outsourcing software quality management using Quality Function Deployment (QFD) [C]. 2008 4th International Conference on Wireless Communications, Networking and Mobile Computing, Vols 1-31, 7959-7963,13133.
Xu B, Dou Y J, Yang X H, et al., 2008. Experience of Collaborative Requirement Management in Dual-shore Software Maintenance Projects [C]. 2008 4th International Conference on Wireless Communications, Networking and Mobile Computing.
Yan Z, 2008. A Comprehensive Trust Model for Component Software [C]. In:Proc of the ICPS 2008 & Co-Located Workshops(AUPC'08, SecPerU'08, SEPS'08, & SIPE'08). 1985/09/13 ed.
Yau S S, Collofello J S, T M, 1978. Ripple effect analysis of software maintenance [C]. Proceedings of the Computer Software and Applications Conference(COM PSAC 78).
Yau S S, Landwehr C, Voas J, et al. 2003a. Challenges and recent advances in developing trustworthy software-based systems [J]. 27th Annual International Computer Software and Applications Conference, 208-208,710.
Yau S S, Landwehr C, Voas J, et al. 2003b. Challenges and recent advances in developing trustworthy software-based systems [C]. 27th Annual International Computer Software and Applications Conference, Proceedings, 208-208,710.
Yeo K T, Ren Y T. 2009. Risk Management Capability Maturity Model for Complex Product Systems (CoPS) Projects [J]. Systems Engineering, 12(4): 275-294.
Yoo N, 2004. XML-based engineering change impact analysis with non-functional requirements [C]. Serp'04: Proceedings of the International Conference on Software Engineering Research and Practice.
Yu D H, He K Q, Wang J, et al., 2008. An Algorithm for Priority Ranking of Individualized Functional Requirements in Networked Software. Gcc 2008: Seventh International Conference on Grid and Cooperative Computing, Proceedings.
Zeng Q T, Zhao Z Y, Liang Y Q. 2009. Course ontology-based user's knowledge requirement acquisition from behaviors within e-learning systems [J]. Computers & Education, 53(3): 809-818.
Zhang a Y, Sun S R, 2009. The Study on Interaction between Knowledge Flow and Knowledge Creation [C]. Proceedings of 2009 International Conference of Management Engineering and Information Technology.
Zhang H, Cao S K, Song L, et al. 2009. Development and Research of a New Open CNC Prototype System [J]. Acc 2009: Etp/Iita World Congress in Applied Computing, Computer Science, and Computer Engineering, 311-314,464.
Zhang H, Deng R R. 2009. Research on Software Requirement Analysis Based on Agile Modeling [C]. Proceedings of the 4th International Conference on Product Innovation Management, Vols I and Ii, 1327-1331,1982.
Zhang H F, Sun S D, Fang W, 2006. The research of user requirement management subsystem for the software R & D project based on the SQFD & ROMC methods [C]. Proceedings of IRNOP VII Project Research Conference.
Zhang Z N, Xie Y B, 2009. Knowledge Flow in Product Design [C]. Proceedings of the 9th Biennial Conference on Engineering Systems Design and Analysis.
Zhao S F, Chen L C, 2009. The Bp Neural Networks Applications in Bank Credit Risk Management System [C]. Proceedings of the 8th IEEE International Conference on Cognitive Informatics.
Zhao W H, Kong D Y. 2008. Complex Product Systems Critical Dimensions and Technological Knowledge Characteristics [C]. Proceedings of the 38th International Conference on Computers and Industrial Engineering, Vols 1-3, 548-552,3082.
Zheng L W, Jin Z, 2007. Requirement driven agent collaboration based on functional ontology and AMD [C]. 11th IEEE International Workshop on Future Trends of Distributed Computing Systems.
Zheng Z, Han B T, 2009. The Study on Knowledge Flow Efficiency Measure of Weighted RIN. Wmso: 2008 International Workshop on Modelling, Simulation and Optimization, Proceedings.
Zhong Q, Wang K Y, 2005. The knowledge flow in the internal knowledge network of enterprise [C]. Proceedings of the 2005 International Conference on Management Science & Engineering (12th), Vols 1- 3.
Zhuang C, Qian W. 2005. Study on the salary system for IT enterprise based on double factor motivation theory - art. no. 60410J [J]. ICMIT 2005: Information Systems and Signal Processing, 6041(J410-J410,582.
Zhuge H. 2002. Knowledge flow management for distributed team software development [J]. Knowledge-Based Systems, 15(8): 465-471.
陈伟,夏建华. 2007.综合主、客观权重信息的最优组合赋权方法[J].数学的实践与认识, 31(1): 17-22.
程平,刘伟,陈艳. 2010.我国可信软件产业的发展现状与应对策略[J].科技进步与对策, 27(3): 51-54.
龚艳斌. 2008.基于方案偏好和部分权重信息的模糊多属性决策方法[J].控制与决策, 23(5): 507-510.
顾新,李久平,王维成. 2006.知识流动、知识链与知识链管理[J].软科学, 2(20): 10-13.
何睿,唐敦兵,薛建彬. 2008.基于设计结构矩阵的工程变更传播研究[J].计算机集成制造系统, 4(14): 656-660.
黄德毅,万江平. 2006.基于SECI的软件需求获取过程中知识转移模式研究[J].研究与发展管理, 27(11): 77-81.
黄蒙,舒风笛,李明树. 2006.一种风险驱动的迭代开发需求优先级排序方法[J].软件学报, 17(12): 2450-2460.
金芝, 2000.基于本体的需求自动获取[J].计算机学报, 5(23): 486-492.
李江,冯勤超. 2006.加性加权法在确定软件需求优先级中的应用[J].现代图书情报技术, (1):79-84.
李顺才,邹珊刚. 2003.知识流动机理的三维分析模式[J]. .研究与发展管理, 15(4): 39-44.
李薇,蒋绍忠. 2005.层次分析法(AHP)在ERP需求分析中的应用[J].技术经济与管理研究, (2): 23-25.
李未, 1999.网络环境下海量信息组织与处理的理论与方法研究[M]. G199903270
李晓明,孙林岩,汪应洛. 2005.基于知识管理的软件需求管理研究[J].研究与发展管理, 17(4): 28-32.
梁梁,熊立,王国华. 2005.王国华.一种群决策中专家客观权重的确定方法[J].系统工程与电子技术, 27(4): 652-655.
林正奎,杨德礼,杨红. 2006.软件开发系统六元结构模型及其复杂性研究[J].系统工程学报, 21(4): 368-374.
刘宏伟,和金生. 2003.“双因素”问题的理论分析[J].南开管理评论, 6(5): 30-35.
刘克,单志广,王戟等. 2008.“可信软件基础研究”重大研究计划综述[J].中国科学基金, (3): 138-151.
刘业政,徐德鹏,姜元春. 2007.多属性群决策中权重自适应调整的方法[J].系统工程与电子技术, 29(1): 45-48.
马永红,周荣喜,李振光. 2007.基于离差最大化的决策者权重的确定方法[J].东北化工大学学报, 34(2): 177-180.
那一沙,夏军. 2007.需求开发的知识转移模型研究[J].中国农机化, 5(53-55.
宋兴光,杨德礼. 2004.基于决策者偏好及赋权法一致性的组合赋权法[J].系统工程与电子技术, 36(9): 1226-1290.
宋兴光,周平. 2010.多属性群决策中决策者权重的确定方法[J].系统工程, 4(5): 84-89.
谭大鹏,霍国庆. 2006.企业知识转移的“双因素”分析[J].研究与发展管理, 12(8): 1-7.
万树平, 2009.区间型多属性决策的心态指标法[J].控制与决策, 24(1): 35-43.
汪应洛,李勖. 2002.知识的转移特性研究[J].系统工程理论与实践, 22(10): 8-11.
王怀民,刘旭东,郎波. 2009.软件可信分级规范[MS]. [EB/OL]http://www.trustie.com/, 2009/6/1-2009/6/12.
王莉,方澜,王方华等. 2007.网络环境下客户参与对产品开发绩效的影响研究-以我国软件企业为例[J].管理工程学报, 21(4): 95-101,135.
王明涛.. 1999.多指标综合评价中权数确定的离差、均方差决策方法[J].中国软科学, (8): 100-101.
王映辉,王立福,张世琨. 2006.一种软件需求变化追踪方法[J].电子学报, 8(34): 1428-1432.
王映辉,张世琨,刘瑜. 2004.基于可达矩阵的软件体系结构演化波及效应分析[J].软件学报, 15(8): 1107-1115.
魏勇,魏江,徐金发. 2004.企业知识平台整体结构:以某软件企业为例[J].研究与发展管理, 16(1): 49-56.
谢守美. 2009.知识生态系统知识流动的生态学分析[J].图书馆学研究, (5): 7-10.
熊健,陈英武,杨克巍. 2009.一种基于多属性群决策的需求优先级排序方法[J].系统工程理论与实践, 3(27): 79-83.
徐建锁,王正欧,李淑伟. 2003.基于知识链的管理[J].天津大学学报(社会科学版), 4(5): 133-136.
徐泽水,达庆利. 2003.区间数排序的可能度法及其应用[J].系统工程学报, 18(1): 67-70.
徐泽水, 2001.模糊互补判断矩阵排序的一种算法[J].系统工程学报, 16(4): 311-314.
徐泽水,. 2002.三角形模糊互补判断矩阵的一种排序方法[J].模糊系统与数学, 16(1): 47-50.
徐泽水, 2009.权重信息完全未知且对方案有偏好的多属性决策法[J].系统工程理论与实践, 23(12): 100-103.
杨崐,王二平. 2004.软件开发管理中的沟通与协调问题研究[J].中国管理科学, 12(3): 141-148.
杨善林,丁帅,付超. 2009.考虑信息源相关的软件可信性评估模型[J].中国管理科学, 17(6): 87-90.
殷国鹏,陈禹. 2009.企业知识整合活动对信息系统吸收的影响研究[J].科学学研究, 5(27): 750-758.
应洪斌,沈瑶. 2009.非正式网络中隐性知识传递的影响机制研究[J].科研管理, 7(30): 130-137.
郑志明,马世龙,李未. 2009a.软件可信性动力学特征及其演化复杂性[J].中国科学F辑:信息科学, 39(9): 946-950.
郑志明,马世龙,李未. 2009b.软件可信复杂性及其动力学统计分析方法[J].中国科学F辑:信息科学, 39(10): 1050-1054.
周晓东,项保华. 2003.企业知识内部转移:模式、影响因素与机制分析[J].南开管理评论, (5): 7-10.
周欣, 2003.面向对象软件变化影响分析技术研究.北京大学,北京.
A. S, N. M. 1998. The domain theory for requirements engineering [J]. IEEE Transactions on Software Engineering, 3(8): 760-773.
A.Ulrich, H.Hallal, A.Petrenko, 2002. Verifying Trustworthiness Requirements in Distributed Systems with Formal Log-file Analysis. In: Proc. Of the 36th Hawaii International Conference on System Sciences (HICSS’03). 1977/11/01 ed. IEEE Computer Society Press.
Abdelmoez W, Shereshevsky M, Gunnalan R, et al., 2004. Software Architectures Change Propagation Tool (SACPT). 20th Ieee International Conference on Software Maintenance, Proceedings.
Acha V, Davies A, Hobday M, et al. 2004. Exploring the capital goods economy: complex product systems in the UK [J]. Industrial and Corporate Change, 13(3): 505-529.
Amirat A, Laskri M, Khammaci T. 2008. Modularization of crosscutting concerns in requirements engineering [J]. International Arab Journal of Information Technology, 5(2): 120-125.
Baxter I D, Pidgeon C W, 1997. Software change through design maintenance. International Conference on Software Maintenance, Proceedings.
Berander P, Svahnberg M. 2009. Evaluating two ways of calculating priorities in requirements hierarchies - An experiment on hierarchical cumulative voting [J]. Journal of Systems and Software, 82(5): 836-850.
Bjornson F O, Dingsoyr T. 2008. Knowledge management in software engineering: A systematic review of studied concepts, findings and research methods used [J]. Information and Software Technology, 50(11): 1055-1068.
Blanes D, Insfran E, Abrahao S, 2009. Requirements Engineering in the Development ofMulti-Agent Systems: A Systematic Review. Intelligent Data Engineering and Automated Learning, Proceedings.
Bohner S A. 1996. Impact analysis in the software change process: A year 2000 perspective [J]. International Conference on Software Maintenance, Proceedings, 42-51,373.
Bohner S A, 2002. Software change impacts - An evolving perspective. International Conference on Software Maintenance, Proceedings.
Borga G, Castelli S, Costa S D, et al. 2008. A prototype system for monitoring information demand and data availability [J]. Urban and Regional Data Management, 333-343,523.
Breech B, Danalis A, Shindo S, et al., 2004. Online impact analysis via dynamic compilation technology. 20th Ieee International Conference on Software Maintenance, Proceedings.
Browning T R. 2001. Applying the design structure matrix to system decomposition and integration problems: A review and new directions [J]. Ieee Transactions on Engineering Management, 48(3): 292-306.
Cao Y, Bai Y, Chen H, et al., 2009. Machining Parameter Optimal Selection for Blades of Aviation Engine Based on CBR and Database. Cutting-Edge Research Topics on Multiple Criteria Decision Making, Proceedings.
Caplinskas A. 2009. Requirements Elicitation in the Context of Enterprise Engineering: A Vision Driven Approach [J]. Informatica, 20(3): 343-368.
Cardoso E C S, Almeida J P A, Guizzardi G. 2009. Requirements Engineering Based on Business Process Models: A Case Study [J]. 2009 13th Enterprise Distributed Object Computing Conference Workshops (Edocw 2009), 320-327,359.
Carlshamre P, Sandahl K, Lindvall M, et al., 2000. An industrial survey of requirements interdependencies in software product release planning. Fifth Ieee International Symposium on Requirements Engineering, Proceedings.
Chan C W. 2004. From knowledge modeling to ontology construction [J]. International Journal of Software Engineering and Knowledge Engineering, 14(6): 603-624.
Chao B, Zhu X, Li Q A, et al., 2006. Reliability management in software requirement analysis. 2006 IEEE International Conference on Management of Innovation and Technology, Vols 1 and 2, Proceedings.
Chau K W. 2007. An ontology-based knowledge management system for flow and water quality modeling [J]. Advances in Engineering Software, 38(3): 172-181.
Chen C H , Ling S F , W C. 2003. Project scheduling for collaborative product development using DSM [J]. International Journal of Project Management, 21(4): 291-299.
Chen C Y, She C W, Tang J D, 2007. An object-based, attribute-oriented approach for softwarechange impact analysis. 2007 Ieee International Conference on Industrial Engineering and Engineering Management.
Chen H G, Jiang J J, Klein G, et al. 2009. Reducing software requirement perception gaps through coordination mechanisms [J]. Journal of Systems and Software, 82(4): 650-655.
Chen Z Z, Pooley R. 2009. Rediscovering Zachman Framework using Ontology from a Requirement Engineering Perspective [J]. 2009 Ieee 33rd International Computer Software and Applications Conference, Vols 1 and 2, 676-681,1234.
Chu W C C, 2008. Retrospect of Taiwan's Software Industry and issues of Software Maintenance and Evolution. 2008 Ieee International Conference on Software Maintenance.
Chung L, Nixon B A, Yu E. 2000. Non-functional requirements in software engineering [M]. Boston: Kluwer Academic
Corbin R D, Dunbar C B, Zhu Q. 2007. A three-tier knowledge management scheme for software engineering support and innovation [J]. Journal of Systems and Software, 80(9): 1494-1505.
Cote M A, Suryn W, Georgiadou E. 2007. In search for a widely applicable and accepted software quality model for software quality engineering [J]. Software Quality Journal, 15(4): 401-416.
Dam K H, Winikoff M, Padgham L, 2006. An agent-oriented approach to change propagation in software evolution. 2006 Australian Software Engineering Conference, Proceedings.
Davies A. 1999. Innovation and competitiveness in complex product systems: The case of mobile phone systems [J]. Europe and Developing Countries in the Globalised Information Economy, 9(107-125,245.
Deng Z H, Peng L Q. 2008. Knowledge map and knowledge flow of supply Chain [J]. Industry Cluster and Meta-Studies, 721-726,953.
Donald E. Harter, Mayuram S. Krishnan, Slaughter S A. 2000. Effects of Process Maturity on Quality, Cycle Time, and Effort in Software Product Development [J]. Management Science, 46(451-466.
Dubois E, Mouratidis H. 2010. Guest editorial: security requirements engineering: past, present and future [J]. Requirements Engineering, 15(1): 1-5.
Eckert C M, Zanker W, Clarkson P J. 2001. Aspects of a better understanding of changes [J]. Design Applications in Industry and Education, 147-154,483.
English K W, Bloebaum C L. 2008. Visual Dependency Structure Matrix for Multidisciplinary Design Optimization Tradeoff Studies [J]. Journal of Aerospace Computing Information and Communication, 5(9): 274-297.
Ethiraj S K. 2007. Allocation of inventive effort in complex product systems [J]. Strategic Management Journal, 28(6): 563-584.
Evelyn J. Barry, Chris F. Kemerer, Slaughter S A. 2006. Environmental Volatility, Development Decisions, and Software Volatility: A Longitudinal Analysis [J]. Management Science, 52(448-464.
Feng W F, Zhu W J, Feng G L, et al. 2009. Dominant Modeling of Implicit Construction Knowledge Based on Ontology [C]. Proceedings of 2009 International Conference of Management Science and Information System, Vols 1-4, 371-375,1848.
Fred B, Schneider, M S. 1999. Building Trustworthy Systems: Lessons from the PTN and Internet [J]. IEEE Internet Computing, 11(4): 53-61.
Fu W, Jia L M, Zhang Y, et al. 2005. Research on software requirement analysis method based on five-key elements arrange [C]. SERP '05: Proceedings of the 2005 International Conference on Software Engineering Research and Practice, Vols 1 and 2, 442-447,953.
Garzas J, Piattini M. 2007. An ontology for understanding and applying object-oriented design knowledge [J]. International Journal of Software Engineering and Knowledge Engineering, 17(3): 407-421.
Gendreau O, Robillard P N, 2009. Exploring Knowledge Flow in Software Project Development [C]. International Conference on Information, Process, and Knowledge Management: Eknow 2009, Proceedings.
Germani M, Mengoni M, Raffaeli R. 2006. Design Structure Matrix Used as Knowledge Capture Method for Product Configuration [C]. 9th International Design Conference - Design 2006, Vols 1 and 2, 36): 253-262,1574.
Gokpinar B, Hopp W J, Iravani S M R. 2010. The Impact of Misalignment of Organizational Structure and Product Architecture on Quality in Complex Product Development [J]. Management Science, 56(3): 468-484.
Gorschek T, Davis a M. 2008. Requirements engineering: In search of the dependent variables [J]. Information and Software Technology, 50(1-2): 67-75.
Gottgtroy P, 2007. Ontology Driven Knowledge Discovery Process: a proposal to integrate Ontology Engineering and KDD [M].
Gu X, Li J P, Wang W C, 2005. Knowledge chain & knowledge chain management based on knowledge flow among organizations [C]. Proceedings of the 11th International Conference on Industrial Engineering and Engineering Management.
Guo J M, Wang Y L, 2008. Context modeling for knowledge flow [C]. Proceedings of the 2008 Ieee International Conference on Information Reuse and Integration.
Guo L T, Guo X F. 2009. Connectivity of the Mycielskian of a digraph [J]. Applied Mathematics Letters, 22(10): 1622-1625.
Hashim K, Khairuddin N N, 2009. A Framework for Software Requirements Engineering [C]. Sepads'09: Proceedings of the 8th Wseas International Conference on Recent Advances in Software Engineering, Parallel and Distributed Systems.
Hassan a E, Holt M C, 2004. Predicting change propagation in software systems [C]. 20th Ieee International Conference on Software Maintenance, Proceedings.
Hasselbring W, Reussner R. 2006. Toward trustworthy software systems [J]. Computer, 39(4): 91-92.
Helo P T. 2006. Product configuration analysis with design structure matrix [J]. Industrial Management & Data Systems, 106(7): 997-1011.
Hogan H. 2007. Building trustworthy software [J]. Control Engineering, 54(7): 78-81.
Hou H, Song Q B, Hou H, et al. 2009. The Research of BPM Software Trustworthy Evaluation Model (based on AHP and group decision-making in linguistic scale) [C]. Proceedings of the First International Workshop on Education Technology and Computer Science, Vol Iii, 815-823,1083.
Hu J, Liao W H, Dai Y, et al. 2006. Study on ontology-based modeling technologies for the construction machinery conceptual design knowledge management [J]. Advances in Machining & Manufacturing Technology Viii, 315-316(361-365.
Huang G. 2008. Detecting and Resolving Undesired Component Interactions by Runtime Software Architecture [J]. Feature Interactions in Software and Communication Systems Ix, 188-192,217.
ISO, 1985a. ISO/IEC 9126-1 Software Engineering-Software Product Quality(Part 3):Internal Metrics.
ISO, 1985b. ISO/IEC 9126-1 Software Engineering-Software Product Quality(Part I):Quality Model.
Jarratt T, Eckert C, Clarkson P J, et al., 2002. Product architecture and the propagation of engineering change [C]. DESIGN 2002: Proceedings of the 7th International Design Conference.
Karlsson J, 1996. Software requirements prioritizing [C]. Proceedings of the Second International Conference on Requirements Engineering.
Karlsson L, Dahstedt a G, Regnell B, et al. 2007. Requirements engineering challenges in market-driven software development - An interview study with practitioners [J]. Information and Software Technology, 49(6): 588-604.
Kassab M, Ormandjieva O, Daneva M, 2008. A traceability metamodel for change management of non-functional requirements [C]. Sera 2008: 6th Acis International Conference on SoftwareEngineering Research, Management and Applications, Proceedings.
Kilsup Lee, Lee S J, 2005. A software product evaluation process for supporting the component based development Software Engineering Research [C].The third ACIS International Conference on Software Engineering Research.
Ko J G, Hu S J. 2008. Balancing of manufacturing systems with complex configurations for delayed product differentiation [J]. International Journal of Production Research, 46(15): 4285-4308.
Kohring G A. 2009. Complex Dependencies in Large Software Systems [J]. Advances in Complex Systems, 12(6): 565-581.
Konrad S, Gall M, 2008. Requirements Engineering in the Development of Large-Scale Systems [C]. Proceedings of the 16th Ieee International Requirements Engineering Conference.
Lamantia M J, Cai Y F, Maccormack a D, et al. 2008. Analyzing the evolution of large-scale software systems using design structure matrices and design rule theory: Two exploratory cases [C]. Seventh Working Ieee/Ifip Conference on Software Architecture, Proceedings, 83-92,336.
Li Y H, Song Y D. 2008. An adaptive and trustworthy software testing framework on the grid [J]. Journal of Supercomputing, 46(2): 124-138.
Lin J J Y, Lin Y S. 2008. Research and Development of a CMMI-Compliant Requirement Management System for Software Engineering [J]. Computer Supported Cooperative Work in Design Iv, 5236(76-86,676.
Lin J X, Fox M S, Bilgic T. 1996. A requirement ontology for engineering design [J]. Advances in Concurrent Engineering: Ce96, 96(343-351,450.
Ling L, Hu Y J, Wang X L, et al. 2007. An ontology-based method for knowledge integration in a collaborative design environment [C]. International Journal of Advanced Manufacturing Technology, 34(9-10): 843-856.
Litt J, Simon D L, Meyer C, et al. 2000. NASA Aviation Safety Program Aircraft Engine Health Management Data Mining Tools roadmap [J]. Data Mining and Knowledge Discovery: Theory, Tools, and Technology Ii, 4057(292-298,428.
Liu X Q, Sun Y, Veera C S, et al. 2006. Priority assessment of software process requirements from multiple perspectives [J]. Journal of Systems and Software, 79(11): 1649-1660.
Liu Z, Huang L. 2008. Research on process-oriented enterprise knowledge modeling and integration management based on ontology [J]. Research and Practical Issues of Enterprise Information Systems 254(349-357,806.
Lockledge J C, Salustri F A. 2001. Design communication using a variation of the design structure matrix [J]. Design Management - Process and Information Issues, 27-34,635.
M. S. Krishnan, C. H. Kriebel, Sunder Kekre, et al. 2000. An Empirical Analysis of Productivity and Quality in Software Products [J]. Management Science, 745-759.
Maccormack A, Rusnak J, Baldwin C Y. 2006. Exploring the structure of complex software designs: An empirical study of open source and proprietary code [J]. Management Science, 52(7): 1015-1030.
Malik H, Hassan a E. 2008a. Supporting Software Evolution Using Adaptive Change Propagation Heuristics [C]. 2008 Ieee International Conference on Software Maintenance, 177-186,483.
Malik H, Hassan a E, 2008b. Supporting Software Evolution Using Adaptive Change Propagation Heuristics [C]. 2008 Ieee International Conference on Software Maintenance.
Marc A, Witold S , Y C. 2005. The evolution path for industrial software quality evaluation methods applying ISO/IEC 9126:2001 quality model: example of MITRE's sqae method [J]. Software Quality Journal, 3(14): 17-30.
March S T, Allen G N. 2009. Challenges in Requirements Engineering: A Research Agenda for Conceptual Modeling [J]. Design Requirements Engineering: A Ten-Year Perspective, 14(157-165,495.
Matulevicius R, Sindre G. 2006. Requirements engineering tool evaluation approach [J]. Advances in Information Systems Development, 695-706,1052.
Mclean J. 2006. Trustworthy Software: Why we need it, Why we don't have it, How we can get it [C]. 30th Annual International Computer Software and Applications Conference, Vol 1, Regular Papers/Panels, Proceedings, 32-33,540.
Miguel A, Languna, M J M. 2003. Docflow: workflow based requirements elicitation [J]. Information and Software Technology, 45(2): 357-369.
Mirarab S, Hassouna A, Tahvildari L, 2007. Using Bayesian belief networks to predict change propagation in software systems [C]. Icpc 2007: 15th IEEE International Conference on Program Comprehension, Proceedings.
Moon D H, Choi M S. 2003. Development of sensitivity analysis algorithm for a straight-line beam structure by the transfer stiffness coefficient method [C]. Jsme International Journal Series C-Mechanical Systems Machine Elements and Manufacturing, 46(1): 138-144.
Mu K D, Jin Z, Zowghi D. 2008. A Priority-Based Negotiations Approach for Handling Inconsistencies in Multi-Perspective Software Requirements [J]. Journal of Systems Science & Complexity, 21(4): 574-596.
Myers C R. 2003. Software systems as complex networks: Structure, function, and evolvability of software collaboration graphs [J]. Physical Review E, 68(4): -.
Pavon J, Garijo F, Gomez-Sanz J. 2008. Complex systems and agent-oriented software engineering[J]. Engineering Environment-Mediated Multi-Agent Systems, 5049(3-16,295.
Penzenstadler B, Sikora E, Pohl K. 2009. A Requirements Reference Model for Model-Based Requirements Engineering in the Automotive Domain [J]. Requirements Engineering: Foundation for Software Quality, 5512(212-217,255.
Port D, Boehm B, Klappholz D, 2008. Nancy R. Mead: Making requirements prioritization a priority [C]. 21st Conference on Software Engineering Education and Training, Proceedings.
Qian Y J, Goh T N, 2007. Development projects scheduling and Design Structure Matrix. 2007 Ieee International Conference on Industrial Engineering and Engineering Management, Vols 1-4.
Rajiv D. Banker, Gordon B. Davis, Slaughter S A. 1998. Software Development Practices, Software Complexity, and Software Maintenance Performance: A Field Study [J]. Management Science, 44(433-450.
Rashid A, Cottenier T, Greenwood P, et al. 2010. Aspect-Oriented Software Development in Practice: Tales from AOSD-Europe [J]. Computer, 43(2): 19-26.
Ruhe G, Greer D. 2003. Quantitative studies in software release planning under risk and resource constraints [C]. 2003 International Symposium on Empirical Software Engineering, Proceedings, 262-271,336.
Ryan K, Karlsson J, 1997. Prioritizing software requirements in an industrial setting [C]. Proceedings of the 1997 International Conference on Software Engineering.
Saleh K, Habil M. 2007. The security requirements behavior model for trustworthy software [C]. 2008 International Mcetech Conference on E-Technologies, Proceedings, 235-238,262.
Shaik I, Abdelmoez W, Gunnalan R, et al., 2006a. Change propagation for assessing design quality of software architectures [C]. 5th Working IEEE/IFIP Conference on Software Architecture, Proceedings.
Shaik I, Abdelmoez W, Gunnalan R, et al., 2006b. Using change propagation probabilities to assess quality attributes of software architectures [C]. 2006 Ieee International Conference on Computer Systems and Applications, Vols 1-3.
Sharareh Afsharian, Marco Giacomobono, Inverardi P, 2008. A Framework for Software Project Estimation Based on COSMIC, DSM and Rework Characterization. In CfPart BIPI’08. 1983/03/30 ed., Germany.
Solemon B, Sahibuddin S, Ghani a a A, 2009. Requirements Engineering Problems and Practices in Software Companies: An Industrial Survey [C]. Advances in Software Engineering, Proceedings.
Song X P, Sherman W, Hwong B, et al., 2009. Requirements Engineering Needs in a Solution and Infrastructure Improvement Project [C]. 2009 IEEE 33rd International Computer Software andApplications Conference,.
Sosa M E, Eppinger S D, Rowles C M. 2004. The misalignment of product architecture and organizational structure in complex product development [J]. Management Science, 50(12): 1674-1689.
Steffen Becker, Marko Boskovic, Dhama A. 2006. Trustworthy Software Systems: A Discussion of Basic Concepts and Terminology [J]. ACM SIGSOFT Software Engineering Notes, 11(31): 1-18.
Sutcliffe A, N M. 1998. The domain theory for requirements engineering [J]. Ieee Transactions on Software Engineering, 3(8): 760-773.
Tahmoush D, Lofland L. 2009. A Prototype National Emergency Deployment System [C]. 2009 IEEE Conference on Technologies for Homeland Security, 323-330,695.
Tran T, Js S, 1995. Quality function deployment (QFD): An effective technique for requirements acquisition and reuse [C]. In: Proc. Of the 2nd IEEE Software Engineering Standards Symp. Los Alamitos: IEEE Computer Society Press.
Trudel S, Lavoie J M, Pare M C, et al. 2006. PEM: The small company-dedicated software process quality evaluation method combining CMMISM and ISO/IEC 14598 [J]. Software Quality Journal, 14(1): 7-23.
Uzuegbunam I S. 2005. Managing collaborative new product development of complex software systems: Mythical man-month re-visited [C]. 2005 IEEE International Engineering Management Conference, Vols 1 and 2, 494-498,922.
Venkatasubramanian V. 2005. Prognostic and diagnostic monitoring of complex systems for product lifecycle management: Challenges and opportunities [J]. Computers & Chemical Engineering, 29(6): 1253-1263.
Wang C H, Chu W C, Wang F J. 2005. Providing a behavioral and static formal model to elicit the functional software requirement [C]. Proceedings of the 2005 IEEE International Conference on Information Reuse and Integration, 44-49,606.
Wang T S, Zhong D M, 2008. Research on the Avionic Software Quality Evaluation Based on the Wsr Methodology [C]. Dasc: 2008 Ieee/Aiaa 27th Digital Avionics Systems Conference.
Wang Z Y, Ding S T, Ding L, et al., 2009. Analysis of Micro Aviation Piston Engine Coolant System for Airworthiness [C]. Proceedings of 2009 International Symposium on Aircraft Airworthiness.
Wieringa R, Maiden N, Mead N, et al. 2006. Requirements engineering paper classification and evaluation criteria: a proposal and a discussion [J]. Requirements Engineering, 11(1): 102-107.
Xiong W, Wang X T, Wu Z X. 2008. Study of a customer satisfaction-oriented model for outsourcing software quality management using Quality Function Deployment (QFD) [C]. 2008 4th International Conference on Wireless Communications, Networking and Mobile Computing, Vols 1-31, 7959-7963,13133.
Xu B, Dou Y J, Yang X H, et al., 2008. Experience of Collaborative Requirement Management in Dual-shore Software Maintenance Projects [C]. 2008 4th International Conference on Wireless Communications, Networking and Mobile Computing.
Yan Z, 2008. A Comprehensive Trust Model for Component Software [C]. In:Proc of the ICPS 2008 & Co-Located Workshops(AUPC'08, SecPerU'08, SEPS'08, & SIPE'08). 1985/09/13 ed.
Yau S S, Collofello J S, T M, 1978. Ripple effect analysis of software maintenance [C]. Proceedings of the Computer Software and Applications Conference(COM PSAC 78).
Yau S S, Landwehr C, Voas J, et al. 2003a. Challenges and recent advances in developing trustworthy software-based systems [J]. 27th Annual International Computer Software and Applications Conference, 208-208,710.
Yau S S, Landwehr C, Voas J, et al. 2003b. Challenges and recent advances in developing trustworthy software-based systems [C]. 27th Annual International Computer Software and Applications Conference, Proceedings, 208-208,710.
Yeo K T, Ren Y T. 2009. Risk Management Capability Maturity Model for Complex Product Systems (CoPS) Projects [J]. Systems Engineering, 12(4): 275-294.
Yoo N, 2004. XML-based engineering change impact analysis with non-functional requirements [C]. Serp'04: Proceedings of the International Conference on Software Engineering Research and Practice.
Yu D H, He K Q, Wang J, et al., 2008. An Algorithm for Priority Ranking of Individualized Functional Requirements in Networked Software. Gcc 2008: Seventh International Conference on Grid and Cooperative Computing, Proceedings.
Zeng Q T, Zhao Z Y, Liang Y Q. 2009. Course ontology-based user's knowledge requirement acquisition from behaviors within e-learning systems [J]. Computers & Education, 53(3): 809-818.
Zhang a Y, Sun S R, 2009. The Study on Interaction between Knowledge Flow and Knowledge Creation [C]. Proceedings of 2009 International Conference of Management Engineering and Information Technology.
Zhang H, Cao S K, Song L, et al. 2009. Development and Research of a New Open CNC Prototype System [J]. Acc 2009: Etp/Iita World Congress in Applied Computing, Computer Science, and Computer Engineering, 311-314,464.
Zhang H, Deng R R. 2009. Research on Software Requirement Analysis Based on Agile Modeling [C]. Proceedings of the 4th International Conference on Product Innovation Management, Vols I and Ii, 1327-1331,1982.
Zhang H F, Sun S D, Fang W, 2006. The research of user requirement management subsystem for the software R & D project based on the SQFD & ROMC methods [C]. Proceedings of IRNOP VII Project Research Conference.
Zhang Z N, Xie Y B, 2009. Knowledge Flow in Product Design [C]. Proceedings of the 9th Biennial Conference on Engineering Systems Design and Analysis.
Zhao S F, Chen L C, 2009. The Bp Neural Networks Applications in Bank Credit Risk Management System [C]. Proceedings of the 8th IEEE International Conference on Cognitive Informatics.
Zhao W H, Kong D Y. 2008. Complex Product Systems Critical Dimensions and Technological Knowledge Characteristics [C]. Proceedings of the 38th International Conference on Computers and Industrial Engineering, Vols 1-3, 548-552,3082.
Zheng L W, Jin Z, 2007. Requirement driven agent collaboration based on functional ontology and AMD [C]. 11th IEEE International Workshop on Future Trends of Distributed Computing Systems.
Zheng Z, Han B T, 2009. The Study on Knowledge Flow Efficiency Measure of Weighted RIN. Wmso: 2008 International Workshop on Modelling, Simulation and Optimization, Proceedings.
Zhong Q, Wang K Y, 2005. The knowledge flow in the internal knowledge network of enterprise [C]. Proceedings of the 2005 International Conference on Management Science & Engineering (12th), Vols 1- 3.
Zhuang C, Qian W. 2005. Study on the salary system for IT enterprise based on double factor motivation theory - art. no. 60410J [J]. ICMIT 2005: Information Systems and Signal Processing, 6041(J410-J410,582.
Zhuge H. 2002. Knowledge flow management for distributed team software development [J]. Knowledge-Based Systems, 15(8): 465-471.