295
designing for operations, 45
details, 233
Details tab in Web Test Runner, 166
developer branch, 34
Developer Manager role, 202
Developer role, 16, 187, 202
developers. See also development manager; lead
developer
on the Adventure Works team, 263
forcing to implement best practices, 136
impact of restrictions on, 153
implementing Web services, 112
reports and, 152
restricting, 153
role of, 125
synchronizing code changes with visual design, 96
Team edition for, 14
tools for, 62–65
tracking for Sarbanes-Oxley, 34
work streams, 190
Developer/Tester role, 16
development
advocates for the technical solution, 265
allocating resources based on the fl ow of value, 185
xing bugs during, 135
model-driven approach to, 48
with a process, 154
solving problems, 6
structure for, 125
team-based, 24
Development advocacy group, 200
development constituency advocate, 183
development life cycle build, 125
development manager, 202
development organization, assessing the maturity of, 193
development tasks, 87, 188, 190, 207
assigning work, 86
implementing, 190
in a scenario, 190
development team, 4, 5–7
Diagnostics. See Mercury Diagnostics
diagrams. See also Distributed Application Diagrams
(DAD)
creating in Application Designer, 108–110
creating in Logical Datacenter Designer, 100–107
dimensions, 233
direct connection over HTTP, 54
disciplines, 179, 191
defi ned by MSF for CMMI Process Improvement, 207
in MSF 3.0, 179
in MSF 4.0, 191
multiple accommodated by CMMI, 195
in process guidance, 179
removed from the metamodel, 179
specializing CMM for, 194
distributed application designers. See visual designers
Distributed Application Diagrams (DAD), 45. See also
diagrams
Distributed System Designers, 50–61
Distributed Systems Designer prototype fi le, 48
Distributed Systems Designers, 44–45
editor used by all, 116
extending in Team Architect, 48
security supported by, 97
storing SDM information, 47
in Team Edition for Software Architects, 95, 96–100
distributed system solution, 47
Distributed System Solutions projects, 56
DLL (dynamic-link library), 128
document libraries
adding and managing, 38
creating, 74
quality of service requirements list, 85
documentation of bugs, 88
documents
adding and managing, 38
uploading, 81
dogfooding, 28
DREAD, tracking, 126
drop location, 149
DSI (Dynamic Systems Initiative), 14, 45–46, 96
DSL (Domain-Specifi c Language) tools, 48–61, 63
DSLs (Domain Specifi c Languages), 96
Duplicate bug, 88, 89
Dynamic Systems Initiative (DSI), 14, 45–46, 96
dynamic-link library. See DLL (dynamic-link library)
E
Eclipse Plugin, 240
Eclipse RCP application, 240
editing sessions, viewing changes made during, 65
editions of Team System, 71
ELead, 287
embedded diagrams in the HTML deployment report,
121
embedded Hosts in Zones, 102
EMPTY fi eld, 221
endgame, 247
Endpoint prototype, 112
endpoint specifi cations, propagating, 112
endpoint types, 105, 110
endpoints, 103, 110
adding to a logical datacenter diagram, 101
in the Application Designer toolbox, 109
checking for compatible, 120
connecting, 54, 105–106, 110–111
contained in a logical server system, 48
defi ning constraints on, 103
lining up for two services, 106
selecting in Deployment Designer, 59
endpoints

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.