Applying a goal-oriented method for hazard analysis: A case study

Proceedings - Fourth International Conference on Software Engineering Research, Management and Applications, SERA 2006

Volumn , Issue , 2006, Pages 22-29

  Supakkul, Sam ^a   Chung, Lawrence ^a  

^a UNIVERSITY OF TEXAS AT DALLAS   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

HAZARDS; RISK ANALYSIS; SECURITY SYSTEMS;

GOAL-ORIENTED METHODS; NON-FUNCTIONAL REQUIREMENTS; OPERATIONALIZATIONS;

COMPUTATIONAL METHODS;

EID: 34547306036     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/SERA.2006.16     Document Type: Conference Paper

References (22)

1. I. Alexander. Misuse cases: Use cases with hostile intent. IEEE Software, pages 58-66, Jan.Feb. 2003.
2. B. Boehm. Software Risk Management. IEEE Computer Society Press, 1989.
3. B. Cheng, L. Campbell, and R. Wassermann. Using security patterns to model and analyze security requirements. In Proc. Requirements for High Assurance Systems Workshop (RHAS 03), 2003.
4. L. Chung, B. A. Nixon, E. Yu, and J. Mylopoulos. Non-Functional Requirements in Software Engineering. Kluwer Academic Publishers, 2000.
5. L. Chung and S. Supakkul. Representing NFRs and FRs: A goal-oriented and use case driven approach. Software Engineering Research and Applications (SERA2004)- LNCS, 3647(29-41), 2005.
6. R. Crook, D. Ince, L. Lin, and B. Nuseibeh. Security requirements engineering: When anti-requirements hit the fan. In Proc. Intl. Conf. Requirements Engineering (RE'02), 2002.
7. J. Doyle and R. Thomason. Background to qualitative decision theory. AI Magazine, 20(1), January 1999.
8. G. Helmer, J. Wong, M. Slagell, V. Honavar, L. Miller, and R. Lutz. A software fault tree approach to requirements analysis. Requirements Engineering, 7:207-220, 2002.
9. I. Jacobson, G. Booch, and J. Rumbaugh. The Unified Software Development Process. Addison-Wesley, 1999.
10. N. Leveson. Software safety: Why, what, and how. ACM Computing Surveys, 18(2), June 1986.
11. L. Lin, B. Nuseibeh, D. Ince, M. Jackson, and J. Moffett. Introducing abuse frames for analysing security requirements. In Proc. Intl. Requirements Engineering Conference, 2003.
12. L. Liu, E. Yu, and J. Mylopoulos. Security and privacy requirements analysis within a social setting. In Proc. 11th IEEE Intl. Requirements Engineering Conference (RE'03), 2003.
13. J. McDermott and C. Fox. Using abuse case models for security requirements analysis. In Proc. Annual Computer Security Applications Conference, 1999.
14. J. Mylopoulos, L. Chung, and B. A. Nixon. Representing and using nonfunctional requirements: A process-oriented approach. IEEE Transactions on Software Engineering, 18(6):483-497, 1992.
15. J. Mylopoulos, L. Chung, and E. Yu. From object-oriented to goal-oriented requirements analysis. Communications of the ACM, 42(1):31-37, 1999.
16. A. Neal, M. Humphreys, D. Leadbetter, and P. Lindsay. Development of hazard analysis techniques for human-computer systems. Innovation Consolidation in Aviation, 2003.
17. B. Schneier. Secrets & Lies: Digital Security in a Networked World. Wiley, 2000.
18. G. Sindre and A. L. Opdahl. Eliciting secutiry requirements with misuse cases. Requirements Engineering, 10:34-44, 2005.
19. S. Supakkul and L. Chung. A UML profile for goal-oriented and use case-driven representation of NFRs and FRs. In Proc. 3rd Intl. Conf. on Software Engineering Research, Management & Applications (SERA05), August 11-13, 2005.
20. A. van Lamsweerde. Requirements engineering in the year 00: A research perspective. In Proc. 22nd Intl. Conf. on Software Engineering (ICSE2000). ACM Press, June 2000.
21. A. van Lamsweerde. Elaborating security requirements by constructing of intentional anti-models. In Proc. Intl. Conf. Software Engineering (ICSE'04), 2004.
22. A. van Lamsweerde and L. Emmanuel. Handling obstacles in goal-oriented requirements engineering. IEEE. Transactions on Software Engineering, 26(10):978-1005, 2000.