384
Index
Smaller-the-better (STB), 295, 335,
336, 337

loss function, 341

output response, 295, 340

proportionality constants, 300

quality loss function, 297

Social classification of integration,
161–162, 368

Social force, 60

Social processes, 81n

Socioeconomic rationale, 285

Sociological theory, 81n

Software listings, 12

Spatial domain, 30n

Specifications, 233, 368. See also

Verification

Stability, 108–111, 112, 368. See also

Instability; Metastability

long-term, 154

points of, 240

poor, 98

of systemness, 198

Stakeholder analysis, 260–262

classification, 262–265

defining stakeholder
requirements, 264

key stakeholder selection, 264

problem statement
development, 264

stakeholder classification, 262–265

stakeholder importance, 263

stakeholder influence, 263

Stakeholders, 233, 259–260, 263, 265,
283, 306, 368

Static objects, 166

STB. See Smaller-the-better (STB)

Subjective frame, 82, 84, 85, 88,
141, 369

Subjective measures, 139, 369

Subjective ontology, 139, 141, 369.
See also Objective ontology

Subjective value, 130, 369. See also

Process

Success, 12n

Successive approximation, 104n

Syndicate, 208–209, 210

Synthesis, 228–229, 369

SysPMI. See Systems Process Model
for Integration (SysPMI)

System, 78, 113, 145n, 189, 202, 231, 370.
See also Boundary; Integration
principles; Process

System of Systems, 198, 199–200,
203, 370

architecture, 206

design, 271–274

emergence, 193–195

framework for integration, 190

function, 97

functional analysis, 197–198

and integration, 198–203, 238

interface, 195–197

level thread, 292

ontology of, 191

organization, 206

Parmenides and, 78

power structures, 207, 208

systemic emergent properties, 201

systemness, 192–193, 199–200

systems engineer’s concept
of system, 202

threads, 311, 312

“to manage”, 204–206, 207n

value, 132

Systemic behaviors, 369

Systemic emergent properties, 201

System-level thread, 292

Systemness, 108, 192–193, 199–200, 370

Systems engineer, 104, 231

cognitive functioning of, 218

engineer’s concept of system, 202

role, 104

view on integration, 116

work of, 229–231

Systems engineering, 4, 81n, 215–218,
370–371. See also Integration
principles; Lifecycle

acquisition cycle, 315

acquisition process, 24–25

architecture, 274–277

best practice, 104

charter of, 232–233

Clarion Call for changes in, 226–227

constraints principle, 226

determination of requirements, 223

development process, 231

for domain engineer, 232

Evergreening, 225n
Précédent

- 405/407

Suivant