|
How to Deliver Client/Server Applications that Work Alex Bakman 1995 | 227 pages ISBN: 013304601X |
|||
| $29.00 | Softbound print book | Out of print (?) | |
Index
100BaseT 62, 663GL52, 115, 116, 160
4GL28,98, 110, 113-116, 158, 160
A
accessing data 34
addressing 66
APPC 70, 72, 73, 75, 78, 160
application architecture 15-18
application code 18
application layer 79
application programming interface 98
Arcnet 63
ATM 62
automatedtestingtool 191, 192
B
background processing 83
big-endian-little endian 79
bridge 16
Btrieve 157
business process 36
business reengineering 36
C
C 110
caching 129
car rental agency, example 40
CDDI 62, 66
CICS 73, 141, 180
client 93
component 91
sponsor 10
tool 18
client/server 4, 5, 18
DBMS 70
myth 24
system 24
clipboard 35
CMIP 220
coaxial cable 62
code reusability 131
collaboration 172
collision detection 63, 64
communication line 15
competitive advantage 33, 36
configuration 17
connection 75
connectionless 73
connection-oriented 73, 75
consultant 13
context switch 107
cooperative processing 6
cost of hardware 24
cost of quality 183, 184
cost of testing 30
cost/benefit analysis 9, 23
D
data 34
conversion 79
distribution 101
integrity 15
interchange 34
data access control 15
data link layer 63
database
contention 15
engine 2G
gateway 99
middleware 97
server 86
datagram 68, 74
DataWindows 112
DB2 99, 100
DB-LIB library 108
DBMS 12, 15, 89, 98, 158
server 4
server memory requirement 107
user support architecture 107
DDCS 100
decision support system 13, 33, 40
declarative language 95
delete 95
departmental system 19
desktop machine 18
desktop programmer 51
development tool 28
device mirroring 108
disaster recovery 212
diskless workstation 93
distributed 3
distributed application 18, 91
distributed application model 127
distributed database model 160, 179
distributed interface 134
distributed interface model 179
distributed logic model 143, 179
distributed request 163
distributed system 3, 4
distributed systems management 220
distributed systems support 32
distributed unit of work 162
DME 221
domain 92
DOS 93
DRDA99, 100
dynamic data exchange 35, 51
dynamic link library 86, 160
dynamic SQL 105, 106
E
Easel 134
ECB 76, 77
EHLLAPI 135-138, 179
encapsulation 170
enterprisewidesystem 19
Ethernet 38, 63, 64
exception 88
F
fatness 129
FDDI 63, 65
fiber optic cable 63
fiber optic network 65
file record level locking 86
file server 90
FlashPoint 111, 134
fourth generation language (4GL) 28, 98, 110, 113-116, 158, 160
front end 18
front ending 139, 176
full duplex 75
function placement, principles 130, 131
function shipping 156
G
geographic location 17
groupware 117
groupware product 70
guaranteed message delivery 75
GUI 30
GUI designer 50
H
half duplex 75
hardware maintenance charge 25
I
IBM 59, 72, 100
IDAPI 99
IDMS 99
IEEE 802.12 66
IEEE 802.3 66
implementation cost 24
information hiding 170
insert 95
Internet protocol 67
interprocess communication facility 82, 86. 87
IP 67
IPX/SPX 71, 72, 75, 76
L
labor expense 29
LAN 16, 57, 62
LAN application 16
LAN Manager 91, 92
LAN Server 91-93
Lantastic 92
laser printer 25
layer 60
locking scheme 15
lost business opportunity
LUW 77
M
mainframe data center 25
MAN 58
management information base 218
management objective 21
management support 9
management task 17
marketectures 160
media independence G7
memory mapped file 86
method 170
methodolog,v 165
MIB 218
Microsoft LAN Manager 3
middleware, see database middleware
Mirroring 108
modem 90
Mozart 111, 134
MS Excel 28
MS-DOS 81, 82
MS-Windows 84
multiple physical databases
multiple sites 17, 19
multiprotocol networking E
multitasking 82, 83, 86
N
NCB 76, 148
NetBIOS 72, 82, 92, 97, 147
command 147, 148
programming 148
NetWare 5, 72, 75, 91, 93
NetWare Lite 92
network 16
analyzer 28
card 25
connection 15
control block 148
layer 66
operating system 26, 27, 70, 89-92
sniffer 216
speed IS
traffic 16
transparency 90
Notes 121-124
Notes server 5
Novell 91
Novell Netware 57
NT 82, 88, 93
O
object-oriented analysis and design 167
objects 170
ObjectView 110, 111
ODBC 98
OLE 51
OLTP 143
ongoing support 30
on-line backups 108
OOA/OOD 167, 169
Open Data Services 109
operating system 26, 81, 88, 89
operational support 19
Oracle 103, 145
OS/2 82, 86, 88, 93, 160
OSF 221
OSI 71, 77-79
OSI model 59
P
page 87
painter 111
Paradox 38
peer-to-peer 7, 38, 92
performance testing 197, 198
mechanics of 198
personal computer 25, 33, 88
physical design 16
physical I/O 86
PL/I I 10
polymorphism 181
PowerBuilder 110-113, 158, 159, 160, 178
presentation layer 78
presentation space 136
process 84, 86, 87, 107
processor-to-l/O access speed 16
processor-to-memoryaccessspeed 16
product support 45
programming interface 70
protocol analyzer 216, 217
R
RAM 88
redirected drive model 156
redirection 89, 90
referential integrity 109
regression testing 191
relational database 95
remote application control 17
remote data management model 155, 179
remote interface model 140
remote procedure call 131
remote request 161
remote unit of work 162
response time 198
responsibility 172
RIPL 93
robustness 88
roll-forward recovery 108
roll-out strategy 53
router 68
routing 66
S
scalability 18
screen scraping 134
security 82, 88
segment 87
select 95
semaphore 87
sequel 95
server 93
accessory 25
component 9 1
machine 25
programmer 52
session 75
session layer 77
shielded twisted pair 62
simple network management protocol (SNMP) 217, 219, 220
skill 12
small law office, example 37
Smalltalk 131
SNA 59, 72
software distribution 17, 24
software distribution tool 27
software maintenance cost 29
software testing tool 29
SPX 75-77
SQA:Robot 192, 193
SQL 95, 104, 144-147, 152
SQL Access Group 98
SQL Server 93, 108
SQLWindows 110, 111, 158, 159, 178
static SQL 104
stored procedure 106
stored procedures 144
stress testing 194
support 24
support group 30
support organization 32
Sybase 102, 103, 108, 144, 145, 147
synchronization 78
syncpoints 78
system size 15
systems administrator 53
systems management tool 27
T
technical architect 49
thinness 129
third generation language (3GL) 52, 115, 116, 160
thread 82, 84-87,
threads 82, 84
throughput 198
Tivoli Systems 221
token ring network 16, 63-65, 128
TP Monitor 89
traditional programmer 51
traffic pattern 1 G
training 24
transaction 15, 83, 144
transaction oriented system 13
transaction program 78
Transact-SQL 109, 144-147
Transmission Control Protocol/lnternet Protocol (TCP/IP) 70-72, 82, 92, 97
transport layer 69, 70
transport protocol 96
trigger 106, 109
two-phase commit protocol 14
U
Uniface 178
UNIX 71, 72, 81, 82, 93, 156, 179, 180, 221
unshielded twisted pair 62
update 95
user 17, 33
user interface/human factors consultant 51
utilization 198
V
vendor's alliance 43
vendor's support 45
Vines 91
virtual circuit 75
virtual LAN 16
virtual memory management 82, 87
Visual Basic 110
VMS 81, 82
VSAM 99
W
watchdog 76
wide area link 16
wide area network (WAN) 16, 58
Windows 86
Windows for Workgroups 92
wiring 25
word processing 38
workflow management 120
workflowsystem 120
workstation 88
X
XWindow 140, 141, 143, 177, 179
Xerox 91
DESCRIPTION
How to Deliver Client/Server Applications that Work focuses on the needs of a project leader or a technical architect who is responsible for turning the vision of the executive into a successful client/server system. Unlike other current books, which are either written for senior management responsible for strategy or for programmers who need low level programming details, this is a practical and concise, "how-to" guide and a roadmap for the process which will successfully deliver client/server applications. It leads the project leader through all the stages of the life cycle -- from conceptualization to system development and deployment. How to Deliver Client/Server Applications That Work offers practical, proven advice on the business and technical issues that a project leader must deal with effectively.Some highlights:
- covers entire system development life cycle
- presents various client/server models
- discusses organizational deployment issues
- provides cost/benefit analyses
- explains distributed systems technologies
- rich in practical pointers, checklists, etc.
- based on real-life experience
How to Deliver Client/Server Applications that Workis for technical architects, systems consultants, project leaders, chief programmers, technical managers, systems support managers, systems administrators, and all others working on client/server applications.