|
||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
ABSTRACT
Non-functional requirements for software systems are typically specified using informal notations such as quality attribute scenarios. Further, implementation strategies for such non-functional attributes are frequently common across systems with quite different functional requirements. In such cases, the time invested in implementing these quality attributes could be salvaged, thereby reducing the project lifetime and increasing software quality. In this paper, we present the design and prototype implementation of a tool and associated framework that enables software engineers to effectively capture non-functional requirements, and then automatically generate implementations of these requirements to be added to the application being built. The quality attribute implementations are generated as aspects (AspectJ in the prototype) that can be weaved in with the application code (Java) with minimal development effort. REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
INDEX TERMS
Primary Classification:
Additional Classification:
Keywords:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||