Eclipse As An End-to-End Platform

Please find below the URL for the Eclipse Foundation site and the Eclipse downloads.

http://www.eclipse.org/

Eclipse is the closest realization of the Model-View-Controller architectural pattern that I know.

One would almost wish to have Requirements and Test Cases be added as Eclipse perspectives and have the vendors deliver those perspectives through developing Plug-ins for Eclipse.

I am not a proponent of Eclipse (I dislike its "slowness" - courtesy of it being written in Java) but I think it is an example of a flexible platform that supports multiple views that inter-operate with one another.

Eclipse enables multiple views of the same underlying model (in the sense of MVC architecture).

For software development requirements engineering, inter-operability with Eclipse could be regarded as a requirement; i.e. one could ask the vendor “Is there an Eclipse Plug-in available for the product?”.

If so, then one could navigate from requirements to models to code to test cases seamlessly and within the same "integrated" environment. We already have rudiments of this; we can go back and forth between UML models and code and between CaliberRM (for requirements) and StarTeam (for configuration management).