Subject-oriented programming: a critique of pure objects
OOPSLA '93 Proceedings of the eighth annual conference on Object-oriented programming systems, languages, and applications
Structuring Z specifications with views
ACM Transactions on Software Engineering and Methodology (TOSEM)
Extreme programming explained: embrace change
Extreme programming explained: embrace change
Problem frames: analyzing and structuring software development problems
Problem frames: analyzing and structuring software development problems
Selected writings on computing: a personal perspective
Selected writings on computing: a personal perspective
Software Abstractions: Logic, Language, and Analysis
Software Abstractions: Logic, Language, and Analysis
Verification of multi-agent negotiations using the alloy analyzer
IFM'07 Proceedings of the 6th international conference on Integrated formal methods
| Hi-index | 0.00 |
Often, a requirements document is structured as a long list of individual ”requirements”, each describing an anticipated function or user interaction. An alternative approach is to identify a collection of subproblems, each representing an aspect of the larger problem, and to describe each subproblem in isolation, deferring their composition to a later stage. This paper illustrates the approach by applying it to the requirements of the positioning functions of a proton therapy installation. It explains how a flaw in the design of the system can be isolated to a single subproblem, which can be formalized and subjected to automatic analysis.