Computer Knowledge
Software Development and Management
3,064 Questions
Software development and management focuses on the system development life cycle, enterprise architecture, and configuration management. It tests your familiarity with system analysis, design models, and IT project planning. This subject is essential for specialist and banking officer scale examinations.
System analysis and designSoftware development life cycleConfiguration managementEnterprise architectureObject oriented design
Software Development and Management Questions
What is the concept of "Zero Defects" in TQM?
-
A goal to eliminate all defects
-
A quality standard that must be met
-
A philosophy that emphasizes continuous improvement
-
A measurement of product/service quality
A
Correct answer
Explanation
The concept of "Zero Defects" in TQM represents a goal to strive for the elimination of all defects, aiming for the highest levels of quality.
Which of the following is NOT a typical component of a real estate appraisal report?
-
Executive summary
-
Property description
-
Comparable sales analysis
-
Cost-benefit analysis
D
Correct answer
Explanation
Cost-benefit analysis is not a typical component of a real estate appraisal report. It is more commonly used in project evaluation and decision-making processes.
Which of the following is NOT a common project management tool?
-
Gantt chart
-
PERT chart
-
Work breakdown structure
-
Risk register
-
Microsoft Project
E
Correct answer
Explanation
Microsoft Project is a commercial project management software, while Gantt chart, PERT chart, work breakdown structure, and risk register are all common project management tools.
Which of the following is NOT a common project management methodology?
-
Waterfall
-
Agile
-
Scrum
-
Kanban
-
PRINCE2
E
Correct answer
Explanation
PRINCE2 is a project management methodology that is specifically designed for use in the UK government. It is not as widely used as other methodologies, such as Waterfall, Agile, Scrum, and Kanban.
Which of the following is NOT a common type of cost reduction strategy?
-
Value Engineering
-
Lean Manufacturing
-
Customer Feedback
-
Total Quality Management
C
Correct answer
Explanation
Customer feedback is not a cost reduction strategy, as it primarily serves to improve product quality and customer satisfaction.
Which of the following is a common technique used in requirement elicitation?
-
Interviewing stakeholders
-
Observing user behavior
-
Document analysis
-
All of the above
D
Correct answer
Explanation
Requirement elicitation is the process of gathering user needs and expectations. Common techniques include interviewing stakeholders, observing user behavior, and analyzing documents.
Which of the following is a common technique used in requirement analysis?
-
Use case analysis
-
Scenario analysis
-
Domain analysis
-
All of the above
D
Correct answer
Explanation
Requirement analysis is the process of understanding and refining the requirements gathered during requirement elicitation. Common techniques include use case analysis, scenario analysis, and domain analysis.
Which of the following is a common challenge in requirement engineering?
-
Gathering complete and accurate requirements
-
Managing changing requirements
-
Communicating requirements effectively among stakeholders
-
All of the above
D
Correct answer
Explanation
Requirement engineering is a complex and challenging process. Common challenges include gathering complete and accurate requirements, managing changing requirements, and communicating requirements effectively among stakeholders.
What is the best way to manage changing requirements?
-
Ignore them
-
Document them and update the requirement specification
-
Communicate them to the stakeholders and get their approval
-
All of the above
D
Correct answer
Explanation
Changing requirements are a reality in software development. The best way to manage them is to document them, update the requirement specification, communicate them to the stakeholders, and get their approval.
Which of the following is a common technique used in requirement validation?
-
Peer review
-
Prototyping
-
User acceptance testing
-
All of the above
D
Correct answer
Explanation
Requirement validation is the process of ensuring that the requirements are complete, accurate, consistent, and feasible. Common techniques include peer review, prototyping, and user acceptance testing.
Which of the following is a common type of requirement management tool?
-
Spreadsheet
-
Database
-
Dedicated requirement management tool
-
All of the above
D
Correct answer
Explanation
Requirement management tools can be implemented using a variety of technologies, including spreadsheets, databases, and dedicated requirement management tools.
What is the best way to ensure that the requirements are met?
-
Test the software system thoroughly
-
Get feedback from the stakeholders
-
Review the software system against the requirements
-
All of the above
D
Correct answer
Explanation
To ensure that the requirements are met, it is important to test the software system thoroughly, get feedback from the stakeholders, and review the software system against the requirements.
Requirement engineering is an iterative process.
A
Correct answer
Explanation
Requirement engineering is an iterative process that involves gathering, analyzing, and refining the requirements until they are complete, accurate, consistent, and feasible.
Which of the following is the most important factor to consider when evaluating the effectiveness of mathematical software?
-
Accuracy
-
Reliability
-
User-friendliness
-
Computational speed
-
Documentation
A
Correct answer
Explanation
Accuracy is the most important factor to consider when evaluating the effectiveness of mathematical software. It is essential that the software produces accurate results, as incorrect results can lead to erroneous conclusions or decisions.
Which of the following is NOT a common software project management methodology?
-
Waterfall
-
Agile
-
Spiral
-
Lean
D
Correct answer
Explanation
Lean is a manufacturing philosophy that emphasizes waste reduction and continuous improvement. It is not a specific software project management methodology.