top - download
⟦6144d133b⟧ Wang Wps File
Length: 10401 (0x28a1)
Types: Wang Wps File
Notes: Spelunked
Names: »~ORPHAN75.00«
Derivation
└─⟦0cd3644ba⟧ Bits:30006012 8" Wang WCS floppy, CR 0051A
└─ ⟦this⟧ »~ORPHAN75.00«
WangText
…00……00……00……00……00…K…02……00……00…K
J…09…J…01…J…07…I…08…I…0e…I…01…I…05…H…08…H…0b…H…0f…H
H…07…G…0c…G…00…G
G…07…F…0b…F…0e…F…01…F E…09…E…0e…E…05…D…09…D…0d…D…01…D C…0a…C…0f…C C…07…B…0c…B…01…A…08…A…0b…A…02…A
A…07…@…0a…@…0d……86…1 …02… …02… …02…
…02…CPS/REP/001
…02…FAH/810403…02……02…#
CAMPS PERFORMANCE REPORT
…02……02…CAMPS
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1 INTRODUCTION .................................
2 MAPPING OF REQUIREMENTS ......................
3 DATA COLLECTION FOR MODEL CALCULATIONS ......
4 MODEL SELECTION CONSIDERATION ................
4.1 GENERAL MODEL LAYOUT AND MECHANISMS ......
4.2 PU SYSTEM ................................
4.2.1 Introduction ..........................
4.2.2 Time Slcing ..........................
4.2.3 Multiserver Queuing ...................
4.2.4 Priority Queuing ......................
4.2.5 CPU Time and Processor Bus Loading ....
4.2.6 Final Conclusions .....................
4.3 TDX SYSTEM .............................
4.3.1 TDX System Load .......................
4.3.2 Terminal Load .........................
4.4 CHANNEL SYSTEM ...........................
4.5 DISC SYSTEM .............................
4.6 CONCLUSIVE MODEL CONSIDERATIONS ..........
5 PERFORMANCE CALCULATIONS .....................
5.1 THROUGHPUT ...............................
5.2 RESPONSE TIMES ...........................
5.3 SIZING ...................................
1̲ ̲ ̲I̲N̲T̲R̲O̲D̲U̲C̲T̲I̲O̲N̲
Performance requirements shall be mapped upon system
components and checked against system capabilities.
Performance requirements have been taken from section3.4.1
of the CPS/210/SYS/0001: All sections until 3.4.1.6
(included) and 3.4.1.8.
Section 2 will list all requirements in the form in
which they shall be checked against the system and
the system components involved in each case:
- Throughput rquirements: Performance calculations
shall be based on busy hour figures except for
i̲n̲c̲o̲m̲i̲n̲g̲ ̲m̲e̲s̲s̲a̲g̲e̲s̲ ̲u̲n̲t̲i̲l̲ ̲f̲i̲r̲s̲t̲ ̲s̲t̲o̲r̲a̲g̲e̲ and o̲u̲t̲g̲o̲i̲n̲g̲
̲m̲e̲s̲s̲a̲g̲e̲ ̲f̲r̲o̲m̲ ̲r̲e̲l̲e̲a̲s̲e̲ ̲(̲i̲n̲c̲l̲u̲d̲e̲d̲)̲ ̲u̲n̲t̲i̲l̲ ̲d̲i̲s̲p̲a̲t̲c̲h̲
̲f̲o̲r̲ ̲e̲x̲t̲e̲r̲n̲a̲l̲ ̲c̲h̲a̲n̲n̲e̲l̲s̲, in these exceptional cases,
the busy minutetraffic shall be considered as well
(throughput only).
- Timing requirements: These requirements are stated
in CPS/210/SYS/0001 as a̲p̲p̲l̲i̲c̲a̲b̲l̲e̲ for b̲u̲s̲y̲ ̲h̲o̲u̲r̲
̲t̲r̲a̲f̲f̲i̲c̲ ̲o̲n̲l̲y̲: This has not been specifically stated
in each case but applies in general.
- Sizing requirements: These requirements are listed
and treated in section 5.3 separately.
In section 3 data for usage of CPU-time, number of
accesses to disc, and character transfer on TDX and
Channel system are collected for each function whic
is addressed in section 2, thereby also listing data
for system packages: The final data for system package
resource consumption will provide the data necessary
for a final performance estimate.
However, the data collected in section 2 may alsobe
taken as a set of requirements to the system packages:
As long as the system packages do not exceed the resource
consumption listed here, the estimated performance
within the requirements shall hold. This is the approach
which shall be followe.
Based on the results from section 3 a system model
shall be selected, hereby including system hardware
characteristics. This discussion is found in section
4.
Finally, performance calculations may be carried through
as in section 5.…86…1 …02… …02… …02… …02…
2̲ ̲ ̲M̲A̲P̲P̲I̲N̲G̲ ̲O̲F̲ ̲R̲E̲Q̲U̲I̲R̲E̲M̲E̲N̲T̲S̲
The requirement sheets presented are a straight forward
listing of performance requirements related in each
case to one of the functions known from th system requirements
specification.
For each requirement is further specified the system
packages involved.
The following general notes shall apply in a̲l̲l̲ cases
as specified here:
- throughput requirements correspond to busy hour
traffic durig war as shown in fig. 2-1.
Busy minute figures are 3 times busy hour figures
for incoming messages and 2 times for outgoing
message traffic.
- Timing requirements are valid for busy hour only.
- Timing requirements for interactive transactins
shall apply from transmission of last character
from VDU until reception of first character on
VDU.
- Timing requirements for incoming message handling
shall apply from reception of last character until
delivery of first character to printer o VDU.
- Security interrogation shall not be included in
timing requirements.
In certain cases (e.g. Statistics, and Log collection
and print) discussions are carried through in order
to derive figures for section 3.
Whenever CPU time consumpton is quoted, CPU time for
disc access is not included.
Storage requirements are listed and discussed in 5.3.
Discussion and listing of certain connectivity oriented
throughput requirements are postponed to the sections
4.3 and 4.4.…86…1 …02… …02… …02… …02…
CAMPS TRAFFIC FLOW…01…BUSY HOUR WAR
M̲A̲P̲P̲I̲N̲G̲ ̲O̲F̲ ̲R̲E̲Q̲U̲I̲R̲E̲M̲E̲N̲T̲S̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
FUNCTION REQUIREMENTS IOC TEP/THP SFM
THR=THROUGHPUT
TIM=TIMING
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
O̲U̲T̲G̲.̲ ̲M̲S̲G̲ T̲H̲R̲: BUSY Format Trans- T̲E̲P̲: MSG. Fetch
Prep.
P̲R̲E̲P̲.̲ HOUR, WAR fer to VDU Validation; format;
Header & Reserve
File
Text Separa- & Store
tely and in
totl.
Msg. Trans-
fer from VDU
Separate 512 ch/msg.
Prep. of out
Header T̲I̲M̲: C̲H̲E̲C̲K̲
̲T̲A̲B̲L̲E̲S̲
and Time from 2 x 1024 ch/ 5 PLA,
0.1 AIG,
Text entering msg. inp 3 SIC/MSG
(last ch.
Incl. transmitted PLA's,
AIG's
request from VDU) SIC's are
for coord. header or text ass.
to result
and release for validation in
only
one
to first ch. disc
access
response: each.
10 sec (90%)
O̲C̲R̲ ̲I̲N̲P̲U̲T̲ T̲H̲R̲:̲ BUSY HOUR,
WAR 2 x 1024 ch/ As above As above
msg inp. except
for pre.
format.
P̲T̲R̲ ̲I̲N̲P̲U̲T̲ T̲H̲R̲: BUSY HOUR, 1536 ch/msg TRAF. HANDL.: Reserve
file
WAR inp. Routing vali- & store
dation of non-
encrypted msg Check
tables:
5 PLA,
0.1 AIG
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
TABLE 2-1
M̲A̲P̲P̲I̲N̲G̲ ̲O̲F̲ ̲R̲E̲Q̲U̲I̲R̲E̲M̲E̲N̲T̲S̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
FUNCTION REQUIREMENTS IOC TEP SFM
THR=THROUGHPUT
TIM=TIMING
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
M̲S̲G̲ ̲E̲D̲I̲T̲I̲N̲G̲ T̲H̲R̲:BUSY HOUR, Complete
re- As
prep.
WAR evaluation as
As prep. but 2x1024 ch/msg prep.
with 1/2 out.
send for
coordina- 2x1024 ch/msg
tion and no in.
send release
T̲I̲M̲: as prep.
2 edit per (Operator
msg will change
256 ch per
edit).
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
TABLE 2-2
M̲A̲P̲P̲I̲N̲G̲ ̲O̲F̲ ̲R̲E̲Q̲U̲I̲R̲E̲M̲E̲N̲T̲S̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
FUNCTION REQUIREMENTS IOC TEP SFM
THR=THROUGHPUT
TIM=TIMING
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
C̲O̲M̲M̲E̲N̲T̲ ̲P̲R̲E̲P̲ T̲H̲R̲: BUSY HOUR, Validation Fetch
format
WAR of total com- reserve
file,
256 ch/comm ment store
out
512 ch/comm.
inp.
T̲I̲M̲: Time from
enry (last
character
transmitted
from VDU
of fully
prep. comment
to first ch.
Resp.: as prep.
= 10 sec (90%)
V̲D̲U̲ ̲P̲A̲G̲E̲S̲ T̲H̲R̲:(BUSY HOUR), 256 ch out As above As above
P̲R̲E̲P̲.̲ WAR
2x1024 ch inp
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
TABLE 2-3
M̲A̲P̲P̲I̲N̲G̲ ̲O̲F̲ ̲R̲E̲Q̲U̲I̲R̲E̲M̲E̲N̲T̲S̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
FUNCTION REQUIREMENTS IOC TEP SFM
THR=THROUGHPUT
TIM=TIMING
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
C̲O̲M̲M̲E̲N̲T̲ ̲ T̲H̲R̲: BUSY HOUR, Complete re- As prep.
E̲D̲I̲T̲I̲N̲G̲ WAR 256 ch/comm. evaluation as
out prep.
1 edit/comm. 512 ch/comm.
T̲I̲M̲: As com- inp.
ment prep.
(Operator will
chage 50 ch)
V̲D̲U̲ ̲P̲A̲G̲E̲S̲ T̲H̲R̲:(BUSY HOUR), 2x1024 ch out As above As above
E̲D̲I̲T̲ WAR
1 edit/page 2x1024 ch inp
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
TABLE 2-4
M̲A̲P̲P̲I̲N̲G̲ ̲O̲F̲ ̲R̲E̲Q̲U̲I̲R̲E̲M̲E̲N̲T̲S̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
FUNCTION REQUIREMENTS IOC TEP SFM
THR=THROUGHPUT
TIM=TIMING
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
R̲E̲L̲E̲A̲S̲E̲ T̲H̲R̲: BUSY MIN, Validate re- Fetch
release
and BUSY HOUR lease format format
+ msg.
WAR 2048 ch/msg queue notifi-
Accept assu- out cation
for
med 512 ch/msg distributon
inp.
Queue msg. to
traffic hand-
ling.
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
TABLE 2-5…86…1 …02… …02… …02… …02…
M̲A̲P̲P̲I̲N̲G̲ ̲O̲F̲ ̲R̲E̲Q̲U̲I̲R̲E̲M̲E̲N̲T̲S̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
FUNCTION REQUIREMENTS MDP TEP IOC
THR=THROUGHPUT
TIM=TIMING
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
D̲I̲S̲T̲R̲I̲B̲U̲T̲I̲O̲N̲ T̲H̲R̲: BUSY HOUR, Fetch
Distr. Transfer
to
of outg. msg WAR inf.; check terminals
locally, and queue security int.
coord, com- for TEP.
ments, re-
lease no- For outg.msg.
tification. ass. 3 SIC & 2
SDL. Add. SCDs
from prepara-
tion, when lo-
cally generated
R̲E̲C̲E̲P̲T̲I̲O̲N̲
of the same
Outg. msg. 1792
ch/msg
Coordination C̲O̲O̲R̲D̲I̲N̲A̲T̲I̲O̲N̲: 1792
ch/msg
15 msg are
coord 2 times
with 5 copies;
Release 256 ch/notif.
notification
10 msg are
presented once,
Comments and coord once 256 ch/comm.
with 5 copies
(ie. 10x6 coord)
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
TABLE 2-6
M̲A̲P̲P̲I̲N̲G̲ ̲O̲F̲ ̲R̲E̲Q̲U̲I̲R̲E̲M̲E̲N̲T̲S̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
FUNCTION REQUIREMENTS THP
THR=THROUGHPUT
TIM=TIMING
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
