Integration with Enterprise Architect > Relationships between RaQuest Objects and Enterprise Architect Objects

This section describes how RaQuest objects are related to Enterprise Architect objects.

RaQuest objects are stored in the Enterprise Architect Project as shown in the following table:

RaQuest Object	Enterprise Architect Object	Remarks
Requirement	Requirement
Change	Requirement
Requirement's Attribute	Requirement's Properties or Tagged Value
User-defined Attribute	Requirement Tagged Value
Relationship between requirements	Dependency connector between requirements
Package	Package
Comment	Note connected with requirement by the Notelink connector	Public comments are stored to Element Issues
File	Requirement's File
Member	Resource	ref. Members
Assigned member	Resource allocation of requirement	ref. Members
Relationships between requirements and Use Cases	Realize connectors between requirements and Use Cases
Relationship between Requirements and elements of Enterprise Architect	Realize connectors between requirements and elements	Diagrams, attributes and methods are stored as File
Test items	Test items of requirement
ID Numbering of RaQuest	Auto Counter (Type = Requirements)	synchronize either active or nonactive statuses
Login user name	Author in the Options dialog	ref.Login User Name
Requirement types	Requirement Types of General Types	ref.Enterprise Architect Requirement Types The order of Requirement Types is not stored in Enterprise Architect.
Status types	Status Types of General Types	ref.Enterprise Architect Requirement Status The order of Requirement Types is not stored in Enterprise Architect.

As you can see above, almost all information about requirements, except requirement update log, is accessible from Enterprise Architect. See Reference Methods for RaQuest Information in Enterprise Architect for details.