“ilities” (systems attributes), 13, 213–214

Implementation, 207–210

• defined, 209

• downstream influences on, 207–210

Inbound marketing, 201, 202–203

Incremental system deployment, 385

Inference algorithm, 441

Influences on system architecture

• downstream influences, 207–217

• principle of architectural decisions, 197

• product case for, 217, 219–221

• upstream influences, 198–207

Initiatives and action plans, corporate strategy, 201

Integral system entities, 19

Integrated concepts, 152–156, 274–279

• concept fragments for, 153–154

• creativity applied to, 274–279

• evolution and refinement of, 274–277

• flexibility of, 154

• form-to-function mapping of, 274–275

• morphological matrix for, 153–156

• selection of for further development, 277–279

Integrated 3D models, 45–48

Intelligence activity, 318

Intent, 139–144

• concept development and, 143–144

• defined, 140

• functional, 139, 141, 146, 149, 153

• Level 2 architecture, 166

• regulatory, 205

• solution-neutral functions, 139–142

• specialization of solution neutral functions using, 143–144

Interferences, 373

Interferences as rules, 443–445

Internal block diagram (SysML), 46, 47, 70

Internal function, 94–98, 107–108

• identification of, 94–95

• predicting emergence of, 96

• process-operand (PO) array for, 96–97

• standard blueprints of processes, 95

• principle value-related, 94

• secondary value-related, 107–108

International Council on System Engineering (INCOSE), 45

IP packet, 172

IT architecture, 254–259

• goal requirements, 256–257

• mappings for, 257–258

• Olympic system challenge, 254–255

• reliability through redundancy, 258–259

• stakeholders and, 254–259

• system boundary of, 255–256

• utility applications, 257–258