Safeware: system safety and computers
Safeware: system safety and computers
Understanding “why” in software process modelling, analysis, and design
ICSE '94 Proceedings of the 16th international conference on Software engineering
Problem frames: analyzing and structuring software development problems
Problem frames: analyzing and structuring software development problems
Business Modeling With UML: Business Patterns at Work
Business Modeling With UML: Business Patterns at Work
A Reference Model for Requirements and Specifications
IEEE Software
Representing and Using Nonfunctional Requirements: A Process-Oriented Approach
IEEE Transactions on Software Engineering - Special issue on knowledge representation and reasoning in software development
Introducing Abuse Frames for Analysing Security Requirements
RE '03 Proceedings of the 11th IEEE International Conference on Requirements Engineering
Security and Privacy Requirements Analysis within a Social Setting
RE '03 Proceedings of the 11th IEEE International Conference on Requirements Engineering
Eliciting security requirements with misuse cases
Requirements Engineering
Requirements engineering for e-business advantage
Requirements Engineering
The turnaround of the London ambulance service computer-aided despatch system (LASCAD)
European Journal of Information Systems
Requirement Progression in Problem Frames Applied to a Proton Therapy System
RE '06 Proceedings of the 14th IEEE International Requirements Engineering Conference
Structured Analysis for Requirements Definition
IEEE Transactions on Software Engineering
Your 80211 wireless network has no clothes
IEEE Wireless Communications
Goal-oriented security threat mitigation patterns: a case of credit card theft mitigation
Proceedings of the 16th Conference on Pattern Languages of Programs
Managing security and privacy in ubiquitous eHealth information interchange
Proceedings of the 5th International Conference on Ubiquitous Information Management and Communication
| Hi-index | 0.00 |
The Problem Frames approach captures problems as seen by developers, but not by stakeholders. This paper presents a framework that extends the problem diagram of the Problem Frames approach to represent stakeholder problems using "soft-problem", a notion referring to an undesirable situation that negatively affects stakeholder goals and may have less clear-cut resolution criteria. A soft-problem may be refined to more specific sub-problems and root causes, which are then traced to corresponding solutions in a diagram called Problem Interdependency Graph. The framework has been applied to the 1992 London ambulance case study, which shows that the framework helps to more precisely represent the stakeholder problems suffered by the existing system ("as-is") together with the solutions to be provided by the new system ("to-be") to such problems. The study also shows that the framework helps to determine whether the problems have been sufficiently addressed and, if not, why.