In: Proceedings of the 5th international workshop on requirements engineering: foundations of software quality (REFSQ’99), Heidelberg, Germanyĭen Braber F et al (2002) Model-based risk management using UML and UP. In: Proceedings of the 22nd international conference on software engineering (ICSE 2000), future of software engineering track, Limerick, IrelandĬarroll JM, Swatman PA (1999) Managing the RE process: lessons from commercial practice. Sams Publishing, Indianapolisĭevanbu PT, Stubblebine S (2000) Software engineering for security: a roadmap. Addison-Wesley, BostonĪndress M (2002) Surviving security: how to integrate people, process, and technology. Viega J, McGraw G (2002) Building secure software: how to avoid security problems the right way. In: Proceedings of the 9th international workshop on requirements engineering: foundation for software quality (REFSQ’03), Klagenfurt, Austria Sindre G, Firesmith D, Opdahl AL (2003) A reuse-based approach to determining security requirements. Kruchten P (2000) The rational unified process-an introduction. In: Proceedings of the 2nd symposium on requirements engineering for information security (SREIS’02), Raleigh, North Carolina Sindre G, Opdahl AL, Breivik GF (2002) Generalization/specialization as a structuring mechanism for misuse cases. OMG (2003) Unified modeling language, version 1.5. IEEE Software 16(4):70–77įiresmith D (2003) Security use cases. IEEE Software 20(1):58–66Įllison R et al (1999) Survivable network system analysis: a case study. In: Proceedings of the 8th international workshop on requirements engineering: foundation for software quality (REFSQ’02), Essen, GermanyĪlexander IF (2003) Misuse cases, use cases with hostile intent. In: Proceedings of the 10th anniversary IEEE international requirements engineering conference (RE’02), Essen, GermanyĪlexander IF (2002) Modelling the interplay of conflicting goals with use and misuse cases. In: Proceedings of the symposium on requirements engineering for information security (SREIS’01), IndianapolisĪlexander IF (2002) Initial industrial experience of misuse cases in trade-off analysis. Potts C (2001) Scenario noir (panel statement, p 2). In: Proceedings of the 17th annual computer security applications conference (ACSAC’01), New Orleans, Los Angeles McDermott J (2001) Abuse-case-based assurance arguments. In: Proceedings of the 15th annual computer security applications conference (ACSAC’99), Phoenix, Arizona McDermott J, Fox C (1999) Using abuse case models for security requirements analysis. In: Proceedings of the 7th international workshop on requirements engineering: foundation for software quality (REFSQ’01), Interlaken, Switzerland Sindre G, Opdahl AL (2001) Templates for misuse case description. In: Proceedings of TOOLS Pacific 2000, Sydney, Australia Sindre G, Opdahl AL (2000) Eliciting security requirements by misuse cases. Mylopoulos J, Chung L, Yu E (1999) From object-oriented to goal-oriented requirements analysis. Kotonya G, Sommerville I (1997) Requirements engineering: processes and techniques. Loucopoulos P, Karakostas V (1995) Systems requirements engineering. Pohl K (1994) The three dimensions of requirements engineering: a framework and its applications. In: Proceedings of the 10th anniversary IEEE international requirements engineering conference (RE‘02), Essen, Germany Technical report, TR/78, ECMA International, Geneva, SwitzerlandĬrook R et al (2002) Security requirements engineering: when anti-requirements hit the fan. Technical report, CCIMB-99–031, Common Criteria Implementation BoardĮCMA (1999) ECMA protection profile: E-COFC public business class. Req Eng 6(1):63–73ĬCIMB (1999) Common criteria for information technology security evaluation. In: Proceedings of TOOLS USA 1999, IEEE Computer Society, Santa Barbara, CaliforniaĪnton AI et al (2001) Deriving goals from a use case based requirements specification. Lilly S (1999) Use case pitfalls: top 10 problems from real projects using use cases. IEEE Software 15(2):34–45Īrlow J (1998) Use cases, UML visual modelling and the trivialisation of business requirements. Weidenhaupt K et al (1998) Scenario usage in system development: a report on current practice. Kulak D, Guiney E (2000) Use cases: requirements in context. Rumbaugh J (1994) Getting started: using use cases to capture requirements. ACM Press, New YorkĬockburn A (2001) Writing effective use cases. Addison-Wesley, BostonĬonstantine LL, Lockwood LAD (1999) Software for use: a practical guide to the models and methods of usage-centered design. Jacobson I et al (1992) Object-oriented software engineering: a use case driven approach.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |