I'm trying to use requirements captured using Volere's Snow Card into an EA requirements diagram.
A typical requirement in Volere has the following fields (in bold in this example):
Requirement Name: UI20
Requirement type: X:1
Use-case #: 1, 2, 3, 4, 5, and 6
Description: The user interface should use
pastel colors.
Rationale: This will be soothing to the eyes and
will look formal.
Source: Ivan Banks, accounting manager
Daisy Brown, HR director
Fit criterion: The colors used in the user
interface must use a combination of pastel
shades provided in the Microsoft Windows
environment.
Customer satisfaction: 5
Customer dissatisfaction: 4
Dependencies: All the requirements referring to
the user interface.
Conflicts: None
Supporting materials: None
History: Created July 3, 2007
In EA, for e/a requirement I can easily define the requirement
Name,
Type,
Description: (under notes),
History (with date created and/or versioning) and
Supporting materials (from the file tab).
Any ideas how to handle the other fields?
Use-case # - how can I reference (link) these for the requirement?
RationaleSourceFit criterion Customer satisfaction/dissatisfaction:DependenciesConflicts [/list]
Any suggestions would be greatly appreciated,
Ed.