Eliciting security requirements with misuse cases
Requirements Engineering
Security Requirement with a UML 2.0 Profile
ARES '06 Proceedings of the First International Conference on Availability, Reliability and Security
Considering Operational Security Risk during System Development
IEEE Security and Privacy
Executable misuse cases for modeling security concerns
Proceedings of the 30th international conference on Software engineering
A UML-Based Framework for Design and Analysis of Dependable Software
COMPSAC '08 Proceedings of the 2008 32nd Annual IEEE International Computer Software and Applications Conference
Designing System Security with UML Misuse Deployment Diagrams
SERE-C '12 Proceedings of the 2012 IEEE Sixth International Conference on Software Security and Reliability Companion
| Hi-index | 0.00 |
Security is becoming required knowledge for software engineers. Building security into the product means that security must be considered during the requirements and throughout the software development process. This workshop considers how UML can be enhanced for security, including through misuse cases, business process diagrams, class diagrams, mis-sequence diagrams, and misuse deployment diagrams. The OCTAVE process to analyze risk is also introduced.