Requirement progression in problem frames applied to a proton therapy system

Proceedings of the IEEE International Conference on Requirements Engineering

Volumn , Issue , 2006, Pages 169-178

  Seater, Robert ^a   Jackson, Daniel ^a  

^a MASSACHUSETTS INSTITUTE OF TECHNOLOGY   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

DOMAIN DECOMPOSITION METHODS; PROBLEM SOLVING; RADIOTHERAPY; SPECIFICATION LANGUAGES;

PROTON THERAPY SYSTEM; RADIOTHERAPY SYSTEM; REQUIREMENT PROGRESSION; REQUIREMENT REFERENCES;

REQUIREMENTS ENGINEERING;

EID: 41149133022     PISSN: 1090705X     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/RE.2006.53     Document Type: Conference Paper

References (30)

1. Space Division Air Force. System safety handbook for the acquisition manager, January 1987.
2. T. E. Bell and T. A. Thayer. Software requirements: are they really a problem? In Proceedings of the 2nd International Conference on Software Engineering, pages 61-68. IEEE Society Press, 1967.
3. Anne Dardenne, Axel van Lamsweerde, and Stephen Fickas. Goal-directed requirements acquisition. Science of Computer Programming, 20(1-2):3-50, 1993.
4. Robert Darimont and Axel van Lamsweerde. Formal refinement patterns for goal-driven requirements elaboration. In Proceedings of the 4th ACM Symp. on the Foundations of Software Engineering (FSE-4), pages 179-190, San Francisco, Oct 1996.
5. Food and Drug Administration. FDA Statement on Radiation Overexposures in Panama. http://www.fda.gov/cdrh/ocd/panamaradexp.html.
6. Sol Greenspan, John Mylopoulos, and Alex Borgida. On formal requirements modeling languages: RML revisited. In Proceedings of the 16th International Conference on Software Engineering (ICSE'94), pages 135-147. IEEE Computer Society Press, 1994.
7. MIT Software Design Group. The Alloy Analyzer. http://alloy.lcs.mit.edu.
8. C. B. Haley, R. Laney, and B. Nuseibeh. Using Problem Frames and projections to analyze requirements for distributed systems. In Proceedings of the 10th International Workshop on Requirements Engineering: Foundation for Software Quality (REFSQ '04), pages 203-217. Essener Informatik Beitrage, 2004. Editors: B. Regneil, E. Kamsties, and V. Gervasi.
9. John G. Hall and Lucia Rapanotti. A framework for software problem analysis, 2005. Tecnical Report.
10. Daniel Jackson. Software Abstractions: Logic, Language, and Analysis. MIT Press, Cambridge, MA, April 2006.
11. Daniel Jackson and Michael Jackson. Rigorous Development of Complex Fault Tolerant Systems, chapter Separating Concerns Requirements Analysis: An Example. Springer-Verlag. To appear.
12. Daniel Jackson, Ilya Shlyakhter, and Manu Sridharan. A micromodularity mechanism. In ACM SIGSOFT Conference on Foundations of Software Engineering / European Software Engineering Conference, Vienna, September 2001.
13. M. A. Jackson. Problem analysis using small Problem Frames. South African Computer Journal, 22:47-60, March 1999.
14. Michael Jackson. Software Requirements and Specifications: a lexicon of practice, principles and prejudice. Addison-Wesley, 1995.
15. Michael Jackson. Problem Frames: analyzing and structuring software development problems. AddisonWesley Longman Publishing Co., Inc., Boston, MA, USA, 2001.
16. Michael Jackson and Pamela Zave. Deriving specifications from requirements: an example. In ICSE'95: Proceedings of the 17th international conference on Software engineering, pages 15-24, New York, NY, USA, 1995. ACM Press.
17. W. Lewis Johnson. Deriving specifications from requirements. In Proceedings of the Tenth International Conference on Software Engineering, pages 428-438. IEEE Computer Society, 1988.
18. Robin Laney, Leonor Barroca, Michael Jackson, and Bashar Nuseibeh. Composing requirements using Problem Frames. In Proceedings of the 2004 International Conference on Requirements Engineering (RE04). IEEE Computer Science Press.
19. E. Letier and A. van Lamsweerde. Deriving operational software specifications from system goals. In ACM SIGSOFT Software Engineering Notes, 27(6), 2002.
20. Nancy G. Leveson. Safeware: system safety and computers. Addison-Wesley Longman Publishing Co., Inc., Boston, MA, USA, 1995.
21. Nancy G. Leveson and C. Turner. An investigation of the Therac-25 accidents. IEEE Computer, 7(26): 18-41, 1993.
22. Zhi Li, Jon G. Hall, and Lucia Rapanotti. A constructive approach to Problem Frame semantics. Technical Report 2004/26, compdep, 2005.
23. Zhi Li, Jon G. Hall, and Lucia Rapanotti. From requirements to specifications: a formal approach. In Proceedings of the Second International Workshop on Applications and Advances in Problem Frames (IWAAPF'06), page 65, Shanghai, May 2006.
24. Zhi Li Lucia Rapanotti, Jon G. Hall. Problem reduction: a systematic technique for deriving specifications from requirements, Feb 2006. Technical Report, ISSN 1744-1986.
25. Henry Ozog. Hazard identification, analysis, and control. Hazard Prevention, pages 11-17, May-June 1985.
26. D. L. Parnas and J. Madey. Functional documentation for computer systems engineering, vol. 2. Technical Report Technical Report CRL 237, McMaster University, Hamilton, Ontario, Sept 1991.
27. Robert C. Ricks, Mary Ellen Berger, Elizabeth C. Holloway, and Ronald E. Goans. REACTS Radiation Accident Registry: Update of Accidents in the United States. International Radiation Protection Association, 2000.
28. Robert Seater and Daniel Jackson. Problem Frame transformations: Deriving specifications from requirements. In Proceedings of the Second International Workshop on Applications and Advances in Problem Frames (IWAAPF'06), page 71, Shanghai, May 2006.
29. Jeffrey M. Thompson, Mats P.E. Heimdahl, and Steven P. Miller. Specification based prototyping for embedded systems. In Seventh ACM SIGSOFT Symposium on the Foundations on Software Engineering, number 1687 in LNCS, pages 163-179, September 1999.
30. Eric S. K. Yu. Towards modelling and reasoning support for early-phase requirements engineering. In Proceedings of the 3rd IEEE Int. Symp. on Requirements Engineering (RE'97), pages 226-235, Washington D.C., USA, Jan 1997.