Editing Software prototyping (section)

===Requirements Engineering Environment===
"The Requirements Engineering Environment (REE), under development at [[Rome Laboratory]] since 1985, provides an integrated toolset for rapidly representing, building, and executing models of critical aspects of complex systems."<ref name="AcostaBurnsRzepkaSidoran1994">Dr. Ramon Acosta, Carla Burns, William Rzepka, and James Sidoran. Applying Rapid Prototyping Techniques in the Requirements Engineering Environment. IEEE, 1994. [https://web.archive.org/web/19990421115836/http://www.stsc.hill.af.mil/CrossTalk/1994/oct/xt94d10g.html]</ref>

Requirements Engineering Environment is currently used by the United States Air Force to develop systems. It is:

:an integrated set of tools that allows systems analysts to rapidly build functional, user interface, and performance prototype models of system components. These modeling activities are performed to gain a greater understanding of complex systems and lessen the impact that inaccurate requirement specifications have on cost and scheduling during the system development process. Models can be constructed easily, and at varying levels of abstraction or granularity, depending on the specific behavioral aspects of the model being exercised.<ref name=AcostaBurnsRzepkaSidoran1994/>

REE is composed of three parts. The first, called proto is a CASE tool specifically designed to support rapid prototyping. The second part is called the Rapid Interface Prototyping System or RIP, which is a collection of tools that facilitate the creation of user interfaces. The third part of REE is a user interface to RIP and proto that is graphical and intended to be easy to use.

Rome Laboratory, the developer of REE, intended that to support their internal requirements gathering methodology. Their method has three main parts: 
* Elicitation from various sources (users, interfaces to other systems), specification, and consistency checking
* Analysis that the needs of diverse users taken together do not conflict and are technically and economically feasible
* Validation that requirements so derived are an accurate reflection of user needs.<ref name=AcostaBurnsRzepkaSidoran1994/>

In 1996, Rome Labs contracted Software Productivity Solutions (SPS) to further enhance REE to create "a commercial quality REE that supports requirements specification, simulation, user interface prototyping, mapping of requirements to hardware architectures, and code generation..."<ref>Software Productivity Solutions, Incorporated. Advanced Requirements Engineering Workstation (AREW). 1996. [https://web.archive.org/web/20070927141008/http://www.sps.com/company/techfocus/modeling/arew.html]</ref> This system is named the Advanced Requirements Engineering Workstation or AREW.