Information Technology Reference
In-Depth Information
<<TV_Object>>
Remote System
<<TV_Object>>
WAN
0..*
0..*
0..*
1
<<TV_Object>>
Firewall
1
1
0..*
1
<<TV_Object>>
LAN
<<TV_Object>>
DMZ LAN
0..*
0..*
0..*
0..*
0..*
0..*
<<TV_Object>>
PC
<<TV_Object>>
Backend
Business
Server
<<TV_Object>>
Enterprise
Application
Server
0..1
0..1
0..1
<<TV_Object>>
BarReader
<<TV_Object>>
Printer
FIGURE 6.1: An overview of the node configuration.
6.2.2
Implementable Standards
Although the level of interoperability between vendor platforms is increas-
ing nowadays, there are still some incompatibilities that force the use of partic-
ular applications that match the operating system selected in the specification
(Linux, MacOS, Windows and so on). This is why there is the need to specify
the implementable standards to which technology objects must conform.
Examples of such implementable standards are the application programming
interfaces for ISO/IEC/IEEE 9945 (POSIX), or for ISO/IEC 9075-10, SQL
| Object Language Bindings (SQL/OLB) and media format specications
like ISO/IEC 13490 CD-ROM filing systems . Figure 6.2 shows a schematic
view of the business server technology object, which contains other technol-
ogy objects that represent the CPU, memory, middleware and so on, and the
implementable standards to which some of these objects should conform.
Implementable standards are effectively templates for the technology ob-
jects. Thus, the technology viewpoint provides a link between the set of
viewpoint specifications and the real implementation by listing the standards
