|
A | B
| C | D |
E | F | G
| H | I |
J | K | L
| M
N | O | P
| Q | R |
S | T | U
| V | W
A
Accounting Department, 80-81
Actual rating, 360-61, 405, 471, 472
Advertising agency, 5-6, 16-18, 24-30, 36-37,
40-44, 58-59, 69-70, 79-80, 84-86, 354ff., 431-37,
451-56, 486ff., 519-20
as an entity, 353-54, 355, 487-91, 523
CRUD check example, 523-24
in data dictionary, 405, 449
in event responses, 469, 473-75
new, 25, 42, 53-54, 371, 414, 438-39, 441-49,
485
in Piccadilly context diagram, 348-50, 355-56,
431-32
Advertising budget, 4-6, 36-37, 41-42, 365, 455-56
Advertising campaign, 5-6, 25, 41-42, 70, 451
as an entity, 22, 354-55, 363
in data dictionary, 365, 405
Advertising revenue, 16-18, 29, 40-41, 69, 80,
464-69
Agreed campaign, 349, 406, 435-36
Airline passenger check-in system, 188-89, 545-46
Airtime analysis, 5-6, 24-25, 407
report, 41
Airtime sales system, 7, 16-19, 24-28, 39-44,
45
context diagram for, 347-48, 431-32
implementation of, 79-88
Ale exercise, 233, 557-58
Algorithm:
in data dictionary, 228, 289
in mini specification, 283-84
ratecard, 468-69
Alias, 231, 582
Allocated event-response model, 78, 80-89, 94,
97, 314-15, 327, 330-31, 582
Analysis model, 7-9, 13-14, 33, 75, 91-94, 102,
105-14, 130-37, 582
See also Data dictionary; Data flow diagram;
Entity-relationship diagram; Event-response model
as estimating tool, 98-99, 328, 331
as management tool, 88, 95, 99-100, 328
as presentation tool, 100-101, 390
correctness criteria for, 75
reusing, 101
stand-alone, 70, 516, 519-20
top-down, 196, 204-5
Analysis strategy, 7-9, 11, 20-21, 65-66, 91-102,
278
detailed, 18-19, 21, 99, 351, 355, 364, 384,
519-20, 585
object-oriented systems and, 338-44
spiral development, 99
Animal file example, 161-64
Application class, 338, 342
Arango, G., 101, 575
Association, 151, 230, 293, 582
Asynchronous model, 123, 582
Attribute, 22, 34, 56, 66, 71, 93, 333, 582
CRUD check and, 72, 269-70, 277
in data dictionary, 37, 149, 366
of an entity, 37, 66, 146-50, 163-64, 354
foreign key and, 153-54
of a relationship, 151, 159-60, 163
stored, 527
Attribution, 157, 163-64, 365-66, 443
Audience measurement bureau, 5, 16, 28, 469-73
Audit, 259, 264
Author/book enquiry example, 292-94
Automatic cassette recording (ACR), 30, 82, 407,
475-76
Automobile policy example, 274, 275
Available technology, 77, 89, 96, 307ff.
top
B
Balancing, 31, 43, 201-6, 509
Diagram 0 and context, 32, 376, 391
exercise, 205-6, 552-53
rule, 201-5, 582
Banking system example, 134, 210, 212
Barbican Centre exercise, 171-73, 540-42
Batched data, 312, 327
Behavioral model, 88, 96, 321-22, 582
Blake Hall, 24, 40, 89, 516-18, 520
statement of, 69-70
Blitzing, 268
Boehm, B., 330, 576
Böhm, C., 106, 282-84
Booch, G., 96, 344, 576
Border guard edit, 260, 316-17
Bottom-up approach, 199-201, 205, 387-90
See also Leveled approach
Boundary data flow, 21, 45, 47, 65-66, 91, 123,
213-14, 228, 241, 339, 342, 452, 525, 547
data carriers and, 313
defined, 117, 582
in Diagram 0, 370
to find entities, 157-58
to identify events, 255-56, 354, 520
in implementation model, 327-28
Piccadilly's, 347-52, 354
tagged for event list, 50, 431-32
Break: See Commercial break
Breakchart, 25-28, 41, 61, 79, 83-85, 315, 435,
493-95, 504-7
in data dictionary, 408, 488, 495, 505
day, 360-61, 408
in Diagram 0, 369, 372
Breaksheet, 26
Break transmission schedule, 27, 30, 80, 409,
498
Bricklin, D., 236
British television industry, 4-6, 15-19, 51,
70, 369-70
Broadcasting Board, 4-6, 16, 26, 360, 362, 434,
513
Broadcasting rule, 26, 363, 409, 513-14
Broad rate, 17, 36, 40, 385, 469
Bubble, 18, 107-8, 116, 583
See also Process
numbering system of, 197, 442
Budget (agency), 5-6, 37, 41-42, 365, 455-56
Business policy, 22, 76, 135, 143, 152, 180-81,
211, 216, 235-43, 255, 351, 449, 583
data model and, 145-64, 353, 363, 518
of Mallard Travel system, 164-70
Piccadilly, 22, 30-32, 40-43, 56, 91-94, 137,
351, 354, 363-64, 365, 375
top
C
Calculations, defining, 228
specifying, 197, 281, 283-87, 289-90
Campaign requirements, 16, 22, 25, 41-42, 61,
79, 83, 85-86, 348-50, 435, 454-62
as an entity, 354, 365
in data dictionary, 365, 410, 454, 488
Capacity factor, 314, 329-30
Cardinality, 267, 583
in data dictionary, 225, 366, 385
in data model, 22, 154-56, 357-58
CASE tool, 13, 34, 100, 268, 527, 583
for cost estimation, 328
for data flow diagram drawing, 185-86, 548
Cavemen's hunting system, 107-12, 531-32
Chen, P., 338, 576
Chen diagram, 20, 146
See also Data model
Child diagram, 39, 195-207, 387-93, 552-54, 583
exercises, 205-7, 552-54
Class, 96, 336-43
Client-server architecture, 312
Cloning objects from classes, 336
Comment:
in data dictionary, 226, 227, 229-30, 365,
394-95
in data flow diagram, 43-44
Commercial Booking Department, 24, 25-28, 30,
41-43, 79-83, 89, 372-74, 434, 492, 493-94, 498,
513
Diagram 0 of, 369, 391, 397
Diagram 4 of, 402
Commercial break, 6, 16-17, 25-30, 35-37, 40,
79-80, 471
in data dictionary, 411
in data model, 354-55, 360-64
viewer response, 517-19
Commercial copy, 18, 30, 349, 481-84
in data dictionary, 411
in data model, 363-64, 474-75
Commercial spot, 16-18, 25, 36-37, 79-80, 315,
360, 435-37
See also Preemption
administrator, 25-28
as an entity, 353-55, 492
cancellation, 42, 390, 426, 487-91
in context diagram, 348, 349, 355-57
in data dictionary, 411
in data model, 363-64
displaced, 27, 412, 436, 497
duration, 25-27, 365, 380-81, 426
moveability, 17, 26-27, 36-37, 61, 379, 384,
494, 495
price, 17, 18, 28, 61, 380-81, 427, 455-56,
493-95
rate, 384-85, 464-69
slotting, 27, 495-97
sticker, 27, 427, 494
transmission time, 17, 18, 28, 29-30, 427,
498-501
upgrade, 18, 25, 42, 436, 491-93
Communication skills, 102, 187, 209, 268, 322
Complexity:
of business descriptions, 51
of data flow, 65-66, 456
of design, 78
of essential activity, 62-63
of event, 65-66
Composite data flow, 201-3
Composite data store, 203-4
Composite identifier, 229, 405
Computer Department, 18, 24, 25, 29, 42, 439
Diagram 0 of, 369, 391, 397
Diagram 1 of, 398
Computer technology, 46, 76-77, 133, 135, 237-40,
307-31
capacity and, 329-30
context diagram and, 124-25
current, 77, 209-19, 236-37
design path and, 343-44
Piccadilly's, 4, 18-19, 29, 31, 81-89, 94-96
Context diagram, 16, 18-19, 20-22, 91-94, 100,
213-19, 243
as input to data model, 21, 157, 164-70, 214-16,
354-56, 361-64
as input to event list, 50-51, 250-52, 276-77,
431-34
balancing, 30-32, 376, 390-93
for Clearing House, 189-90, 536-38
defined, 123, 583
for employment agency, 124
for hotel room exercise, 553
in leveled set, 194-95
for Morey Saint-Denis system, 549
new requirements and, 69-71, 74, 351
numbered for event list, 432-34
Piccadilly's, 7, 16, 19, 20-22, 30-31, 34,
45-46, 137, 339-42, 347-52, 361-64, 375
Piccadilly's updated, 369-71, 392, 396
for Regional Theater Casting system, 214
for taxi system, 247
Context of event response, 56, 65-68, 438-40,
451-58
Context of study, 18-19, 45-46, 65-66, 75-76,
81, 583
changing, 70, 92, 304, 350-51
CRUD check and, 75, 269-70, 525-26
data dictionary definitions and, 222-23, 227
Diagram 0 and, 45
identifying, 91-92, 98-99, 135, 193-95, 213-16,
348-49
new requirements and, 70, 77, 93, 299-305
in object-oriented environment, 340-44
Piccadilly's, 347-49, 374-75
stored data in, 20-21
users' agreement of, 17, 123, 213, 348-49
verifying, 31, 75, 93, 215-16, 370-71, 525-26
Continuous data element, 227
Continuous processing, 439, 451
Contract workers pay system, 281-89
Control flow, 325, 545
Controlling complexity, 65-66, 193-207, 389-90
Control structure, 123, 179
Copy disposal instructions, 30, 412, 477
Copy transmission instructions, 30
in context diagram, 349, 360-61
in data dictionary, 412
in event response, 473-75
Cost factor, 309-11, 314
Create operator, 56, 63, 72-73, 170, 444, 448-49
in CRUD table, 72-73, 521-23, 525
Credit card example, 301-3
Cross references, 88
in CRUD table, 526
in mini specification, 275, 284
CRUD check, 56, 72-73, 75, 93, 269-70, 275-77,
444, 448, 464, 521-27, 583
of context, 75, 269-70, 525-26
CRUD operator, 56, 63, 471-72, 490-92, 503, 512
CRUD table, for Piccadilly, 72-73, 521-24
Current physical model, 40-43, 45-46, 49-51,
77, 92-93, 209-19, 242-43, 245-47, 369-76
abbreviated, 269
as input to essential model, 254-55, 259-60,
277
of banking system, 134, 210-11
defined, 209, 583
of dental system, 265
numbering in, 431-33
Piccadilly's, 39-43, 45-47, 49-51, 53-54, 61-63,
92-93, 339-40, 431-34, 438-39
Piccadilly's complete, 394-430
of Piccadilly's organization, 23-24, 30-31,
369-76, 392, 396
for Sales Department, 388, 400, 434
time to build, 374
Current physical viewpoint, 39, 134-35, 209-19,
393
Current system, 7-8, 209-19, 223
environment, 308ff.
implementation, 46-47, 55, 77-78, 134-35, 161,
200, 210-11, 393, 394, 441-42
Piccadilly's, 16-18, 23-31, 40-43, 46, 369-76,
396, 463-515
Custodial activity, 269, 584
Sid Edison radio example, 569-71
Custodial processing, 73, 584
top
D
Dagenham Heathway, 24, 28, 372-74
Data:
names, 231
physical description of, 223, 231, 315, 326-27
redundant, 56, 73, 93, 287
viewpoint, 20-22, 45-47, 123, 135-36
Database:
designer, 76, 230, 330
management system, 76, 85, 154, 181-82
Piccadilly's, 441
Data carrier, 78, 80-88, 95, 96, 313-16
Data Conservation, Rule of, 116, 124, 176, 188,
278, 545
Data container, 78, 96, 148, 313, 330
Data dictionary, 9, 11, 13, 34, 35, 37, 46, 56,
58, 63, 116, 117, 221-34, 278-81, 584
balancing and, 202-3
Barbican Centre example, 541
continuous vs. discrete values in, 227
CRUD check and, 73
current physical model and, 100
data model and, 145-46
defining algorithms in, 228, 289
defining attributes in, 34, 56, 148, 366, 383
defining data flows in, 34, 56, 62, 66, 75,
93, 94-96, 220-30, 231-32, 315
defining entities in, 37, 66, 93, 228-30, 365-66,
383
defining relationships, 228-30, 384-85
design and implementation details in, 95-96,
309, 315, 327-28, 330
employment agency example, 533-34
exercises, 232-34, 555-60
Hopper's Choppers, 296
mini specification and, 58-59, 447
names in, 378-79
new programme exercise, 34-35, 377-79
new requirements and, 70, 75, 516-20
notation, 34, 162, 224-26, 229-30, 365-66,
378, 380, 393
operators in, 224-26
pay contract workers system, 281-82
physical description in, 223, 231, 315, 326-27
for Piccadilly, 7, 33-37, 54, 91-94
Piccadilly's complete, 405-30
precedence rules in, 378-79
redundant, 56, 73, 93
underlining in, 168, 229
Data element:
as attribute, 37, 66, 147-50, 158-60, 162,
366
in boundary data flow, 66, 354
in class or class hierarchy, 336-38
continuous vs. discrete, 227
CRUD check and, 73, 526-27
in data dictionary, 35, 62-63, 93, 118, 220,
226, 227, 366, 380
in data flow, 34, 117-18, 197-98
encapsulating, 333-36, 344
primitive, 226, 227
stored, 37
Data flow, 584
See also Boundary data flow
allocating to data carrier, 83-84, 313-15
complexity of, 66
components of, 179, 193-95, 204-5
composite, 179, 203
composition in data dictionary, 34, 56, 62,
66, 75, 93, 221-22, 224-29, 315
crossing, 186
events and, 276-77, 431-34
external, 202, 350
incoming/outgoing, 50, 62, 98, 108, 110, 113-23,
248, 250-58, 294
internal, 350, 434
naming, 119, 178-79, 210, 220, 351, 372, 537
physical characteristics of, 95-96
in transaction synchronization model, 324-25
triggering, 65, 177, 249-50, 315, 439, 454,
527
unnamed, 179-80, 456-57, 552
Data flow diagram, 9, 113-29, 174-92, 322-24,
584
See also Leveling; Process model; System environment
model
as a presentation tool, 387ff.
as a working model, 115-20
balancing, 31, 43, 201ff.
current physical, 30-31, 280
drawing rules, 185-87
exercises, 126-29, 187-91, 205-7, 531-32, 533-38,
544-50, 552-54
leveled, 45, 109-10, 121ff., 193-208, 216ff.,
275-76, 387-93
of Piccadilly organization, 30-31
of Sales Department, 44, 387-92
Data model, 7, 20-22, 46, 135, 145-73, 339, 385-86,
584
See also Entity; Event-response data model;
Relationship; Stored data
of banking system, 134-36
of Barbican Centre exercise, 540-42
cardinality in, 22, 154-56, 357-64
first-cut, 91-94, 100, 170, 367, 381-82, 405
new requirements and, 517-18
Piccadilly's, 34, 46-47, 70, 73, 137
Piccadilly's first-cut (preliminary), 21-22,
30-31, 62, 91-94, 100, 214-15, 340, 353, 364,
366-67, 373, 385
Piccadilly's system, 93, 514
Piccadilly's updated, 371, 381-84, 405
Data storage and retrieval, 180-82, 392
duplicated, 443-45
specifying, 142-43, 291-94
Data store, 65-66, 115-16, 118-21, 142-43, 145-46,
180-82, 217, 237, 532
See also Stored data
allocating to data container, 84-87, 315
balancing, 203-4
in data dictionary, 220, 224, 228-30, 233,
315
defined, 120, 584
event response and, 438-39
false, 260-61, 587
notation, 115, 120
physical, 53, 63, 325, 451-52
in transaction synchronization model, 326-27
unnamed data flows and, 179-80, 456-57
Decision table, 287-90, 294, 585
for Hopper's Choppers, 572
Decision tree, 290, 294, 585
Decomposition, 32, 63, 76, 142, 226, 279
See also Leveling; Partitioning
Delete operator, 56, 63, 72-73, 170, 521-27
in CRUD table, 72-73, 521-27
DeMarco, T., 100, 183, 328, 576-77
Design, 585
activity, 75-78, 307-31
constraints, 77-78, 94-98
implementation of, 80-89
path, 97-98, 342-44
tasks in implementation model, 76-78, 88-89,
94-96, 327-28
template, 321, 343
Design strategy, 76-78, 80-89, 94-98
detailed, 76-78, 96-98, 322-25, 585
external vs. internal, 76, 81-85, 94-96, 307-9,
317-18, 587, 588
for object-oriented environment, 96, 332ff.,
343
preliminary, 76-78, 79ff., 94-96, 137, 589
spiral development, 99
Diagram 0, 195, 196, 200-201, 216, 217
balancing, 201ff., 370-71
for Clearing House, 547
exercises, 205-7
Piccadilly's, 32, 43-44, 45, 369ff., 391, 397
top
E
Employment agency system, 115-27, 326, 533-35
Encapsulation, 333, 339, 342, 344
Entity, 22, 32, 34, 62-63, 145-64, 220, 241-42,
339, 365-66, 585
in data dictionary, 66, 93, 220, 228-32, 365-66,
383-84
rules of thumb to find, 150-60
Entity-relationship approach, 338
Entity-relationship diagram, 9, 146
See also Data model
Essence, 137, 211, 218, 237-39, 305, 441, 461,
585
Essential activity, 58ff., 268-69, 280, 458-61
Essential analysis, 218, 338, 586
Essential data, 93, 211, 241, 255-59, 279, 444-45
allocating, 80, 84-87
stores, 46, 56, 62, 84-85, 240-42, 308, 443-45
Essential data flow, allocating, 85-87, 313-15
Essential event-response data model, 47, 59,
268, 278, 294, 441-42, 448-49, 458-59
Essential event-response process model, 47, 59,
64, 84, 268, 278, 294, 442, 456, 458
Essential model, 45ff., 65-66, 92, 218, 242,
254ff., 276
See also Essential requirements model
Essential requirements, 7, 45-48, 49-52, 66,
75, 143, 180, 218, 235-43, 245-48, 259-60, 280,
464ff., 515, 580
design and implementation of, 76-78, 80-90,
94-98, 307-31
Essential requirements model, 45-47, 69ff., 91-94,
137, 245-48, 309-10, 404, 449, 586
Essential stored data, 443ff.
specifying, 84ff., 291-94
Essential viewpoint, 7-8, 46-47, 62-63, 75-76,
135, 235-44, 586
Estimation technique, 98-99, 328-31
Event, 246-77, 431ff., 586
external, 49-51, 65, 248-54, 277, 431ff., 586
missing, 56, 72, 93, 269, 523-26
model, allocated, 80-89, 94-98, 314-15, 327-31,
582
naming, 49-52, 65, 246-47, 431-37
partitioning, 49-50, 65-66, 78, 93, 248-77,
314, 366-67, 386, 434, 586
temporal, 50, 65, 249-52, 264, 276, 434, 501-11,
518
Event list, 49-52, 251-52, 433, 563, 586
Piccadilly's, 49-52, 60, 67, 71, 74, 93, 433
Event response:
allocating, 83-90, 314
CRUD check and, 56, 72-73, 521-27
defined, 248, 586
for Piccadilly, 53ff., 60ff., 70, 93-94, 431-37,
438ff., 451-62, 463-69
Event-response data model, 55-56, 65-66, 75,
93-94, 257ff., 294, 367, 457, 586
Event-response model, 8, 47, 53-54, 245-77, 278,
515, 587
allocated, 78, 81-90, 94, 96, 314-15, 327,
330, 582
exercises, 265-70, 561-71
mini specification and, 58-59, 63
for new requirements, 70, 301-5, 516-20
notation in, 271-74
numbering, 438, 442, 456
Piccadilly's, 53-54, 65-66, 93-94, 339, 385-86
refining, 55-57, 62-63, 257-64, 441-45, 453-57,
461-62, 464ff.
Event-response process model, 21, 55, 66, 92-93,
254-56, 280, 293, 587
Piccadilly's, 53, 75, 92-94
top
F
False data store, 260-61, 498, 587
Flavin, M., 338, 577
Flight reservation system, 323-25
Foreign key, 153-54, 241, 587
Frankston, R., 236
Functional component, 110-11, 123-25, 142, 278
Functional primitive, 75, 197-201, 243, 587
specifying, 279-81
Functional process, 183-84, 199, 389-90
Fundamental activity, 50, 269, 434, 587
Fundamental processing, 587
top
G
Government Research Paper Clearing House, 128-29,
189-90, 536-38, 547-48
Grouping processes, 43, 388, 389-90
top
H
Hayakawa, S., 223
Head-sized piece, 109, 121, 367, 587
High-level diagram, 193ff., 388, 389-90
top
I
Identifiers:
composite, 229, 405
unique, 229, 405, 474
Implementation, 75-78, 230, 587
constraints, 76-78, 94-96, 307-31
of data, 223-24, 230, 326-27
of essential requirements, 134-35, 307-31
model, 76-78, 80-81, 88, 94-96, 307-9, 315-16,
588
of Piccadilly system, 79-89, 94-96
Implementation-dependent processes and data,
54, 55, 62, 66, 223, 230, 280, 441-45, 461
Implementation process, 441-42, 445-46
Information model, 20, 146
See also Data model
Inheritance, 336-38
Input data, 215, 220-21
in data dictionary, 230-31, 278
Instance, 588
of an entity, 22, 146-50, 157
of an object, 333
Interface, 110-11, 183-84, 199-200, 349, 588
in implementation model, 78, 94, 327, 330
messy, 216-17
minimizing, 199-201, 275, 389-90, 434
process notation, 324
simulated automated, 86, 322
specified in data dictionary, 310
technological, 86-87, 309-13
user, 76, 82-83, 320-21
Internal design, 76-78, 83-85, 94-96, 307ff.,
588
Interprocessor interface, 87, 94-95, 315, 330
top
J
Jacobson, I., 344, 578
Jacopini, 106, 282-84, 576
Judgmental process, 184-85, 290-91, 311, 549
top
K
Key field, 168, 588
Kitchen design example, 318-19
top
L
Leveling:
defined, 121, 588
downward, 43, 63, 194-98, 216, 279, 375, 459
exercises, 205-7, 552-54
upward, 43, 199-201, 275, 388, 389-90, 459
Lister, T., 577, 583
Lower-level diagram, 7, 39, 194-207, 217-18,
372, 552-54
See also Child diagram
Piccadilly's, 370, 388, 389-90, 397-403, 431
top
M
Mallard Travel system, 164-70
Many-to-many relationship, 155, 160
in Piccadilly data model, 357ff.
Map, 113-14, 130-32, 194, 320
McMenamin, S., 66, 268, 269, 338, 578
Mellor, S., 96, 344, 579, 580
Message, flow, 96, 334-36, 340-42
Meyer, B., 96, 578
Miller, G., 196, 578
Mini specification, 8, 11, 58-59, 63, 66, 93,
109, 116, 121, 183, 184-85, 217, 269, 279-97,
463ff., 532
briefer form of, 448-49
calculations and, 228
composite identifiers in, 405
cross referencing in, 275, 284
CRUD check and, 73, 151, 448-49
data dictionary and, 58, 448
exercises, 294, 295-97, 573-74
functional primitive and, 75, 197-98
Piccadilly's, 58-59, 63, 93, 447-50, 451, 459-61,
463, 467ff.
Miss Tweedy's Dating Service, 174-86, 290-91
MOe & LARry Dental system, 250-52, 255, 257-59,
261-68, 270
exercise, 265-66, 561-62
Morey Saint-Denis system, 191, 549-50
Moveability, spot, 17, 18, 27, 28, 36-37, 61,
379-80, 414
Myers, G., 96, 579
top
N
Naming conventions:
for data flows, 118-19, 178-79, 210, 220, 351,
375, 537
for events, 50, 65, 247, 372, 431-37
for processes, 183, 389
for terminators, 537
NanoSoft Corporation, 138-42
Nelson Buzzcott Employment Agency, 115-27, 326
exercise, 126-27, 533-35
New implementation environment, 77, 79-89, 136
New physical model, 78, 79-89, 136, 137, 305,
307-31, 589
New physical viewpoint, 8, 136, 307-31
Notation:
in data dictionary, 37, 162, 224-26, 229, 231,
232, 365-66, 378-79, 380, 393
in data flow diagram, 115-17, 181, 185, 291
in data model, 148
in mini specification, 281ff.
top
O
Object, 332-44, 589
Object-oriented design, 96, 332-44, 589
One-to-many relationship, 155, 160, 167
in Piccadilly data model, 357-62
One-to-one relationship, 155, 160, 357ff.
Output data, 215, 220
defined in data dictionary, 231, 278
top
P
Page-Jones, M., 96, 579
Palmer, J., 66, 268, 269, 338, 342, 578
Parent bubble, 43, 196-97, 201, 202-4
exercise, 206-7, 553
Parent diagram, 195, 197, 202-7, 393, 589
balancing, 43, 201-3
numbering, 195-97
Participation, 170-71, 366, 589
Partitioning, 31, 43-44, 45, 145-46, 183, 216-17
allocation, implementation and, 96, 314-15
into data flows, 125, 142
defined, 199, 589
into entities and relationships, 146, 156-60
into event responses, 49-50, 66, 78, 99, 248-77,
314-15
exercise, 207, 554
functional, 93, 109, 110-11, 183-84, 199-201,
207, 216, 279, 547, 587
logical, 199, 216-17
at narrowest interface, 110-11, 183, 199
Perry Vale, 24, 29-30, 34-35, 371, 377-79, 434
Physical data, 53, 56, 62-63, 280, 443-45, 451ff.
in event-response model, 259-60
implementation of, 223, 230
Physical file, 62-63, 445, 451-52, 457, 465ff.
Physical modeling, 7, 39-40, 209-19, 242, 268,
280
for events, 53-54, 56, 62-63, 431-37, 438-40,
441-42, 451ff.
Physical process, 281, 294
in event-response model, 53-54, 56, 62-63,
259-60, 436, 438ff., 451-57, 464ff.
Physical processor: See Processor
Physical requirements, 315-16
Physical viewpoint, 7-8, 374
See also Current physical; New physical
Piccadilly Television, 4-8, 16-19, 23-31, 39-44,
45-46, 369-76
context diagram of, 7, 16, 18, 20-22, 30-31,
34, 137, 339, 347-52, 363, 370, 376, 392, 396
current physical models of, 23ff., 39ff., 45-47,
49-51, 394-430
data model of, 21-22, 30, 34, 37, 46-47, 49,
70-71, 74, 137
Diagram 0 of, 32, 43-44, 45, 369, 390, 391,
394, 397
system data model of, 56, 93, 266-68, 277,
457-58, 514, 591
updated data model, 371-72, 373, 381-82, 404
Pointer, 241, 310, 311
Policy statement:
of Blake Hall, 69-70
to build data model, 171
of Dollis Hill, 61-62
of duck race, 150-53
of pay contract workers system, 281-82
of Piccadilly, 16-18, 23-32
of Stamford Brook, 40-43, 58-59, 79-80
Predicted rating, 42-43, 61, 79, 469-73, 511-12
in data dictionary, 417
in data model, 360-61
Preemption, 6, 18, 25-27, 37, 42
replacement, 42, 390, 435-37, 417
warning, 18, 25, 42, 349, 417, 504-6
Preliminary data model: See Data model
Preliminary design, 76-78, 80-81, 94-96, 589
model, 136
Primitive data element, 227-30
Private stored data, 63, 493
Process, 18-19, 108, 115-25, 142, 220, 231, 590
allocating to processors, 314-15
as functional primitive, 75, 99, 197-98, 243,
278, 279-81, 587
as part of a class or object, 332-44
complexity and, 193-97, 389-93
duplicate, 370, 464-67, 493-95
functional, 183-84, 389-90
grouping, 198-201, 387-90
judgmental, 184-85, 290-91, 311, 549-50
mini specification and, 115-16, 278ff.
naming, 183-85, 389
numbering of, 197, 442
Rule of Data Conservation and, 116, 124, 175,
176, 188-89, 278, 455, 545, 590
specifying, 278-97, 590
in transaction synchronization model, 324-25
Process model, 6-8, 20-22, 156, 176-77, 182-85,
290-91, 339-40, 366-67, 541-42, 590
See also Event-response process model
Processor, 77, 80-81, 94-96, 245-46, 248, 259-60,
309, 310-31, 590
allocation and, 78, 81-84, 313-15
client-server architecture, 312
model partitioning and, 81-83, 199-201, 245-46
Programme supplier, 4-6, 16, 29, 34-35, 82
in data dictionary, 377-79, 381, 383, 420
in data model, 359, 382
Programme Transmission Department, 18, 24, 27,
29-30, 34-35, 79-83, 369, 371-74, 434, 476, 478,
481, 483, 513
Diagram 0 of, 369, 391, 397
Diagram 5 of, 403
Programme transmission schedule, 16, 25, 26,
29, 42, 61, 360-61, 371-72, 373, 432-34, 507-10
in data dictionary, 420, 507
Programming language, 29, 76, 96-97, 282, 309,
324
object-oriented, 332-33, 343
Programming plan, 29-30, 420
Programming rules, 4, 6, 16-18, 25, 28, 29-30,
420-21, 513-14
in data dictionary, 421
in data model, 361-63
Project estimate, 93, 98-99, 328-30
Project plan, 93, 100-101, 305, 331
Project scope, 6-7, 18-19, 20-22, 30, 117, 123-25,
213-16
Piccadilly's, 30, 91-94, 137, 347-52, 396
Prototype, 78, 86, 308, 315, 326, 330, 590
automated, 86, 96, 322, 330
top
Q
Question mark notation, 21, 31, 536
in data dictionary, 37, 377-78, 379-80, 381,
405
top
R
Ratecard, 17-18, 25, 28, 35-36, 40-42, 61, 350,
361, 374
in data dictionary, 37, 379-80, 384, 421
in event responses, 464-67
Ratings: See Television ratings
Reference operator, 56, 63, 73, 170, 444, 448-49,
521ff.
Relationship, 21-22, 32, 34, 56, 62, 66, 71,
146, 150-71, 220, 240-42, 590
attributes and, 151-52, 158-60, 364, 366
CRUD check and, 56, 63, 73, 170, 521-27
in data dictionary, 66, 93, 220, 228-32, 365-66
naming, 152, 159, 367
rules of thumb to find, 150-53, 159-60, 355-57
specifying in structured language, 292-94
Repartitioning, 199-201
into event responses, 50
exercise, 207, 554
Repeating group, 162, 224, 229, 380, 590
Repetition construct, 106, 282-84, 590
Requirements, 69ff., 123, 136, 299ff., 307-9
See also Essential requirements
analysis, 101, 123, 307-9, 328
current physical and, 209-19
data dictionary and, 230
integrating, 70, 519-20
missed, 93, 455, 525
model, 8, 45-47, 70, 72-73, 136, 245ff., 405,
449
new, 7-8, 69-71, 75, 93, 101, 210-12, 299-305,
350, 516-20, 589
specification, 13, 93-94
Research Department, 24, 28, 30, 79-80, 372,
434, 471
Diagram 0 of, 369, 391, 397
Diagram 2 of, 399
Reusability:
of analysis components, 101
of design components, 88, 315, 321-22
object-oriented approach and, 338-44
templates and, 92, 321, 329
Reviews, project, 99-101
Risk management, 330, 590
Rule of Data Conservation, 116, 124, 175, 176,
188, 278, 455, 545, 590
Rules of thumb:
for estimating length of analysis, 98-99
for event-response processing, 431-37, 451
for finding entities, 156-58, 353-54
for finding relationships, 151-52, 159-60,
355-56
for grouping processes, 389
for naming events, 49-52
for naming relationships, 152
for repeating group, 231
for size of context of study, 124
Rumbaugh, J., 96, 344, 579
top
S
Sales Department, 24-25, 30, 40-44, 58-59, 79-80,
342, 372, 387-91, 434, 439, 441, 466, 493
Diagram 0 of, 369, 391, 397
Diagram 3 of, 45, 388, 389, 400
lower-level data flow diagrams of, 390, 391,
401
Sales policy, 40-43, 387, 464-66
Sales target, 16, 24-30, 40, 464-67
in data dictionary, 424
Scope, project: See Project scope
Selection construct, 106, 225, 284
Sequence construct, 282, 325
Shlaer, S., 96, 344, 579, 580
Single processor, 96, 466
Specification, 108-10, 114, 115, 125, 174-75,
193-95, 204, 211, 279-82
See also Mini specification
completeness of, 75, 279, 367, 524-27
of data storage and retrieval, 161-63, 291-94
techniques, 278-94
of technology, 307-13
Spiral development strategy, 99
Spot: See Commercial spot
Stevens, W., 96, 580
Stored data, 7, 20, 37, 93, 137, 142-43, 145-73,
214, 308, 390-92
common usage of, 275-77, 390
CRUD check and, 72, 525-27
in data dictionary, 228-31
in event-response model, 62, 73, 386, 443-45
modeling, 115-16, 145-63, 255-59, 390-93
private, 63
specifying, 161-63, 291-94
Structure chart, 96
Structured analyst, 338
Structured design, 106
Structured language, 282-87, 447-48
for author/book enquiry system, 291-94
for data storage and retrieval, 291-92
for Terry's Ski Tuning Service, 573
Structured programming, 106, 282
Subtype, 160-61, 591
of RATING, 360-61, 471
Supertype, 160-61, 471, 591
System boundaries, 7, 18-19, 45, 123-25, 213-16,
329
See also Boundary data flow
System context: See Context diagram; Context
of study
System environment model, 77, 80-88, 309-11,
317, 330-31, 591
Piccadilly's, 81-85, 94
See also Data model; Data store
System policy:
See Business policy; Essential policy
for Piccadilly Television, 14-17, 20
System response, 53-54, 62-63, 93, 245-77, 431-37,
438-46, 451-52, 464-69
grouping, 279
Systems analysis, 8-14, 202-4, 211, 278, 338
defined, 130, 591
filtering information and, 132, 133-36, 193ff.
tasks, 6-8, 30-31, 70, 145-46, 354
top-down, 65, 110, 199, 204, 386, 459
Systems design: See Design
top
T
Taxi system example, 246-50, 253, 260-61
Techn-O-Filter, 242, 442
Television industry:
See British television industry
Television ratings report, 28, 351, 374, 469-73
in data dictionary, 428
Temporal event, 65, 249-54, 264, 277, 501-10
naming, 50, 434
response, 65, 254-59
viewer response report example, 517-19
Terminating data store, 181, 545
Terminator, 47, 65, 116-20, 121, 122-25
as entity, 157
as time-delaying mechanism, 248
defined, 116, 592
events and, 50, 248, 249-50, 439-40, 452-53
in implementation model, 81-83, 85-87, 327-28
naming, 537
notation for, 117
in Piccadilly context diagram, 348-49, 350
Terry's Ski Tuning Service, 296-97, 573-74
Top-down approach, 45-46, 65-66, 108-10, 194-96,
199, 204, 459, 592
Trail Guide, 10-14, 611-12
Transaction, 76, 95, 266, 316, 327, 329
Transaction synchronization model, 86, 96, 97,
308, 315, 321-27, 330, 592
Trivial reject, 182-83, 547-48, 592
top
U
Update operator, 56, 63, 170
in CRUD table, 72-73, 521-23, 527
User:
-analyst relationship, 31, 211, 212-18, 307-9,
349, 372-74, 461
communication with, 43, 91, 174, 187, 209-19,
268-69, 321-22
context and, 19, 122, 213-16, 348-50
current physical viewpoint and, 134-35, 209-19,
370-71, 375-76
data model and, 158, 354
Diagram 0 and, 216-18, 370-71, 375-76
interface, 51, 93-94
new requirements and, 299ff.
raising questions with, 12, 21, 31, 40, 44,
350, 354, 464, 518
recording interviews with, 43-44, 101-2, 186-87,
204-5, 212-15, 372-74, 387
role of, 21, 31, 43-44, 51, 91-94, 204, 218,
348-49, 350, 370
in systems design, 76, 307ff.
User-oriented viewpoint, 83, 210-19, 307ff.
top
V
Viewer response example, 69-70, 516-20
Viewpoint, 7-10, 83, 100-102, 130-37, 592
See also Current physical viewpoint; Data viewpoint;
Essential viewpoint; External viewpoint; New
physical viewpoint
top
W
Warren Street, 24, 29
Waterfall model, 78, 592
Woolly Mammoths example, 107-12, 531-32
Working model, 107-11, 220-21, 278, 592
data flow diagram as, 115-24, 174-76
A | B | C
| D | E |
F | G | H
| I | J |
K | L | M
N | O | P
| Q | R |
S | T | U
| V | W
Return to
Book Page
|
