How to best represent Subsystem Requirements & trace among levels.

[AskGeeves]

I'm looking for the best practice method in EA to manage a 3-tiered requirements breakdown structure.

EA (and perhaps SysML more broadly) doesn't appear to me to be able to natively manage requirements that sit at differing levels. I was thinking that maybe I need to manage subsystems is via the placement of "requirement" objects into respective packages and applying a "trace" relationship.

Lack of attributes that I can attribute to the "requirement" type seems to be constraining in the way requirements could be managed in DOORs and is leading me to believe that EA is not the most effective tool for requirements management (despite needing to have them in the EA to trace to model elements).

Is there a smarter way? Is my naivete tripping me up perhaps.

Looking for any advice or learnings from experience on how to progress.