Requirements experience in practice: Studies of six companies

Engineering and Managing Software Requirements

Volumn , Issue , 2005, Pages 405-426

  Gorschek, Tony ^a   Svahnberg, Mikael ^a  

^a BLEKINGE INSTITUTE OF TECHNOLOGY   (Sweden)

Author keywords

Inductive assessment; Model based assessment; Process assessment; Requirements engineering; Software process improvement; State of practice

Indexed keywords

EID: 38349038062     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.1007/3-540-28244-0_18     Document Type: Chapter

References (35)

1. (2004) http://www.sei.cmu.edu/cmm/ipd-cmm.html. Last Accessed: 2004-04-11.
2. (2004) http://www.sei.cmu.edu/cmm/cmm.html. Last Accessed: 2004-04-11.
3. (2002) http://www.tickit.org/Last Accessed: 2002-10-01.
4. Basili VR (1985) Quantitative evaluation of software methodology. Technical report TR- 1519, University of Maryland, College Park, Maryland, USA.
5. Bratthall L, Joergensen M (2002) Can you trust a single data source exploratory software engineering case study? Empirical Software Engineering 7 (1): 9-26.
6. Briand L, El Emam K, Melo WL (1995) An inductive method for software process improvement: concrete steps and guidelines. In: Proceedings of ESI-ISCN'95: Measurement and training based process improvement, ISCN. Vienna, pp.34-49.
7. CMMI-PDT (2002) Capability maturity model integration (CMMI), Version 1.1. CMMI for systems engineering, software engineering, integrated product and process development, and supplier sourcing version 1.1 (CMMI-SE/SW/IPPD/SS, V1.1), Pittsburgh.
8. Curtis B, Krasner H, Iscoe N (1998) A field study of the software design process for large systems. Communications of the ACM 31 (11): 1268-1287.
9. El Emam K. Madhavji NH (1995) A field study of requirements engineering practices in information systems development. In: Proceedings of the 2nd IEEE international symposium on requirements engineering, IEEE Computer Society. Los Alamitos CA, pp.68-80.
10. El Emam KE, Madhavji NHE (1999) Elements of software process assessment & improvement. Wiley-IEEE, Los Alamitos CA.
11. Gorschek T (2004) Software process assessment & improvement in industrial requirements engineering. Licentiate thesis No. 2004:07, ISBN 91-7295-041-2. Blekinge Institute of Technology, Ronneby, Sweden.
12. Gorschek T, Svahnberg M, Tejle K (2003) Introduction and application of a lightweight requirements engineering process evaluation method. In: Proceedings of the 9th international workshop on requirements engineering: foundation for software quality (REFSQ'03), Universität Duisburg-Essen. Essen, Germany, pp.101-112.
13. Gorschek T, Tejle K (2002) A method for assessing requirements engineering process maturity in software projects. Master thesis in computer science. Thesis No: MCS- 2002:2. Blekinge Institute of Technology, Ronneby, Download at http://www.bth.se/fou/cuppsats.nsf/.
14. Gorschek T, Wohlin C (2003) Identification of improvement issues using a lightweight triangulation approach (Eurospi'03). In: Proceedings of European software process improvement conference (EuroSPI'2003), Verlag der Technischen Universität. Graz, Austria. Download at: http://www.bth.se/fou/Forskinfo. nsf/, pp.VI.1-VI.14.
15. Gorschek T, Wohlin C (2004) Packaging software process improvement issues: A method and a case study. Software: practice & experience 34 (14): 1311-1344.
16. Hass AMJ (2003) Configuration management principles and practice. Addison-Wesley, Reading MA.
17. Hofmann HF, Lehner F (2001) Requirements engineering as a success factor in software projects, IEEE Software 18(4): 58-66.
18. (1998) http://www.sei.cmu.edu/iso-15504/. Last Accessed: 2004-01-07.
19. Jirotka M, Goguen JA (1994) Requirements engineering social and technical issues. Academic press, London.
20. Juristo N, Moreno AM, Silva A (2002) Is the European industry moving toward solving requirements engineering problems? IEEE Software 19(6): 70-78.
21. Kotonya G, Sommerville I (1998) Requirements engineering: processes and techniques. John Wiley, New York.
22. Laitenberger O, Beil T, Schwinn T (2002) An industrial case study to examine a nontraditional inspection implementation for requirements specifications. In: Proceedings of the 8th IEEE symposium on software Metrics, IEEE Computer Society. Los Alamitos CA, pp.97-106.
23. Leffingwell D, Widrig D (2000) Managing software requirements: A unified approach. Addison-Wesley, Reading MA.
24. Lubars M, Potts C, Richter C (1992) A review of the state of the practice in requirements modeling. In: Proceedings of IEEE international symposium on requirements Engineering, IEEE. Los Alamitos CA, pp.2-14.
25. Nikula U, Sajaniemi J, Kälviäinen H (2000) A state-of-the-practice survey on requirements engineering in small-and-medium- sized enterprises, Technical report (Http://www.Cs.Ucl.Ac.Uk/Research/Renoir/ Tbrc-Rr01.Pdf). Lappeenranta University of Technology, Lappeenranta, Finland.
26. Paulk MC (1995) The capability maturity model: guidelines for improving the software process. Addison-Wesley, Reading MA.
27. Rakitin SR (2001) Software verification and validation for practitioners and managers. Artech House, Boston MA.
28. (2003) http://www.comp.lancs.ac.uk/computing/research/cseg/projects/ reaims/index.html. Last accessed: 2003-05-01.
29. Reifer DJ (2000) The CMMI: It's formidable. Journal of Systems and Software 50(2): 97-98.
30. Saaty TL, Vargas LG (2001) Models, methods, concepts & applications of the analytic hierarchy process. Kluwer Academic Publishers, Boston MA.
31. Sawyer P, Sommerville I and Viller S (1999) Capturing the benefits of requirements engineering, IEEE Software 16 (2): 78-85.
32. Shull F, Rus I, Basili V (2000) How perspective-based reading can improve requirements inspections. Computer 33 (7): 73-79.
33. Sommerville I, Sawyer P (1999) Requirements engineering: A good practice guide. John Wiley & Sons, Chichester UK.
34. (2003) http://www.sqi.gu.edu.au/spice/. Last accessed: 2003-09-11.
35. Zahran S (1998) Software process improvement: practical guidelines for business success. Addison-Wesley, Reading MA.