Index
A
Action Language for Foundational (ALF) 256
agility
concepts 3
analysis model 302
animated sequence diagrams 447
architectural allocation 321
inputs 321
non-allocable requisites, decomposing 323
outputs 322
postconditions 322
preconditions 321
purpose 321
system requisites, allocation 323
Architectural Analysis Package 105
architectural design 270
Architectural Design Package 105
architectural merge 286
example 290
inputs 287
interfaces, copying from use cases to system block 290
interfaces, merging 290
interfaces, updating to refer copied system functions 290
issues, with merging specifications 286, 287
outputs 287
performing 287
postconditions 287
preconditions 287
purpose 287
system architecture 286
system context, creating 288
system data, copying from use cases to system block 289, 290
system function conflicts, resolving 289
system functions, copying from use cases to system block 289
architectural trade studies 272
architectural merge 286
assessment criteria, defining 275, 276
candidate solutions, identifying 274
inputs 272
key systems functions, identifying 274
MoE, assigning to candidate solution 278
pattern-driven architecture 299
Pegasus smart bicycle trainer example 279
preconditions 272
purpose 272
sensitivity analysis, performing 278
solution, determining 278
subsystem and component architecture 310, 311
utility curve, defining for assessment criterion 277
weights, assigning to criteria 277
architecture 85
critical views 270
Architecture 0
electronic technical work items 100
inputs and preconditions 87
mechanical technical work items 100
outputs and postconditions 87
purpose 87
technical work items 100
Architecture 0, Harmony process views
concurrency and resource view 85
dependability view 86
deployment view 86
distribution view 85
subsystem and component view 85
Architecture 0, workflow
computational needs, identifying 89, 90
computational patterns, selecting 90
dependability needs, identifying 90
dependability patterns, selecting 91
distribution needs, identifying 90
distribution patterns, selecting 91
electronic architecture, creating 91
engineering disciplines contributions, considering 89
existing technologies assets, considering 89
key technologies, identifying 89
mechanical architecture, creating 91
primary architectural optimizations, determining 88
scope of functionality, reviewing 88
subsystem architecture, creating 91
subsystem organizational concerns, identifying 89
subsystem patterns, selecting 90
technical work items, allocating to iterations 91
technical work items, creating 91
asset diagram 217
assets
types 221
authoritative source 380
automatic initialization of context and runtime objects
reference link 447
B
inputs and preconditions 8
outputs and postconditions 8
purpose 8
workflow 9
backlog management, workflow
effort, estimating 11
resolved work item, removing 12
work item, allocating in iteration backlog 12
work item, approving 11
work item, performing 12
work item, placing in project backlog 12
work item, prioritizing 11
work items, reorganizing 13
work performed, rejecting 12
work performed, reviewing 12
backward traceability 495
baseline 115
Bluetooth Low Energy (BLE) 393
branch 116
burn down chart 24
Business Analysis Body of Knowledge (BABOK)
reference link 67
C
Cameo prototype
reference link 199
Cameo Safety and Risk Analyzer 198
Cameo Teamwork Cloud 117
Capabilities Package 104
inputs and preconditions 115
outputs and postconditions 115
purpose 114
workflow 115
change management, workflow
branch and merge 116
change activity, making 117
changes, verifying 117
elements, locking 117
elements, modifying 117
elements, unlocking 117
Lock and Release 116
model, opening 116
modification, determining 116
updated model, storing 117
work item, obtaining 116
collaboration design 270
collaboration parameter 300
Collaborator 509
Command-and-Control Battle Management (C2BM) platform 354
Commercial Off-the-Shelf (COTS) 365
Common Vulnerability Enumeration (CVE) 222
Common Weakness Enumeration (CWE) 222
compliance in form 441
compliance in meaning 441
component architecture 270
computable constraint modeling 483
inputs and preconditions 484
outputs and postconditions 484
purpose 483
computable constraint modeling, example 486
analysis of units, performing 490
available truths, identifying 487
mathematical formulation, constructing 488
necessary properties of acceptable solutions, determining 488
problem, constraining to relevant information 488
problem, rendering as set of connected constraint properties 488, 490
problem, understanding 486
sanity check, performing 493
computable constraint modeling, workflow
analysis of units, performing 486
available truths, identifying 485
mathematical formulation, constructing 485
necessary properties of acceptable solutions, determining 485
problem, constraining to relevant information 485
problem, rendering as set of connected constraint properties 485
problem, understanding 485
sanity check, performing 486
computable model 444
concurrency and resource architecture 270
Configuration Item (CI) 114
configuration management 113
reference link 114
constraints 485
blocks 485
parameters 485
Control Area Network (CAN) 394
Cost of Delay (CoD) 72
Critical Design Review (CDR) 443
critical views, architecture
concurrency and resource architecture 270
data architecture 270
dependability architecture 270
deployment architecture 271
distribution architecture 270
subsystem/component architecture 270
cut set 200
Cyber-Physical Security 213
cyclomatic complexity 20
D
data architecture 270
Data Distribution Service (DDS) 391
data schema 248
Decision Analysis Matrix 273
dependability architecture 270
deployment architecture 271, 404
engineering facets 404
interdisciplinary interfaces 421
privacy architecture 270
reliability architecture 270
safety architecture 270
security architecture 270
Deployment Architecture Package 110
design patterns 299
design context, defining 302
design solution, validating 302
dimensions 299
example 303
in architectural context 300
inputs 301
issues, determining 302
issues, solving 302
outputs 301
pattern roles 300
postconditions 301
potential pattern solutions, selecting 302
preconditions 301
purpose 301
selected pattern, instantiating 302
trade study, performing 302
detailed design 270
Digital Indexed (DI) 396
DI shifting
reference link 191
distribution architecture 270
DO-178C
reference link 464
E
effort estimation 58
inputs and preconditions 59
outputs and postconditions 59
purpose 58
user stories and scenarios 59
ego-less reviews 513
Engineering Change Order (ECO) 114
engineering facets
deployment architecture 404-406
example 411
initial facet load analysis, performing 409, 410, 420
inputs and preconditions 406
involved disciplines, identifying 407, 411
non-allocatable requisites, decomposing 408, 413-415
non-allocatable subsystem features, decomposing 408, 417-420
outputs and postconditions 406, 407
purpose 406
requisites, allocating 408, 417
subsystem features, allocating 408, 420
epic 39
example, of architectural allocation 323, 324
non-allocable requirements 324, 325
non-allocable system functions and data, decomposing 332-334
system functions and data allocation 330, 331
system requirements allocation 328-330
example, of architectural merge
interfaces, copying from use cases to system block 297
interfaces, merging 298
interfaces, updating to refer copied system functions 297
interfaces, updating to refer copied systems data 297
system context, creating 291
system data conflicts, resolving 296
system data, copying from use cases to system block 296
system function conflicts, resolving 295
system functions, copying from use cases to system block 292-294
example, of design pattern 303
design context, defining 303, 304
design solution, validating 310
issues, determining 304
issues, solving 304
potential pattern solutions, selecting 304-308
selected pattern, instantiating 309
trade study, performing 309
example, of reference architecture
architectural elements, adding 360, 361
areas of deviation, identifying 357
instance specifications, creating 361
instance specification slots, populating 361, 362
reference architecture, selecting 356, 357
relevant architectural elements, subclassing 358, 361
specific architectural elements, redefining 359
specific system block, defining 358
specific system instance specification, defining 361
executable model 444
F
Fagan inspections
reference link 505
Failure Means and Effect (FMEA) 198
Fault Tree Analysis (FTA) 198
Federating Models for Handoff 380, 381
example 386
inputs and preconditions 382
outputs and postconditions 382
purpose 381
SE model references, adding to Shared Model 383-386
SE model references, adding to subsystem model 385, 388
Shared Model, creating 383, 386
Shared Model references, adding to subsystem model 386, 388
Shared Model, structuring 383, 386
subsystem model, creating 384, 387
subsystem model, structuring 384, 385, 388
federation 380
Final Operating Condition (FOC) 40
forward traceability 495
Fraction of Inspired Oxygen (FiO2) 205
free-form diagram 447
Functional Analysis Package 105
functional analysis with activity model, example 157
execution context, defining 158
ports and interfaces, creating in execution context 163-167
primary functional flow, identifying 160
related actors, identifying 158
Requirements_change 170
requisites set, updating 170, 171
requisites show, performing 171
requisites, validating 168, 169
requisites, verifying 168, 169
trace links, adding 171
use case, describing 158
use case, performing 171
use case scenarios, deriving 161, 162
functional analysis with activity model, workflow
executable state model, creating 156
execution context, defining 155
ports and interface, creating in execution context 156
primary functional flows, identifying 155
related actors, identifying 155
Requirements_change 156
requisite set, updating 156
requisites review, performing 157
requisites, validating 156
requisites, verifying 156
trace links, adding 157
use case, describing 155
use case, identify 154
use case, performing 157
use case scenarios, deriving 156
functional analysis with scenarios 134
inputs and preconditions 135, 153
outputs and postconditions 135, 153
functional analysis with scenarios, example 138
activities 153
executable state model, creating 146-149
execution context, defining 139
ports and interface, creating in execution context 145
related actors, identify 139
Requirements_change 151
requisites review, performing 152
requisites set, updating 151
requisites, validating 149-151
trace links, adding 152
use case, describing 138
use case, identifying 138
use case, performing 152
use case scenarios, capturing 141-144
functional analysis with scenarios, workflow 135, 153
executable state machine, creating 137
execution context, defining 136
ports and interface, creating in execution context 136
related actors, identify 136
Requirements_change 137
requisites review, performing 137
requisites set, updating 137
requisites, validating 137
requisites, verifying 137
trace links, adding 137
use case, describing 136
use case, identify 136
use case, performing 137
use case scenarios, capturing 136
functional analysis with state machine 171
inputs and preconditions 172
outputs and postconditions 172
purpose 172
functional analysis with state machine, example 176
executable state model, creating 179-182
execution context, defining 177
ports and interface, creating in execution context 179
related actors, identifying 177
Requirements_change 183
requisites review, performing 185
requisites set, updating 184
requisites, validating 183
requisites, verifying 183
trace links, adding 184
use case, describing 176
use case, performing 185
use case scenarios, generating 182
functional analysis with state machine, workflow 172
executable state model, creating 174
execution context, defining 174
ports and interface, creating in execution context 174
related actors, identifying 174
Requirements_change 175
requisites review, performing 175
requisites set, updating 175
requisites, validating 175
requisites, verifying 175
trace links, adding 175
use case, describing 173
use case, identifying 173
use case, performing 175
use case scenarios, generating 174
functional analysis with user stories 185, 186
inputs and preconditions 189
outputs and postconditions 189
purpose 189
functional analysis with user stories, example 191
buttons, using to shift gears 193
functional requisites, specifying 194
quality of service as requisites, identifying 194
related actors, identifying 192
Requirements_change 195
requisites review, performing 196
requisites set, updating 195
requisites, verifying 195
trace links, adding 195
use case, describing 192
use case, identifying 191
use case, performing 196
functional analysis with user stories, workflow 189
<role> statement 190
acceptance criteria, specifying 190
quality of service as requisites, identifying 190
related actors, identifying 190
Requirements_change 191
requisites review, performing 191
requisites set, updating 191
requisites, validating 190
requisites, verifying 190
trace links, adding 191
use case, describing 190
use case, identifying 190
use case, performing 191
H
Handoff to Downstream Engineering
purpose 363
Handoff to Downstream Engineering, activities
logical interface, migrating to physical interfaces 389
model federation 380
preparation 372
Harmony Agile Model-Based Systems Engineering process (Harmony aMBSE) 85
Harmony for Embedded Software process (Harmony ESW) 85
Harmony process
Harmony aMBSE 85
Harmony ESW 85
hazard analysis 202
inputs and preconditions 202
outputs and postconditions 202
purpose 202
hazard analysis, example 205
causality model, creating 208
conditions and events, describing 207
cut set, identifying 209
hazard, describing 206
hazard, identifying 205
problem statement 205
related conditions and events,identifying 207
results, adding in FTA 210
safety concept, reviewing 211
safety measures, adding 209
safety requisites adding 212
hazard analysis, workflow 202
causality model, creating 204
conditions and events, describing 204
cut set, identifying 204
hazard, describing 203
hazard, identifying 203
related conditions and events,identifying 203
requisites review, performing 205
safety concept, reviewing 205
safety measures, adding 204
safety requisites, adding 205
trace links, adding 205
use case, performing 205
I
Initial Operating Condition (IOC) 40
interdisciplinary interfaces 421
agreed-upon interfaces, storing in configuration management 424, 437
allocations, reviewing to engineering facets 422
examples 424
facet properties, identifying 422, 425
inputs and preconditions 421
interaction, defining among facet properties 423, 426, 427
interaction metadata, capturing 423, 428, 433
interactions, grouping across facets into interfaces 423, 437
interface details, negotiating 423, 437
outputs and postconditions 421
port pairs, defining between facets 423, 425
purpose 421
Interdisciplinary Product Team (IPT) 406
Interface Control Document (ICD) 389
Interface Diagram 390
Interfaces Package 105
Interface Specification Table 390
Internal Block Diagram (IBD) 95
Iteration 0 78
inputs and preconditions 78
outputs and postconditions 79
purpose 78
workflow 80
Iteration 0, workflow
architectural goals, identifying 82
high-level architecture, defining 83
product roadmap, creating 81
product vision, creating 81
providing, team with domain knowledge 81
providing, team with process knowledge 82
providing, team with skills and tools 81
release plan, creating 81
risk management plan, creating 81
team, selecting 81
team workspaces, setting up 82
tool installations, testing 82
tools, configuring 82
tools, installing 82
iteration plan 51
backlog, adjusting 54
effort, estimating for work tasks 53
inouts and preconditions 51
iteration mission, reviewing 53
outputs and postconditions 52
purpose 51
tasks, adding to backlog for iteration 53
team, adjusting 54
team loading, evaluation 54
use cases, breaking into user scenarios 53
use stories, breaking into tasks 53
workflow 52
work items, selecting from backlog 53
iteration plan, workflow
K
Key Performance Indicator (KPI) 19
L
League of Racers Extraordinaire (LORE) 358
logical data schema
creating 246
inputs and preconditions 251
outputs and postconditions 251
purpose 251
logical data schema, example 257
blocks, identifying 258
collaboration, creating 257
properties for metadata, defining 266, 267
relations, adding 259
structure, defining 258
type model, constructing 263
units, defining 263
value properties, identifying 260
value type, applying to relevant properties 265
logical data schema, workflow 252
block, identifying 254
collaboration, creating 254
flow item to structure, defining 255
flow message, defining 255
flow property, identifying 254
interaction, defining 254
message, identifying 255
message parameters, adding 255
metadata of interest, identifying 257
metadata aspects, specifying 256
metadata properties, filling 257
metadata tags, adding 257
operation, defining 255
quantity kind, defining 256
relation, adding 254
signal attributes, defining 255
signal reception, defining 255
stereotype, creating 257
stereotypes to properties, applying 257
structure, defining 254
type, applying to relevant properties 256
type model, constructing 255
unit, defining 256
value property, identifying 254
value type, defining 256
logical interface, migrating to physical interface 389, 390
examples 393
ICD, representing 390
inputs and preconditions 390
interface visualization, creating 393, 403
navigable links, adding 393, 401, 402
outputs and postconditions 391
purpose 390
logical interfaces
physical realization, defining 392, 393, 396-400
logical system interfaces
inputs and preconditions 235
outputs and postconditions 235
purpose 235
specifying 231
SysML ports and interfaces 231, 232
logical system interfaces, example 237
activity flow, creating 238-240
execution context, creating 238
flows, adding 244
message parameters, adding 244
parameter and flow types, creating 244
ports and interfaces, creating 244
related actors, identifying 237
use case, identifying 237
use case scenarios, capturing 241, 243
logical system interfaces, workflow 235
activity flow, creating 236
execution context, creating 236
message parameters, adding 237
parameter and flow types, creating 237
ports and interfaces, creating 237
related actors, identifying 236
UML flows, adding 237
use case, identifying 236
use case scenarios, capturing 236
Low-energy Bluetooth (BLE) 92
M
Mathematically-Addressable Problems (MAPs) 483
MBSE and MDD guidelines
reference link 441
Mean Time Between Failure (MTBF) 204, 279
Measure Performance Metrics 223
Medical Gas Mixer (MGM) 205
metrics 20
Minimal Testable Feature (MTF) 521
Minimal Verifiable Feature (MVF) 521
model
purpose 103
model-based safety analysis 196
key terms 197
Model-Based Systems Engineering (MBSE) 4-6
model-based testing (MBT) 460, 461
inputs and preconditions 462
outputs and postconditions 462
purpose 462
reference link 461
model-based testing (MBT), example 465, 466
defects, fixing in SUT 482
system under test, identifying 466-471
test architecture, defining 472
test cases, applying 481
test cases relating to requirements 474
test cases, specifying 473
test coverage, analyzing 474
verdicts, rendering 481
model-based testing (MBT), workflow 463
defects, fixing in SUT 465
system under test, identifying 463
test architecture, defining 463
test cases, applying 465
test cases relating to requirements 464
test cases, rendering 465
test cases, specifying 464
test coverage, analyzing 464
verdicts, rendering 465
model-based threat analysis 212
Cyber-Physical Security 213
inputs and preconditions 220
modeling for security analysis 215
outputs and postconditions 220
purpose 220
model-based threat analysis, example 223
asset contexts, describing 224
asset contexts, identifying 224
assets, describing 224
assets, identifying 224
attack chain, specifying 225
causality tree, creating 228
countermeasures, adding 229
requisites review, performing 230
security posture, reviewing 229, 230
security requisites, adding 230
trace links, adding 230
use case, performing 230
vulnerabilities, identifying 225
model-based threat analysis, workflow 220
asset contexts, describing 222
asset contexts, identifying 221, 222
assets, describing 222
attack chains, specifying 222
causality tree, creating 222
countermeasures, adding 222
requisites review, performing 223
security posture, reviewing 223
security requisites adding 223
trace links, adding 223
use case, performing 223
vulnerabilities, identifying 222
model federation 380
model fidelity 103
modeling for security analysis 215, 216
asset diagram 217
security analysis diagram (SAD) 217
tabular views 220
Model Manager 509
Model Overview Diagram
example 106
Model Overview Package 104
model simulation 444
inputs and preconditions 445
outputs and postconditions 445
purpose 445
model simulation, example 448
behaviors, defining 450
creating 452
desired outputs/outcomes, identifying 450
outputs and outcomes, analyzing 454, 455, 458, 460
purpose, defining 448
running 452
structural context, defining 448, 449
view, defining 451
model simulation, workflow 445
behaviors, defining 446
creating 447
desired outputs/outcomes, identifying 447
outputs and outcomes, analyzing 448
purpose, defining 446
running 447
structural context 446
structure, defining 447
model version 114
model work items
inputs and preconditions 514
managing 514
outputs and postconditions 514
purpose 514
model work items, example
creating 517
enacting 519
selecting 518
updating 519
model work items, workflow 515
characterizing 516
creating 515
enacting 516
selecting 516
structures, creating 515
updating 516
N
nanocycle 520
O
Over-the-Air (OTA) updates 409
P
package 114
Pain Cave model
composition architecture 118
connected context 118
elements, behavior 120
pattern arguments 300
pattern-driven architecture 299
pattern instantiation 299
pattern mining 299
pattern roles 300
Pegasus 545
Pegasus key features 545
customizable bike fit 546
emulation, gearing 547
exercise metrics, exporting 546
exercise metrics, monitoring 546
exercise metrics, uploading 546
incline control 547
online training system compatible 548
OTA firmware updates 548
power level, controlling 547
user interface 547
variable power output 547
Pegasus smart bicycle trainer, trade study example
assessment criteria, defining 279, 280
candidate solutions, identifying 279
key system functions, identifying 279
MoE, assigning for candidate solution 283, 284, 285
sensitivity analysis, performing 285
solution, determining 286
utility curve, defining for criterion 282
weights, assigning to criteria 281, 282
Pegasus system architecture, example
abstract common services layer 318
application layer 317
communications layer 318
mission statement, assigning 320
potential architectural patterns, reviewing 316
requirement allocation 321
subsystem and component architectural pattern, selecting 317
subsystem interfaces, creating 321
system features, allocating 321
systems functions and data, grouping into coherent sets 315, 316
UI layer 318
Pegasus System Model
overview diagram 112
physical interfaces
planning poker 58
polymorphic behavior 354
Preliminary Design Review (PDR) 443
preparation, of Handoff to Downstream Engineering
examples 374
inputs and preconditions 372
interface data, organizing 373, 378
outputs and postconditions 372
purpose 372
requirements, organizing 373, 376
review model, for handoff readiness 373, 380
subsystems, organizing 373, 375
prioritized epics 44
priority 66
influencing, factors 66
priority poker 67
product owner/presenter 508
agreement, obtaining 42
broad product timeframe, assigning 42
epics, allocating in product timeframe 42
epics, creating 42
epics, prioritizing 42
inputs and preconditions 39
outputs and postconditions 39
product themes, enumerating 41
purpose 39
updating 43
product roadmap, for Pegasus system
agreement, obtaining 45
epic, allocating into product timeframe 45
epics, creating 43
epics, prioritizing 44
product themes, enumerating 43
product timeframe, assigning 44
updating 45
project risk management 28
inputs and preconditions 29
outputs and postconditions 29
purpose 29
types 28
Q
Qualities of Service (QoS) 299
Quality Assurance (QA) reviewer 508
quantity kind
R
Real-Time Agility 3
reference architecture 349
architectural element, adding 354
areas of deviation, identifying 353
compliance, demonstrating 355
example 356
inputs 351
instance specification slots, populating 355
outputs 351
postconditions 351
preconditions 351
purpose 351
relevant architectural elements, subclassing 354, 355
selecting 353
specializing 348
specific architecture elements, redefining 354
specific architecture instance, creating 354
specific architecture type, creating 353
specific system block, defining 354
specific system instance specification, defining 355
system instance specification, creating 355
workflow 352
release plan 46
epics decomposing 47
epics high-level goals, identifying 47
inputs and preconditons 46
iteration missions, establishing 47
iteration plan, reviewing 48
iteration work items, prioritizing 48
outputs and postconditons 46
purpose 46
work items, allocating to iterations 48
Request for Proposals (RFPs) 365
Requirements Package 105
resistance generation, smart bicycle trainer
electric motor with flywheel 279
electrohydraulic 279
hydraulic with flywheel 279
Wind Turbine 279
review
inputs and preconditions 506
outputs and postconditions 506
purpose 505
review coordinator 508
reviewers
comments and issues 513
review, example 510
action item resolutions, planning 514
action items, resolving 514
issues, capturing as action items 514
materials, disseminating 511
materials, preparing 510
purpose, establishing 510
reviewer comments, discussing 513
reviewer roles, assigning 511
reviewers independently inspect materials 512
scheduling 512
review, workflow 506
action item resolutions, planning 510
action items, resolving 510
issues, capturing as action items 509
materials, disseminating 509
materials, preparing 507
purpose, establishing 507
reviewer comments, discussing 509
reviewer roles, assigning 508
reviewers independently inspect materials 509
scheduling 509
revision 114
Rhapsody RAAML prototype
reference link 199
Risk Analysis and Assessment Modeling Language (RAAML) 198
risk list 29
risk management plan 30
outcome, assessing 33
potential source, identifying 31
replanning 33
risk, characterizing 31
risk list, adding in priority order 32
spike, identifying to address risk 32
spike, performing 33
spike work item, allocating to iteration plan 32
updating 33
work item, creating for spike 32
S
Scaled Agile Framework (SAFe) 67
scribe 508
security analysis diagram (SAD) 217
semantic reviews 504
semantic verification 441
smart packages 508
SME reviewer 508
Subject Matter Experts (SMEs) 504
subsystem and component architecture 310, 311
data, allocating 314
example 315
inputs 312
mission statement, assigning 314
outputs 313
pattern, selecting 314
postconditions 313
potential architectural patterns, reviewing 314
preconditions 312
purpose 312
requirements allocation 314
selecting 311
subsystem interfaces, creating 315
subsystem, modeling in SysML 311
system features, allocating 314
systems functions and data, grouping into coherent sets 314
validating 315
workflow 313
subsystem interfaces
creating 338
creating, from use case scenarios 334, 335
example 339
inputs 335
outputs 335
owner, adding to hold white box scenarios 336
postconditions 335
preconditions 335
purpose 335
scenario, creating 337
source scenario, replicating 337
subsystem interaction messages, adding 337
subsystem ports, creating 338
updating, with messages 339
subsystem interfaces, example
interfaces, creating 347
interfaces, updating with messages 348
original scenario, replicating 341, 342
owner, adding to hold white box scenarios 339
subsystem interaction messages, adding 342-345
subsystem ports, creating 347
Subsystem Package 111
subsystems 89
cons 89
pros 89
success metrics measurement 19, 20
inputs and preconditions 21
outputs and postconditions 21
purpose 21
SW Design Package 111
syntactic reviews 504
syntactic verification 441
SysML ports and interfaces 231, 232
system requirement
System Requirements Review (SRR) 443
Systems Models 112
organizing 101
Requirements package 111
Systems Models, organizing
inputs and preconditions 101
outputs and postconditions 101
purpose 101
T
tabular views 220
test-driven development (TDD) 519
Test-Driven Modeling (TDM) 519, 520
inputs and preconditions 520
outputs and postconditions 520
purpose 520
Test-Driven Modeling (TDM), workflow 520
bit, modeling 522
defects, fixing 522
test case, applying 522
test case, defining 521
textual requirements 132
definitions 495
inputs and preconditions 497
outputs and postconditions 498
purpose 497
traceability, example 502
goals, establishing 502
links, adding 502
relations, deciding to use 502
views, creating 502
views, specifying 502
traceability, workflow 498
goals, establishing 498
links, adding 501
relations, deciding to use 499
reviewing 501
views, creating 501
views, specifying 500
trace matrices 495
trace ownership 495
Traffic Light Controller (TLC) 523
trunk 116
U
UML Testing ProfileTM 2 (UTP 2)
reference link 461
Use Case Package 105
user interfaces (UIs)
technology, selecting 392, 395, 396
user interfaces (UIs), Pegasus key features
gearing 547
incline 548
ride 548
setup 548
V
velocity 24
W
Weighted Shortest Job First (WSJF) 67
work items
mapping 46
work items prioritization 66
inputs and preconditions 67
outputs and postconditions 67
purpose 67
Download a free PDF copy of this book
Thanks for purchasing this book!
Do you like to read on the go but are unable to carry your print books everywhere?Is your eBook purchase not compatible with the device of your choice?
Don’t worry, now with every Packt book you get a DRM-free PDF version of that book at no cost.
Read anywhere, any place, on any device. Search, copy, and paste code from your favorite technical books directly into your application.
The perks don’t stop there- you can get exclusive access to discounts, newsletters, and great free content in your inbox daily.
Follow these simple steps to get the benefits:
- Scan the QR code or visit the link below:
https://packt.link/free-ebook/9781803235820
- Submit your proof of purchase.
- That’s it! We’ll send your free PDF and other benefits to your email directly.