Engineering Complex Systems With Models and Objects

with Models and Objects......Page 1
Goals of the Book......Page 5
Audience......Page 6
Table of Contents......Page 9
1.1.1 This Book......Page 17
1.1.2 Systems Engineering as a Discipline......Page 19
1.2.1 Global Economic and Technical Change......Page 20
Importance of systems engineering......Page 21
1.3 The Gap......Page 22
Prior experience in other disciplines......Page 23
Closing the gap in the engineering of complex systems......Page 24
1.4 Definitions......Page 25
1.4.3 Model......Page 26
1.4.8 Optimization......Page 27
Things or objects......Page 28
Classification......Page 29
1.5.2 Basic abstractions used with behavior......Page 30
1.6.1 Principles of modeling......Page 31
1.6.2 An example of modeling......Page 32
1.8 Exercises......Page 33
1.9 References......Page 34
2.1.1 Structure and behavior......Page 37
2.1.2 Basic views of structure......Page 38
2.1.3 Executable models of structure......Page 39
2.2 Example - Modeling a Pocket Knife......Page 42
2.3.1 Definition......Page 43
Class name......Page 44
Class attributes......Page 45
Instances......Page 46
Figure 2-6. Initial Class Definition for Pocket Knife......Page 47
2.3.4 Example: pocket knife instances......Page 48
2.4.1 Modeling aggregation in OMT......Page 49
Figure 2-8. Aggregation used to model the structure of the universe......Page 50
Figure 2-9. Pocket knife disassembled......Page 51
Figure 2-10. Parts tree for pocket knife......Page 52
Figure 2-11. Parts tree for six tool pocket knife......Page 53
2.6 Classification of Objects......Page 54
Figure 2-12. Cardinallity and conditions expressed in OMT......Page 55
2.6.2 Example - classification of tools......Page 56
Figure 2-15. Types of tools for class tool......Page 57
Figure 2-16. Multitool pocket knife family......Page 58
Input/Output and interconnection......Page 59
2.7.3 Example: multitool pocket knife context......Page 60
2.8 Roles......Page 62
Figure 2-18. Assembly Interconnections for Metal Knife Case......Page 63
Interconnection applied to:......Page 64
2.12 References......Page 65
3.1 Introduction to Behavior......Page 67
3.1.1 Elements of behavior......Page 68
3.1.3 This chapter......Page 69
3.3 Functional Flow Block Diagrams......Page 70
Concurrency......Page 71
Selection......Page 72
3.3.3 Example: pocket knife......Page 73
Figure 3-7. FFBD for person using pocket knife......Page 74
Example: behavior hierarchy......Page 75
3.3.5 Input and output......Page 76
Figure 3-11. Behavior diagram for pocket knife......Page 77
Figure 3-12. Behavior diagram for person using pocket knife......Page 78
Figure 3-13. Behavior diagram for pocket knife in its context......Page 79
3.5 Representation of Behavior as State......Page 80
Figure 3-15. Data flow elements for pocket knife context......Page 81
Figure 3-16. States in statecharts......Page 82
3.6 Pocket Knife Example, Summary......Page 83
3.7.2 Input/output......Page 84
3.7.4 Control operations......Page 85
3.8 Information Model for Input/Output......Page 86
Figure 3-19. Information model for input/output......Page 87
3.9 Relationship of Behavior and Structure......Page 88
Figure 3-20. Behavior and structure information model......Page 89
3.10 Models and Text for Requirements/Specifications......Page 90
3.11 Summary for Behavior......Page 91
3.13 References......Page 92
4.1 Process......Page 95
4.1.1 Process, methodology, and tools......Page 96
Figure 4-1. Associations between metaprocess, methodology tools and infrastructure......Page 97
Figure 4-2. Parts list for systems engineering process......Page 98
Figure 4-3. Associations of process, product life cycle and acquisitions......Page 99
Figure 4-4. Extended part list for system engineering process......Page 101
Systems engineering management tasks......Page 102
Figure 4-5. Model for the system engineering process......Page 103
Figure 4-6. FFBD view for the system engineering core technical process......Page 104
4.2.1 The six steps in the core technical process......Page 105
Define effectiveness measures......Page 106
Create structure model......Page 107
Iterate to find a feasible solution......Page 108
Application at each tier.......Page 109
4.3.1 Small Systems vs. Large Systems......Page 110
System tier: core process applied to my product. Use to review context and requirements. Use to c.........Page 111
Table 1: Tiers......Page 114
4.4 Re-Engineering......Page 115
Figure 4-8. Behavior model for the system engineering core technical process......Page 116
4.7 Exercises......Page 117
4.8 References......Page 118
5.1 What Core Step 1 Is......Page 119
5.2 A Requirements Taxonomy......Page 120
Figure 5-1. Associations of available information......Page 121
5.2.1 Classification by origin......Page 122
5.2.2 Classification by the work needed to be done......Page 123
5.2.3 Classification by their use......Page 124
Figure 5-3. Information model for requirements......Page 126
5.3.1 Decomposition of the behavior of core step 1......Page 127
Figure 5-4. Functional flow block diagram decomposition of core step 1......Page 128
5.5 Exercises......Page 130
5.6 References......Page 132
6.2 Importance of Effectiveness Measures......Page 133
Figure 6-1. Context for systems engineering......Page 135
6.4 How effectiveness measures drive the solution......Page 136
Figure 6-3. Timeline......Page 137
6.4.2 Problem: system 2......Page 138
6.4.3 Problem: system 3......Page 139
Figure 6-8. Behavior of System 3......Page 140
6.5 Types of Effectiveness Measures......Page 141
6.6 Priorities among Effectiveness Measures......Page 142
6.7 Information Model for Core Step 2.......Page 143
Figure 6-10. Information model for create effectiveness measures......Page 144
Figure 6-11. FFBD view of define effectiveness measures, core step 2......Page 145
Figure 6-12. Two resources......Page 146
6.10 References......Page 147
7.1 What Core Step 3 Is......Page 149
Figure 7-1. FFBD view of core step 3......Page 150
Figure 7-2. Context diagram for bottling wine......Page 153
Time duration or probabilities associated with the excitation scenario......Page 154
7.3.6 Effectiveness Measures......Page 155
Top-level behavior......Page 156
Figure 7-5. Gathering supplies for bottling wine......Page 157
7.3.8 Emergent Behavior......Page 158
Figure 7-7. Completed functional flow block diagram, bottling wine......Page 159
7.3.9 Completing the behavior: adding inputs and outputs......Page 160
7.3.10 Views of behavior......Page 161
Figure 7-11. Data flow diagram for bottling wine......Page 162
Figure 7-12. Reformatted data flow diagram for bottling wine......Page 163
7.3.11 Behavior, structure, and effectiveness measures......Page 164
7.5 Behavior, Context and Traceability: An Information Model......Page 166
7.5.2 Explanation of the Behavior Region......Page 167
Figure 7-14. Information model for text requirements, behavior, and context......Page 168
Design and traceability......Page 169
7.7 Summary......Page 170
7.8 Exercises......Page 171
7.9 References......Page 172
8.1 What Core Step 4 Is......Page 173
Figure 8-1. FFBD view of core step 4......Page 174
8.3.2 The first parts selection: define objects......Page 177
8.3.3 The first parts list or aggregation......Page 178
8.3.4 Allocate functions......Page 179
Case 1: allocation to one person......Page 180
Case 2: allocation to three people......Page 181
Case 4: allocation in the context of the problem......Page 182
8.4 Information Model for Structure......Page 183
Figure 8-6. Information model for text requirements, structure, and context......Page 184
8.5 Architecture and Design......Page 185
Table 3: Application of Core Process for Design......Page 186
Table 4: Application of Core Process for Architecture......Page 187
8.6 Architecture, Applications, Effectiveness Measures and Reuse......Page 188
8.7 Summary......Page 189
8.8 Exercise......Page 190
8.9 References......Page 191
9.1 What Core Step 5 Is......Page 193
Simulation.......Page 194
Estimation.......Page 195
9.2.3 Calculate system performance......Page 196
9.2.7 Display system effectiveness......Page 197
9.3 Information Model......Page 198
9.4 The Problem of Tool Integration......Page 199
9.4.1 Prerequisites for tool integration......Page 200
Rigorous capture of details......Page 201
Semiautomated search of the system design space......Page 202
9.5 Exercises......Page 203
9.6 References......Page 204
10.1 What Core Step 6 Is......Page 205
10.2.1 Network scheduling approaches......Page 207
10.2.2 Resource allocation......Page 208
10.3 Behavior Model for Core Step 6......Page 209
10.4 Information Model for Core Step 6......Page 210
Figure 10-2. Information model for core step 6......Page 212
10.5 A Check-off List for Planning Plan......Page 211
10.6 Exercises......Page 214
10.7 References......Page 215
11.1 What Concept Analysis Is......Page 217
11.2 Applying the Core Technical Process to Concept Analysis......Page 218
Table 11.1: Modeling Items......Page 219
Initial information for an automated teller machine system......Page 220
Requirements for the ATM system......Page 224
Defining effectiveness measures......Page 225
Effectiveness measures for the bank......Page 226
Preference for the ATM system......Page 227
Which transactions to automate......Page 228
11.4.1 Structure of the bank with the system, core step 4.5......Page 229
11.4.2 Effectiveness measure for bank with the system, core step 2......Page 230
Figure 11-7. Classes of bank......Page 231
Figure 11-9. View of behavior of individual customer using the ATM system......Page 232
Figure 11-10. View of behavior of the ATM system......Page 233
11.4.4 Trade-off analysis of the bank with the ATM system, core step 5......Page 234
Table 11.2: Feature Benefits to Bank......Page 235
11.4.5 Create the sequential build and test plan, core step 6......Page 236
11.7 References......Page 238
12.1 What System Analysis Is......Page 239
12.2.2 The three concurrent core steps, 2, 3, and 4......Page 240
12.2.4 Structure of the context of the ATM System, core step 5......Page 241
Figure 12-1. Context of ATM System......Page 242
Figure 12-2. Kinds of Thief......Page 243
Figure 12-4. View of behavior of mugger......Page 244
Figure 12-6. Sub-systems of ATM System......Page 245
Figure 12-7. View of system behavior......Page 246
Figure 12-8. ATM Machine......Page 247
Scenario 3......Page 248
Scenarios 1 to 4......Page 249
12.3.3 Structure implications of the theft scenarios, core step 4......Page 250
Figure 12-10. Classification of Secure Locations......Page 251
Figure 12-11. Kinds of ATM machines, modified......Page 252
12.3.4 Response of ATM machine to ATM customer......Page 253
Figure 12-12. Behavior of ATM machine......Page 254
12.3.5 Structure of the ATM machine and related objects, core step 5......Page 255
Figure 12-13. Associations with ATM machine......Page 256
12.4 Exercises......Page 257
12.5 References......Page 258
13.1 What Subsystem Analysis Is......Page 259
Impact of Installation and Field Service......Page 260
Figure 13-2. View of response of ATM machine to thief......Page 261
13.3.1 Effectiveness measure for the ATM machine, core step 2......Page 262
13.3.2 Structure of the ATM machines, core step 5......Page 263
Figure 13-3. Kinds of ATM machines, modified......Page 265
Figure 13-4. ATM machines, parts list and associations......Page 266
Attributes and Allocation of Behavior......Page 267
Software Components......Page 268
Figure 13-8. The five ATM machines......Page 269
13.4 Exercises......Page 270
13.5 References......Page 271
14.1 What Handoff Is......Page 273
14.2 Context For Handoff......Page 274
14.3 ATM Handoff to User Interface......Page 275
Models......Page 276
Effectiveness measures......Page 277
14.3.2 Parallel design steps......Page 278
Figure 14-4. Behavior of display start instruction......Page 279
Figure 14-5. Structure of user interface components......Page 280
Figure 14-7. User Interface mock-up prompting for a transaction selection......Page 281
Figure 14-8. Fragements of executable code produced by user interface mockup tool......Page 283
14.4.1 Available database information......Page 282
Structure......Page 284
Figure 14-9. View of ATM machine database behavior......Page 285
Figure 14-10. View of ATM machine database structure......Page 286
14.5 Handoff......Page 287
14.7 References......Page 288
15.2 Introduction of Modeling into Business Cultures......Page 289
15.3 Commercial Product/Service Development Businesses......Page 291
15.4 Modeling and Aerospace Acquisition......Page 294
15.4.1 Relativity of systems: products......Page 296
15.4.3 Requirements come from the tier above......Page 297
Figure 15-2. Renaming of P1220 System-part breakdown......Page 298
Figure 15-3. The P1220 system engineering process......Page 299
15.5 Summary......Page 300
15.6 Exercises......Page 301
15.7 References......Page 302
16.1 Tailoring Metaprocess to Methodology......Page 303
16.3 Views of Information in Systems Engineering......Page 305
Figure 16-1. Possible views of behavior and structure......Page 306
Views of behavior and notations......Page 307
16.3.3 Equivalences - statechart and functional flow block diagrams......Page 308
Figure 16-4. Statechart view of core technical steps......Page 309
16.5 Discovery and the Change Control Process......Page 310
Figure 16-5. FBBD view of the change control process......Page 311
16.5.2 Change to the system, upper branch......Page 312
16.5.3 Process improvement......Page 313
16.6 Concluding Remarks......Page 314
16.8 References......Page 315
Figure 17-1. Semantics and symbols for executable structure......Page 317
Figure 17-2. Information model for behavior......Page 318
Figure 17-3. Information model for input/output......Page 319
Figure 17-4. Behavior and structure information model......Page 320
Figure 17-5. Associations of metaprocess, methodology, tools, and infrastructure......Page 321
Figure 17-6. Associations of process, product life cycle and acquisition......Page 322
Figure 17-8. FFBD view for the system engineering core technical process......Page 323
Figure 17-9. Sequential application of core technical process to context and subject......Page 324
Figure 17-10. Functional flow block diagram decomposition of core step 1......Page 325
Figure 17-12. FFBD view of core step 3......Page 326
Figure 17-14. FFBD view of core step 5......Page 327
Figure 17-15. FFBD view of core step 6......Page 328
Figure 17-16. Information model for requirements......Page 329
Figure 17-17. Context for systems engineering......Page 330
Figure 17-18. Information model for create effectiveness measures......Page 331
Figure 17-19. Information model for text requirements, behavior, and context......Page 332
Figure 17-20. Information model for text requirements, structure, and context......Page 333
Figure 17-21. Information model for perform trade-off analysis......Page 334
Figure 17-22. Information model for core step 6......Page 335
Figure 17-23. Tiers of analysis and decomposition/synthesis......Page 336
D......Page 337
P......Page 338
V......Page 339