Software Development and Management

According to PRPC Standards of Design, the recommended development order is: Class Structure → ProcessFlow → User Interface → Properties. This order ensures that data structure is defined first, then business processes, then how users interact, and finally the detailed properties. Option D captures the key sequence (Structure, ProcessFlow, UI) without Properties, which is the closest correct answer among the options.

The Decision Tree SmartShape is specifically designed for complex 'if...then' logic where you need to evaluate multiple conditions in a structured hierarchy. Decision Trees allow you to visualize and execute branching logic based on property values and expressions. Utility shapes are for calling activities, Routers determine assignment routing, and Split For Each is for iterating over page groups - none are primarily for conditional logic.

Pega SmartBuild best practices recommend keeping flows contained on a single Visio page for readability and maintainability. Spanning flows across multiple Visio pages (D) makes them harder to understand and maintain. The other options are acceptable: Assignments can have multiple connectors, flows can call subflows, and utilities can be chained.

SmartBuild best practices recommend keeping flows compact, readable, and modular. Spanning a flow across multiple Visio pages indicates excessive complexity and violates the principle of modularity (subflows should be used instead). Having multiple flow actions, subflows, or utilities is standard design.

All three options - Extreme Programming (XP), Crystal, and Scrum - are recognized Agile Development methodologies. XP emphasizes engineering practices, Crystal focuses on people and communication, and Scrum uses iterative sprints. Since all three listed are valid Agile methodologies, 'All of the above' is the correct answer.

Agile Development encompasses multiple methodologies including Extreme Programming (XP), Crystal Clear (Crystal), Scrum, and others like Kanban and Lean. The question lists XP, Crystal, and Scrum as individual options, but 'All of the above' is the correct answer since all three are recognized Agile methodologies.

Extreme Programming (XP), Crystal, and Scrum are all recognized methodologies within the Agile Development framework. Each has its own approach to iterative development, customer collaboration, and responding to change. Agile is not a single methodology but a philosophy encompassing multiple approaches.

Decision tables are specifically designed to capture complex business rules and logical conditions in a structured tabular format. They systematically show all possible combinations of conditions and their corresponding actions, making them ideal for documenting requirements with multiple logical rules that must be evaluated together.

SDK is a standard industry term that stands for Software Development Kit. An SDK is a collection of software development tools and libraries that developers use to create applications for specific platforms or frameworks.

Configuration management tools provide version control, traceability, and audit capabilities. Statement C is correct because these tools establish and maintain traceability links between testware (test cases, test scripts) and software work products (code, requirements) across different product variants. They don't typically provide statistical analysis (A), don't store bug reports (B) - that's bug tracking tools, and don't analyze structures (D) - that's static analysis.

Based on technology and business experts, the Consultative Approach is most likely to be true as it involves seeking guidance from domain experts who understand the technical and business context. Reactive approach responds after problems occur, while Preventive approach tries to prevent issues.

When software is not user-friendly as expected, it indicates a Product Risk because it directly relates to the product's quality and fitness for use. Customer risk relates to customer satisfaction, Project risk relates to project constraints, and Organizational risk relates to organizational impact.

Discrete manufacturing involves producing distinct, identifiable, countable items (like cars or computers) in batches or lots. The other options describe configuring option classes or general assembly rules rather than the fundamental definition.

Project Manufacturing is designed for companies that manage large, complex contracts that cannot be fully or efficiently managed using standard discrete, process, or repetitive manufacturing alone, allowing integration of manufacturing with project tracking.

In TOGAF, Architecture Building Blocks (ABBs) originate from the Architecture Continuum, which contains generic architecture assets and models from the enterprise and industry. The Solutions Continuum (A) provides Building Blocks (SBBs) for specific solutions. Architecture Vision (B) is a phase in TOGAF, not a source of ABBs. The Architecture Board (D) governs architecture, and the CIO (E) is an executive role - neither are building block sources.