Be the first to like this
No matter whether a heavy-weight approach like RUP is employed or an agile one - requirements have to be collected and organized somehow. It is desirable to maintain the requirements and to establish …
No matter whether a heavy-weight approach like RUP is employed or an agile one - requirements have to be collected and organized somehow. It is desirable to maintain the requirements and to establish a traceability between the requirements and the development artifacts. Such a traceability has many uses, including to support project management, testing or change management, to name just a few. In practice, it is difficult to find the right balance for requirements management: If requirements are not updated, their usefulness is severely limited. Likewise, an incomplete or incorrect traceability can be worse than having none at all. The cost of a correctly maintained traceability can in some circumstances out-weight their value. In this talk, we present the Eclipse Requirements Modeling Framework (RMF) and its GUI, ProR. RMF supports a generic data model that is based on the emerging ReqIF standard. ReqIF is an OMG standard that was developed by the automotive industry to aid the exchange of requirements between manufacturers and suppliers. ProR is the first clean-room implementation of a ReqIF tool. We expect most industry tools to support ReqIF by the end of 2012 (many tools, including Rational DOORS, already support the predecessor of ReqIF). Support for the project was pledged by Airbus, Thales, MKS and many others (see http://eclipse.org/rmf). As ProR is generic, it can be used with a wide range of development processes. But the real power stems from the ability to extend it with plugins to provide additional functionality. In this talk, we will also present a method for building a formal model of requirements. The method supports the iterative addition of requirements to the model, while evolving the requirements. We demonstrate how ProR (with the integration plugin) support tasks like link creation, change management and requirements evolution. As an Eclipse project, RMF can easily be integrated into existing tools. There is a lot of interest in the Topcased community, for instance, to integrate ProR for better requirements engineering support. Further, we are evaluating traceability support for SysML, implemented in Topcased. This talk addresses everybody who manages requirements and who deals with the software development process. Besides requirements engineers, this includes product managers, project managers and software architects. As systems being developed are getting more and more complex, the importance of an effective development process and an integrated tool chain are becoming increasingly important. RMF makes an open contribution in an area that so far has been under-represented in the Eclipse ecosystem.