260 likes | 409 Views
This presentation will probably involve audience discussion, which will create action items. Use PowerPoint to keep track of these action items during your presentation In Slide Show, click on the right mouse button Select “Meeting Minder” Select the “Action Items” tab
E N D
This presentation will probably involve audience discussion, which will create action items. Use PowerPoint to keep track of these action items during your presentation • In Slide Show, click on the right mouse button • Select “Meeting Minder” • Select the “Action Items” tab • Type in action items as they come up • Click OK to dismiss this box • This will automatically create an Action Item slide at the end of your presentation with your points entered. Requirement-Based Automated Aspect Verification Boris Vaysburg
Outline • Problem Statement • Proposed Approach • Aspectual Requirements • Automated Model and Test Generation • Aspect-oriented Regression Testing • Conclusion Illinois Institute of Technology
Aspect Testing • Testing of aspects is challenging • A single aspect affects multiple areas of the system • Affects of an aspect are not localized with respect to system functionality • Increasingly difficult to track aspect influence as system goes through revisions Illinois Institute of Technology
Aspect Testing Illinois Institute of Technology
Aspect Testing Illinois Institute of Technology
Aspect Testing Illinois Institute of Technology
Limitation of Existing Methods • Limited support of aspect verification on requirement level • Support for generation of tests against the entire system only • No selective aspect testing • No regression testing with respect to system aspects Illinois Institute of Technology
Proposed Approach • Approach to automatically track affect of aspectual requirements on the system • Provide support for automated aspect testing: • Selectively verify aspect functionality • Regression test affect of aspects on new system functionality • Automated model-based test generation directly from specification • Based on UML for formal description • Individual aspect requirements mapped into system model Illinois Institute of Technology
Automated Aspect Testing • Automatically create UML system model from individual requirements • Generate system-level test suite from the system model • Generate aspect test suites from the system test suite. Illinois Institute of Technology
Automated Aspect Testing Illinois Institute of Technology
System Specifications • Comprised of individual requirements • Functional requirements • Aspectual Requirements • Performance • Security • Textual requirements maybe ambiguous • Each requirement has: • Requirements ID • Textual description • Formal UML specification Illinois Institute of Technology
Example of Requirement R1 The system shall accept PIN Illinois Institute of Technology
Example of Requirement R2 If entered amount exceeds account balance, produce error, disregard action Illinois Institute of Technology
Automated Model Generation • Individual requirements (functional and aspectual) collected from system engineers • System model generated from individual requirements • Requirement marking preserved Illinois Institute of Technology
AutomatedTest Case Generation • Tests generated from UML system model • Support for various testing strategies • State coverage • Transition coverage • Path coverage • Tests mapped to individual requirements Illinois Institute of Technology
Test Generation Illinois Institute of Technology
Test Generation Illinois Institute of Technology
Test Generation Pointcut Illinois Institute of Technology
Test Generation Pointcut Illinois Institute of Technology
Test Generation Pointcut Illinois Institute of Technology
Aspect-basedRegression Testing • Automatically detect model changes • Automatically detect affect of an aspect on the system changes Pointcut Illinois Institute of Technology
Aspect-basedRegression Testing • Automatically detect model changes • Automatically detect affect of an aspect on the system changes Pointcuts Illinois Institute of Technology
Conclusions • New approach to requirement-based aspect test generation • System-level test suites • Aspect-based selective testing • Aspect-based regression testing • May provide significant benefits: • Reduce number of test cases • Maintain test suite quality Illinois Institute of Technology
Proposed PhD Research • Continue review of existing methods/literature • Formalize the approach • Formalize model merging algorithm • Formalize test selection algorithm • Further study and formalize automated aspect-based regression testing • Design and develop tool to support approach • Conduct experimental study Illinois Institute of Technology
References • Aldawud, M.O., “Aspect-Oriented Modeling With UML,” PhD Dissertation • Clarke S., “Towards a Standard Design Language for AOSD,” Proceedings AOSD 2002 • Grundy, J., “Aspect-orinted Requirements Engineergin for Component-base Software Systems,” Proceedings IEEE Symposium on Requirements Engineering, 1999 • Rashid, A., et.al., “Modularisation and Composition of Aspectual Requirements,” Proceedings, AOSD 2003 Illinois Institute of Technology