ADS Operational Model Notation Version 2.0– Version 2.0
© Copyright IBM Corporation 2002. All rights reserved Page 12 of 71
IBM Confidential
2.2.1.1 Unsized Physical Level of the Operational Model
o The Unsized Physical Level documents all technologies and products, but the detailed
configurations necessary to deliver the non-functional requirements are not defined. The
configuration yet to be done may be as simple as sizing an unsized computer, or more complex,
such as the need for a “fail-over” design” to achieve high levels of availability, or a “network
dispatcher” technology to achieve high levels of performance.
This level is typically created as part of a “top down” technique, in which the Operational Model is
developed “from scratch”.
2.2.1.2 Ranged Physical Level
o The ranged physical level describes a typical physical configuration for a set of technologies,
usually proven to achieve a bounded range of requirements as defined by a corresponding logical
OM for a defined range of circumstances. Such physical OM diagrams may show how higher
levels of availability, performance etc. can be achieved with the selected technologies, such as
how to use a “network dispatcher” or a “fail over” technology. This level does not normally
document the placement of application components (e.g. packages) although it can be
associated with specific application level products such as Lotus Notes or SAP.
Typically, this level is used in a development technique that involves the placement of application
components directly onto a ranged physical OM, together with additional activities for detailed sizing and
other activities associated with achieving specific non-functional requirements such as transaction
volumes or high levels of availability.
2.2.1.3 Comparing Partial Levels of the Physical OM
Te following table may help to position the various partial levels of the physical OM:
Level of the
Operational Model
Sized and
Configured?
Includes application
components?
Includes technical
components?
Unsized Physical No detailed
configurations
Yes Yes
Ranged Physical Ranged, outline
approaches
No, but does provide
placement guidelines
Yes
Sized Physical Fully configured Yes Yes
2.3 Other Factors Affecting the Presentation of OM Diagrams
The notation presented in the remainder of this document may depend on the diagram’s level (e.g.
specification” or “physical”) or its type (“relationship” or “walkthrough”).
There are also other factors that may determine an OM diagram’s appearance. However, although these
other factors may affect the OM diagram’s content
they do not affect its notation.
These factors include:
Elaboration of the OM: Any development process requires the OM to be created in a
particular way. Whatever the approach (waterfall, iterative, etc.), each OM
剩余70页未读，继续阅读
u011095730
- 粉丝: 0
- 资源: 8
我的内容管理
展开
最新资源
- 构建Cadence PSpice仿真模型库教程
- VMware 10.0安装指南：步骤详解与网络、文件共享解决方案
- 中国互联网20周年必读：影响行业的100本经典书籍
- SQL Server 2000 Analysis Services的经典MDX查询示例
- VC6.0 MFC操作Excel教程：亲测Win7下的应用与保存技巧
- 使用Python NetworkX处理网络图
- 科技驱动：计算机控制技术的革新与应用
- MF-1型机器人硬件与robobasic编程详解
- ADC性能指标解析：超越位数、SNR和谐波
- 通用示波器改造为逻辑分析仪：0-1字符显示与电路设计
- C++实现TCP控制台客户端
- SOA架构下ESB在卷烟厂的信息整合与决策支持
- 三维人脸识别：技术进展与应用解析
- 单张人脸图像的眼镜边框自动去除方法
- C语言绘制图形：余弦曲线与正弦函数示例
- Matlab 文件操作入门：fopen、fclose、fprintf、fscanf 等函数使用详解
资源上传下载、课程学习等过程中有任何疑问或建议，欢迎提出宝贵意见哦~我们会及时处理！
点击此处反馈
