WorksheetsSPM_Quiz-2_unit-2
Total questions: 80
Worksheet time: 40mins
Which principle of Davis’s Top 30 Principles directly contradicts premature optimization in conventional software engineering?
Minimize intellectual distance
Get it right before you make it faster
Inspect code
Put techniques before tools
In conventional software engineering, success is MOST heavily dependent on which combination?
Rapid prototyping and user feedback
Documentation, discipline, and control
Continuous refactoring and reuse
Architecture-first development
Which Davis principle emphasizes that management quality outweighs technical superiority?
People are the key to success
Use tools, but be realistic
Good management is more important than good technology
Follow with care
The statement “People and time are not interchangeable” primarily warns against:
Poor estimation models
Adding manpower to delayed projects
Lack of documentation
Excessive coupling
Which modern software management principle MOST directly supports early risk mitigation?
Component-based development
Demonstration-based assessment
Configurable and scalable process
Iterative life-cycle that confronts risk early
The architecture-first approach is primarily established during which life-cycle phase?
Construction
Inception
Elaboration
Transition
Which activity BEST differentiates Elaboration from Inception?
Stakeholder identification
Business case approval
Risk identification
Architecture validation and risk mitigation
Which life-cycle phase has the highest cost of defect correction if errors are discovered late?
Transition
Construction
Elaboration
Inception
Engineering and Production stages mainly help project managers control:
Customer satisfaction
Cost, risk, and quality
Only schedule
Only development cost
Which of the following is a Primary Evaluation Criterion of the Inception Phase?
Architecture stability
Fully implemented functionality
System deployment readiness
Business case justification
Which artifact BEST captures high-level goals and system scope?
Architecture Description
Vision Document
Software Development Plan
Use-Case Model
Which artifact belongs to the Management Artifact Set and supports hierarchical task decomposition?
Release Specification
Test Plan
Architecture Document
WBS
Low coupling and high cohesion are MOST closely related to which Davis principle?
Design for change
Avoid tricks
Use coupling and cohesion
Encapsulate
Which artifact is MOST critical for traceability of functional requirements?
Supplementary Specifications
Stakeholder Requests
Use-Case Model
Glossary
Which artifact evolves continuously across all life-cycle phases?
Artifacts as a whole
Release Package
Test Report
User Manual
Which Test Artifact subsystem is responsible for evaluating test outcomes?
Test Analysis Subsystem
Test Execution Subsystem
Test Planning Subsystem
Test Design Subsystem
Which artifact ensures environment-specific execution settings?
Build Scripts
Executable Components
Configuration Files
Libraries
Which modern principle MOST directly supports synchronization between design and code?
Scenario-based releases
Objective quality control
Round-trip engineering tools
Model-based notation
The Transition Phase primarily focuses on:
Requirement validation
Architecture stabilization
User acceptance and deployment
Code optimization
Which artifact BEST supports change tracking and impact analysis?
Status Assessment
Software Change Order Database
Release Description
Deployment Environment
Which principle acknowledges that customer requirements evolve after interaction with software?
Give products to customers early
Design for change
Expect excellence
The more they see, the more they need
Which artifact is MOST relevant for maintenance teams post-deployment?
Use-Case Diagrams
Test Scripts
Operational Procedures
Design Models
Which phase produces the most executable artifacts?
Construction
Inception
Transition
Elaboration
Which artifact explicitly defines non-functional requirements?
Vision Document
Glossary
Supplementary Specifications
Use-Case Model
Pragmatic artifacts MOSTLY address:
Architectural modeling
Real-world execution constraints
Testing strategies
Coding standards
Which Davis principle warns against overreliance on automation?
Put techniques before tools
Inspect code
Avoid tricks
Use tools, but be realistic
Which artifact bridges business goals and technical planning?
Product Roadmap
Vision Document
Release Notes
Architecture Overview
Which modern practice BEST supports objective progress measurement?
Scenario-based releases
Component-based development
Objective quality control
Iterative lifecycle
Which phase approval confirms project feasibility and continuation decision?
Construction
Transition
Inception
Elaboration
Which principle MOST directly combats software entropy?
Analyze causes for errors
Encapsulate
Design for change
Inspect code
Which Davis principle MOST strongly enforces accountability in software engineering?
People are the key to success
Take responsibility
Follow with care
Expect excellence
Which life-cycle phase emphasizes eliminating high-risk technical uncertainties before full-scale development?
Inception
Construction
Elaboration
Transition
Which artifact BEST supports release-level scope control?
Vision Document
Release Specifications
Status Assessment
Test Plan
In modern software management, scenario-based intermediate releases mainly help in:
Improving code performance
Validating architecture
Aligning software with real usage patterns
Reducing documentation effort
Which artifact provides a formal justification for investment decisions?
Software Development Plan
Business Case
Release Description
Deployment Environment
Which Davis principle MOST discourages clever but unreadable programming?
Inspect code
Avoid tricks
Encapsulate
Use coupling and cohesion
Which artifact is MOST useful for validating system behavior from the user’s perspective?
Configuration File
Architecture Description
Use-Case Model
Class Diagram
Which modern principle MOST directly supports reuse and faster development?
Iterative lifecycle
Component-based development
Architecture-first approach
Demonstration-based assessment
Which evaluation criterion confirms that major risks are resolved?
Inception approval
Transition acceptance
Elaboration milestone
Construction exit
Which artifact ensures repeatable and automated builds?
Executable Components
Build Scripts
Libraries
Unit Test Code
Which Davis principle recognizes inevitable requirement evolution?
The more they see, the more they need
Design for change
Give products to customers early
Expect excellence
Which artifact is MOST critical for tracking defects across testing cycles?
Defect Log
Test Report
Test Plan
Test Script
Which phase produces the maximum number of test artifacts?
Construction
Inception
Elaboration
Transition
Which artifact helps users operate the system rather than understand its design?
Use-Case Model
Vision Document
User Manual
Software Architecture Document
Which modern principle replaces document-heavy reviews with working evidence?
Model-based notation
Demonstration-based assessment
Objective quality control
Iterative lifecycle
Which Davis principle MOST strongly enforces measurement of complexity?
Inspect code
Use the McCabe complexity measure
Encapsulate
Avoid tricks
Which artifact explicitly defines acceptance conditions for a release?
Status Assessment
Release Specification
Test Case
Release Description
Which artifact group ensures installation, delivery, and operational readiness?
Deployment Artifacts
Test Artifacts
Pragmatic Artifacts
Engineering Artifacts
Which principle emphasizes that tools cannot compensate for poor processes?
Put techniques before tools
Follow with care
Inspect code
Use tools, but be realistic
Which life-cycle phase has the highest user involvement?
Transition
Construction
Elaboration
Inception
Which artifact is MOST useful for tracking project health over time?
Status Assessment
Vision Document
Build Script
Architecture Diagram
Which modern software principle MOST supports scalability across project sizes?
Architecture-first
Configurable and scalable process
Objective quality control
Iterative lifecycle
Which Davis principle ensures alignment with customer value?
Analyze causes for errors
Understand the customer’s priorities
Expect excellence
Design without documentation is not design
Which artifact bridges requirements and architecture?
Test Plan
Vision Document
Use-Case Model
Software Architecture Document
Which Test Artifact subsystem is responsible for creating test cases?
Test Planning
Test Execution
Test Analysis
Test Design
Which principle MOST directly supports maintainability?
Design for change
Avoid tricks
Inspect code
Encapsulate
Which artifact ensures hardware and software readiness for deployment?
Support Documentation
Installation Script
Deployment Environment
Release Package
Which phase exit indicates the system is ready for production use?
Inception
Transition
Elaboration
Construction
Which Davis principle emphasizes learning from failures?
Expect excellence
Inspect code
Avoid tricks
Analyze causes for errors
Which artifact MOST directly supports change impact analysis?
Vision Document
Software Change Order Database
Test Case
Release Description
Which Davis principle MOST directly supports independent verification and validation?
Don’t test your own software
Inspect code
Follow with care
Analyze causes for errors
Which artifact ensures alignment between features, constraints, and acceptance criteria for a release?
Business Case
Release Description
Release Specification
Status Assessment
Which phase outcome confirms that requirements are well understood and documented?
Inception
Transition
Elaboration
Construction
Which modern principle MOST reduces documentation–code inconsistency?
Objective quality control
Iterative life cycle
Model-based notation
Round-trip engineering tools
Which artifact supports long-term system evolution and maintenance?
Status Reports
Build Scripts
Software Architecture Document
Test Scripts
Which Davis principle highlights that the first solution is rarely the best?
Evaluate design alternatives
Design for change
Expect excellence
Avoid tricks
Which artifact MOST directly supports risk tracking throughout the project?
Use-Case Model
Status Assessment
Vision Document
Test Plan
Which life-cycle phase produces training materials and user manuals?
Inception
Transition
Construction
Elaboration
Which principle explicitly acknowledges software decay over time?
Software entropy increases
Expect excellence
Analyze causes for errors
Design for change
Which artifact is MOST useful for environment replication?
Executable Components
Test Case
Deployment Environment
Release Package
Which modern practice BEST supports early customer validation?
Model-based notation
Architecture-first approach
Objective quality control
Demonstration-based assessment
Which artifact ensures automated testing of individual modules?
Unit Test Code
Test Cases
Test Reports
Defect Logs
Which phase has the maximum impact on project feasibility decision?
Inception
Elaboration
Construction
Transition
Which Davis principle MOST discourages blind adherence to standards?
Encapsulate
Inspect code
Avoid tricks
Follow with care
Which artifact BEST represents functional system behavior?
Supplementary Specification
Architecture Description
Design Model
Use-Case Model
Which modern principle MOST strongly supports reuse and scalability?
Iterative lifecycle
Configurable process
Component-based development
Architecture-first approach
During a project audit, which evidence BEST shows decisions were aligned with documented principles?
Traceability from principles to decisions
Signed meeting minutes
Weekly velocity dashboards
A consolidated risk register
When comparing standards and principles, which statement is MOST accurate for engineering teams?
Standards define why; principles define how
Principles define why; standards define how
Standards mandate practices; principles guide choices
Principles mandate practices; standards guide choices
Which artifact is MOST appropriate to capture non-functional constraints for controlled deployment?
Iteration burndown chart
Design Model
Supplementary Specification
Use-Case Model
To validate functional behavior before deployment, what is the MOST suitable strategy?
Execute use-case driven acceptance tests
Run smoke tests only
Review architecture sketches
Audit coding standards conformance
