The Community for Technology Leaders
RSS Icon
Issue No.05 - Sept.-Oct. (2012 vol.29)
pp: 82-87
Christof Ebert , Vector Consulting Services
Michael Jastram , Formal Mind GmbH
The primary sources of project risks and product problems are poor, missing, or changing requirements. Often, the underlying root cause is insufficient collaboration between business partners. This article provides insight into how to effectively collaborate in requirements engineering. We describe the Requirements Interchange Format (ReqIF) standard and technologies for seamless requirements development and management. I look forward to hearing from both readers and prospective column authors about this and the technologies and tools you want to know more about.
Software engineering, Software management, Standards, requirements engineering, software technology, ReqIF
Christof Ebert, Michael Jastram, "ReqIF: Seamless Requirements Interchange Format between Business Partners", IEEE Software, vol.29, no. 5, pp. 82-87, Sept.-Oct. 2012, doi:10.1109/MS.2012.121
1. C. Ebert, and R. Dumke, Software Measurement, Springer, 2007.
2. C. Ebert, Global Software and IT, Wiley-IEEE CS, 2012.
3. What Are Your Requirements?, tech. report, Standish Group, 2003.
4. Requirements Interchange Format (ReqIF), version 1.0.1, Object Management Group, 2011;
5. M. Jastram and A. Graf, “ReqIF: The New Requirements Standard and its Open Source implementation Eclipse RMF,” tech. report, Commercial Vehicle Technology Symp., 2012.
6. M. Jastram and A. Graf, “Requirement Traceability in Topcased with the Requirements Interchange Format (RIF/ReqIF),” Proc. 1st Topcased Days Toulouse, 2011; a/acPub-topcase-JaGr2011.pdf.
74 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool