1 Requirements Engineers, in IBM Rational DOORS, might develop and manage requirements, and send a list of requirements to business analysts in System Architect, by, for example, exporting a CSV file from IBM Rational DOORS and importing that CSV file into System Architect's repository. System Architect’s metamodel would need to be extended first to add definitions or properties that would contain this information.

2 Business Analysts in System Architect specify that model artifacts (imported into the repository from IBM Rational DOORS) meet a requirement or requirements (or, in general, any IBM Rational DOORS object imported).

3 Business Analysts, using the System Architect DOORS link, send model artifacts (containing the information on what IBM Rational DOORS object the artifact satisfies) over to IBM Rational DOORS.

4 Requirements Engineers, in IBM Rational DOORS, create traceability links between System Architect model artifacts and IBM Rational DOORS objects.

5 At certain stages during the project, Business Analysts in System Architect use the System Architect DOORS interface to update information in System Architect from IBM Rational DOORS. Model artifacts that have been linked to IBM Rational DOORS objects are annotated appropriately in System Architect, and a skeleton of the actual IBM Rational DOORS objects are brought into System Architect.

6 System Architect users can view the IBM Rational DOORS requirements (or objects) linked with model artifacts in System Architect, use its reporting system to publish reports detailing such information, use the Explorer diagram to investigate “what if” relationships, and publish all information to websites using System Architect’s publishing capabilities.

1 Business Analysts, working in System Architect, elucidate new requirements from the business models that they are building. Within System Architect, users can create Requirements definitions, and, using its customizable repository, tailor its metamodel to introduce new definition types, such as Functional Requirement, System Requirement, Technology Requirement, and so forth. These new requirements can be ported to IBM Rational DOORS to a module separate from modules that model artifacts are sent to; the System Architect DOORS interface enables you to send System Architect artifacts to multiple modules in IBM Rational DOORS.

2 In IBM Rational DOORS, Requirements Engineers link the new requirements to model artifacts.

3 System Architect users perform an update from IBM Rational DOORS, and view model artifacts linked to IBM Rational DOORS requirements (or objects). As with Workflow Example #1, users can use System Architect's reporting system to publish reports detailing such information, use the Explorer diagram to investigate 'what if' relationships, and publish all information to websites using System Architect's publishing capabilities.

1 Within System Architect, Business Analysts and other users such as Enterprise Architects, Systems Engineers, Database Designers, and so forth build models to represent the systems, applications, and databases that support the business processes. These system, application, and data models are also sent to IBM Rational DOORS using the System Architect DOORS interface.

2 Meanwhile, Requirements Engineers in IBM Rational DOORS derive Functional Requirements from high-level Business Requirements, and develop and maintain System Requirements, Technology Requirements, and so forth in IBM Rational DOORS. The Requirements Engineers link these requirements with applicable System Architect model artifacts ported in through the interface.

3 System Architect users perform an update from IBM Rational DOORS, and view and report on requirements linked with model artifacts, as described in the previous workflows.