WorksheetsSoftware Project Management_Unit-1_ Quiz
Total questions: 95
Worksheet time: 48mins
Software is best defined as
A physical device
A set of programs and related data
A computer system
A hardware component
Software Project Management mainly focuses on
Coding only
Hardware procurement
Planning, organizing, monitoring, and controlling software projects
User training
Conventional Software Management was mainly followed during
1950s–1960s
1960s–1980s
1990s–2000s
After 2010
A key assumption of conventional software management is that
Software development is unpredictable
Software development is like manufacturing
Changes are encouraged
Requirements evolve continuously
The Waterfall Model is characterized by
Parallel development
Iterative cycles
Strict sequential phases
Continuous deployment
In the Waterfall Model, the output of one phase becomes
The final product
The input to the next phase
Obsolete data
Test cases
A major drawback of the Waterfall Model is
High flexibility
Early risk resolution
Difficulty in accommodating changes
Rapid delivery
Late Risk Resolution means risks are handled
During requirements
During design
Early in the project
At the end of the project
Requirements-driven functional decomposition results in
Flexible design
Poor modularity
Reusable components
Agile systems
Adversarial stakeholder relationships mainly occur due to
Collaboration
Clear communication
Blame culture
Agile practices
Conventional software management emphasizes more on
Working software
Documentation and reviews
User feedback
Automation
Conventional software management performance is measured using
Social metrics
Industrial metrics
Marketing metrics
AI metrics
According to Boehm, fixing a defect after delivery costs
Same as fixing during design
2× more
10× more
100× more
Schedule compression in conventional projects is limited to about
10%
25%
50%
75%
Maintenance cost compared to development cost is approximately
Equal
Half
Double
One-fourth
Software cost increases mainly with
Hardware speed
Source Lines of Code (SLOC)
Number of meetings
Testing tools
The most significant factor affecting productivity is
Tools
Technology
People
Budget
Programming effort accounts for roughly
5%
15%
40%
60%
Walkthroughs are effective in detecting about
20% of errors
40% of errors
60% of errors
90% of errors
The 80–20 rule implies
80% effort gives 20% results
20% effort gives 80% results
Equal effort and results
Random productivity
Software economics studies the relationship between cost and
Hardware only
People, process, size, and quality
Marketing strategy
Network speed
Which is NOT a basic software economics parameter?
Size
Personnel
Weather conditions
Process
The Conventional Era of software development belongs to
1940s–1950s
1960s–1970s
1980s–1990s
2000+
The Transition Era introduced
Waterfall model
Late testing
Spiral model
DevOps
Modern software practices emphasize
Late ROI
Continuous integration
Fixed requirements
Waterfall model
Diseconomies of scale occur when:
Small projects grow cheaper
Cost grows slower than size
Cost grows faster than size
Team size decreases
Pragmatic cost estimation focuses on:
Theoretical values
Practical and realistic estimates
Guesswork
Vendor claims
COCOMO stands for:
Cost Control Model
Constructive Cost Model
Common Cost Module
Continuous Cost Model
Function Points are:
Language dependent
Language independent
Used only late
Hardware dependent
Improving software economics mainly aims to
Increase code size
Reduce productivity
Reduce cost and time
Increase documentation
Reducing software product size helps in
Increasing bugs
Increasing maintenance cost
Reducing development time
Delaying delivery
High-level languages reduce
Code reuse
Code readability
Lines of code
Automation
Object-Oriented methods improve
Hardware usage
Complexity management
Project delays
Documentation volume
Reuse requires
No investment
Upfront investment
Manual coding
More defects
Commercial components are
Custom-built modules
Free tools
Ready-made vendor products
Prototypes
The metaprocess focuses on
Coding
Testing
Improving the process itself
Deployment
Productive activities include
Meetings
Documentation
Coding and testing
Reporting
Early error correction is
Costly
Impossible
Beneficial
Recommended
Performing tasks in parallel improves which aspect of a project?
Documentation
Schedule
Budget overrun
Rework
Team effectiveness mainly depends on which of the following?
Team size
Tools only
Proper role matching
Salary
What does poor architecture usually result in?
Project success
Minimal rework
Project failure
Faster delivery
Boehm’s staffing principle emphasizes which of the following?
More people
Top talent
Long meetings
Equal skills
Phase-out principle suggests
Retaining misfits
Removing unsuitable members early
Promoting all
Delaying decisions
A successful project manager must have
Coding skill only
Selling and communication skills
Hardware expertise
Legal knowledge
Software environments improve productivity through
Manual processes
Automation
Increased documentation
Meetings
Integrated environments ensure
Inconsistency
Ad-hoc development
Standardization
Manual builds
Semantic integration means
Tools share understanding of data
Tools work independently
Manual updates
Increased documentation
Round-trip engineering supports which of the following?
One-way development
Model-code synchronization
Manual documentation
Testing only
Tool vendors often
Underestimate productivity
Promise exaggerated productivity gains
Avoid automation
Reduce efficiency
Software quality ensures
Low performance
Customer dissatisfaction
Meeting customer expectations
Minimal testing
Quality should be
Tested only at the end
Ignored early
Built throughout the lifecycle
Optional
Continuous integration mainly helps
Delay testing
Improve defect detection
Increase rework
Reduce automation
Demonstration-based evaluation helps in
Hiding defects
Early performance assessment
Avoiding users
Increasing documentation
Final performance issues are often discovered during
Requirements phase
Integration and testing
Planning
Inception
Peer inspections are used to
Replace testing
Detect defects early
Increase documentation
Delay delivery
Peer inspections should focus on
Every file
Critical artifacts
User manuals only
UI colors
Peer inspections are considered
Primary quality mechanisms
Secondary quality mechanisms
Final validation
Testing tools
Which is a primary quality mechanism?
Peer inspection
Life-cycle testing
Review meeting
Documentation
Inspections help junior developers by
Increasing workload
Professional development
Reducing learning
Avoiding feedback
Architectural issues are best exposed by
Inspections alone
Prototyping and experimentation
Documentation
Meetings
Executable implementations help in
Hiding defects
Validating design
Avoiding testing
Increasing cost
Demonstrating critical use cases helps
Validate real behavior
Delay delivery
Increase documentation
Avoid feedback
Feeding lessons learned back supports
Continuous improvement
Rework increase
Documentation overload
Team conflict
Waterfall model discourages changes because
Testing is early
Phases are rigid
Feedback is continuous
Requirements evolve
System-of-systems cost is approximately
Equal to programs
2× more
Half of programs
Less than programs
Software cost dominates hardware cost due to
Declining hardware prices
Increasing software complexity
Manual testing
Reduced tools
CASE tools were introduced mainly during which era?
Conventional era
Transition era
Modern era
Pre-1960
Continuous testing mainly reduces which of the following?
Team size
Late defect discovery
Requirements clarity
Documentation
Overhead activities are best described as
Useless
Always avoidable
Necessary but indirect
Core development
Removing unnecessary steps helps in
Increasing delays
Schedule improvement
Reducing quality
Increasing complexity
Parallel development mainly improves which of the following?
Cost overrun
Schedule efficiency
Rework
Defect rate
Mismanaged projects fail mainly due to which reason?
Lack of tools
Poor management and architecture
High salaries
Fewer documents
Configuration management mainly deals with which aspect?
UI design
Version control
User training
Marketing
DevOps pipelines mainly automate which process?
Documentation
Build, test, deploy
Requirement changes
Meetings
Quality metrics help in which of the following?
Ignoring defects
Tracking progress objectively
Increasing defects
Reducing productivity
Early demonstrations reduce which of the following?
Customer trust
Late surprises
Feedback
Quality
Peer inspections should NOT do which of the following?
Support quality
Replace execution-based testing
Focus on risk
Be selective
Static code analysis tools are part of which category?
Primary mechanisms
Peer reviews
Documentation
Customer feedback
Change management metrics track which of the following?
Hardware changes
Defects and rework
Salaries
UI themes
Software environments act as what?
Secondary tools
Primary delivery vehicles
Documentation tools
Feedback mechanisms
Highly integrated environments reduce:
Automation
Consistency
Manual errors
Productivity
Forward engineering converts:
Code to model
Model to code
Tests to code
Design to requirements
Reverse engineering converts:
Model to code
Code to model
Tests to requirements
Documentation to design
Modern software economics focuses on:
Late ROI
Early ROI
Fixed delivery
Heavy documentation
Larger projects usually suffer from:
Economies of scale
Diseconomies of scale
Increased productivity
Reduced costs
Historical data improves
Guesswork
Cost estimation accuracy
Documentation size
Risk
Reuse improves economics by
Increasing development effort
Reducing rework
Increasing defects
Delaying delivery
Commercial components require
No licensing
License management
Manual coding
No integration
Early performance testing mainly reduces
Hardware dependency
Late performance failures
Code readability
Documentation
Quality is NOT achieved by
Continuous testing
Iterative development
Code readability
Documentation
Major milestone demonstrations validate which of the following?
Documentation
Working software
Contracts
Budgets
What is increased by peer inspections in a software development process?
Defect leakage
Accountability
Rework
Conflicts
Which method is best for achieving architecture visualization?
UML models
Plain text
Spreadsheets
Emails
Integrated tools in software development mainly improve what aspect?
Fragmentation
Coordination
Redundancy
Manual effort
Software economics mainly deals with which of the following?
UI design
Cost-benefit trade-offs
Redundancy
Manual effort
