1. Gibbs W (1994) Software’s chronic crisis. Sci Am 271(3):86–95

   Article  Google Scholar 

2. Sommerville I, Sawyer P (1999) Requirements engineering: a good practice guide. Wiley, Chichester/New York

   Google Scholar 

3. Robertson S, Robertson J (1999) Mastering the requirements process. Addison-Wesley, Reading

   Google Scholar 

4. Capability Maturity Model Integration-SE/SW, Ver. 1.2, Technical Report CMU/SEI-2006-TR-008, 2006

   Google Scholar 

5. Marschall F, Schoenmakers M (2003) Towards model-based requirements engineering for web-enabled B2B applications. In: Proceedings of the 10th IEEE international conference and workshop on the engineering of computer-based systems (ECBS’03), digitally available from IEEExplore, pp 312–320

   Google Scholar 

6. OMG Model Driven Architecture.http://www.omg.org/mda/

7. Jackson MA (1994) The role of architecture in requirements engineering. In: Proceedings, 1st IEEE international conference on requirements engineering, Colorado Springs, April 1994, p 241

   Google Scholar 

8. Ramesh B (1998) Factors influencing requirements traceability practice. Commun ACM 41(2):37–44

   Article  Google Scholar 

9. Brooks F (1975–1995) The mythical man-month. Addison-Wesley, Reading

   Google Scholar 

10. Gotel O, Finkelstein A (1994) Modeling the contribution structure underlying requirements. In: Proceedings of the first international workshop on requirements engineering: foundation of software quality (REFSQ ’94), Utrecht, June 1994, p 21

    Google Scholar 

11. Ramesh B, Stubbs C, Powers T, Edwards M (1997) Requirements traceability: theory and practice. Ann Softw Eng 3:397–415

    Article  Google Scholar 

12. Kleppe A, Warmer J, Bast W (2003) MDA explained, the model driven architecture: practice and promise. Addison-Wesley, Boston

    Google Scholar 

13. Brooks F (1987) No silver bullet – essence and accident in software engineering. IEEE Comp 20(4):10–19

    Article MathSciNet  Google Scholar 

14. Harel D (1992) Biting the silver bullet: towards a brighter future for system development. IEEE Comp 25(1):8–20

    Article  Google Scholar 

15. Boehm B, Port D (1999) Escaping the software tar pit: model clashes and how to avoid them. Softw Eng Notes Assoc ComputMach 24(1):36–48

    Article  Google Scholar 

16. Rolland C, Prakash N (2000) From conceptual modeling to requirements engineering. Ann Softw Eng 10:151–176

    Article MATH  Google Scholar 

17. Nuseibeh B, Easterbrook S (2000) Requirements engineering: a roadmap. In: Proceedings, conference on the future of software engineering (ICSE), Limerick, June 2000, pp 35–46

    Google Scholar 

18. Lavazza L, Valetto G (2000) Enhancing requirements and change management through process modeling and measurement, In: ICRE2000 fourth IEEE international conference on requirements engineering, Schaumburg, 19–23 June 2000

    Google Scholar 

19. IBM, the Rational Unified Process.http://www-01.ibm.com/software/awdtools/rup/

20. Gotel O, Finkelstein A (1994) An analysis of the requirements traceability problem. In: Proceedings of the first international conference on requirements engineering, Colorado Springs, April 1994, pp 94–101

    Google Scholar 

21. Ramesh B, Jarke M (2001) Toward reference models for requirements traceability. IEEE Trans Softw Eng 27(1):58–93

    Article  Google Scholar 

22. Egyed A, GrunbacherP (2002) Automating requirements traceability: beyond the record & replay paradigm. In: Proceedings of the 17th international conference on automated software engineering, IEEE CS, Edinburgh

    Google Scholar 

23. Boehm B, Egyed A (1999) Optimizing software product integrity through life-cycle process integration. J Comp Stand Inter 21:63–75

    Article  Google Scholar 

24. The International Council on Systems Engineering (INCOSE) (1999) Tools survey: requirements management tools.http://www.incose.org/tools/tooltax.html, April 1999

25. Badar M, Zowghi D Developing a requirement toolset: lessons learned. In: Proceedings of the Australian software engineering conference (ASWEC’04), Melbourne, April 2004

    Google Scholar 

26. Dori D, Reinhartz-Berger I, Sturm A (2003)OPCAT – a bimodal case tool for object-process based system development. In: Proceedings IEEE/ACM 5th international conference on enterprise information systems (ICEIS 2003), Angers, pp 286–291

    Google Scholar 

27. Dori D (1995) Object-process analysis: maintaining the balance between structure and behavior. J Logic Comput 5(2):227–249

    Article  Google Scholar 

28. Dori D (2002) Object-process methodology – a holistic systems paradigm. Springer, Berlin/New York

    Book  Google Scholar 

29. OPM – The Official Web Site.http://www.objectprocess.org

30. Kotonya G, Sommervile I (1998) Requirements engineering: processes and techniques. Wiley, Chichester/New York

    Google Scholar 

31. DOORS – IBM Rational.http://www-01.ibm.com/software/awdtools/doors/

32. IBM Software – Rational RequisitePro.http://www-01.ibm.com/software/awdtools/reqpro/

33. Cradle: requirements management tools.http://www.threesl.com/pages/index.php

34. Dori D, Korda N, Soffer A, Cohen S (2004) SMART: system model acquisition from requirements text.In: Proceedings: international conference on business process management, Potsdam June 2004

    Google Scholar 

Download references