Deriving tabular event-based specifications from goal-oriented requirements models

Proceedings of the IEEE International Conference on Requirements Engineering

Volumn 2003-January, Issue , 2003, Pages 200-210

  De Landtsheer, R ^a   Letier, E ^a   Van Lamsweerde, A ^a  

^a UNIVERSITÉ CATHOLIQUE DE LOUVAIN   (Belgium)

Author keywords

Analytical models; Buildings; Coolants; Documentation; Embedded software; Environmental management; Humans; Software tools; Switches; Thyristors

Indexed keywords

ANALYTICAL MODELS; BUILDINGS; COMPUTATIONAL LINGUISTICS; COMPUTER AIDED SOFTWARE ENGINEERING; COMPUTER SOFTWARE; COOLANTS; EMBEDDED SOFTWARE; ENVIRONMENTAL MANAGEMENT; REQUIREMENTS ENGINEERING; SEMANTICS; SPECIFICATIONS; SWITCHES; SYSTEM PROGRAM DOCUMENTATION; THYRISTORS;

EVENT-BASED METHOD; GOAL SPECIFICATIONS; HUMANS; OPERATIONAL REQUIREMENTS; OPERATIONAL SPECIFICATIONS; REQUIREMENTS MODELS; SOFTWARE REQUIREMENTS; TECHNIQUES AND TOOLS;

MODEL CHECKING;

EID: 34548713139     PISSN: 1090705X     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/ICRE.2003.1232751     Document Type: Conference Paper

References (35)

1. A.I. Anton and C. Potts, "The Use of Goals to Surface Requirements for Evolving Systems", Proc. ICSE-98: 20th Int.l Conference on Software Enginering, Kyoto, April 1998.
2. Archer, Myla M., Heitmeyer, Constance L., and Sims, Steve, "TAME: A PVS Interface to Simplify Proofs for Automata Models,"Proc. UITP '98, July 1998.
3. J.M. Atlee, State-Based Model Checking of Event-Driven System Requirements, IEEE Transactions on Software Engineering Vol. 19 No. 1, January 1993, 24-40.
4. G.Berry, G.Gonthier, "The Esterel synchronous programming language: Design, semantics, implementation", Science of Computer Programming. 19, 2, 89.
5. L. Chung, B. Nixon, E. Yu and J. Mylopoulos, Non-functional requirements in software engineering. Kluwer Academic,, 2000.
6. th Intl. Conf. on Software Engineering, 1993, pp. 315-323.
7. A. Dardenne, A. van Lamsweerde and S. Fickas, "Goal-Directed Requirements Acquisition", Science of Computer Programming, Vol. 20, 1993, 3-50.
8. R. Darimont and A. van Lamsweerde, "Formal Refinement Patterns for Goal-Driven Requirements Elaboration", Proc. FSE'4 - 4th ACM Symp. on Foundations of Software Engineering, Oct. 1996, 179-190.
9. R. De Landtsheer, Deriving Tabular Event-Based Specifications from Goal-Oriented Requirements Models. Ms. Thesis, University of Louvain, June 2002.
10. A. Gargantini and C. Heitmeyer, "Using Model Chcking to Generate Tests from Requirements Specifications", Proc. ESEC/FSE'99, Springer-Verlag LNCS Nr. 1687, 1999, 146-162.
11. M.P. Heimdahl and N.G. Leveson, "Completeness and Consistency in Hierarchical State-Based Requirements", IEEE Transactions on Software Engineering Vol. 22 No. 6, June 1996, 363-377.
12. C. Heitmeyer, R.D. Jeffords and B. G. Labaw, "Automated Consistency Checking of Requirements Specifications", ACM Trans. on Software Eng. and Methodology 5, 3, July 1996, 231-261.
13. C. Heitmeyer, J. Kirby, and B. Labaw. "Tools for Formal Specification, Verification, and Validation of Requirements," Proc. COMPASS '97, June 1997, Gaithersburg, MD.
14. C. Heitmeyer, J. Kirkby, B. Labaw, M. Archer and R. Bharadwaj, "Using Abstraction and Model Checking to Detect Safety Violations in Requirements Specifications", IEEE Transactions on Software Engineering Vol. 24 No. 11, November 1998, 927-948
15. K.L. Heninger, "Specifying Software Requirements for Complex Systems: New Techniques and their Application", IEEE Transactions on Software Engineering Vol. 6 No. 1, January 1980, 2-13.
16. M. Jackson, Principles of Program Design. Academic Press, 1975.
17. R. Jeffords and C. Heitmeyer, "Automatic Generation of State Invariants from Requirements Specifications", Proc. FSE-6: 6th ACM Symp. Foundations of Software Engineering, 1998, 56-69.
18. A. van Lamsweerde, R. Darimont, E. Letier, "Managing Conflicts in Goal-Driven Requirements Engineering", IEEE Transactions on Software Engineering, Special Issue on Managing Inconsistency in Software Development, November 1998.
19. nd Intl. Conference on Software Engineering, ACM Press, May 2000.
20. A. van Lamsweerde and E. Letier, "Handling Obstacles in Goal-Oriented Requirements Engineering", IEEE Transactions on Software Engineering, Special Issue on Exception Handling, October 2000.
21. th Intl. Symp. Requirements Engineering, Toronto, August 2001, pp. 249-263.
22. E.Letier, "Goal-Oriented Elaboration of Requirements for a Safety Injection Control System", http://www.info.ucl.ac.be/people/eletier/safety-injection.pdf
23. th Intl. Conf. on Software Engineering, Orlando, IEEE Press, May 2002.
24. th ACM Symp. Foundations of Software Engineering, Charleston, November 2002.
25. K.L.Mc Millan, "The SMV∗ system for SMV version 2.5.4", November 2000, http://www2.cs.cmu.edu/~modelcheck/smv/smvmanual.ps
26. J. Mylopoulos, L. Chung and B. Nixon, "Representing and Using Nonfunctional Requirements: A Process-Oriented Approach", IEEE Trans. on Software. Engineering, Vol. 18 No. 6, June 1992, 483-497.
27. D.L. Parnas and J. Madey, "Functional Documents for Computer Systems", Science of Computer Programming, Vol. 25, 1995, pp. 41-61.
28. S. Pollack and H. Hicks, Decision Tables - Theory and Practice. Wiley, 1971.
29. C. Potts, "Using Schematic Scenarios to Understand User Needs", Proc. DIS'95 - ACM Symposium on Designing interactive Systems: Processes, Practices and Techniques, Univ. Michigan, August 1995.
30. K.Taeho, D. Stringer-Calvert and S. Cha ,"Formal Verification of Functional Properties of an SCR-Style Software Requirements Specification Using PVS", Proc. TACAS'2002, Springer-Verlag, April 2002.
31. O. Vandenbroucke, Derivation of Tabular Specification from Goal-Oriented Specifications for a Simple Autopilot System, M.S. Thesis, University of Louvain, June 2000.
32. st Int. Symp. on Requirements Engineering, San Diego, IEEE, 1993, 198-207.
33. th Intl Symp. Requirements Engineering, Limerick, IEEE, June 1999.
34. E.S.K. Yu, "Modelling Organizations for Information Systems Requirements Engineering", Proc. RE'93 - 1st Intl Symp. on Requirements Engineering, IEEE, 1993, 34-41.
35. K. Yue, "What Does It Mean to Say that a Specification is Complete?", Proc. IWSSD-4, Fourth International Workshop on Software Specification and Design, Monterey, 1987.