UML and ASP.NET Web Technologies

ListView and DataPager were new data controls introduced in ASP.NET 3.5 to provide improved data presentation and paging capabilities. The other options existed in earlier versions.

.NET Framework 3.5 builds on the 2.0/3.0 runtime and supports versions 2.0, 3.0, and 3.5. .NET 1.1 was a separate, earlier runtime version not supported by the 3.5 framework.

The ASP.NET Merge Tool (aspnet_merge.exe) was introduced in .NET 3.5 to merge pre-compiled assemblies into a single assembly for deployment. ILDASM is for disassembly, while Remote Spy and Remote File Viewer are unrelated tools.

Visual Studio 2008 (.NET 3.5) introduced IntelliSense support for JavaScript and AJAX to improve client-side development. CSS, LINQ, and HTML support existed or aren't the primary new feature.

ASP.NET 3.5 uses the same runtime engine as ASP.NET 2.0. It adds new features and controls but builds on the 2.0 foundation without changing the core engine.

Use case diagrams are primarily used during requirement gathering to capture functional requirements and user-system interactions. While they may be referenced during development, their main purpose is in the requirements phase.

Use case diagrams are indeed a primary tool for documenting requirements from a user perspective. Options B and C describe benefits but are not definitional statements. Option D is incorrect because fully-dressed use cases focus on WHAT (functionality) not HOW (implementation details).

Use Case diagrams show interactions between actors and system functions, while Sequence diagrams show object interactions over time - both represent dynamic behavior, not static structure. Class diagrams are static.

UML is a notation/language for modeling OOAD concepts, but knowing the notation doesn't guarantee understanding of analysis and design principles themselves - similar to knowing syntax vs knowing programming.

Use case diagrams consist of actors (users/external systems), use cases (system functions), and communications/associations between them. Activities are for activity diagrams, messages are for sequence diagrams.

Packages in UML are used as grouping mechanisms to organize model elements like classes into cohesive groups, simplifying large diagrams. Storing classes in packages makes the overall architecture and dependencies clearer, which validates the statement as true.

In a UML deployment diagram, a software component is represented by a rectangle with two small tabs protruding from its left side. A three-dimensional box represents a deployment node, whereas rounded rectangles depict states in state machine diagrams.

An event can cause an object to stay in the same state if guard conditions are not met - this is a key statechart feature. Option A is false (entry/exit actions exist), C is false (states can be re-entered), D is false (transitions must have unique triggers).

Collaboration diagrams show objects interacting over time, making them dynamic behavior models. Sequence numbers are required to show message ordering. They CAN show iteration and self-messages, making B, C, and D incorrect.

UML models serve multiple stakeholders: Business Analysts define requirements, Designers create architecture, Developers implement classes. All roles interact with UML artifacts, making D the correct answer.

Valid subclassing reasons include adding attributes/associations or needing different operations. Statement C violates the Liskov Substitution Principle - if a subclass can't handle superclass operations, it shouldn't inherit.

Use case diagrams are most directly useful to testers as they define test scenarios and user flows. Activity diagrams help with test flow but are less directly used. Deployment and class diagrams are less relevant for functional testing.

UML notation uses '-' for private (hidden), '+' for public, and '#' for protected. Option B correctly states the meaning of the minus symbol. Options A and C have incorrect symbol mappings.