Requirements engineering in the development of large-scale systems

Proceedings of the 16th IEEE International Requirements Engineering Conference, RE'08

Volumn , Issue , 2008, Pages 217-222

  Konrad, Sascha ^a   Gall, Michael ^a  

^a SIEMENS CORPORATE RESEARCH   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

ENGINEERING;

APPLICATIONS.; INDUSTRIAL PROJECTS; LARGE-SCALE SYSTEMS; LESSONS LEARNED; PRACTICAL GUIDELINES;

REQUIREMENTS ENGINEERING;

EID: 58049138657     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/RE.2008.31     Document Type: Conference Paper

References (20)

1. I. Alexander and T. Zink. Introduction to systems engineering with use cases. Computing & Control Engineering Journal, 13(6):289-297, Dec 2002.
2. B. W. Boehm. Software Engineering Economics. Prentice Hall, Englewood Cliffs, NJ, 1981.
3. B. W. Boehm and P. N. Papaccio. Understanding and controlling software costs. IEEE Trans. Softw. Eng., 14(10):1462-1477, 1988.
4. N. Cassaigne. The dashboard: a knowledge conversion tool. Engineering Management Conference, 2002. IEMC '02. 2002 IEEE International, 1:292-297, 2002.
5. B. H. C. Cheng and J. M. Atlee. Research directions in requirements engineering. In FOSE '07: 2007 Future of Software Engineering, pages 285-303, Washington, DC, USA, 2007. IEEE Computer Society.
6. M. B. Chrissis, M. Konrad, and S. Shrum. CMMI : Guidelines for Process Integration and Product Improvement. Addison-Wesley Professional, February 2003.
7. J. Cleland-Huang, B. Berenbach, S. Clark, R. Settimi, and E. Romanova. Best practices for automated traceability. Computer, 40(6):27-35, June 2007.
8. D. G. Firesmith. Requirements engineering. Journal of Object Technology, 1(4):93-103, 2002.
9. INCOSE. INCOSE Systems Engineering Handbook. Technical Report Version 3.1, INCOSE, 2007.
10. I. Jacobson, M. Christerson, P. Jonsson, and G. Övergaard. Object-oriented software engineering: A use-case driven approach. Addison-Wesley Publishing, 1992.
11. M. K. Jaelson Castro and J. Mylopoulos. Towards requirements-driven information systems engineering: the Tropos project. Information Systems, 27(6):365-389, 2002.
12. J. C. Kelly, J. S. Sherif, and J. Hops. An analysis of defect densities found during software inspections. J. Syst. Softw., 17(2):111-117, 1992.
13. S. McConnell. Code complete: a practical handbook of software construction. Microsoft Press, Redmond, WA, USA, 1993.
14. H. W. J. Rittel and M. M. Webber. Dilemmas in a general theory of planning. Policy Sciences, 4(2):155-169, June 1973.
15. R. Sangwan, M. Bass, N. Mullick, D. J. Paulish, and J. Kazmeier. Global Software Development Handbook (Auerbach Series on Applied Software Engineering Series). Auerbach Publications, Boston, MA, USA, 2006.
16. R. Selby. Measurement-driven dashboards enable leading indicators for requirements and design of large-scale systems. Software Metrics, 2005. 11th IEEE International Symposium, page 10 pp., September 2005.
17. Software Engineering Standards Committee of the IEEE. IEEE Recommended Practice for Software Requirements Specifications. IEEE, 1998.
18. X. Song, G. Matos, B. Hwong, A. Rudorfer, and C. Nelson. S-rap: A concurrent prototyping process for refining workflow-oriented requirements. In Proceedings of the 13th IEEE International Conference on Requirements Engineering, pages 416-420, August 2005.
19. R. Sorensen. CCB - An Acronym for "Chocolate Chip Brownies"? A Tutorial on Control Boards. CrossTalk, 12:3-6, March 1999.
20. W. Swartout and R. Balzer. On the inevitable intertwining of specification and implementation. Commun. ACM, 25(7):438-440, 1982.