separating application and security concerns in use case models
This paper describes an approach to model complex applications by modeling application requirements separately from security requirements in use case models. By careful separation of concerns, the security requirements are captured in security use cases separately from the application requirements, which are captured in application use cases. The approach reduces system complexity caused by mixing security requirements with business application requirements with the goal of making complex systems more maintainable. Furthermore, the security use cases can be reused by other software applications. This paper describes how the application and security concerns are modeled separately, and how they can be woven together into an application.
security use case models separation of concerns weaving