Software Development and Management

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.

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 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 goal of ensuring a system works successfully with all interfaced components is typically called integration testing or interoperability testing. Monitoring tracks system health, Configuration manages settings, and Analysis Support provides insights, but none of these directly address component integration. The question uses 'None of the above' as the catch-all correct answer since the specific integration service is not listed.

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.

The SEG team's scope does NOT include Database Administration or Application deployment on Desktop systems. DBA work is typically handled by a dedicated database team, and desktop application deployment falls under end-user computing or desktop support teams. SEG focuses on server-side application deployment and technical consultation, while third-party vendor coordination may or may not be within their scope depending on the organization.

SmartBuild is a structured methodology in Pega Process Commander that provides a 14-step sequence for developing BPM and BRE solutions. Process Commander is the platform itself, Process Architect is a design tool, and Project Methodology is a generic term - none are specific 14-step methodologies.

Activities are the executable rules in Process Commander that perform automated processing steps - they are the 'muscles' that power the application. Rulesets are containers for rules, flow actions control UI navigation, forms are for user interface, and correspondence handles template-based communications.

SmartBuild Step 10 focuses on adding communication capabilities to applications, with correspondence being the primary feature implemented - the ability to generate and manage correspondence documents and communications.

Data flow analysis (option C) studies how data is used and flows on paths through code - where variables are defined, used, and killed. It's a white-box technique that identifies potential anomalies like using variables before initialization. Option A refers to performance analysis, not data flow. Option B is incorrect - data flow doesn't study rate of change. Option D describes complexity metrics like cyclomatic complexity, which is different from data flow analysis.

Inspection is the most formal review type, characterized by peer examination, defined entry/exit criteria, formal roles, and collection of metrics. Walkthroughs and management reviews are less formal and lack strict entry/exit metrics.