Use Case and Non-functional Scenario Template-Based Approach to Identify Aspects

Use cases are widely used to describe requirements to be validated by users and used by builders to drive the software development process. However, use cases are only used to define functional requirements, leaving out global properties that affect the whole or part of the system. Furthermore, the crosscutting nature of some requirements is not handled. This approach is based on use cases and we describe and map non-functional requirements into function and architectures through non-functional scenario template. It not only improves modularity in the requirements which make it possible to begin tackling the problem of tangling, scattering of the requirement as early as in requirement analysis phrase, but also improves traceability from requirement analysis level to implement level, so it achieves a smooth transition between the system analysis and the design.