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