Domain analysis is essential to core assets development in software product line engineering. Most existing approaches, however, depend on domain experts’ experience to analyze the commonality and variability of syst...Domain analysis is essential to core assets development in software product line engineering. Most existing approaches, however, depend on domain experts’ experience to analyze the commonality and variability of systems in a domain, which remains a manual and intensive process. This paper addresses the issue by proposing a model-driven approach to automating the domain requirements derivation process. The paper focuses on the match between the use cases of existing individual products and the domain functional requirements of a product line. By introducing a set of linguistic description dimensions to differentiate the sub-variations in a use case, the use case template is extended to model variability. To this end, a transformation process is formulated to sustain and deduce the information in use cases, and to match it to domain functional requirements. This paper also presents a prototype which implements the derivation as a model transformation described in a graphical model transformation language MOLA. This approach complements existing domain analysis techniques with less manual operation cost and more efficiency by automating the domain functional requirements development.展开更多
A software security testing behavior model,SETAM,was proposed in our previous work as the integrated model for describing software security testing requirements behavior,which is not only compatible with security func...A software security testing behavior model,SETAM,was proposed in our previous work as the integrated model for describing software security testing requirements behavior,which is not only compatible with security functions and latent typical misuse behaviors,but also with the interaction of them.In this paper,we analyze the differences between SETAM with security use case and security misuse case in different types of security test requirements.To illustrate the effectiveness of SETAM,we compare them in a practical case study by the number of test cases and the number of faults detected by them.The results show that SETAM could decrease about 34.87% use cases on average,and the number of faults detected by SETAM increased by 71.67% in average,which means that our model can detect more faults with fewer test cases for software security testing.展开更多
UML is widely accepted and applied by the international software industry. UML is a powerful language for Object oriented modeling, designing, and implementing software systems, but its Use Case method for requirem...UML is widely accepted and applied by the international software industry. UML is a powerful language for Object oriented modeling, designing, and implementing software systems, but its Use Case method for requirement analysis and modeling software patterns has some explicit drawbacks. For more complete UML, this paper proposes the Role Use Case modeling and its glyphs, and provides an instance of requirement analysis using Role Use Case method. Uses the Role Model to modeling software pattern at knowledge level. This paper also extends the UML Meta Model and accentuates “RM before UML's class Modeling”.展开更多
文摘Domain analysis is essential to core assets development in software product line engineering. Most existing approaches, however, depend on domain experts’ experience to analyze the commonality and variability of systems in a domain, which remains a manual and intensive process. This paper addresses the issue by proposing a model-driven approach to automating the domain requirements derivation process. The paper focuses on the match between the use cases of existing individual products and the domain functional requirements of a product line. By introducing a set of linguistic description dimensions to differentiate the sub-variations in a use case, the use case template is extended to model variability. To this end, a transformation process is formulated to sustain and deduce the information in use cases, and to match it to domain functional requirements. This paper also presents a prototype which implements the derivation as a model transformation described in a graphical model transformation language MOLA. This approach complements existing domain analysis techniques with less manual operation cost and more efficiency by automating the domain functional requirements development.
基金Supported by the National High Technology Research and Development Program of China (863 Program) (2009AA01Z402)the PLA University of Science and Technology Pre-research Project (20110202, 20110210)+1 种基金the Natural Science Foundation of Jiangsu Province of China (BK2012059,BK2012060)the PLAUST Outstanding Graduate Student Thesis Fund (2012)
文摘A software security testing behavior model,SETAM,was proposed in our previous work as the integrated model for describing software security testing requirements behavior,which is not only compatible with security functions and latent typical misuse behaviors,but also with the interaction of them.In this paper,we analyze the differences between SETAM with security use case and security misuse case in different types of security test requirements.To illustrate the effectiveness of SETAM,we compare them in a practical case study by the number of test cases and the number of faults detected by them.The results show that SETAM could decrease about 34.87% use cases on average,and the number of faults detected by SETAM increased by 71.67% in average,which means that our model can detect more faults with fewer test cases for software security testing.
基金Supported the Middleware Software Division of Software Group of F ujitsu L imited in Japanthe National Depart-ment of Educat
文摘UML is widely accepted and applied by the international software industry. UML is a powerful language for Object oriented modeling, designing, and implementing software systems, but its Use Case method for requirement analysis and modeling software patterns has some explicit drawbacks. For more complete UML, this paper proposes the Role Use Case modeling and its glyphs, and provides an instance of requirement analysis using Role Use Case method. Uses the Role Model to modeling software pattern at knowledge level. This paper also extends the UML Meta Model and accentuates “RM before UML's class Modeling”.
