Information Technology Reference
In-Depth Information
table 6.3
Domain risks template
Domain
Confidentiality
Integrity
Availability
Person X
Person Y
Laptop
WAP
Server
Domain
Possession
Authenticity
Utility
Person X
Person Y
Laptop
WAP
Server
Domain
Nonrepudiation
Authorized Use
Privacy
Person X
Person Y
Laptop
WAP
Server
6.5
requirements traceability
Whichever method provides the IA requirements, there is need to provide formal
and comprehensive requirements traceability. Table 6.4 provides a template for a
requirements traceability matrix. Most projects will have a series of traceability
tables that together make up one large traceability matrix. Depending on the gran-
ularity of the WBS, a single traceability table may represent a component. Multiple
component tables may trace to a single subsystem table. Multiple subsystem tables
may trace to a single system table. All traceability tables should ultimately trace to a
business requirement table that contains the root business drivers, e.g., RFP, legisla-
tive compliance, mission, or strategic objective. An effective requirements matrix
provides many benefits, including:
n
Ensures meeting of the minds between architect and sponsor
