| A | B | C | D | E | F | G | H | I | J | L | M
N
| O | P | Q | R
| S | T | U | V
| W| Y
A abstract interface module 261, 263-66 abstraction/detailing
65-66, 67, 92, 233, 272, 274, 402 ACD See architecture context diagram Ada-based
Design Approach for Real-Time Systems (ADARTS) 255, 402 AFCD See architecture
flow context diagram afd See architecture flow diagram aggregation
272, 402 aggregation/decomposition 64-65, 92, 93, 96, 99, 103, 106, 123,
233, 257, 258, 402 rules and guidelines 123 AICD
See architecture interconnect context diagram AID See architecture interconnect
diagram aircraft example 193, 194 AIS See architecture interconnect
specification AMCD See architecture message context diagram AMD See
architecture message diagram AMS See architecture module specification architect
200-204, 273, 402 architecture 226, 268-73, 348, 393, 403
channel 204, 357, 393, 403 communication model 92-103, 403 context
286-87, 346 context level 206, 222 diagram 90-92, 107, 227, 403 inheritance
model 106-8 interface 343 level 393, 400 method 4, 7, 64, 179,
190-99, 200, 205, 244, 245, 250, 253, 257, 273, 275, 389, 391, 396, 398, 400,
404 structure 274 architecture context diagram (ACD)
75, 215, 222, 284, 288, 341-43, 391, 392, 403 architecture dictionary (AD)
75, 80, 92, 108-10, 111-12, 177, 197, 233, 362, 376, 385-86, 388, 403
rules and guidelines 110 architecture flow 79-82, 83, 84,
88, 94, 177, 206, 222, 223, 229, 239, 249, 250, 357, 362, 373, 383, 388, 393-94,
403 rules and guidelines 110 architecture
flow context diagram (AFCD) 75, 87, 88-89, 171-72, 222, 223, 224, 284-85, 288,
241-42, 392, 403 rules and guidelines 88-89 architecture
flow diagram (AFD) 76, 91, 92, 94-96, 97, 98, 103, 108, 110, 111, 172, 174, 228,
229-30, 238ff., 247, 248, 254, 255, 258, 348, 363, 373, 376-77, 380, 381, 393
rules and guidelines 95-96 architecture inheritance model
403 architecture interconnect 86-87, 240, 249, 250, 362, 393, 403
rules and guidelines 87 architecture interconnect context
diagram (AICD) 75, 87, 88-90, 171, 223, 225, 288, 341-43, 382, 392, 403 architecture
interconnect diagram (AID) 76, 103, 104-6, 110, 111, 229-30, 238ff., 245-46, 247,
248, 258, 288, 290, 362, 363, 373-74, 376, 378, 381, 391-92, 403
rules and guidelines 105-6 architecture interconnect specification
(AIS) 76, 106, 111, 239, 250, 382, 388, 395, 403 rules and
guidelines 106 Architecture Level 1 Model 220-23, 224-27, 228,
229, 233 architecture message context diagram (AMCD) 75, 87, 89, 403 architecture
message diagram (AMD) 76, 89, 91-92, 97-98, 99-100, 103, 110, 111, 403
balancing 111-12 hierarchy style 99-100 network style 97-98 architecture
model 64, 69, 72, 74-112, 135, 136, 141, 142, 164, 167, 169, 170, 177, 180, 190,
192, 194, 197, 200, 206, 209, 224-27, 230, 233-34, 257ff., 274, 276, 277, 288-89,
304, 311, 315, 316, 318, 334, 387-88, 391, 396, 398ff., 404 allocation
of 224-27 balancing 110-12 development 233 requirements model
and 170-78 architecture module 76, 77ff., 81, 83, 85, 88, 92,
94ff., 103ff., 108, 112, 138, 172, 174ff., 192, 194, 196, 198, 224ff., 230, 233,
236, 247, 250, 254, 256-57, 259-61, 264, 267-68, 271, 274, 290, 315, 345, 347ff.,
352, 357, 362, 366, 377, 382, 387-88, 390, 395, 404 concurrent
376 rules and guidelines 78 architecture module specification
(AMS) 76, 92, 101-2, 106, 110, 111-12, 126, 198, 212, 230, 250, 252, 303, 375,
378-82, 388, 395, 404 rules and guidelines 101-2 architecture
template 53-54, 88, 97, 99, 166-69, 171-72, 198, 220-21, 224, 228, 257, 259, 261,
275, 276, 291-95, 331, 393, 394, 404 customer specification
293 hardware/software 292 hardware specification 295 rules and
guidelines 168-69 software specification 295 system integration 293 system
specification 295 variations on 291-95 assembly/subassembly/component
193 associative entity class 123-25 attributes and 123-25 rules
and guidelines 125 attribute 116, 123-25, 162, 164, 233, 267,
308, 404 associative entity classes and 123-25 rules
and guidelines 116 automated tool 8, 183, 200, 212, 397, 404 Axiom/Sys
404, 423 top B
balancing 177-78, 404 black box 186, 226, 244, 315, 404 Boehm,
Barry W. 184, 419 Booch, Grady 85, 119, 178, 180, 256, 419, 421 Brooks,
Frederick P., Jr. 256, 419 bubtangle 78, 404 buffer 221, 263
input and output 266 output-processing 221 support 262 user
interface 221 top
C capability 315, 404 Capability Maturity
Model (CMM) 181, 404, 420 cardinality See multiplicity CASE 3, 4,
164, 183, 254, 352, 389, 396, 399, 405 case study 6, 7, 8, 171, 180 CCD
See control context diagram CFD See control flow diagram channel 76,
198, 288, 342, 349, 362, 381, 405 Chen, Peter 118, 419 child 405
diagram 65, 96, 98, 105, 138, 158, 172, 174, 196, 221, 226, 227, 234, 364-65,
393 model 236 processes 233 child architecture
flow diagram 234, 288 child control flow diagram 158 child DFD 138,
140, 142 child process specification 140 class diagram 28, 33, 73,
90-92, 115, 125-26, 128, 170, 281, 307-8, 397, 405 rules and
guidelines 126 class model 270 Clemens, Paul C. 399,
422 client 277-78, 281, 405 requirements 278, 281, 284 system
277-78 client/server 274 CMM See Capability Maturity
Model Coad, Peter 64, 256, 420 COBOL 269 CODARTS 255-56, 268,
405 combinational machine 153-54, 405 commercial off-the-shelf system
(COTS) 252, 405 component 162, 175, 234, 247, 259, 271-72, 278, 345, 405
kinds of 278 composed-of 193 Concurrent Design Approach
for Real-Time Systems (CODARTS) 255-56, 268, 405 concurrent
engineering 184, 187-90, 291, 405 model 188-90 process 268 consists
of 143-44 constraint 301-3 design 301-2 input/output
301 other 303 content perspective 12 context 12,
213, 215 control vs. 160-61 diagram 87, 88, 96, 138,
285, 304-5, 406 control 406 hierarchy 271 layers
269 model 68, 113-14, 139, 143-56, 166, 169, 170, 206, 233, 267-68, 395,
398-99, 406 module 269 process 161, 165, 168, 169, 406 control
context diagram (CCD) 156-57, 171-72, 406 rules and guidelines
157 control/data flow diagram (C/DFD) 172, 174, 352
enhanced 172 control flow 106, 114, 129, 131, 144, 151,
155-56, 157, 158, 159-60, 161, 162, 164, 169, 399 input 153 model
155-56 output 153-54 rules and guidelines 155-56 sources for
144 control flow diagram (CFD) 131, 156-60, 164, 166, 168,
221, 406 data condition 159 rules and guidelines 159-160 controlling/controlled
64, 67-68, 93, 97, 254, 258, 268-69, 271-72, 274, 406 control specification
(CSPEC) 101, 114, 144, 146-47, 150, 154ff., 158, 159-60, 161, 164, 166, 169, 174ff.,
227, 233, 334, 352, 356, 388, 395, 396, 406 bar 156, 158, 159-60,
174, 175, 407 guide 175, 407 COTS 252, 405 Crosby,
Philip B. 36, 420 CSPEC See control specification customer 307-8,
342, 407 requirements 376, 387 customer
specification 210, 299-303, 305, 318, 322, 326, 331, 338, 341, 375, 378, 380
for groundwater analysis system 299-303 top
D DARTS 255 data 407
condition 160, 166, 169, 407 control and 394-95 flow 383, 399,
407 information modeling and 24 model 267, 395, 407 database
management system (DBMS) 268 data context diagram (DCD) 131, 135-37, 157,
171, 407 rules and guidelines 136-37 data
flow 83, 106, 129, 131-33, 137ff., 144, 150, 155, 157ff., 164, 169, 249, 395,
399, 407 rules and guidelines 132-133 data
flow diagram (DFD) 65, 110, 131, 137-39, 140, 159-60, 164, 166, 168, 169, 216,
217, 218, 227, 230, 233-35, 275, 278-80, 317-25, 327-29, 334, 337-40, 352, 355-57,
362, 364-67, 390, 395, 397, 407 definition of 137 elements
of 137-38 rules and guidelines 138-39 data flow model
155 data process 165, 168 data store 131, 164, 175, 270, 278, 407
splitting a 175 DBMS 268 DCD See data context diagram DDL
268 decision table (DT) 154, 158, 160, 268, 408 DeMarco, Tom 130,
420 Deming, W. Edwards 36, 420 derived requirement 32, 141, 364, 391,
393, 408 design 257, 301-2, 408 Design Approach for Real-Time Systems
(DARTS) 255, 301-2, 408 detailing diagrams 139-41 with
child DFD 139-41 with PSPEC 139-41 development process
181, 183-90, 205, 275, 277-78, 408 architecture 288-90 concurrent
development process 184-87 evolution of 183-84 model 278, 291 psare
6, 181, 413 task allocation 291 DFD See data flow diagram dictionary
See architecture dictionary, requirements dictionary domain 273, 288 DT
See decision table dynamic allocation 177, 242-44, 408 top
E EDFD See enhanced
data flow diagram Eeles, Peter 271, 420 encapsulation 256-57 Engineering
of Computer-Based Systems (ECBS) 244, 409 enhanced control/data flow diagram
(EC/DFD) 172 enhanced data flow diagram (EDFD) 222, 233, 282-83, 284, 291,
332-33, 335-36, 349-51, 357-62, 364, 370-72, 380-81, 409 enhancement
of models 221, 277, 281-84, 288, 290 of requirements 206, 222, 224-25,
228, 343, 348, 388, 409 of requirements model 166, 220-23, 225-26, 228,
233, 259, 275-76, 289, 311-12, 315, 334, 342, 346, 349-56, 387, 409 entity
233, 307-8, 409 model 112-14, 119-29, 166-67, 169, 170, 174,
180, 304, 307-11, 392 modeling 121, 124 specification 308, 409 entity
class 32, 33, 73, 116-18, 120, 121, 123-24, 126, 127, 128, 129, 162, 164, 409
rules and guidelines 118 specification 126-27 environment
210, 212, 217, 222, 331, 391, 409 essential model 222, 271, 276, 284-85,
290, 291, 312, 315, 316-30, 331-40, 346, 409 enhancing the
331-40 essential requirements 166, 222, 289, 311, 357, 388 event
160, 409 Existing Sampling Module 311-15 external stakeholders 285 top
F feasibility analyses 202-3 field
programmable gate arrays (FPGA) 252 flight management system 149-50 flow
76, 81, 83-85, 88, 95, 100, 106, 109, 131, 132-33, 134-35, 136, 138, 139, 153,
158, 161, 198, 212, 217, 218, 222, 227, 229, 233, 240, 247, 249, 257, 274, 288,
304, 311, 344, 357, 362, 381, 394, 395, 410 controlled 144 data
144 input 144 messages and 83-85 output 144, 304 stores
and 131, 212 flow diagram 106, 133, 177, 278, 410
child architecture 96 function 254, 410 functional
primitive 139 top G
Gomaa, Hassan 255, 420 groundwater analysis system
6, 249, 250, 299-388, 391, 396 Existing Sampling Module for
302, 304, 311-15, 343-46, 348, 364-66, 379, 381, 387 Groundwater Specimen
for 307-8, 311 Sample Analyzer Module for 344-47, 348-49, 355, 358-59, 370-71,
376-78, 379-80, 381, 387 top H
hardware layers 251-52 hardware/software 236-44,
392 configuration 239, 241 interfaces 239, 392 partitioning
14 hardware technologies 244-51 chemical
249 electrical 245-46 electromechanical 247 electronic 247 hardware
design 250 hydraulic 248-49 manufacturing 250 mechanical 248 mixed
technologies 250-51 optical 249 pneumatic 248-49 Harel,
David 147, 396, 420 Hatley, Derek 3, 180, 420-21 Hatley/Hruschka/Pirbhai
methods (H/H/P) 6, 7, 136, 299, 315, 389, 401, 410 Hatley/Pirbhai methods
(H/P) 3, 5, 389, 410 H/H/P methods See Hatley/Hruschka/Pirbhai methods hierarchy
46, 67, 410 aggregation/decomposition 93, 99 class 67 control
269, 271 controlling/controlled 93 is-a 67 networks and 90-92 supertype/subtype
107 hospital monitoring system 6 H/P methods See Hatley/Pirbhai
methods Hruschka, Peter 5, 422 Humphrey, Watts 183 top
I IEEE 244 "-ilities"
303, 380 implementation 267-68, 410 INCOSE 410 information hiding
256, 259, 262, 269 module 261, 410 information/material/energy
55-60, 161, 212, 257 information model 206, 233, 261, 410 inheritance
76, 77, 86, 107, 256-57, 258, 268, 274, 410 structure 274 inheritance
relationship 85-86, 106, 107, 108 rules and guidelines 86 input
and output flows 82, 138 processing 331 input
processing 187, 410 interconnect 87, 206, 212, 228, 230, 234, 245, 249,
250, 344, 382, 392, 393-94, 395, 410 interface 236, 277, 288, 315, 331,
410 International Council on Systems Engineering (incose) 410 is-a
relationship 121, 122, 411 top
J Jackson, Michael
255, 421 Jackson System Development (JSD) 255 Jacobson, Ivar 178,
180, 256, 271, 419, 421 top
L layer 185-87,
270-71, 280-81, 411 application 269 architectural 223 control
269 Deliverable System Development 186 Implementation 185 in
model 60-70, 411 structure 205, 253 in systems 46-47, 185 Top
System Element 186 top M Maier,
Mark 18, 421, 422 Manhattan Island example 27-28 McConnell, Steve
16, 421 McMenamin, Stephen 66, 112, 180, 421 message 76, 79, 81-85,
97, 100, 256-57, 411 definition of 81 diagrams 98 flows
and 83-85 rules and guidelines 82 message/call 98 message
specification 102-3, 111, 411 definition of 102-3 meta-model
275-96, 411 method 178, 181-83, 200, 209, 250, 256, 389, 390, 397-400, 411
See also Hatley/Hruschka/Pirbhai method (H/H/P), Hatley/Pirbhai method (H/P) process,
tool, and 181-83 MID 76, 106, 107-8, 110 model 205-74,
275, 278, 280, 311, 344, 346-47, 393, 411 See also architecture
model, concurrent model, control model, meta-model, requirements model abstraction/detailing
68, 192, 197 aggregation/decomposition 64, 69, 192-93, 197 client/server
67 context-level 210 environment 212, 213, 217, 222 essential
222 layered 60-70, 411 requirements/architecture/design 191 supertype/subtype
67 system specification 191-93, 207 modeling elements
76-87 See also architecture flow, architecture interconnect,
architecture model, flow, inheritance relationship, message, and terminator module
87, 100, 106, 168, 212, 225, 233, 247, 249, 254, 259, 268, 315, 344, 347, 349,
357, 393, 396, 411 See also architecture module application
270 control 269 hardware 236 hardware/software 237 software
236, 240 specification 376 module inheritance diagram
(MID) 76, 106, 107-8, 110, 411 rules and guidelines 108 multiple
architecture models 174-75 multiple hierarchies 9 multiple inheritance
107 multiplicity 119-20, 121, 124, 128, 305, 308, 412 top
N Naval Research Laboratory's Software Cost
Reduction Method 255 networks 90-92 top
O object orientation (OO) 67, 94, 178-79,
256-58, 268, 271, 391, 392, 399, 412 architecture and 272 constructs
of 391 methods of 178-79, 257, 271 object-oriented design
(OOD) 255, 256-57, 412 output processing 221, 276, 412 top
P Page-Jones, Meilir 86, 254, 255, 258, 421 Palmer,
John 102, 421 Parnas, David 52, 64, 255, 259, 299, 421-22 partitioning
49, 412 pat See process activation table patient-monitoring system
6, 209-36, 238, 252 architecture 229-33 Architecture
Level 1 Model 220-23, 224ff., 233 context-level model 213-18 enhanced
requirements model 220-23 enhancements 228 environment 210-13 interconnects
228 lower-level models 233 problem statement 210 technology
constraints 219-20 people-made systems 9, 10, 11, 27 Pirbhai,
Imtiaz 413, 420 Premerlani, William 422 primitive 164, 413 process
16, 131, 133, 137, 138, 139, 154, 174, 176, 177, 181-83, 200, 212, 221, 233, 249,
250, 271, 277, 284, 395, 398, 399, 413 See also Process for
System Architecture and Requirements Engineering (PSARE) activators 154,
395 definition of 133 method 413 methods, tools, and 181-83 model
113-14, 130-42, 150, 166, 167, 170, 180, 206, 233, 267, 270, 395, 398, 399, 413 module
250 rules and guidelines 133 for system development 16 process
activation table (PAT) 146, 154, 268, 396, 413 Process for System Architecture
and Requirements Engineering (psare) 6, 181, 413 processing view 18, 20-21 processors
230 processor view 18, 19-20 process specification (PSPEC) 139-43,
144, 150, 161, 164, 166, 169, 174, 175, 196, 212, 216, 217, 221, 233, 267, 311,
314, 318-25, 327-30, 334, 335-40, 364-65, 367, 376, 388, 393ff., 400, 413
rules and guidelines 142-43, 394 Programmable Logic Arrays
(PLAs) 20 programming language 268, 269 project coordination 203 prototype
202, 413 PSARE 6, 181, 413 PSPEC See process specification push
and pull indicators 81, 82, 83-85, 94, 95, 97, 99 top
Q quality 36-37 quick-ticketing system
(QTS) 7 top R
RD See requirements dictionary real-time (RT) 48, 398-99,
413 Rechtin, Eberhardt 18, 37, 422 relationship 118, 121, 123-25,
129, 162, 164, 267, 307-8, 311, 413 abstraction/detailing 65-66,
92 aggregation/decomposition 64-65, 92, 123 binary 118-19 class
91 controlling/controlled 67-68 generalization/specialization 67 is-a
121, 122 is-boss-of/is-supervised-by 67 multiplicity 119-20 name
119-20 n-ary 128 parent/child 198 rules and guidelines 120-21 specification
127-28, 413 subclass/superclass 92, 121 superclass/subclass 121 supertype/subtype
66-67, 85 symbols 118-20 required capability
210, 219, 387, 413 constraint 387, 414 requirements 24-40,
226, 228, 230, 233, 235, 242, 257, 264, 281, 285, 288-89, 299-303, 304, 307-8,
345-46, 347, 348-49, 380, 387-88, 390, 393, 414 See also requirements
model aggregation/decomposition of 33 capabilities and 26-27, 33,
39 categorizing 39-40, 202 class diagram 28ff., 32, 34, 36 constraints
26, 27, 33, 34, 39, 301-3 core 267 customers and 24 decomposing
202 defined 26-28 derived 30-31, 39, 194-97, 198, 202, 393 detailing
30-31, 38-39, 194-97 enhancement and allocation 194, 202, 267 entity
class 38-39 essential 167-68, 222, 266, 393 external 37-38, 185 feasibility
analysis of 38, 202 functional 26, 138 gathering of 30, 37-38, 202 hiding
264, 266-67 integrity analysis of 38, 202 management of 37-40, 202 managers
and 24, 25 performance 27, 32-33, 164, 196, 375, 387, 414 primitive
32-34, 194, 196 for quality 36-37 sources of 24-26 specification
299 stakeholders 24ff., 200, 266 standards as source for 24, 25 sub/supertyping
relationship and 34 for timing 164-65, 375, 377 users and 24, 25,
331 requirement context diagram 172, 214, 277, 284, 290, 304-5,
341 requirement entity class 28, 38-39 requirements/architecture relationships
See also superbubbles, traceability balancing 177-78 scope differences
171-72 requirements dictionary (RD) 75, 113, 129, 131, 132,
155, 162-70, 177, 218, 221, 233, 311, 376, 383-84, 388, 414 requirements-driven
systems 22 requirements flow 250 requirements method 4, 7, 160-61,
179, 190-99, 200, 205, 244, 250, 257, 273, 275, 389, 391, 392, 396, 398, 400,
414 requirements model 28-36, 65, 72, 84, 112-61, 162ff., 169-70, 171, 174,
177, 180, 190, 192, 194, 197, 200, 206, 209, 218, 221, 222, 224, 233-34, 249,
250, 261, 267, 270, 275, 279, 304, 311, 315, 316, 318, 347, 366, 387, 391ff.,
398ff. architecture model and 170-78 balancing 141, 166 components
of 169 is-a relationship 34 summary of 169-70 Robertson,
James 66, 180, 422 Robertson, Suzanne 66, 180, 422 Rumbaugh, James
178, 256, 421, 422 top S
SA See Structured Analysis SD See Structured Design sequential
machine 147-48, 149-50, 151-53, 414 defined 147-48 other
representations of 151-53 Sheard, Sarah 200, 422 Shenhar,
Aaron J. 189, 422 Shlaer, S. 256, 422 Society of Concurrent Engineering
(SOCE) 422 software architecture 259, 272-72 software design 269-70
methods 254, 258 software development 84-85, 254-58, 393
history of 254-58 software layers 253-73 specifications
311, 315, 414 spiral model 184 stakeholder 289, 414 starvation
of bubbles 139, 414 state 415 state chart 154, 158, 160, 396, 415 state
machine 152 state transition 165, 415 state transition diagram (STD)
146, 147, 148, 149, 150, 151, 268, 396, 415 state transition matrix (STM)
146, 415 state transition table (STT) 146, 415 state/event matrix
152, 415 state/state matrix 152, 415 STG See Structured Technology
Group store 131, 134-35, 137, 138, 157, 162, 164, 168, 174, 176, 177, 212,
227, 233, 257, 397, 415 flows and 131, 387 rules and
guidelines 134-35 symbol for 134-135, 397 Strategies
for Real-Time System Specification 3, 4, 5, 6, 60, 68, 79, 84, 106, 144, 146,
147, 151, 164, 165, 181, 214, 389, 397 StructSoft 415 structure 64,
97 aggregation/decomposition 103, 106 assembly/subassembly/component
64 container/content 64 controlling/controlled 97 message/call
98 whole/part 64 Structured Analysis (SA) 34, 47, 65-66,
73, 92, 96, 110, 130, 131, 135, 136, 141, 209, 397, 398, 400, 415 Structured
Design (SD) 47, 68, 86, 102, 254-55, 258, 268-69, 415 structured English
142, 394, 415 structured methods 178-79, 415 Structured Technology
Group (stg) 416 subtype/supertype 122, 256, 416 superbubbles 171,
172-75, 176, 213-14, 225-27, 228, 230, 233-34, 291, 349, 364, 390, 416
rules and guidelines 174-75 traceability and 176-77 superclass/subclass
121-23 rules and guidelines 122-23 supertype/subtype
64, 66-67, 85, 107, 121, 416 system 10-40, 205, 416 See
also system development approach 9 architect 200-204, 273, 402 architecture
49, 74, 224, 245, 281, 290, 395 artifacts 5 categories of 17-18 classification
23 complexity of 17-18 components of 10 concept of 9 engineer
200-204, 214 engineering 290, 416 errors 15 hierarchies 11-13,
14 life cycle 15, 182 module specification 375 networks 14-15 people-made
9, 10, 11, 27 properties of 12 requirements 24-40, 49 requirements
context 216 requirements driven 22 role of 200-204 specification
of 20, 280, 388 stakeholders 281 views of 18-24 system
development 4, 16, 181-204, 275-96, 318, 348, 389, 416 essential
model of 277-81 meta-model for 276 nature of 183-90 overview
of 275-76 patient-monitoring system example 209-36 process and methods
16, 190-99 process, methods, and tools 181-83 top
T Taylor, David A. 271, 422 terminator
76, 78-79, 87, 88-89, 109, 131, 135, 136, 137, 144, 156, 157, 204, 214, 222-23,
277, 284-85, 288, 290, 341-42, 349, 392, 417 definition of
78 examples of 277-78, 285, 288 naming rules 79 symbol for 78 testing
187, 417 timing specification (TSPEC) 166, 177-78, 196, 222, 304, 305-7,
346, 377, 381, 392, 417 tools 181-83, 200, 423 traceability 176-77,
185, 196, 197-99, 226, 236, 393, 417 traceability matrix 101, 176-77, 194,
197, 198, 228, 230-33, 234, 242, 244, 352-54, 366, 368-69, 380, 388, 390, 393,
417 rules and guidelines 176-77 trade-off
study 202, 347, 348, 376, 377, 382, 417 training 423 TSPEC See timing
specification Turbocase/Sys 418, 423 top
U Unified Modeling Language (UML) 7, 85, 118,
121, 125, 178, 179, 180, 418 use case 180, 418 user 394 user
interface 89, 221, 259, 261, 264-65, 269, 271-73, 276, 290, 418 user-interface
processing 331 top V
views of a system 18-24 activity level 19,
23-24 intelligence level 19, 22-23 processing 18, 19-20 processor
18, 20-21 what/how 18, 21-22 top
W waterfall model 183-84, 188, 189, 190 Weinberg,
Daniela 43, 422 Weinberg, Gerald M. 43, 422 what/how classification
49-54, 142 architecture model and 50 requirements model
and 50 separation of 50-51, 70 whole/part 64, 193 www.psare.com
7, 36, 391, 423 top Y
Yourdon, Edward 254, 420, 423
Return
to Book Page
|
