Software Development and Management

Business Analysts are primarily responsible for identifying and documenting the business impact of requirements or business processes. They work with stakeholders to understand business value and consequences. Option A correctly assigns this responsibility to Business Analysts, who bridge business needs and technical solutions.

Solution Designers and IT Architects are primarily responsible for identifying the probability of failure for requirements or business processes. They assess technical feasibility, system constraints, and implementation complexity. Option B correctly assigns this technical risk assessment to Solution Designers/IT Architects who understand technical challenges.

Each repository in Informatica requires exactly one Repository Service to manage it. Multiple repositories would each need their own Repository Service, but a single repository is managed by one service instance.

The System Architect role in PEGA primarily works with Properties and data modeling, defining the data structure and property definitions for applications. While flows and harnesses are important, they are typically owned by Process Architects or Developers. Correspondence rules are template-based and not the primary focus of System Architects.

Informatica Designer provides Source Analyzer for importing and analyzing source definitions, Transformation Developer for creating reusable transformations, and Mapping Designer for creating data flow mappings. Workflow Manager is a separate tool for workflow design and scheduling.

Declarative rules in Pega Process Commander (PRPC) automatically control when processing occurs based on conditions and changes. Examples include Declare-Expression, Declare-Constraint, and Declare-OnChange rules that trigger processing when specified conditions are met or when property values change. Decision tables and decision trees are rule types that execute logic but don't automate the timing of execution.

Meeting customer needs is the primary design consideration because applications exist to solve specific user problems. Without addressing actual user requirements, even highly scalable, maintainable, reliable, or performant applications fail to deliver value. While all the other factors (scalability, maintainability, reliability, performance, budget/timeline) are important considerations, they are secondary to ensuring the application fulfills its intended purpose for the customer.

UML consists of three main components: views (structural and behavioral perspectives of the system), diagrams (graphical representations like class diagrams, sequence diagrams), and model elements (basic building blocks like classes, objects, relationships). All three are essential parts of UML.

The PeopleSoft KES (Key Enterprise Selling) process includes both Stages and Tasks. Stages represent the major phases in the sales cycle (like qualification, proposal, negotiation), while Tasks are the specific activities that need to be completed within each stage. This structure helps manage complex enterprise sales processes systematically.

When technical jobs are modified in an OPC (Operations Planning and Control) scheduling system, the schedule must be refreshed to recognize the changes. Option A correctly states this. Option B (rebuilding) is not the immediate step after job modification - the schedule must be updated first to know about the changes.