Index

A
ABAP 496
access violations
    COM 510
    during debugging 510
accessing data 454–55
action planning for risks 222
Active Directory 100
Active Server Pages. See ASP
ActiveX
    client-side components 376
    and COM 401
    controls and COM 398
    controls in applications 354
    limitations of 359
    marking of 381
    and safety issues 381
    user layer use 354
ActiveX Data Objects. See ADO
active directory security interface. See ADSI
activity diagrams 214
administration costs, reducing 67
ADO 455, 474
    accessing data with 478
    cursor types 480
    errors in, handling 481
    performance 521
    programming with 476
    remote data service 481
    when to use 484
ADO object model 474
ADO objects, inline connection strings 521
adopting product mindset 58
ADSI 455
Advanced Business Application Programming Interface (ABAP) 496
Advanced Program-to-Program Communications (APPC) 495
affordances 366
alpha releases 153, 169
analysis
    in Conceptual Design 270, 272
    in Envisioning Phase 213
    in Logical Design 278–79
    in Physical Design 286, 289–92
    noun-verb 281, 283
analysis paralysis 151, 157
Analysis Workflow 136, 138
analyzing risks 220
antipatterns, design 56
apartment model 399
API 454
APPC 495
application architecture 76, 151. See also architecture
    deployment 625
    development constraints 513
    development models 132
    documentation 624
    packages 527
    services 419
Application Model. See MSF Application Model
Application Perspective 12
application program interface (API) 454
applications
    ActiveX controls in 354
    backing up 467
    beta testing for 508
    client/server 77
    and COM 389
    creating native user interface 371
    defining goals 514
    defining metrics 514
    dependencies in 509
    deploying 50, 526, 625
    designing 264
    distributed 50, 509
    distributing using logon scripts 632
    enterprise 44, 508–9
    interim releases 574
    into existing infrastructure 50
    layers 76
    logic 79
    mapping 526
    measuring performance in 515
    modification process 503
    native 360–61, 382
    partitioned, deployment 527
    partitioning, illustrated 528
    performance testing 515
    progress through MSF Phases 574
    requirements 7
    scalable 79
    scaling 50
    securing 540
    services 82
    size 48
    specifics in ASP 375
    technologies used, examples 360
    testing 504, 507–9
    UI requirements 355
    user interface options 367
    user-centric 269
    Web-based 354, 505–7
    Win32 354
architecture 4
    application 45, 63, 76, 151
    as basis for planning 25
    client/server 77
    dangers to avoid 16
    enterprise. See enterprise architecture
    forms 51
    IT 4
    limitations on scope 20
    multi-layer 78
    myths about 19
    N-tier 48, 78, 151, 265
    perspectives 12, 14
    planning 5, 16
    and projects 25
    RDS 482
    two-tier 77
    Windows NT 420
architecture-first approach 4, 5, 45, 59
architectures, Web-based as ideal 355
artifacts 170–71
AS/400 data, accessing 488
ASP 372
    application specifics of 375
    and Automation 374
    benefits of 372
    browser and display variations 373
    browser capabilities of 357
    and business logic 374
    business objects 528
    and client-side components 376
    in deployment configuration 524
    dynamic content 373
    and familiar programming model 373
    and IIS 374
    and MTS 374
    role in production channel 505
    and security 373
    Web design 505
attributes
    in Logical Design analysis 280
    and task sequences 280
authentication
    exchange with Internet Explorer 544
    Kerberos, benefits of 542
    security 540
    Web-based 543
    of Windows NT 540
    Windows NT challenge/response 544
Automation
    and ASP 374
    and COM 402
    and dual interfaces 406
    and IDispatch 402
    late binding 403

B
backing up applications 467
balancing
    submodel interaction 67
    tradeoffs 159
BAPI 496
baselines
    design 268
    in Conceptual Design 270
    performance goals 516
    in performance testing 516
    Physical Design 285
behavior 390
best practices, use of 108–9
beta
    external releases. See external product releases
    releases 153, 169
    testing applications 508
Bill of Rights 112
bottlenecks
    ADO 521
    client protocols 520
    dynamic memory allocation 522
    eliminating 516
    file DSNs 521
    identifying 516
    inline connection strings 521
    MDAC as fix for 521
    in MTS Performance Toolkit 522
    ODBC Data Source Administrator 521
    OLE DB 521
    SQL Server 520
    system administrator login 520
    system DSNs 521
    system registry access 522
bottom-up scheduling 92, 95, 162, 164, 309
budget owner 94
buffer time 158, 162–63, 165, 310
bugs 96, 153
    active 529
    classifications 530
    closing 530
    contrasted with defects 588
    decrease in tolerance for 508
    defined 529, 588
    Development team leader’s role in 529
    examples 529
    management of 529
    prioritizing 529
    priority level classifications 530
    priority levels for 588
    reactivating 529
    resolving 529, 531, 589
    severity levels 530, 588
    tolerance in Stabilizing Phase 508
    tracking 529
builds, daily 164, 590
business
    considerations in Physical Design analysis 289
    processes, researching 271
    requirements 107, 269
    rules for data access 463
Business Application Programming Interface Object (BAPI) 496
business layer 78
    main classes 388
    implementation requirements 388
business logic and ASP 374
Business Model 66–68, 70, 72–73
    impact of Internet 69
    interaction with other submodels 68
business objects
    Active Server Pages 528
    COM 504–5
    component packaging 388
    and IIS servers 527
    key design points of 388
    remote, access of 382
Business Perspective 12, 15
business services 82
    and COM 387
    implementation requirements 388
business tier 78

C
C++ objects 390
candidate technologies, in Physical Design analysis 289
Capability Maturity Model. See CMM
certificates
    client 545
    digital 544
    mapping 545
    server 545
certification
    databases 507
    environment 507
    production channel 504, 507
    production data 507
    server 504
challenge/response authentication in Windows NT 544
change control
    establishing policies 505
    importance of enforcing system 502
    process 97
change management 62, 97
CICS transactions 494
Customer Information Control System transactions (CICS) 494
class factories 397
class objects 397
classes, COM 397
client
    certificates 545
    computers, deployment 527
    documentation 625
client protocols
    bottlenecks 519
    SQL Server 519
    TCP/IP 519
    TCP/IP Sockets 519
client/server
    applications 77
    architecture 77
clients, fat 77
clustering
    in data fault-tolerance 467
    to allow fault-tolerance 634
clusters 50, 528
    deployment 528
CMM
    five layers of 640
    importance of project reviews in 641
    maturity levels 641
    and MSF 641
code
    golden 169
    number of lines 48
coding standards, traditional focus of 586
cohesion in Physical Design, rationalization 295
COM 389
    access violations 510
    and ActiveX 401
    and ActiveX controls 398
    and applications 389
    as a binary standard 394
    and Automation 402
    business objects 504–5
    and business services 387
    and class objects 397
    classes 397, 509
    communication errors 510
    components 359, 397, 418
    elements 390
    Executive Service 421
    functionality exposed in testing 509
    and globally unique identifiers 392
    goal of 389
    and GUIDGEN 392
    and GUIDs 392
    identifiers 391
    and IDispatch 402
    and IDL 393
    interfaces, requirements for 391
    and IUnknown interface 395
    language independence in 390
    library packages 412
    marshaling 399
    method calls 510
    monikers 425
    and MTS environment 417
    object lifetime management 396
    object model, compared to C++ 391
    objects 390, 425, 505
    and OLE 401
    possible unavailability of 357
    security model 407
    server packages 412
    Service Control Manager 407
    standards for applications 389
    and STAs 399
    technical challenges of 389
    terminology 390
    testing method calls 510
    threading models 399
    and vtable pointers 394
COM classes, packaging 412
COM objects, role in production channel 505
COM+ 426
    in-memory database. See IMDB
    monikers 425
    multi-service layers 425
commitment to project goal 60
common format in data conversion 629
communicating
    artifacts 171
    project vision 215, 230
    risks 216, 221
    with UML 213
communication
    challenges of 87
    improving 109
communication errors
    COM 510
    during debugging 510
communication protocols 377
company mission, aligning projects with 206
competition, research about 228
compiling project files 164
component
    interfaces 299
    model 61
    topologies, in Physical Design analysis 292
Component Object Model. See COM
component-based development 61
    models 48
components
    COM, writing 418
    COM-based 397
    defining 294
    executing 389
    locating 389
    of MDAC 470
    packaged as DLLs 398
    packaging of business objects 388
    in Physical Design implementation, defining internal structure of 300
    programming models for 297
    reusing 46–48
    standards 290
    testing 509
COMTI
    extending transactions with 493
    integrating with MTS 493
    interfaces 494
COMTI Component Builder 492
COMTI Management Console 494
Conceptual Design 265–66, 269
    analysis 270, 272
    and requirements 269
    baselines 270
    goals 269
    optimization 270, 275–76
    proof-of-concept systems in 276
    research 270
conflicts of interest 102
connected vs. connectionless modes 298
connections
    with data sources 477
    and development decisions 360
    limitations 7
    speeds in deployment, importance of 628
    types of 360
consequences of risks 217
constraints of Physical Design 287
Construction Phase 140, 142
contingency strategies for risks 223
control in Logical Design rationalization 283
controlling
    revisions 97
    risks 225
converting data in deployment 629
cookies 544
cooperative multitasking 423
coordinating with other teams 110
costs 58, 61
    of changing requirements 80
    of creating reusable components 47
    of creating test environment 50
    hardware 51
    of product support 98
    reducing administration 67
coupling in Physical Design rationalization 295
coverage testing 508
critical-path timeline 158
cursor types in ADO 480
customer
    advocate 91
    expectations, managing 92
    participation 107
    research 228
    researching 212
Customer’s Bill of Rights 112

D
daily builds 164, 590
DAO 485
data
    access. See data access
    AS/400, accessing 488
    defining 458
    dependency 462
    design 457
    fields 458
    identifying 457
    integrity 461
    modeling 456
    normalizing 461
    production 507
    records 458
    redundancy 462
    services 83
    stores. See data stores
    tables 458–59
    topologies in Physical Design 291
    types 460
    validation 463, 465–66
data access 454
    AS/400 488
    business rules 463
    challenges for distributed application developers 469
    choosing 484
    key characteristics of 487
    security 464
    selecting method 290
    strategy, choosing 486
    testing 511
    tier 79
    using ADO 478
    using UDA 455
data binding and Web browsing 384
data consumers in OLE DB architecture 472
data conversion 629
data fault tolerance, clustering 467
Data Modeling Language (DML) 460
data objects, key design points 469
data providers, OLE DB architecture 472
Data Source Administrator, creating bottlenecks 521
data source connections 477
data source names. See DSNs
data storage technology, choosing 468
data stores 454
    single 454
    using native access method 469
    tier 79
database management system. See DBMS
databases
    bug tracking 529
    certification 507
    deployment on separate nodes 525
    hierarchical 468
    indexed 468
    key value 527
    logical 526
    maintaining 466
    management system tools 511
    mapping 526
    partitioned, deployment 526
    relational 459, 468
    SQL Server 527
DBMS 454, 511
DCOM 406
    limitations in applications 359
    security difficulties 356
DCOM Component Connector, benefits 496
DCOM Connector for SAP 495
DDM processes 489
debriefing, importance of 272
debugging 510
debugging tools in testing 510
decision-making within project team 529
declarative security testing 510
defects 588. See also bugs
defining
    components 294
    data 458
deliverables 147, 170
    Functional Specification 263
    Master Project Plan 264
    Master Project Schedule 264
    Master Risk Assessment Document 226, 230
    Project Plan Approved Milestone 152, 286, 302
    Project Structure Document 226, 229
    Release Milestone 154, 623
    Scope Complete Milestone 153
    Vision Approved Milestone 149, 226
    Vision Document 207, 226–27
delivery, preparing for 154
demonstrations 60
dependencies
    data 462
    in distributed applications 509
    in enterprise applications 509
deploying applications
    for use over Internet 50
    into existing infrastructure 50
deployment 60
    applications 526
    and ASP 524
    client computers 527
    clusters 528
    conditions during 49
    connection speeds, importance of 628
    converting data 629
    databases on separate nodes 525
    Development’s role in 96
    fault-tolerance 528
    goal planning 626
    IIS on a separate node 523
    and IIS servers 527
    location 627
    mapping 526
    owner 99
    partitioned applications 527
    partitioned databases 526
    Release Milestone 623
    replication 526
    risks 621, 626
    server load 628
    single-node configuration 523
    single-node, illustrated 523
    and SQL Server 524
    system documentation 624
    testing 626
    timeline 628
    tools 625
    using e-mail 625, 633
    using logon scripts 626, 632
    using SMS 626
    with SMS system 631
    using the Web 625
    and Web pages 524
    Web-based 633
Deployment Process 630
    pilot phase 630
    previous installations, importance of 630
    zero defect in 630
design
    antipatterns 56
    baselines 268
    characteristics of 268
    Conceptual 266, 269
    data 457
    iterative 268
    Logical 266
    object-oriented, reusing 52
    overlapping 268
    patterns 52
    Physical 266
    sequencing 268
    spiral 268
    testing 60
    total participation in 108
Design Process Model. See MSF Design Process Model
Design Workflow 136, 139
designing
    applications 264
    within context 59
    with submodels 65
developer’s rights in production channel 505
Developer’s Bill of Rights 112
Developing Phase 146, 152, 572
    analysis and rationalization in 576
    coverage testing 508
    daily build 590
    deliverables of 573
    Development role in 576
    and external product releases 581
    Functional Specification in 574, 582
    illustrated 572
    implementation in 576
    and integration testing 579
    and interim milestones 579
    internal product releases in 580
    Logistics Management role in 576
    and Master Project Schedule 574, 584
    Planning Phase, compared to 573
    primary goal of 578
    Product Management role in 575
    Program Management role in 575
    and quality bar 581
    and risk assessment 578
    Scope Complete Milestone 573
    significance of 574
    similarities to other phases 573
    source code and executables 585
    steps in 576
    team member roles in 575
    testing 508
    Testing role in 576
    testing specifications for 508
    transition to Stabilizing Phase 587
    and user performance 586
    validation in 577
    versions in 153
    zero-defect mindset 589
Development 95, 170
    and Physical Design 285
    grouping by code type 102
    grouping by service layer 101
    in Planning Phase 264
    in Stabilizing Phase 620
    server 505
    single role for 102
development 95, 170
    in all phases, advantages of 167
    change control system in 502
    component-based 61
    enterprise application 63
    models for 132
    possible constraints 513
    process, scope of 86
    production channel 503
    tasks in each phase 168
    Web 502
development environment, managing 502
Development Model 66, 74
    impact of Internet 75
    interaction with other submodels 75
Development Phase, Scope Complete Milestone in 508
Development Process Model
    Developing Phase 572
    testing 508
Development role and Developing Phase 576
Development Team Model. See MSF Development Team Model
diagrams 52
    activity 214
    use case 214
dialog box control mechanisms 363
digital certificates 544
disconnected recordsets 480, 483
discoverability and user interface 370
distributed application developers, challenges of accessing data 469
distributed applications 50
    dependencies in 509
    enterprise 509
    testing 509
Distributed COM. See DCOM
Distributed Data Management (DDM) 489
distributed testing 511
distribution 298
    strategies 293
    topology 50
DLLs, components packaged as 398
DML 460
documentation 155
    application 624
    client 625
    Frequently Asked Questions (FAQ) 624
    system in deployment 624
    training 624
documents, living 157, 167
DSNs 521
dual interfaces and Automation 406
dumping to back up applications 467
dynamic memory allocation as a bottleneck 522
dynamic process, advantages 22

E
e-mail as deployment method 625, 633
ECMA Script, browser-neutral application use 358
educating teams 109
Elaboration Phase 140, 141
Enterprise Application Model 63, 65, 95
enterprise applications
    challenges of 45
    common UI characteristics in 355
    dependencies in 509
    development 63
    features of 44
    implementation requirements 63
    testing 508–9
    testing requirements 509
enterprise architecture 4, 45
    creating 19
    goals of 8
    in Physical Design analysis 290
    principles of 19
Enterprise Architecture Model. See MSF Enterprise Architecture Model
Envisioning Phase 146, 148, 206
    analysis 213
    and Master Risk Assessment 585
    pitfalls of 209
    rationalization 214
    research 211
    specification 214
    team roles during 210
error handling 298
error paths, execution in testing 510
errors handling in ADO 481
executables 153, 155
Executive Services 420–21, 423
expectations
    customer, managing 92
    of typical IT environment 6
    users, managing 99
extending transactions using COMTI 493
extensibility mechanisms 52
external product releases
    beta releases 153, 169
    and Developing Phase 581

F
fat clients 77
fault-tolerance
    deployment 528
    system, implementing 634
    testing 634
    using clustering 634
feature
    buckets 214, 228
    teams 101
features 148, 151, 228
    accepting 161
    constraining 161
    deciding which to implement 214
    determining 213
    of enterprise applications 44
    in first release 156
    optimizing 160
    owner of 92, 94
    prioritizing 162
feedback loop and project review 641
field-level files 491
fields 458, 481
files
    compiling 164
    field-level 491
    mainframe 490
    record-level 491
firewalls 50
    problem resolutions 356
    and server-side computers 356
fixed ship-date mindset 162, 309
focus, maintaining 24
fonts and user interface 369
foreign keys 459, 464
framework
    object-oriented 61
    scalable 62
free-threaded model 399
Frequently Asked Questions (FAQ) documentation 624
function
    calls, in-process vs. out-of-process 298
    teams 101, 149
Functional Specification 62, 65, 67, 263, 302
    consensus 306
    and Developing Phase 574, 582
    Development role 95
    and MSF Design Process 267
    ownership 94, 304
    in Physical Design 285
    in Planning Phase 304
    at Project Plan Approved Milestone 152
    reviewing 305, 582
    revisions 582
    at Scope Complete Milestone 153
    and user performance 586

G
globally unique identifier (GUID) 392
goals
    aligning project with business 58
    alignment of business and IT 14
    commitment to 60
    competing 67
    of Conceptual Design 269
    corresponding team roles 89
    defining 68
    in Deployment 626
    of enterprise architecture 8
    of IT solutions 8
    of MSF Design Process 266
    of MSF Enterprise Architecture Model 18
    of optimization 275
    performance 51
    of Product Management 91
    of Program Management 93
    progressing toward clearly defined 16
    project 88
    of project vision 206
    of projects 206
    of software developers 58
    in Stabilizing Phase 626
    of Testing 96
    measuring success 59
golden release 154, 169
grouping Development
    by code type 102
    by service layer 101
GUID 392
GUIDGEN, and COM 392

H
handling errors 298
hardware
    costs 51
    limitations 7
harnesses
    in MTS Performance Toolkit 516
    testing 509
hierarchical databases 468
hierarchical model 86
high cohesion 296
HTML 3.2, limitations of 358
HTTP
    and object access 384
    Web browser uses 377
human-resource management 87

I
I/O Manager 421
icons and user interface 368
IDE and user interface 371
identifiers, COM 391
identifying
    data 457
    project requirements 213
    requirements 55
    risks 61, 219
identities 106, 390
IDispatch
    and Automation 402
    and COM 402
    interface and Web-based applications 359
IDL 393
    and COM interfaces 393
    and language independence 394
IIS
    and ASP 374
    configuration settings 375
    servers. See IIS servers
    single-node installation 523
IIS servers
    and business objects 527
    deployment 527
    illustrated 527
IMDB
    as alternative to Shared Property Manager 497
    restrictions of 498
impact of risks 221
implementation
    in Physical Design 286, 297, 299
    technologies 298
Implementation Workflow 137, 139
in-memory database. See IMDB
in-process vs. out-of-process function calls 298
Inception Phase 140–41
index keys 458
indexed databases 468
Information Perspective 13
Initial Operation Capability Milestone 142
integrated milestone testing 587
integration
    into existing environment 100
    testing 511, 579
intent vs. impact 104
Interactive Development Environment. (IDE) 371
Interface Definition Language. See IDL
interfaces
    COM 391
    COMTI 494
    defining 393
    IUnknown 395
    navigation 395
    versioning 396
interim milestones 147, 303, 310
internal releases 162–63
    and Developing Phase 580
Internet
    deploying applications for use over 50
    impact on Business Model 69
    impact on Development Model 75
    scenarios 483
Internet Component Download and Web access 381
Internet Explorer, authentication with 544
Internet Information Server. See IIS
interrupt handling 421
IT
    architecture 4
    environment 6, 8, 14, 23
iterations 20, 165–66
    advantages of 22
    identifying project problems 168
    and living documents 167
    within MSF Development Process Model 165
    Spiral Model 134
    in Unified Process (UP) 143
iterative
    approach 20
    design qualities 268
IUnknown interface and COM 395

K
Kerberos authentication, benefits of 542
kernel mode 420
key design points in data objects 469
key pair 545
key value databases 527

L
language independence
    COM 390
    and IDL 394
languages 290
    Data Modeling Language (DML) 460
    modeling 49
    Unified Modeling Language (UML) 49, 51, 136
    various, for project phases 59
large projects 101
late-binding Automation 403
layers, application 76
leaders
    effective 103
    of role teams 90
    role 106
Leadership Evaluation Checklist 111
library packages 412
life cycle, project 132
Life-Cycle Architecture Milestone 141
Life-Cycle Objective Milestone 141
limitations
    on architecture scope 20
    connection 7
    hardware 7
    storage 7
lines of code, number of 48
living documents 157, 167
load balancing and Internet access 379
local integration testing 510
localization and data validation 466
location deployment 627
location transparency 50
locking recordset 479
logging on
    through MSV Authentication Package 541
    to a Windows NT system 541
logic, application 79
Logical Data Model 71
Logical Design Model 265–66, 277
    analysis 278–81
    modules 278
    rationalization 278, 282–84
Logical Model 66, 68, 70–73, 81, 95
Logical Object Model 71
Logistics Management 99, 170
    and Developing Phase 576
    in Planning Phase 264
    in Stabilizing Phase 620
logon scripts
    deployment in 632
    distributing applications with 632
    performing deployment with 626
    testing 632
loose coupling 296

M
main classes and business layer 388
mainframe files 490
maintaining databases 466
major milestones 147
management
    change 62, 97
    human-resource 87
    Logistics 99
    Product 91
    Program 93
    risk 61
    tools 111
managing
    customer expectations 92
    risks 160–61, 211, 300–302
    tradeoffs 159
    user expectations 99
many-to-many relationships 459
MAPI 455
mapping
    applications 526
    certificates 545
    databases 526
    deployment 526
    wildcards 546
marshaling 399
    remote activation 411
    unmarshaling 412
Master Project Plan 94, 264, 286, 307
    owner of 307
    Program Management responsibility for 584
    at Project Plan Approved Milestone 152, 302
    revisions in 584
    at Scope Complete Milestone 153
Master Project Schedule 165, 264, 286, 308
    contents of 584
    and Developing Phase 574
    owner of 308
    at Project Plan Approved Milestone 152, 303
    at Scope Complete Milestone 153
Master Risk Assessment
    and Envisioning Phase 585
    Program Management responsibility for 585
    and risk management 577
Master Risk Assessment Document 149, 222, 226, 230, 286
    at Project Plan Approved Milestone 152, 303
    revising 301, 311
    at Scope Complete Milestone 153
maturity levels
    challenges of 641
    CMM 641
MDAC 456
    as fix for bottlenecks 521
    components of 470
memory
    Virtual Memory Manager 421
    Windows NT controlling access to 420
menus, Windows UI use 370
message pump 400
Messaging API (MAPI) 455
Microsoft Certificate Server 546
Microsoft Consulting Services 111
Microsoft Data Access Components. See MDAC
Microsoft Excel for risk tracking 98
Microsoft Index Server 456
Microsoft Management Console (MMC) 100
Microsoft Solutions Framework. See MSF
Microsoft Transaction Server. See MTS
Microsoft Visual SourceSafe 97
Microsoft Windows 2000 100
Microsoft Windows NT Directory Service API (ADSI) 455
Microsoft Word revision marks 97
milestones 20
    interim 147, 310
    major 147
    and MSF Development Process 642
    MSF Development Process Model 147
    Project Plan Approved 151, 263, 286, 302
    Release 154, 619
    reviewing 108
    roles 170
    Scope Complete 153
    Vision Approved 149, 207, 222, 226
mindsets
    fixed ship-date 162, 309
    product 106, 166
    zero-defect 107
mirroring, to back up applications 467
modeling
    data 456
    Data Modeling Language (DML) 460
    elements 52
    languages 49
    Unified Modeling Language (UML) 49, 51, 136
models 132
    Business Model. See Business Model
    component 61
    component-based development 48
    Conceptual Design Model 265
    Development Model. See Development Model
    Enterprise Application Model. See Enterprise Application Model
    Logical Design Model. See Logical Design Model
    Logical Model. See Logical Model
    MSF Design Model 172
    MSF Development Process Model 145, 170
    MSF Development Team Model 88, 90
    MSF Enterprise Architecture Model 171–72
    MSF Risk Management Model 309
    Physical Design Model. See Physical Design Model
    Physical Model. See Physical Model
    programming 297–98
    relationships between 171
    Spiral Model. See Spiral Model
    team vs. hierarchical 86
    Technology Model. See Technology Model
    threading 298
    Unified Process. See Unified Process (UP)
    User Model. See User Model
    Waterfall Model. See Waterfall Model
modes, connected vs. connectionless 298
modules in Logical Design 278
monikers 425
MSF 9
    adapting 88
    advantages of 109
    and CMM 641
MSF Application Model 11, 82, 277
MSF Design Model 172
MSF Design Process Model 10, 264, 265
    and Functional Specification 267
    goals of 266
    and Planning Phase 263
MSF Development Process Model 75, 145
    characteristics of 146
    Developing Phase 574
    Envisioning Phase 206
    iterations within 165
    milestones 147
    phases 146, 155
    Planning Phase 262
    principles of 155
    relationship with MSF Development Team Model 155
    roles 170
    versioned releases 148
MSF Development Team Model 75, 88, 90
    advantages of 155
    relationship with MSF Development Process Model 155
    roles of 90
MSF Enterprise Architecture Model 10–11, 171–72
    characteristics of 18
    focus 24
MSF Process Model for Application Development. See MSF Development Process Model
MSF Risk Management Model 10, 309
MSF Team Model for Application Development. See MSF Development Team Model
MSV Authentication Package, logging on through 541
MTS
    application package deployment 527
    and ASP 374
    business objects 382
    COM implementation in 417
    in distributed application environment 509
    in enterprise applications 509
    and IIS 375
    Performance Toolkit 516, 522
    surrogate, launching 510
    testing 509
    transactions 494
    using with COMTI 493
MTS Performance Toolkit
    examples of bottlenecks from 522
    test harness samples 516
    testing with 516
multi-layer architecture 78, 82
multi-tier systems, tuning 624
multitasking
    cooperative 423
    overview 422
    pre-emptive 423
multithreading 423