Information Technology Reference
In-Depth Information
R
3
R
5
R
1
R
2
R
4
PX
l1
PX
l2
PY
l1
PY
l2
L
l1
L
l2
L
l3
L
l4
W
l1
S
l1
Domains
WAP
Server
Peripherals
Laptop
Person X
Person Y
LAN
Camera
= Interaction
Printer
Tape
Ix
= Interface
= Relationship
Rx
Figure 6.5
Domain functional-isolation requirements engineering.
table 6.2
Domain Attributes template
Domain
Interfaces
Relationships
Data Flows
Person X
Person Y
Laptop
WAP
Server
the fingerprint reader for biometric validation. The laptop interacts with the WAP
domain via wireless network. The WAP domain interacts with the server domain
via the wired network. The labels R
x
denote the domain relationships.
The IA architect determines IA requirements by examining each domain, each
domain interface, each domain interaction (relationship), and data flows with
respect to each IA core principle. Table 6.2 provides a template to list the domains
and capture details of their respective interfaces, relationships, and data flows.
Table 6.3 provides a template to capture the risks and how to address the risks
with respect to the IA core principles.
IA requirements obtained using system decomposition or domain functional
isolation must eventually trace to business drivers in the form of high-level business
requirements. There is a need for requirements traceability from the lowest-level
technical and IA requirements to the highest-level business drivers behind them.
Table purposely left blank.
Table purposely left blank.
