需求工程中的若干问题研究
|
摘要
需求问题的处理是软件项目成功与否的前提条件，软件需求工程的目标是采用系统化的方法和工程化的管理手段，为软件系统提供一个准确、安全、无二义性的开发文档。本文从面向方面文档驱动需求方法出发，在需求形式化描述方法、形式化需求建模过程、面向方面需求模型的一致性验证、需求变更影响分析几个方面进行了深入研究，提出了若干方法和算法。本文主要工作如下：
1) Tabular表达式的指称语义定义。Tabular表达式是一种兼具数学的严谨性、规范性与可读性的形式化表示方法，针对Tabular表达式通用模型，给出了Tabular表达式的形式文法及指称语义。本文方法通过定义形式文法中各语法单元的语义指派方程描述了Tabular表达式的指称语义，并和其他几种Tabular表达式的语义描述方法进行了比较，分析表明，本文的语义描述方法不受Tabular表达式模型和Tabular表达式类型的限制，打破了现有方法的局限性。同时，语义的明确定义可以让用户更加精确的理解文档的含义，为后续形式化的分析与验证奠定基础。
2)基于Tabular表达式的需求文档定义方法。本文使用Tabular表达式通用模型给出了4-变量模型的形式化描述。利用Tabular表达式通用模型描述4-变量模型中变量及变量间的关系,定义了从4-变量模型到Tabular表达式的映射规则；将Tabular表达式转换为逻辑系统，定义了一系列约束，并提出了需求完整性验证方法和可行性验证方法；对构建的Tabular表达式实例提出了软件系统的可接受性验证；本文使用灯控系统典型实例对本文的方法进行了验证，实验结果表明，提出的一系列方法可以有效地描述4-变量模型并对其进行软件可接受性验证。
3)基于面向方面需求模型的完整性和一致性验证。本文针对面向方面需求方法给出了一系列提高建模准确度、检验模型完整性和一致性的策略和手段。首先，从需求依赖准确性、候选关注点分组可靠性和横切关注点判定三个角度给出了需求建模过程的验证策略；其次，给出了一个基于本体的关注点模型定义及验证方法，定义了基于本体的关注点模型，并定义了基于本体的关注点模型中完整性和一致性约束，介绍了从关注点模型到基于本体的关注点模型的映射规则及映射后的验证方法；最后通过一个实例验证了方法的可靠性，为设计和实现一个可靠的软件系统提供了有效信息。
4)量化的需求变更影响分析方法。本文提出了一种基于可达矩阵的需求变更影响分析方法，从关注点和变量两个层面分别构建其关联矩阵和可达矩阵，并通过关注点重要度、关注点距离、影响程度、隶属相同和不同关注点变量间影响程度等定义，给出了一种计算需求变更波及影响范围和影响程度的量化算法。本文给出变更影响分析具有很好的连贯性，获得的量化结果可以为后续设计和代码编写提供有效的参考。
In recent years, IT technology and its application has made rapid development, the totalinvestment of government and enterprise on IT application project has made rapid growth, atthe same time the software requirements are also increasing, the size and complexity ofsoftware is also growing, faced with this situation, software development and softwaremanagement tools are still faced with a variety of problems, making the development of manyprojects finally ending with a lot of problems or totally failure.Among the factors that lead tothe project problems and failures, requirements-related factors account for over50%of theproportion, so the processing of the requirements is a prerequisite for decide weather thesoftware development is success or not.
The goal of software requirements engineering is to use systematic methods andengineering management tools to efficiently develop the software requirements specificationwhich accurate expresses the needs of the user. In other words, the purpose of the softwarerequirements engineering is to provide a reasonable and correct development documentationfor software systems.Software requirements engineering is divided into5stages, they arerequirements elicitation, requirements modeling, formal description of requirements,requirements validation and requirements management, different requirements analysisanalyze the requirements through different aspects, and give a series of methods andtechniques range from requirements elicitation to requirements management, the currentpopular requirements analysis methods mainly are goal-oriented, object-oriented,feature-oriented and aspect-oriented.
This paper is based on aspect-oriented document-driven requirement method and has aseries of deep research on formal description method of software requirements, formalrequirement modeling process, the consistency detection of aspect-oriented requirementmodel, the requirement change impact analysis.The main work is as follows:
1) The definition of denotational semantics in Tabular expressionsTabular expressions is a formal description tool using form structure to organize function orrelationship, and it has a wide range of application in the field of requirement engineering,and it is very necessary to establish a form of semantic model for Tabular expressions. Atpresent most of the semantic description of traditional Tabular expressions is from the angle of evaluation, but there are some limitations on the semantic description of general tabularexpressions from the angle of evaluation. According to the general model for Tabularexpressions, this paper put forward the formal grammatical and denotational semantics ofTabular expressions. This method describes Tabular expressions denotational semanticsthrough defining every semantics assigned equation of the syntax unit in the formal grammar,and describes some typical form type denotational semantics in traditional and new typeTabular expressions respectively, the analysis shows that the semantic description in thispaper does not only accurately describes the semantic of Tabular expressions and is no longersubject to the Tabular expressions model and Tabular expressions type and break thelimitations of existing method, an it is a very effective method.
2) The definition method of requirement document based on Tabular expressions4-variable model is a requirement description model using environment variables and theirrelation to characterize the software behavior, it has a wide range of application inrequirements engineering.Tabular expressions general model is a formal description tool, inorder to make the4-variable model formally described and verifiable, we use Tabularexpressions general model gives a formal description of the4-variable model and give theappropriate authentication method. First, the method use Tabular expressions general model todescribe the monitor variable, control variable, and variables such as NAT, REQ, and therelation between different variables, and defines the mapping rules from4-variable model toTabular expressions; then Tabular expressions is converted to the logic system, and defines aseries of constraints and proposes the requirements integrity verification method andfeasibility authentication method based on these constraints; and put forward the acceptableverification of software system on the constructed Tabular expressions instance; for theanalysis of the feasibility and effectiveness of the proposed method, this paper uses thefamous light control system in the field of requirements engineering verified this method, theexperimental results show that the proposed method can effectively describe the4-variablemodel and verify it.
3) Integrity and consistency verification based on aspect-oriented requirements modelsEstablish the requirement model which satisfied with the integrity and consistency is thefundamental to the success of software project, verify whether requirements model related tothe nature of software development is of great significance. Aspect-oriented requirementsanalysis method is a method which takes the separation of concerns, crosscutting concernsdecision, construct the concern model as the core. This paper proposed a series strategy andmeans to improve the modeling accuracy and the integrity and consistency of verify model. First，in the acquisition process for concern model, from the requirements dependencyaccuracy, the candidate concern grouping reliability and crosscutting concerns determine thethree angles given validation strategy, to improve the accuracy of the modeling; then it gives aconcern model definition and validation method which is based on ontology, it also gives thedefinition of the concepts and their relationship in the concerns models based on ontology,and summarized the existing ontology-based requirement model integrity and consistencyconstraint rules, combined with the actual characteristics of aspect-oriented requirementsmodel defines the integrity and consistency constraints in the concerns model based onontology，and introduces the mapping rules from concern model to ontology-based concenrmodel and the verification method after mapping. Finally use an example to verify thereliability of the method, and provide useful information for the design and implementation ofa reliable sotfware system.
4) Quantified requirements change impact analysis methodSince the requirements changes in the sotfware development is inevitable, thereforeeffective software change impact analysis on the assessment and management of softwaredevelopment is necessary, requirements change impact dialysis via its assessment of thescope and extent, provide effective information for sotfware developers and managers.Aspect-oriented document-driven requirements engineering departures from the documentrequirement to provide the processes and methods based on the concerns and theirrelationship such as requirements modular, crosscutting concerns decision, and generateformalized requirements documents, under this framework, this paper proposed arequirements change impact analysis method base on the reachable matrix, in this method theassociated matrix and reachable matrix were constructed from concerns and variables the twolevel, and according to the definitions such as the importance of the concerns, the concernsdistance, the degree of inlfuence, and under the impact of the extent of the same and differentvariables concerns, it gives the quantified algorithm to calculate the scope and extend of therequirements changes impact. The change impact analysis of the concerns layer and variableslayer in this paper has good continuity, and the results can provide effective reference for thesubsequent design and code writing.
Aspect-oriented document-driven requirements method is a new requirements engineeringmethod proposed in recent years, in this paper, a lot of research work carried out under theframework of the method, and in the aspects of requirements formal deifnition, formalrequirement document method, requirement model validation and change impact analysishave got a series of achievements, and an example is given to verify.
1) Tabular表达式的指称语义定义。Tabular表达式是一种兼具数学的严谨性、规范性与可读性的形式化表示方法，针对Tabular表达式通用模型，给出了Tabular表达式的形式文法及指称语义。本文方法通过定义形式文法中各语法单元的语义指派方程描述了Tabular表达式的指称语义，并和其他几种Tabular表达式的语义描述方法进行了比较，分析表明，本文的语义描述方法不受Tabular表达式模型和Tabular表达式类型的限制，打破了现有方法的局限性。同时，语义的明确定义可以让用户更加精确的理解文档的含义，为后续形式化的分析与验证奠定基础。
2)基于Tabular表达式的需求文档定义方法。本文使用Tabular表达式通用模型给出了4-变量模型的形式化描述。利用Tabular表达式通用模型描述4-变量模型中变量及变量间的关系,定义了从4-变量模型到Tabular表达式的映射规则；将Tabular表达式转换为逻辑系统，定义了一系列约束，并提出了需求完整性验证方法和可行性验证方法；对构建的Tabular表达式实例提出了软件系统的可接受性验证；本文使用灯控系统典型实例对本文的方法进行了验证，实验结果表明，提出的一系列方法可以有效地描述4-变量模型并对其进行软件可接受性验证。
3)基于面向方面需求模型的完整性和一致性验证。本文针对面向方面需求方法给出了一系列提高建模准确度、检验模型完整性和一致性的策略和手段。首先，从需求依赖准确性、候选关注点分组可靠性和横切关注点判定三个角度给出了需求建模过程的验证策略；其次，给出了一个基于本体的关注点模型定义及验证方法，定义了基于本体的关注点模型，并定义了基于本体的关注点模型中完整性和一致性约束，介绍了从关注点模型到基于本体的关注点模型的映射规则及映射后的验证方法；最后通过一个实例验证了方法的可靠性，为设计和实现一个可靠的软件系统提供了有效信息。
4)量化的需求变更影响分析方法。本文提出了一种基于可达矩阵的需求变更影响分析方法，从关注点和变量两个层面分别构建其关联矩阵和可达矩阵，并通过关注点重要度、关注点距离、影响程度、隶属相同和不同关注点变量间影响程度等定义，给出了一种计算需求变更波及影响范围和影响程度的量化算法。本文给出变更影响分析具有很好的连贯性，获得的量化结果可以为后续设计和代码编写提供有效的参考。
In recent years, IT technology and its application has made rapid development, the totalinvestment of government and enterprise on IT application project has made rapid growth, atthe same time the software requirements are also increasing, the size and complexity ofsoftware is also growing, faced with this situation, software development and softwaremanagement tools are still faced with a variety of problems, making the development of manyprojects finally ending with a lot of problems or totally failure.Among the factors that lead tothe project problems and failures, requirements-related factors account for over50%of theproportion, so the processing of the requirements is a prerequisite for decide weather thesoftware development is success or not.
The goal of software requirements engineering is to use systematic methods andengineering management tools to efficiently develop the software requirements specificationwhich accurate expresses the needs of the user. In other words, the purpose of the softwarerequirements engineering is to provide a reasonable and correct development documentationfor software systems.Software requirements engineering is divided into5stages, they arerequirements elicitation, requirements modeling, formal description of requirements,requirements validation and requirements management, different requirements analysisanalyze the requirements through different aspects, and give a series of methods andtechniques range from requirements elicitation to requirements management, the currentpopular requirements analysis methods mainly are goal-oriented, object-oriented,feature-oriented and aspect-oriented.
This paper is based on aspect-oriented document-driven requirement method and has aseries of deep research on formal description method of software requirements, formalrequirement modeling process, the consistency detection of aspect-oriented requirementmodel, the requirement change impact analysis.The main work is as follows:
1) The definition of denotational semantics in Tabular expressionsTabular expressions is a formal description tool using form structure to organize function orrelationship, and it has a wide range of application in the field of requirement engineering,and it is very necessary to establish a form of semantic model for Tabular expressions. Atpresent most of the semantic description of traditional Tabular expressions is from the angle of evaluation, but there are some limitations on the semantic description of general tabularexpressions from the angle of evaluation. According to the general model for Tabularexpressions, this paper put forward the formal grammatical and denotational semantics ofTabular expressions. This method describes Tabular expressions denotational semanticsthrough defining every semantics assigned equation of the syntax unit in the formal grammar,and describes some typical form type denotational semantics in traditional and new typeTabular expressions respectively, the analysis shows that the semantic description in thispaper does not only accurately describes the semantic of Tabular expressions and is no longersubject to the Tabular expressions model and Tabular expressions type and break thelimitations of existing method, an it is a very effective method.
2) The definition method of requirement document based on Tabular expressions4-variable model is a requirement description model using environment variables and theirrelation to characterize the software behavior, it has a wide range of application inrequirements engineering.Tabular expressions general model is a formal description tool, inorder to make the4-variable model formally described and verifiable, we use Tabularexpressions general model gives a formal description of the4-variable model and give theappropriate authentication method. First, the method use Tabular expressions general model todescribe the monitor variable, control variable, and variables such as NAT, REQ, and therelation between different variables, and defines the mapping rules from4-variable model toTabular expressions; then Tabular expressions is converted to the logic system, and defines aseries of constraints and proposes the requirements integrity verification method andfeasibility authentication method based on these constraints; and put forward the acceptableverification of software system on the constructed Tabular expressions instance; for theanalysis of the feasibility and effectiveness of the proposed method, this paper uses thefamous light control system in the field of requirements engineering verified this method, theexperimental results show that the proposed method can effectively describe the4-variablemodel and verify it.
3) Integrity and consistency verification based on aspect-oriented requirements modelsEstablish the requirement model which satisfied with the integrity and consistency is thefundamental to the success of software project, verify whether requirements model related tothe nature of software development is of great significance. Aspect-oriented requirementsanalysis method is a method which takes the separation of concerns, crosscutting concernsdecision, construct the concern model as the core. This paper proposed a series strategy andmeans to improve the modeling accuracy and the integrity and consistency of verify model. First，in the acquisition process for concern model, from the requirements dependencyaccuracy, the candidate concern grouping reliability and crosscutting concerns determine thethree angles given validation strategy, to improve the accuracy of the modeling; then it gives aconcern model definition and validation method which is based on ontology, it also gives thedefinition of the concepts and their relationship in the concerns models based on ontology,and summarized the existing ontology-based requirement model integrity and consistencyconstraint rules, combined with the actual characteristics of aspect-oriented requirementsmodel defines the integrity and consistency constraints in the concerns model based onontology，and introduces the mapping rules from concern model to ontology-based concenrmodel and the verification method after mapping. Finally use an example to verify thereliability of the method, and provide useful information for the design and implementation ofa reliable sotfware system.
4) Quantified requirements change impact analysis methodSince the requirements changes in the sotfware development is inevitable, thereforeeffective software change impact analysis on the assessment and management of softwaredevelopment is necessary, requirements change impact dialysis via its assessment of thescope and extent, provide effective information for sotfware developers and managers.Aspect-oriented document-driven requirements engineering departures from the documentrequirement to provide the processes and methods based on the concerns and theirrelationship such as requirements modular, crosscutting concerns decision, and generateformalized requirements documents, under this framework, this paper proposed arequirements change impact analysis method base on the reachable matrix, in this method theassociated matrix and reachable matrix were constructed from concerns and variables the twolevel, and according to the definitions such as the importance of the concerns, the concernsdistance, the degree of inlfuence, and under the impact of the extent of the same and differentvariables concerns, it gives the quantified algorithm to calculate the scope and extend of therequirements changes impact. The change impact analysis of the concerns layer and variableslayer in this paper has good continuity, and the results can provide effective reference for thesubsequent design and code writing.
Aspect-oriented document-driven requirements method is a new requirements engineeringmethod proposed in recent years, in this paper, a lot of research work carried out under theframework of the method, and in the aspects of requirements formal deifnition, formalrequirement document method, requirement model validation and change impact analysishave got a series of achievements, and an example is given to verify.
引文
[1]金芝，刘璘，金英.软件需求工程：原理和方法[M].北京:科学出版社,2008.
[2] Ian K Bray.An Introduction to requirements engineering[M]. Addison-Wesley,2002
[3] Flowers S. Software Failure:management failure[M].New York:Wiley,1996
[4] Jin Zhi, Revisiting the meaning of requirements[J],Journal of Computer Science andTechnology,2006,21(1):32~40
[5] Macaulay LA. Requirements Engineering[M]. Springer Verley,1996
[6]史济民.软件工程原理方法及应用[M].北京：高等教育出版社,2009
[7] Roger S.Pressman.Software Engineering: A Practitioner's Approach[M]. McGraw-Hill,2005
[8] John Boddie.Crunch mode: building effective systems on a tight schedule[M].Prentice-Hall,1987
[9] Edward Yourdon. Death March[M]. Prentice Hall,2004
[10]Jackson M. Problem Frames:Analyzing and structuring software developmentproblems[M].Addison-Wesley,2001
[11]Charette R N. Why software fails[J]. IEEE spectrum,2005,42(9):36.
[12]卢梅,李树明,软件需求工程——方法及工具评述[J].计算机研究与发展,1999,36(11),1289~1300
[13]Thayer R H. Tutorial:System and software requirements engineering[C].Los Alamitos,IEEE Computer Society Press,1990,1~3
[14]Jeffrey O.Grady. System requirements analysis[M].Academic Press,2006
[15]Ralph R Young, The requirements engineering handbook[M].Artech House,2004
[16]Herb Krasner, A field study of the software design process for largesystems[J],Communications of theACM,1988,31(11),1268-1287
[17]M Jarke.K Pohl, Software engineering in2001(vitually)managing a changing reality[J].Software Engineering Journal,1994,9(6),257~266
[18]Anton Ana I. Goal-Based requirements analysis[C], Proceedings of the SecondInternational Conference on Requirements Engineering, IEEE,ICRE’96,136-144
[19]Anton Ana I. Goal identification and refinement in the specification of software-basedinformation systems[D].Georgia Institute of Technology,1997
[20]Dardenne A, van Lamsweerde A. Goal-directed requirements acquisition[J],Science ofComputer Programming,20(1),3~50
[21]Van Lamsweerde,A. Goal-oriented requirements engineering:a guided tour[C],Requirements Engineering,IEEE,2001,249-262
[22]Goldsby,H.J. Goal-based modeling of dynamically adaptive system requirements[C],Engineering of Computer Based System,IEEE, ECBS2008,36-45
[23]刘璘,面向主体的需求分析[D],中国科学院数学研究所1999
[24]Mylopoulos J, Borgida A, Telos:Representing knowledge about information systems[J].ACM Transactions on Information systems(TOIS),8(4),1990
[25]王家重,王志坚,尹波,许家福.对象式软件需求模型及其机器支撑[J].软件学报,1998,9(6):414-418.
[26]Peter Coad, Edward Yourdon, Object-oriented analysis[M], Yourdon Press,1991
[27]Donald G. Firesmith, Object-Oriented Requirements Analysis and Logical Design: ASoftware Engineering Approach[M], Wiley,1993
[28]Sarnath Ramnath, Object-Oriented Analysis and Design[M], Springer,2011
[29]Don S. Batory. Feature Models, Grammars, and Propositional Formulas[C], Proceedingsof the9th international conference on Software Product Lines (SPLC’05),Springer-Verlag,2005:7-20.
[30]Czarnecki,K. Feature diagrams and logics:there and back again[C],IEEE Proceedings ofSPLC’07,2007,23-34
[31]K.C.Kang,J.Lee. Feature-oriented product line engineering[J] IEEE Software,2002,19,28-65
[32]Rashid, A. Early aspects: a model for aspect-oriented requirementsengineering[C],Proceedings of the10h IEEE International Requirements EngineeringConference(RE '02),Washington: IEEE,2002:199-202.
[33]Ying Jin, Weiping Hao, Pengfei Ma. Concern Based Approach to Generating SCRRequirement Specification: A Case Study[C],2009WRI World Congress on ComputerScience and Information Engineering(CSIE2009).Washington: IEEE,2009:695-700.
[34] HaithamS.Hamaza. Separetion of Concerns for Evolving Systems: A Stability-DrivenApproach[C],Workshop on Modeling and Analysis of Concerns in Software (MACS2005). New York:ACM,2005.
[35]Meyer B. On formalism in specifications[J]. IEEE software,1985,2(1):6-26.
[36]Wing J M. Aspecifier's introduction to formal methods[J]. Computer,1990,23(9):8-22.
[37]Spivey J M. Introducing Z: a Specification Language and its Formal Semantics[J].1988.
[38]Jones C B. Systematic software development using VDM[M]. Englewood Cliffs: PrenticeHall,1990.
[39]Koymans R, Vytopil J, de Roever W P. Real-time programming and asynchronousmessage passing[C]//Proceedings of the second annual ACM symposium on Principles ofdistributed computing.ACM,1983:187-197.
[40]Abrial J R, Hallerstede S. Refinement, decomposition, and instantiation of discretemodels:Application to Event-B[J]. Fundamenta Informaticae,2007,77(1):1-28.
[41]D.L.Parnas. Inspection of safety critical software using function tables[C], Proccedings ofIFIP World Congress,1994,pp270-277
[42]K. L. Heninger, J. Kallander, D. L. Parnas, J. E. Shore, Software requirements for theA-7E Aircraft[R], NRL Memorandum Report3876, U.S. Naval Research Lab,1978.
[43]K. L. Heninger, Specifying software requirements for complex systems: New Techniquesand theirApplications[C], IEEE Transactions on Software Engineering,1980,6(1),2-13.
[44]P. C. Clements, function specification for the A-7E function driver module[R], NRLMemorandum Report4658, U.S. Naval Research Lab,1981.
[45]D. L. Parnas, G. J. K. Asmis, J. D. Kendall, Reviewable development of safety criticalsoftware[C], International Conference on Control and Instrumentation in NuclearInstallations, Glasgow, U.K,1990, No.4.3.
[46]D. L. Parnas, G. L. K. Asmis, J. Madey, Assessment of safety-critical software in nuclearpower plants[J], Nuclear Safety,1991,32(2),189-198.
[47]D. L. Parnas, J. Madey, Functional documentation for computer systems engineering[J],Science of Computer Programming,1995,25(1),41-61.
[48]D. L. Parnas, J. Madey, M. Iglewski, Precise documentation of well-Structuredprograms[C], IEEE Transactions on Software Engineering,1994,948-976.
[49]R.Janicki, R. Khédri, On formal semantics of tabular expressions[J], Science ofComputer Programming,2001,39,189-214.
[50]R.Janicki, A.Wassyng. Tabular expressions and their relational semantics[J],FundamentaInformaticae,2005,67(4),343-370.
[51]R.F. Abraham. Evaluating generalized Tabular expressions[D]. McMaster UniversityCanada,1997.
[52]W. Kahl. Compositional syntax and semantics of tables[R]. Technical Report SQRL15,Software Quality Research Laboratory, McMaster University Canada,2003.
[53]Ying Jin,D,L,Parnas. Defining the meaning of tabular mathematical expressions[J].Science of Computer Programming,2010,75(11),980-1000.
[54]H. Markus, Dr. Konrad, Tabular notations for state machine-based specifications[J]. TheJournal of Defense Software Engineering,2008,3,18-23.
[55]Renaud De Landtsher,E.Letier, Deriving tabular event-based specifications fromgoal-oriented requirements models[J].Requirements Engineering,2004,9(2),104-120.
[56]Constance L.Heitmeyer, Software Cost Reduction[M],Wiley,2002
[57]Xin Feng,Tabular Expression-Based Testing Strategies: A Comparison[C], IEEETAICPART,2007,134.
[58]Xin Feng,Fault Propagation in Tabular Expression-Based Specifications[C], IEEECOMPSAC’08,2008,180-183.
[59]R.Degiovanni,Abstraction Based Automated Test Generation from Formal TabularRequirements[J],Tests and Proofs,2011,6706,84-101.
[60]Baber, Disciplined methods of software specification:A case study[C], InformationTechnology:Coding and Computing,IEEE,2005,2,428-437.
[61]David L.Parnas,The Tabular method for relational documentation[J]. Electronic Notes inTheoretical computer science,2003,44(3),1-26.
[62]C.Eles,M.Lawford,A Tabular expression toolbox for Matlab/Simulink[J].NASA FormalMethods,2011,6617,494-499.
[63]Dennis K. Peters,M.Lawford, An IDE for software development using tabularexpressions[C],ACM CASCON‘07,2007,248-251.
[64]O.Sam, R.John, Analyzing Tabular and state-transition requirements specifications inPVS[R],NASALangley Technical Report,2007
[65]Nathan Weston, Ruzanna Chitchyan, Awais Rashid. Formal semantic conflict detection inaspect-oriented requirements[J]. Requirements Engineering,2009,14(4):247-268.
[66]Alberto Sardinha, Ruzanna Chitchyan,.EA-Analyzer: automating conflict detection in alarge set of textual aspect-oriented requirements [J]. Automated Software Engineering,2012.(In Press)
[67]Joao Araujo, Jon Whittle. Modeling and composing scenario-based requirements withaspects [C].Proceedings of the12th IEEE International Requirements EngineeringConference(RE '04), Washington: IEEE,2004:122-131.
[68]Katharina Mehner,Mattia Monga,Gabriele Taentzer. Interaction analysis inaspect-oriented models[C].Proceedings of the14th IEEE International RequirementsEngineering Conference(RE '06). Washington: IEEE,2006:66-75.
[69]Kedian Mu, Zhi Jin,Verfying software requirements based on answer set programming[J].Knowledge Science, Engineering and Management,2009,5914,263-274.
[70]陆汝钤,金芝.面向本体的需求分析,软件学报,2000,11(8):1009-1017.
[71]Seok Won Lee, Robin A. Gandhi. ontology-based active requirements engineeringframework[C]//Proceedings of the12th Asia-Pacific Software Engineering Conference.Washington: IEEE,2005:481-490.
[72]Chi-Lun Liu. Ontology-Based Requirements Conflicts Analysis in ActivityDiagrams[C]//Proceedings of the International Conference on Computational Science andItsApplications.Berlin: Springer-Verlag,2009.
[73]Katja Siegemund, Edward J Thomas, Yuting Zhao, Jeff Pan, Uwe Assmann. TowardsOntology-driven requirements engineering[C]//Proceedings of The10th InternationalSemantic Web Conference. Koblenz, Germany,2011.
[74]陈小红,尹斌,金芝.基于问题框架的需求建模:一种本体制导的方法[J].软件学报,2011,22(2):177-194.
[75]Jianmei Guo, Yinglin Wang, Pablo Trinidad, David Benavides. Consistency Maintenancefor Evolving Feature Models [J]. Expert Systems with Applications,2012,39(5):4987-4998.
[76]Bohner SA. Impact analysis in the software change process: A year2000perspective[C].International Conference on Software Maintenance (ICSM’96). IEEE,1996.42~51.
[77]Erich SG, Graves TL, Karr AF. Visualizing software changes[J]. Software Engineering,2002,28(4):396~412.
[78]Lai AY, Murphy GC. Behavioural concern modeling for software changetasks[C].International Conference on Software Maintenance (ICSM‘2002). IEEE,2002.112~121.
[79]王映辉,张世琨.基于可达矩阵的软件体系结构演化波及效应分析[J].软件学报,2004,15(8),1107-1115.
[80]Chaumun Ma,Kabaili H, Keller RK, Lustman F. Achange impact model for changeablityassement in object-oriented software systems[C]. Proceedings Of the3rd EuropeanConference on Software Maintenance and Reenginnering. Washington: IEEE,1999.
[81]Kung,D.C.On regression testing of object-oriented programs[J].Journal of Systems andSoftware.1996,32(1),21-40.
[82]Barbara G. Ryder, Change impact analysis for object-oriented programs[C]. PASTE’01,2001,ACM,46-53.
[83]Antje von Knethen. A trace model for system requirements changes on embeddedsystems[C], IWPSE’01,ACM,2001,17-26.
[84]Nicolas Sannier, Toward multilevel textual requirements traceability using model-drivenengineering and information retrieval[C],Scond International Model-DrivenRequirements Engineering Workshop,2012.
[85]Wanja Hofer, Daniel Lohmann. Concern Impact Analysis in Configurable SystemSoftware The AUTOSAR OS Case[C]//Proceedings of the2008AOSD workshop onAspects, components, and patterns for infrastructure software2008. New York:ACM,2008.
[86]Ying Jin, Applying pagerank algorithm in requirement concern impactanalysis[C],COMSPAC,IEEE,2009,361-366.
[87]Jameleddine Hassine. Change impact analysis for requirement evolution use Use CaseMaps[C] Principles of Software Evolution,IEEE,2005,81-90.
[88]Ying Jin, A concern-based approach to generating formal requirements specification[J],Frontiers of computer Science In China,2010,4(2),162~172.
[89]Awais Rashid, Yijun Yu. Aspect-Oriented Requirements Engineering: AnIntroduction[C].Proceedings of the16th IEEE International Requirements EngineeringConference (RE'08). IEEE,2008,306-309.
[90]D. L. Parnas. Tabular Representation of Relations. Technical Report CRL260, McMasterUniversity Canada,1992.
[91]D.L. Parnas. The use of mathematics in software quality assurance[J].Frontiers ofComputer Science,2012,6(1),3-16.
[92]Stefan Queins, Gerhard Zimmermann.The Light Control Case Study:ProblemDescription[J]. Journal of Universal Computer Science, Vol.6, No.7(2000),586-596.
[93]Heitmeyer, C. L., Bharadwaj, R.,Applying the SCR Requirements Method to the LightControl Case Study[J], Journal of Universal Computer Science, Vol.6, No.7(2000),650-678.
[94]Yunja Choi, Model Checking RSML-e requirements[C],High Assurance SystemsEngineering,IEEE,2002,109-118.
[95]Joanne M.Atlee,Michael A.Buckley,A logic-model semantics for SCR softwarerequirements[C]. SIGSOFT international symposium on Software testing andanalysis,ACM,1996,21(3),280-292.
[96]Heitmeyer C. Automated consistency checking of requirements specifications[C].Transactions on software engineering and methodology,ACM,1996,5(3),231-261.
[97]Angelo Gargantini, Using model checking to generate tests from requirementsspecifications[J],Software Engineering ESEC/FSE’99,1999,1687,146-162.
[98]Heitmeyer C. SCR*:A toolset for specifying and analyzing software requirements[J].ComputerAided Verification,1998,1427,526-531.
[99]Heitmeyer,C. Using the SCR*toolset to specify software requirements[C].IndustrialStrength Formal Specification Techniques,IEEE,1998,12-13.
[100] Isabel Sofia Brito, Filipe Vieira, Ana Moreira, Rita A. Ribeiro. Handling conflicts inaspectural requirements compositions [J]. Trans Aspect Oriented SoftwDev (TAOSD),2007,4620(2007),144-146.
[101] Bran McBride,Jena:Implementing the RDF model and syntax specification[C],Semantic Web Workshop,2001.
[102] Bran McBride, Jena:a semantic web toolkit[C],InternetComputing,IEEE,2002,6,55-59
[103] A Sampaio, R Chitchyan, A Rashid, P Rayson.EA-Miner:a Tool for AutomatingAspect-Oriented Requirements Identification[C].International Conference on Automatedsoftware engineering(ASE05).ACM,2005:352-355.
[104] Ramzan S, Ikram N. Making Decision in Requirement Change Management[C].1stInternational Conference on ICIT. IEEE,2005:309-312.
[105]李引,李娟,李明树,动态需求跟踪方法及跟踪精度问题研究[J].软件学报,2009.20(2):177-192
[106] James Steven. Analyzing the impact of changing softwarerequirements[C]//Proceedings of IEEE International Conference on SoftwareMaintenance. Washington: IEEE,2001:190-195.
[2] Ian K Bray.An Introduction to requirements engineering[M]. Addison-Wesley,2002
[3] Flowers S. Software Failure:management failure[M].New York:Wiley,1996
[4] Jin Zhi, Revisiting the meaning of requirements[J],Journal of Computer Science andTechnology,2006,21(1):32~40
[5] Macaulay LA. Requirements Engineering[M]. Springer Verley,1996
[6]史济民.软件工程原理方法及应用[M].北京：高等教育出版社,2009
[7] Roger S.Pressman.Software Engineering: A Practitioner's Approach[M]. McGraw-Hill,2005
[8] John Boddie.Crunch mode: building effective systems on a tight schedule[M].Prentice-Hall,1987
[9] Edward Yourdon. Death March[M]. Prentice Hall,2004
[10]Jackson M. Problem Frames:Analyzing and structuring software developmentproblems[M].Addison-Wesley,2001
[11]Charette R N. Why software fails[J]. IEEE spectrum,2005,42(9):36.
[12]卢梅,李树明,软件需求工程——方法及工具评述[J].计算机研究与发展,1999,36(11),1289~1300
[13]Thayer R H. Tutorial:System and software requirements engineering[C].Los Alamitos,IEEE Computer Society Press,1990,1~3
[14]Jeffrey O.Grady. System requirements analysis[M].Academic Press,2006
[15]Ralph R Young, The requirements engineering handbook[M].Artech House,2004
[16]Herb Krasner, A field study of the software design process for largesystems[J],Communications of theACM,1988,31(11),1268-1287
[17]M Jarke.K Pohl, Software engineering in2001(vitually)managing a changing reality[J].Software Engineering Journal,1994,9(6),257~266
[18]Anton Ana I. Goal-Based requirements analysis[C], Proceedings of the SecondInternational Conference on Requirements Engineering, IEEE,ICRE’96,136-144
[19]Anton Ana I. Goal identification and refinement in the specification of software-basedinformation systems[D].Georgia Institute of Technology,1997
[20]Dardenne A, van Lamsweerde A. Goal-directed requirements acquisition[J],Science ofComputer Programming,20(1),3~50
[21]Van Lamsweerde,A. Goal-oriented requirements engineering:a guided tour[C],Requirements Engineering,IEEE,2001,249-262
[22]Goldsby,H.J. Goal-based modeling of dynamically adaptive system requirements[C],Engineering of Computer Based System,IEEE, ECBS2008,36-45
[23]刘璘,面向主体的需求分析[D],中国科学院数学研究所1999
[24]Mylopoulos J, Borgida A, Telos:Representing knowledge about information systems[J].ACM Transactions on Information systems(TOIS),8(4),1990
[25]王家重,王志坚,尹波,许家福.对象式软件需求模型及其机器支撑[J].软件学报,1998,9(6):414-418.
[26]Peter Coad, Edward Yourdon, Object-oriented analysis[M], Yourdon Press,1991
[27]Donald G. Firesmith, Object-Oriented Requirements Analysis and Logical Design: ASoftware Engineering Approach[M], Wiley,1993
[28]Sarnath Ramnath, Object-Oriented Analysis and Design[M], Springer,2011
[29]Don S. Batory. Feature Models, Grammars, and Propositional Formulas[C], Proceedingsof the9th international conference on Software Product Lines (SPLC’05),Springer-Verlag,2005:7-20.
[30]Czarnecki,K. Feature diagrams and logics:there and back again[C],IEEE Proceedings ofSPLC’07,2007,23-34
[31]K.C.Kang,J.Lee. Feature-oriented product line engineering[J] IEEE Software,2002,19,28-65
[32]Rashid, A. Early aspects: a model for aspect-oriented requirementsengineering[C],Proceedings of the10h IEEE International Requirements EngineeringConference(RE '02),Washington: IEEE,2002:199-202.
[33]Ying Jin, Weiping Hao, Pengfei Ma. Concern Based Approach to Generating SCRRequirement Specification: A Case Study[C],2009WRI World Congress on ComputerScience and Information Engineering(CSIE2009).Washington: IEEE,2009:695-700.
[34] HaithamS.Hamaza. Separetion of Concerns for Evolving Systems: A Stability-DrivenApproach[C],Workshop on Modeling and Analysis of Concerns in Software (MACS2005). New York:ACM,2005.
[35]Meyer B. On formalism in specifications[J]. IEEE software,1985,2(1):6-26.
[36]Wing J M. Aspecifier's introduction to formal methods[J]. Computer,1990,23(9):8-22.
[37]Spivey J M. Introducing Z: a Specification Language and its Formal Semantics[J].1988.
[38]Jones C B. Systematic software development using VDM[M]. Englewood Cliffs: PrenticeHall,1990.
[39]Koymans R, Vytopil J, de Roever W P. Real-time programming and asynchronousmessage passing[C]//Proceedings of the second annual ACM symposium on Principles ofdistributed computing.ACM,1983:187-197.
[40]Abrial J R, Hallerstede S. Refinement, decomposition, and instantiation of discretemodels:Application to Event-B[J]. Fundamenta Informaticae,2007,77(1):1-28.
[41]D.L.Parnas. Inspection of safety critical software using function tables[C], Proccedings ofIFIP World Congress,1994,pp270-277
[42]K. L. Heninger, J. Kallander, D. L. Parnas, J. E. Shore, Software requirements for theA-7E Aircraft[R], NRL Memorandum Report3876, U.S. Naval Research Lab,1978.
[43]K. L. Heninger, Specifying software requirements for complex systems: New Techniquesand theirApplications[C], IEEE Transactions on Software Engineering,1980,6(1),2-13.
[44]P. C. Clements, function specification for the A-7E function driver module[R], NRLMemorandum Report4658, U.S. Naval Research Lab,1981.
[45]D. L. Parnas, G. J. K. Asmis, J. D. Kendall, Reviewable development of safety criticalsoftware[C], International Conference on Control and Instrumentation in NuclearInstallations, Glasgow, U.K,1990, No.4.3.
[46]D. L. Parnas, G. L. K. Asmis, J. Madey, Assessment of safety-critical software in nuclearpower plants[J], Nuclear Safety,1991,32(2),189-198.
[47]D. L. Parnas, J. Madey, Functional documentation for computer systems engineering[J],Science of Computer Programming,1995,25(1),41-61.
[48]D. L. Parnas, J. Madey, M. Iglewski, Precise documentation of well-Structuredprograms[C], IEEE Transactions on Software Engineering,1994,948-976.
[49]R.Janicki, R. Khédri, On formal semantics of tabular expressions[J], Science ofComputer Programming,2001,39,189-214.
[50]R.Janicki, A.Wassyng. Tabular expressions and their relational semantics[J],FundamentaInformaticae,2005,67(4),343-370.
[51]R.F. Abraham. Evaluating generalized Tabular expressions[D]. McMaster UniversityCanada,1997.
[52]W. Kahl. Compositional syntax and semantics of tables[R]. Technical Report SQRL15,Software Quality Research Laboratory, McMaster University Canada,2003.
[53]Ying Jin,D,L,Parnas. Defining the meaning of tabular mathematical expressions[J].Science of Computer Programming,2010,75(11),980-1000.
[54]H. Markus, Dr. Konrad, Tabular notations for state machine-based specifications[J]. TheJournal of Defense Software Engineering,2008,3,18-23.
[55]Renaud De Landtsher,E.Letier, Deriving tabular event-based specifications fromgoal-oriented requirements models[J].Requirements Engineering,2004,9(2),104-120.
[56]Constance L.Heitmeyer, Software Cost Reduction[M],Wiley,2002
[57]Xin Feng,Tabular Expression-Based Testing Strategies: A Comparison[C], IEEETAICPART,2007,134.
[58]Xin Feng,Fault Propagation in Tabular Expression-Based Specifications[C], IEEECOMPSAC’08,2008,180-183.
[59]R.Degiovanni,Abstraction Based Automated Test Generation from Formal TabularRequirements[J],Tests and Proofs,2011,6706,84-101.
[60]Baber, Disciplined methods of software specification:A case study[C], InformationTechnology:Coding and Computing,IEEE,2005,2,428-437.
[61]David L.Parnas,The Tabular method for relational documentation[J]. Electronic Notes inTheoretical computer science,2003,44(3),1-26.
[62]C.Eles,M.Lawford,A Tabular expression toolbox for Matlab/Simulink[J].NASA FormalMethods,2011,6617,494-499.
[63]Dennis K. Peters,M.Lawford, An IDE for software development using tabularexpressions[C],ACM CASCON‘07,2007,248-251.
[64]O.Sam, R.John, Analyzing Tabular and state-transition requirements specifications inPVS[R],NASALangley Technical Report,2007
[65]Nathan Weston, Ruzanna Chitchyan, Awais Rashid. Formal semantic conflict detection inaspect-oriented requirements[J]. Requirements Engineering,2009,14(4):247-268.
[66]Alberto Sardinha, Ruzanna Chitchyan,.EA-Analyzer: automating conflict detection in alarge set of textual aspect-oriented requirements [J]. Automated Software Engineering,2012.(In Press)
[67]Joao Araujo, Jon Whittle. Modeling and composing scenario-based requirements withaspects [C].Proceedings of the12th IEEE International Requirements EngineeringConference(RE '04), Washington: IEEE,2004:122-131.
[68]Katharina Mehner,Mattia Monga,Gabriele Taentzer. Interaction analysis inaspect-oriented models[C].Proceedings of the14th IEEE International RequirementsEngineering Conference(RE '06). Washington: IEEE,2006:66-75.
[69]Kedian Mu, Zhi Jin,Verfying software requirements based on answer set programming[J].Knowledge Science, Engineering and Management,2009,5914,263-274.
[70]陆汝钤,金芝.面向本体的需求分析,软件学报,2000,11(8):1009-1017.
[71]Seok Won Lee, Robin A. Gandhi. ontology-based active requirements engineeringframework[C]//Proceedings of the12th Asia-Pacific Software Engineering Conference.Washington: IEEE,2005:481-490.
[72]Chi-Lun Liu. Ontology-Based Requirements Conflicts Analysis in ActivityDiagrams[C]//Proceedings of the International Conference on Computational Science andItsApplications.Berlin: Springer-Verlag,2009.
[73]Katja Siegemund, Edward J Thomas, Yuting Zhao, Jeff Pan, Uwe Assmann. TowardsOntology-driven requirements engineering[C]//Proceedings of The10th InternationalSemantic Web Conference. Koblenz, Germany,2011.
[74]陈小红,尹斌,金芝.基于问题框架的需求建模:一种本体制导的方法[J].软件学报,2011,22(2):177-194.
[75]Jianmei Guo, Yinglin Wang, Pablo Trinidad, David Benavides. Consistency Maintenancefor Evolving Feature Models [J]. Expert Systems with Applications,2012,39(5):4987-4998.
[76]Bohner SA. Impact analysis in the software change process: A year2000perspective[C].International Conference on Software Maintenance (ICSM’96). IEEE,1996.42~51.
[77]Erich SG, Graves TL, Karr AF. Visualizing software changes[J]. Software Engineering,2002,28(4):396~412.
[78]Lai AY, Murphy GC. Behavioural concern modeling for software changetasks[C].International Conference on Software Maintenance (ICSM‘2002). IEEE,2002.112~121.
[79]王映辉,张世琨.基于可达矩阵的软件体系结构演化波及效应分析[J].软件学报,2004,15(8),1107-1115.
[80]Chaumun Ma,Kabaili H, Keller RK, Lustman F. Achange impact model for changeablityassement in object-oriented software systems[C]. Proceedings Of the3rd EuropeanConference on Software Maintenance and Reenginnering. Washington: IEEE,1999.
[81]Kung,D.C.On regression testing of object-oriented programs[J].Journal of Systems andSoftware.1996,32(1),21-40.
[82]Barbara G. Ryder, Change impact analysis for object-oriented programs[C]. PASTE’01,2001,ACM,46-53.
[83]Antje von Knethen. A trace model for system requirements changes on embeddedsystems[C], IWPSE’01,ACM,2001,17-26.
[84]Nicolas Sannier, Toward multilevel textual requirements traceability using model-drivenengineering and information retrieval[C],Scond International Model-DrivenRequirements Engineering Workshop,2012.
[85]Wanja Hofer, Daniel Lohmann. Concern Impact Analysis in Configurable SystemSoftware The AUTOSAR OS Case[C]//Proceedings of the2008AOSD workshop onAspects, components, and patterns for infrastructure software2008. New York:ACM,2008.
[86]Ying Jin, Applying pagerank algorithm in requirement concern impactanalysis[C],COMSPAC,IEEE,2009,361-366.
[87]Jameleddine Hassine. Change impact analysis for requirement evolution use Use CaseMaps[C] Principles of Software Evolution,IEEE,2005,81-90.
[88]Ying Jin, A concern-based approach to generating formal requirements specification[J],Frontiers of computer Science In China,2010,4(2),162~172.
[89]Awais Rashid, Yijun Yu. Aspect-Oriented Requirements Engineering: AnIntroduction[C].Proceedings of the16th IEEE International Requirements EngineeringConference (RE'08). IEEE,2008,306-309.
[90]D. L. Parnas. Tabular Representation of Relations. Technical Report CRL260, McMasterUniversity Canada,1992.
[91]D.L. Parnas. The use of mathematics in software quality assurance[J].Frontiers ofComputer Science,2012,6(1),3-16.
[92]Stefan Queins, Gerhard Zimmermann.The Light Control Case Study:ProblemDescription[J]. Journal of Universal Computer Science, Vol.6, No.7(2000),586-596.
[93]Heitmeyer, C. L., Bharadwaj, R.,Applying the SCR Requirements Method to the LightControl Case Study[J], Journal of Universal Computer Science, Vol.6, No.7(2000),650-678.
[94]Yunja Choi, Model Checking RSML-e requirements[C],High Assurance SystemsEngineering,IEEE,2002,109-118.
[95]Joanne M.Atlee,Michael A.Buckley,A logic-model semantics for SCR softwarerequirements[C]. SIGSOFT international symposium on Software testing andanalysis,ACM,1996,21(3),280-292.
[96]Heitmeyer C. Automated consistency checking of requirements specifications[C].Transactions on software engineering and methodology,ACM,1996,5(3),231-261.
[97]Angelo Gargantini, Using model checking to generate tests from requirementsspecifications[J],Software Engineering ESEC/FSE’99,1999,1687,146-162.
[98]Heitmeyer C. SCR*:A toolset for specifying and analyzing software requirements[J].ComputerAided Verification,1998,1427,526-531.
[99]Heitmeyer,C. Using the SCR*toolset to specify software requirements[C].IndustrialStrength Formal Specification Techniques,IEEE,1998,12-13.
[100] Isabel Sofia Brito, Filipe Vieira, Ana Moreira, Rita A. Ribeiro. Handling conflicts inaspectural requirements compositions [J]. Trans Aspect Oriented SoftwDev (TAOSD),2007,4620(2007),144-146.
[101] Bran McBride,Jena:Implementing the RDF model and syntax specification[C],Semantic Web Workshop,2001.
[102] Bran McBride, Jena:a semantic web toolkit[C],InternetComputing,IEEE,2002,6,55-59
[103] A Sampaio, R Chitchyan, A Rashid, P Rayson.EA-Miner:a Tool for AutomatingAspect-Oriented Requirements Identification[C].International Conference on Automatedsoftware engineering(ASE05).ACM,2005:352-355.
[104] Ramzan S, Ikram N. Making Decision in Requirement Change Management[C].1stInternational Conference on ICIT. IEEE,2005:309-312.
[105]李引,李娟,李明树,动态需求跟踪方法及跟踪精度问题研究[J].软件学报,2009.20(2):177-192
[106] James Steven. Analyzing the impact of changing softwarerequirements[C]//Proceedings of IEEE International Conference on SoftwareMaintenance. Washington: IEEE,2001:190-195.