Abstract
PurposeSecurity is a vital requirement for software systems. Misuse case models allow system designers to inject security considerations within their designs early in the development cycle rather than patching an end system with security mechanisms after it was developed. The notation and syntactical rules of misuse case models are relatively simple. However, misuse case modeling practitioners are highly vulnerable to modeling pitfalls, creating defective models that can have catastrophic effects downstream in the development cycle. This paper seeks to present a framework that unitizes antipatterns to help remedy defective misuse case models and poor modeling practices.Design/methodology/approachA repository of antipatterns was constructed and formatted to be machine‐readable whenever possible so that it can be utilized by the proposed framework. The feasibility of the proposed approach was then demonstrated using a real‐world misuse case model of an online bookstore system.FindingsThe results indicate that the overall quality and clarity of the bookstore misuse case model is improved by applying the proposed technique and framework.Research limitations/implicationsThis research work presents a series of domain‐independent antipatterns. Users of this framework may be interested to develop domain‐dependent antipatterns to better suit their modeling and development needs.Originality/valueThe proposed approach will help misuse case modelers, especially novice ones, to improve the quality of their current models as well as future models.
Subject
Business, Management and Accounting (miscellaneous),Business and International Management
Reference52 articles.
1. Adolph, S. and Bramble, P. (2002), Patterns for Effective Use Cases, Addison‐Wesley, Reading, MA.
2. Alexander, I.F. (2002), “Initial industrial experience of misuse cases in trade‐off analysis”, Proceedings of the 10th Anniversary IEEE International Requirements Engineering Conference (RE'02), Essen, Germany.
3. Anda, B. and Sjøberg, I.K. (2002), “Towards an inspection technique for use case models”, Proceedings of the 14th International Conference on Software Engineering and Knowledge Engineering, pp. 127‐34.
4. Anderson, E., Bradley, M. and Brinko, R. (1997), “Use case and business rules: styles of documenting business rules in use cases”, Addendum to the ACM SIGPLAN Conference on Object‐oriented Programming, Systems, Languages, and Applications.
5. Armour, F. and Miller, G. (2000), Advanced Use Case Modeling, Addison‐Wesley, Reading, MA.
Cited by
9 articles.
订阅此论文施引文献
订阅此论文施引文献,注册后可以免费订阅5篇论文的施引文献,订阅后可以查看论文全部施引文献