298
IT operations, communicating to developers, 44
IT Professional role, 16
items, copying from one project to another, 29
iteration names for development cycles, 209
iterations, 78
for the Adventure Works scenario, 266–273
closing down the current, 248
creating, 78–79
defi ning initial, 214
guiding, 189
planning, 189
reducing the batch size for, 198
renaming default, 78
small, 184
IWarehouseAdapter interface, 233, 234
J-K
J2EE services, modeling, 100
Java applications, Allerton clients as, 240
KPAs (key project areas), 194
L
labels, hiding for endpoints, 110
languages
selecting for test projects, 139
specifying prior to implementation, 113
supported by Visual Studio 2005, 99
supported in Visual SourceSafe, 35
layers
of architecture, 94, 189
described by SDM, 47
.ldd fi les, 47, 101
.lddprototype fi le, 106, 107
lead developer
on the Adventure Works team, 263
implementing scenarios, 83
role of, 202
learning, ongoing, 181
Levels of CMM
Defi ned tier (Level 3), 194
Initial tier (Level 1), 194
Managed tier (Level 4), 194
Optimizing tier (Level 5), 194
Repeatable tier (Level 2), 194
linking service of Team Foundation Server, 226
links, 226
Links tab of a work item, 26
Linux, running Allerton from, 240
Load Agent, 169
load front end, 169
load profi le for a load test scenario, 167
load test results, 168
Load Test Runner, 168
load test scenario, 167
load testing, 65, 142, 145
load tests, 160, 167–169
load Web testing, 14
local area network (LAN) performance booster, 35
local overwrite confl ict, 135
locks, 131
logical datacenter
designing, 101
selecting to test a deployment against, 58
understanding and modeling, 94–95
validating an application against, 119
Logical Datacenter Designer, 50–55, 95, 96, 100–107
probing for servers and confi gurations automatically, 104
prototype fi le, 106
toolbox, 104, 107
logical datacenter diagrams, 45, 50
connecting endpoints in, 54
contained in a solution, 108
containing a Zone, 106
creating, 97, 100–107
defi ning element attributes, 116
developing in tandem with application diagrams, 101
in a distributed system solution, 47
fi rewalls not directly supporting, 51
logical servers contained in, 50
renaming, 101
steps for creating, 101
Logical Machines and Network Topology layer of SDM, 47
logical model, generating, 104
logical server constraints, 116
Logical server prototype, 106
logical server system, 48
logical servers
contained in logical datacenter diagrams, 50
no direct correlation with physical machines, 104
placing in Zones, 51
Logical Servers section in the toolbox, 106
Longhorn, 47
M
Mac OS, running Allerton from, 240
main menu, accessing version control, 133
main process defi nition fi le, 214–215
Managed tier (Level 4) of CMM, 194
manual test runner, 162
manual tests, 65, 159, 160–162
executing, 162
as fi rst-class project artifacts, 160
MATCH pattern fi eld, 222
maturity of a software development organization, 193
measures, 233
memory leaks, fi nding, 241
Mercury Diagnostics, 243
Mercury Interactive Corporation, 243
Mercury Performance Center, 243
IT operations
299
Mercury Quality Center, 243
merge history, updating for items, 31
Merge Wizard, 31
merging in TFVC, 30–31
merging technology, 80
metadata
capturing about components, 46
defi ning, 100
saving in spreadsheets, 43
tracking in DSI designs, 45
MetaData.xml fi le, 213, 216
metamodel
built-in rules, 27
for describing SDLCs, 175
interchangeable with framework, 178
methodologies, 8
confi guring, 72
customizing, 13
defi ning for new projects, 208
exporting existing, 73
implementing different work item types, 126
mid-course corrections to, 177
multiple supported by Team System, 208
need for, 8
perceived as an impediment to productivity, 176
popular, 8
selecting, 72–73
Team System supporting, 11–12
methodology process guidance, 179
methodology templates, managing, 39
MethodologyTemplate.xml fi le, 213, 214
editing, 218
metadata elements from, 216
methods
implementing using Object Test Bench, 130
strongly coupled, 137
metrics, recording in a central data warehouse, 209
.mht fi le, 124, 269
Microsoft, suite of tools used internally, 7
Microsoft BizTalk applications. See BizTalk applications
Microsoft Excel. See Excel
Microsoft Internet Explorer. See Internet Explorer
Microsoft Offi ce Excel. See Excel
Microsoft Offi ce Project, 24, 37, 83, 193
creating and launching documents from inside Team
Explorer, 39
installation of, 44
integrating with Team System, 17, 257
limited set of columns, 43
Professional Edition required, 43
support for Team System, 43–44
Microsoft Operations Manager (MOM)
leveraging SDM, 47
management packs, 243
possible deployment report future integration with, 123
Microsoft patterns & practices Web site, 94
Microsoft Solutions Framework. See MSF (Microsoft
Solutions Framework)
Microsoft Source Code Control Interface (MSSCCI)
plug-in, 18
Microsoft SQL Server. See SQL Server 2005
Microsoft SQL Server Reporting Services. See SQL
Server Reporting Services
Microsoft Visual SourceSafe 6.0. See Visual SourceSafe
(VSS)
Microsoft Windows SharePoint Portal Service. See WSS
(Windows SharePoint Services)
Microsoft Windows SharePoint Products and
Technologies 2003 (SDK), 236
milestones, 78
mindsets, 180–181, 196
minimum standards for code, 136
model-driven approach, 48
model-driven development, 94
modeling, value of, 93
models
fi rst-class development artifacts, 93
generating code, 93
as more than just documentation, 98
MOM. See Microsoft Operations Manager (MOM)
mouse pointer, no drop shape, 59, 120
MS Project. See Microsoft Offi ce Project
MSBuild, 36, 146, 234
MSDN Enterprise, 15
MSDN Premium Subscription, 15
MSDN Universal, 15
MSF (Microsoft Solutions Framework), 8–9, 175
evolution of, 175
incremental improvement built into, 178
management and development of, 175
process templates for Team System, 176
versions of, 176
MSF 3.0
disciplines included in, 179
foundational principles of, 178
framework compared to the MSF 4.0 metamodel, 178
Role Clusters in, 179
team member roles, 179
MSF 4.0
Advocacy Groups in, 179
agile development techniques, 176
core ideas, 180
Cycles and Iterations, 184
as a descriptive framework, 177
disciplines included in, 191
foundational principles of, 178
governance, 185
governance checkpoints, 192
implementing with Team System, 208–210
key concepts, 180–185
MSF 4.0
Get Working with Microsoft® Visual Studio® 2005 Team System now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
