Software Development and Management

The five core components of Team Foundation Server are: (1) Work Item Tracking - bugs, tasks, requirements; (2) Version Control - source code management; (3) Build Automation - automated build and CI/CD; (4) Project Portal - SharePoint-based team collaboration site; (5) Reporting - SQL Server Reporting Services reports for project metrics. Process templates are not a component but templates that configure these components.

The Agile process template in TFS 2010 includes two key Excel workbooks: Product Backlog (for capturing and prioritizing all user stories/features for the product) and Iteration Backlog (for planning work in specific iterations). Sprint backlog is a Scrum term - TFS Agile uses 'iteration' instead of 'sprint'.

The Call Hierarchy window allows developers to view and navigate incoming and outgoing calls for a selected method, property, or constructor at design time (without running the application). The Call Stack window is only available during debugging at run time.

In Visual Studio 2010 Modeling projects, you can add UML Class, Sequence, Component, Activity, Use Case, and Layer diagrams. However, UML Collaboration Diagrams were not supported - they were replaced by Communication Diagrams in UML 2.0, which VS 2010 supports under a different name.

Session Facade provides coarse-grained access to the business tier by encapsulating fine-grained business components and presenting a simplified, unified interface to clients. Business Delegate provides client-side abstraction, and Transfer Object is for data transfer. Session Facade is specifically designed for coarse-grained business tier access.

DAO (Data Access Object) pattern provides an abstraction layer between business logic and data source. It encapsulates all details of connecting to and interacting with data sources, making the application code independent of the underlying data storage mechanism. The pattern can work with any type of data source - relational databases, LDAP directories, XML files, flat files, or even NoSQL stores.

Transformation Developer creates reusable transformations that can be used across multiple mappings. Mapping Designer allows you to create transformations within a specific mapping context. Source Analyzer and Target Designer are used exclusively for defining source and target metadata - they don't create transformations.

Enterprise Content Management (ECM) encompasses both workflow procedures and data validations for managing organizational content. ECM systems coordinate document lifecycle, business processes, and compliance requirements - not just validations or workflows in isolation.

With fixed delivery dates and quality standards, adding resources (options B, D) or overtime (option C) often delays further due to ramp-up time and coordination overhead (Brooks' Law). Scope reduction by eliminating unimplemented requirements (option A) is the most viable approach to recover schedule while maintaining quality of the remaining features.

Procedures and standards within individual workbenches ensure consistent and correct output production. Tools are instruments used, while techniques are methods applied - but procedures and standards govern HOW work is done to achieve right outputs.

Web services are characterized as loosely coupled (minimal dependencies between services), NOT loosely cohesive. Cohesion refers to how related the functionality within a single module is - web services aim for HIGH cohesion internally, while being loosely coupled from each other. The question asks which is NOT a characteristic, making 'loosely cohesive' the correct answer because it misstates the standard principle.

In SOA contexts, DIS stands for Data Interchange Standard. This refers to the standards and protocols used for exchanging data between services, such as XML, JSON, SOAP, or RESTful message formats. These interchange standards enable different services to communicate seamlessly regardless of their internal implementations.

Metadata Web Service provides repository-wide operations. getAllDIServers lists available Integration Services. getAllFolders retrieves folder hierarchy. getAllRepositories returns repository information. Workflow instances and tasks are operations-specific, not metadata.

Web services are specialized software tools that enable e-commerce solutions through standardized interfaces for communication between different systems. They provide pre-built functionality for common e-commerce tasks like payment processing, shipping calculation, inventory management, and customer data handling. Firewalls are security tools, not e-commerce implementation tools. Peer-to-peer networks are an architecture pattern, not specialized e-commerce tools. Grid tools are for distributed computing, not e-commerce specifically. Object-oriented programming languages are general-purpose development tools, not specialized e-commerce solutions.

The bug lifecycle follows: Open (reported) -> Assigned (to developer) -> Fixed (developer resolves) -> Closed (tester verifies). Options B and C have wrong order. Option D appears to be a duplicate with a typo prefix.