Index


A

Abbreviations, conventions for using, 409

Abuse cases, defined, 118

Academic Edition (Visual Studio .NET), 24

Access and usage privilege, 119

Accessibility (for web sites), 114-125

requirements, 114

validating, 115, 372-373

Accessible applications, need for, 98-99

Account properties, examples of, 213

Accounts, deleting inactive, 86

ACLs (access control lists), 190

ACT (Application Center Test) Project template, 22

Action verbs, in user requirements, 289-290

ActiveX documents, .NET and, 12

Activity diagrams (UML), 296

Actors (use case), 87-90

communication links, 90

user profiles for, 96

Add Reference dialog box (Visual Studio .NET), 178

Administrator user documents, 394

ADO (ActiveX Data Objects), 6, 13

ADO versions of, 9

Adobe Photoshop, 307

ADO.NET, 7

ADO.NET classes, 18, 269, 308

ADO.NET data access classes, 18

Aesthetics, of user interface, 418

After-the-fact security, 339

Ambiguity, removing from schema, 218

Americans with Disabilities Act, 98

Analyzing Requirements and Defining .NET Solution Architectures exam, 4, 463-470

Animations, accessible, 115

Anti-virus software, as a Windows service, 357

Apache Enterprise Ready Server (ERS), 30

Apache 2.0, enterprise-level version of, 30

API (Application Programming Interface), 357

APIs, designing for backward compatibility, 357

Applets, accessible, 115

Application architecture, 295

and current business processes, 300

for enterprise application, 56

selection of, 151

services and, 151

Application bugs. See Bugs

Application Center 2000, 362

Application domain, defined, 104

Application errors, 343

analyzing potential, 344

categories of, 343

identifying potential, 299

Application event log (Windows), 341

Application failures, reasons for, 158

Application functionality behaviors, 294

Application integration

considerations for, 346-348

specifications for, 345-348

Application interface (services and components), 308

Application interoperability, 165

Application isolation, explained, 9

Application languages. See Programming languages

Application layers, 266, 269

Application logging, purposes for, 339

Application menus, designing, 356

Application model packages, 296

Application monitoring, 162-163

designing, 367-368

tools for, 367

Application object attributes, identifying, 294

Application object behaviors, identifying, 292-293

Application object functions or methods, 290

Application object methods, identifying, 292-293

Application objects

creating and loading, 292

deleting, 292

establishing or severing relationships, 292

grouping, 297

identifying potential, 288-292

logical relationships between, 295

mandatory behaviors of, 292

Application packages, transaction servers for, 271

Application partitions, 10

Application queries

analyzing performance of, 370

execution plans for, 369

Application security, integrating with Windows, 352

Application site map, building, 264-265

Application state, in distributed environment, 310

Application support staff, access to application code for, 366

Application thread, 308

Application-defined exceptions, 299-300

Applications (see also Software)

categories of, 287-288

consuming of web services, 14

distributed, 6-7

identifying major, 124

Applications inventory, 123

Application-specific exceptions, 299

Appointment object (calendar application), 292, 294

Architect Version of Visual Studio .NET, 88

Architecture (application). See Application architecture

Architecture documents, 393

Architecture review, 425

Archived data, legal implications of, 193

Arithmetic derivations, 230-231, 233-234

Arity count, 224

checking, 231-233

checking for high, 232

Arity (of a fact), 224, 231-233

Arrays of hard drives, 272

Artifacts (of a project)

explained, 96, 104

gathering requirements from, 105

validating usage scenarios against, 150

validating use cases against, 150

Artifacts list (functional specifications), 144-145

As is discovery, 121

ASP (Active Server Pages), 6, 13

ASP Application object, 13, 360

ASP applications, 13

ASP pages, download speed of, 85

ASP Request and Response objects, 13

ASP Session object, 13, 360

ASP/COM web application structure, 13

ASP.NET, 7, 18

caching pages or fragments, 360

ERS Apache support for, 30

Mono project support for, 30

state management, 169-170

storing session state, 359-361

ASP.NET applications, security for, 303

ASP.NET deployment, 173

ASP.NET testing interface for web services, 15

ASP.NET web application, 269

explained, 21

multi-user processing, 359

ASP.NET web service, explained, 21

Assemblies, 18-19, 308

creating strong-named, 176-178

incremental builds of, 397

isolated from each other, 354

setup and distribution of, 174

strong-named, 175-178

Assembly filenames, 396

Assembly manifest, 176

Assembly metadata, 18

Assembly version number (four-part), 175-176, 182

Assembly versioning, 175-182

Assembly versions, multiple, 182-183

Assembly-binding request, resolving, 175

Asymmetric cryptography, 186

Asynchronous application, 321

Asynchronous architecture, 307-308

Asynchronous messaging, 158

Asynchronous processes, 153

ATL (Active Template Library), 21

Audit of current production environment, 121

Audit log Audit trail, 298

Audit log events, 340

Audit logs, 339

access to, 298

nonsecurity, 298

of users who log in and out, 298

Auditing, 297-299, 353

defined, 298

specifications for, 339-343

strategies for, 162-163

Auditory disability, requirements for, 114

Authentication, 119, 187-189, 351-352

for application IDs and passwords, 303

mechanisms for, 187

for role-based security, 303

strategies for, 190-191

Authentication requirement, 119

Authentication schemes (HTTP), 303

Authentication system, web-based, 304

Authorization, 189

granted to individuals or groups, 119

strategy for, 190-191

Authorization requirement, 119

Automated monitoring (of application), 162

Automated testing of code, 422, 424

Automatic Insertion of End Constructs (Visual Basic), 414

Availability, 155-158

challenge of, 348-349

defined, 155

designing for, 156-158

determining the level of, 156

formula for calculating, 155-156

measurements for calculating, 155

reliability and, 158

validating, 372

Availability benchmarks, 368

Availability percentage, 156

Availability requirements, 116-117




MCSD Analyzing Requirements and Defining. NET Solutions Architectures Study Guide (Exam 70-300)
MCSD Analyzing Requirements and Defining .NET Solutions Architectures Study Guide (Exam 70-300 (Certification Press)
ISBN: 0072125861
EAN: 2147483647
Year: 2003
Pages: 94

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net