Abstract
The goal of this paper is to propose the of the Misuse Case and Obligation concepts in the Software Development Life Cycle (SDLC) in order to position security concerns at the very beginning of this process and to get secure applications. These concepts are built upon the use case concept which is well known by the community of application developers in companies and by the application sponsors. The application sponsors are the key business stakeholders that fund and/or rely on the application for their business benefits. As stated in [1] and [3], the concept has proven helpful for the elicitation of, communication about and documentation of requirements [4]. So, we think it is easier to introduce security requirements in the development lifecycle by reusing and/or constructing security requirement artifacts around the and UML approach.
Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
