IBM SC34-4499-03 Uživatelský manuál Strana 31
- Strana / 356
- Tabulka s obsahem
- KNIHY
Hodnocené. / 5. Na základě hodnocení zákazníků
the parts modified for the specified defect or feature in one release and
records the status of the defect or feature. The work area moves through
successive states during its life cycle. The TeamConnection actions that you
can perform against a work area depend on its current state.
You must use the
track subprocess
if you want to use any of the other release
subprocesses.
approval
This subprocess ensures that a designated
approver
agrees with the decision
to incorporate changes into a particular release and electronically signs a
record. As soon as approval is given, the changes can be made.
fix This subprocess ensures that as users check in parts associated with a work
area, an action is taken to indicate that they have completed their portion.
When everyone is done, the owner of the
fix record
(usually the component
owner) can change the fix record to complete. The parts are then ready for
integration.
driver A
driver
is a collection of all the work areas that are to be integrated with each
other and with the unchanged parts in the release at a particular time. The
driver subprocess allows you to include these changes incrementally so that
their impact can be evaluated and verified before additional changes are
incorporated. Each work area that is included in a driver is called a
driver
member
.
test The test subprocess guarantees that testing occurs prior to verifying that the
fix is correct within the release.
TeamConnection is shipped with several predefined processes. If these do not apply to
your organization, you can configure your own processes by defining different
combinations of subprocesses.
See “Chapter 4. The states of TeamConnection objects” on page 41 for an explanation
of TeamConnection states.
Build
The TeamConnection build function automates the process of building individual parts
or entire applications, both in the work group LAN environment and on an enterprise
server. This function enables you to reliably and repeatedly build the same output from
the same inputs. You can also build different outputs from the same inputs for different
environments.
You start a build against an output part that has an associated
builder
. A builder is an
object that describes how to translate input parts to get the desired output, such as a
linker or compiler. An input part might have an associated parser, which determines the
dependencies for the input parts in a build.
The build function does the following:
Chapter 1. An introduction to TeamConnection 11
- User’s Guide 1
- Contents 5
- Contents v 7
- Contents vii 9
- Contents ix 11
- Trademarks 17
- About this book 19
- Tell us what you think 20
- 2 User’s Guide 22
- TeamConnection definitions 24
- TeamConnection database 25
- Interfaces 25
- Families 26
- Users and host lists 26
- Components 27
- Releases 28
- Work areas 28
- Defects and features 30
- Processes 30
- Packaging 32
- Roles people play 32
- 14 User’s Guide 34
- Using the GUI 37
- Starting the GUI 38
- Stopping the GUI 39
- Performing tasks with the GUI 39
- Using the Settings notebook 40
- Online help information 41
- 22 User’s Guide 42
- 24 User’s Guide 44
- Laying the groundwork 45
- Authority to perform tasks 46
- Finding parts 47
- Using work areas 48
- Naming your work areas 49
- Creating parts 49
- Naming your parts 50
- Preparing to build your parts 50
- Working with parts 51
- Working with common parts 52
- PartExtract 53
- PartCheckOut 53
- Commands Reference 53
- 34 User’s Guide 54
- Versioning releases 55
- Versioning work areas 56
- Versioning drivers 57
- Versioning parts 58
- 40 User’s Guide 60
- 42 User’s Guide 62
- 44 User’s Guide 64
- The states of work areas 65
- 46 User’s Guide 66
- The states of drivers 67
- 48 User’s Guide 68
- Verification and test records 69
- 50 User’s Guide 70
- Working in serial development 71
- Creating a work area 73
- Searching for a part 75
- 56 User’s Guide 76
- Checking in a part 78
- 60 User’s Guide 80
- Figure 12. Build Parts window 81
- Extracting a part 82
- Figure 14. Check Out Parts 83
- Checking the part back in 84
- Integrating the work area 88
- Closing a defect 89
- 70 User’s Guide 90
- Reconciling differences 93
- 74 User’s Guide 94
- 76 User’s Guide 96
- Changing the defect owner 79 97
- Accepting the defect 80 97
- 78 User’s Guide 98
- Changing defect ownership 99
- Accepting a defect 100
- Approving the fix 101
- Checking out a part 102
- Checking in the changes 103
- 84 User’s Guide 104
- Freezing the work area 105
- Building the application 106
- Accepting fix records 107
- Adding a driver member 108
- Reconciling the differences 109
- Reactivating the fix record 110
- Refreshing the work area 110
- Refreshing the driver 111
- Building the driver 112
- Restricting the driver 113
- Integrating the parts 114
- Completing the driver 115
- Testing the built application 116
- Using a configured process 117
- 98 User’s Guide 118
- 100 User’s Guide 120
- 102 User’s Guide 122
- Databases 123
- Sources of user information 124
- Database types 125
- Forms and subforms 126
- 108 User’s Guide 128
- Document archiving 129
- 110 User’s Guide 130
- 112 User’s Guide 132
- 114 User’s Guide 134
- 116 User’s Guide 136
- Performing reconciliation 138
- 120 User’s Guide 140
- 122 User’s Guide 142
- Notes Database Customization 143
- Modify TeamConnection Access 144
- Advanced customization 145
- 126 User’s Guide 146
- 128 User’s Guide 148
- The build object model 150
- 132 User’s Guide 152
- Working with a build tree 153
- 134 User’s Guide 154
- Putting the pieces together 155
- 136 User’s Guide 156
- Installing the build function 157
- 138 User’s Guide 158
- 140 User’s Guide 160
- Starting an MVS build server 161
- 142 User’s Guide 162
- 144 User’s Guide 164
- Stopping the build servers 165
- Stopping an MVS build server 165
- 146 User’s Guide 166
- Creating a builder 167
- 148 User’s Guide 168
- Writing a build script 170
- 152 User’s Guide 172
- Writing a simple build script 173
- Testing a build script 174
- Putting a builder to work 175
- 156 User’s Guide 176
- 158 User’s Guide 178
- 160 User’s Guide 180
- 162 User’s Guide 182
- Writing an MVS build script 183
- File name conversions for MVS 184
- Supported JCL syntax 186
- EXEC statement 186
- DD STATEMENT 187
- 168 User’s Guide 188
- 170 User’s Guide 190
- 172 User’s Guide 192
- 174 User’s Guide 194
- Creating a parser 195
- 176 User’s Guide 196
- Writing a parser command file 197
- Putting a parser to work 198
- Removing a parser from a part 199
- 180 User’s Guide 200
- 182 User’s Guide 202
- Starting the build servers 203
- Creating builders and parsers 204
- 186 User’s Guide 206
- 188 User’s Guide 208
- 190 User’s Guide 210
- 192 User’s Guide 212
- Canceling a build 214
- More sample build trees 215
- 196 User’s Guide 216
- -release 9503 217
- 198 User’s Guide 218
- 200 User’s Guide 220
- 202 User’s Guide 222
- 204 User’s Guide 224
- Command line flags 226
- 208 User’s Guide 228
- 210 User’s Guide 230
- 212 User’s Guide 232
- 214 User’s Guide 234
- 218 User’s Guide 238
- 220 User’s Guide 240
- Sample package file 241
- 222 User’s Guide 242
- 224 User’s Guide 244
- Part 6. Appendixes 245
- 226 User’s Guide 246
- 228 User’s Guide 248
- 230 User’s Guide 250
- 232 User’s Guide 252
- Setting environment variables 254
- 236 User’s Guide 256
- Creating a rules file 257
- 238 User’s Guide 258
- 240 User’s Guide 260
- TeamConnection 261
- Project actions 262
- Part actions 263
- 244 User’s Guide 264
- 248 User’s Guide 268
- TeamConnection Bridge 269
- Scope of this documentation 270
- Basic functionality 270
- Prerequisites 272
- Environment variables 272
- 254 User’s Guide 274
- Setting default properties 275
- Context page 276
- Operations page 276
- Import page 277
- Export page 278
- Exporting files 280
- Scenario assumptions 281
- 262 User’s Guide 282
- Build generation 283
- 264 User’s Guide 284
- Making a change to a member 285
- 266 User’s Guide 286
- Projects vs Families 287
- 268 User’s Guide 288
- Before you start 289
- Opening a project 290
- Integrated features 290
- Migrating project data bases 292
- Starting a new project 293
- 274 User’s Guide 294
- 276 User’s Guide 296
- 278 User’s Guide 298
- 280 User’s Guide 300
- 282 User’s Guide 302
- 284 User’s Guide 304
- 286 User’s Guide 306
- 288 User’s Guide 308
- 290 User’s Guide 310
- 292 User’s Guide 312
- 294 User’s Guide 314
- 296 User’s Guide 316
- 298 User’s Guide 318
- 300 User’s Guide 320
- Sample REXX execs 321
- 302 User’s Guide 322
- 304 User’s Guide 324
- Sample build scripts 325
- Sample parsers 326
- Sample package files 326
- Customer support 327
- 308 User’s Guide 328
- Bibliography 329
- 310 User’s Guide 330
- Related publications 331
- 312 User’s Guide 332
- Glossary 333
- 314 User’s Guide 334
- Glossary 315 335
- 316 User’s Guide 336
- Glossary 317 337
- 318 User’s Guide 338
- Glossary 319 339
- 320 User’s Guide 340
- Glossary 321 341
- 322 User’s Guide 342
- Special Characters 343
- 324 User’s Guide 344
- (continued) 345
- 326 User’s Guide 346
- 328 User’s Guide 348
- 330 User’s Guide 350
- 332 User’s Guide 352
- BUSINESS REPLY MAIL 354
- SC34-4499-03 356
LG V-4030T Handbücher
Bedienungsanleitungen und Benutzerhandbücher für Staubsauger LG V-4030T.
Wir stellen 1 PDF-Handbücher LG V-4030T zum kostenlosen herunterladen nach Dokumenttypen zur Verfügung Bedienungsanleitung
Komentáře k této Příručce