The "Requirements Modeling Framework" (RMF) project is a proposed open source project under the Model Development Tools Project.
This proposal is in the Project Proposal Phase (as defined in the Eclipse Development Process) and is written to declare its intent and scope. We solicit additional participation and input from the Eclipse community. Please send all feedback to the Eclipse Proposals Forum.
The vision is to have at least one clean-room implementation of the OMG ReqIF standard in form of an EMF model and some rudimentary tooling to edit these models. The idea is to implement the standard so that it is compatible with Eclipse technologies like GMF, Xpand, Acceleo, Sphinx, etc. and other key technologies like CDO.
The Eclipse ecosystem provides a number of projects to support software development and systems engineering. However, in the open source community, one important aspect of the engineering process is very much neglected: requirements management, consisting of a number of sub-disciplines including requirements capturing, requirements engineering, requirements traceability, change management and product line engineering, to name just a few.
The goal of RMF is to provide the technical basis for open source projects that implement tools for requirements management. The conditions for the inception of such a project are perfect: Until now, all tools for requirements engineering suffered from the lack of a standard for the exchange and storage of requirements. Each tool provider invented his own method and meta-model for requirements, thereby limiting the common user base and the possibility for exchange between tools.
The OMG just released the Requirements Interchange Format (ReqIF), an XML-based data structure for exchanging requirements. The first draft of this standard with the name RIF was created in 2004, and various requirements tools (commercial and otherwise) already support it to some degree. Currently there are three actively used versions of the standard: RIF 1.1a, RIF 1.2 and ReqIF 1.0.1.
This open standard could have as much impact on requirements structuring as the UML had on modeling. The implementation of the ReqIF standard as an Eclipse project could similarly be as important for the requirements community as was the implementation of UML2 in Ecore for the modeling community by paving the way for such tools as Topcased and Papyrus MDT.
Providing such a project under the Eclipse umbrella would offer a possibility for many projects that are involved in requirements management to find a common implementation of the standard. It would push Eclipse in to phases of the development process where it is currently under-represented.
The RMF project's focus is the creation of libraries and tools for working with ReqIF-based requirements. The objective is to provide the community with a solid implementation of the standard upon which various tools can be built. RMF will provide a means for data exchange between tools, an EMF-based data model, infrastructure tooling and a user interface.
RMF will not provide support for Requirements Management. Instead, it is expected that users will use specialized tools or work with the available Eclipse tooling (EMF Compare, version control integration, etc.). Generic or specific parts of the tooling can be hosted as part of the RMF project.
The following diagram depicts the architecture of the current development and indicates which elements will be part of the initial contribution:
We created an EMF-based implementation of the ReqIF core that supports persistence using the RIF XML schema. Further, we created a GUI for capturing requirements.
These contributions have their origins in research projects, where they are actively used. In particular, these research projects already produced extensions, demonstrating the value of the platform.
The Eclipse ecosystem will benefit from an implementation of a requirements standard to cover more aspects of system development. Currently, modelling is covered well on the low level (EMF, TMF, CDT, etc.) and high level (UML, SysML, etc.). Adding the domain of requirements capturing would extend the coverage. To promote it, we need not only a standard, but also a common implementation that tools build upon.
Being an Eclipse project will draw the interest of more parties to the project. The implementation of a standard benefits greatly from the participation of many parties (improvement of quality, reduction of cost). In addition, long-term support through the participation of many parties is essential for many domains.
The first initial contribution will come from itemis and will include our implementation of the ReqIF and RIF metamodels as .ecore models, including special (de)serializers that map the EMF-models to a ReqIF conforming standard. The model and (de)serializers are already available at itemis and need only be provided.
The initial contribution has been internally tested. A ReqIF export from production data from the automotive domain from a commercial tool has been imported into Eclipse and exported again, keeping all the structural data, with the exception of ReqIFs XHTML extensions (see table below).
They have been implemented according to the specification, but since ReqIF is a new standard, no extensive tests with ReqIF files coming from other sources / other tools have been made.
The second contribution will come from the University of Düsseldorf and will include a front end that facilitates working with ReqIF data (ProR). While ReqIF data could also be edited with the default EMF editor, this is not even remotely practical: a tree view of the requirements, with the details shown in the property view, doesn't allow users to efficiently navigate requirements or get an overview of what's there.
The GUI allows users to arrange only those requirements attributes that they care about in a grid view and implements a number of shortcuts for frequent operations that actually consist of a number of model transformations. Further, it contains an extension mechanism that allows integration with other EMF-based tools and supports custom rendering. The GUI currently only support RIF 1.2, and not all RIF features are implemented yet.
The GUI so far has been developed under the name ProR. This name, including the pror.org property, will be part of the contribution to the project (see legal issues below).
All contributions will be distributed under the Eclipse Public License. The ReqIF metamodel has been fully developed by itemis. The GUI has been developed by University of Düsseldorf with changes from itemis.
The GUI development to date has been branded as ProR, supported by the pror.org website. The rights to the brand and the name reside with Michael Jastram, who is willing to agree to the Eclipse Trademark Transfer Agreement.
Sphinx: Requirements models tend to grow quite large in commercial projects. Using Sphinx will improve the performance and scalability. The current implementation is not yet based on / integrated with Sphinx.
EMF Compare: Since the RMF is based on EMF, EMF Compare could be a key technology for the comparison of requirements documents.
M2T/BIRT: With the new Indigo Release, BIRT includes an EMF adapter. BIRT could be one of the technlogies used to create documents out of requirement models. The M2T technologies (Xpand, Acceleo) are possible technologies as well.
The initial committers will deliver the initial release. Funding can be provided through the ITEA2 research project until June 2012 and through the Deploy project until February 2012. Funding may be available thereafter.
The following individuals are proposed as initial committers to the project:
We welcome additional committers and contributions.
The following Architecture Council member will mentor this project:
The following individuals, organisations, companies and projects have expressed interest in this project:
|25-Jul-2011||Added more interested parties; provided a link to the ProR website; fixed umlauts.|
|26-Jul-2011||Added even more interested parties; Updated the feature table (XHTML Support)|
|27-Jul-2011||Added one more committer biographies of committers. Updated the feature table (XHTML and Tool Support)|
|28-Jul-2011||Added information about the transfer of the ProR trademark to the Eclipse Foundation.|
Back to the top