adplus-dvertising
frame-decoration

Question

What is the main idea behind the Taylorian approach to software development?

a.

Tasks are recursively decomposed into simpler tasks and each task has one ‘best way’ to accomplish it.

b.

The analyst actively participates in the shaping of the UoD.

c.

The developer is the system expert who searches for measurable cause--effect relationships.

d.

Systems are often developed to support the interests of the owners, at the expense of the interests of labor.

Answer: (a).Tasks are recursively decomposed into simpler tasks and each task has one ‘best way’ to accomplish it. Explanation:The main idea behind the Taylorian approach to software development is that tasks are recursively decomposed into simpler tasks and each task has one ‘best way’ to accomplish it. This approach is commonly called ‘scientific management’, in which tasks are recursively decomposed into simpler tasks and each task has one ‘best way’ to accomplish it.

Engage with the Community - Add Your Comment

Confused About the Answer? Ask for Details Here.

Know the Explanation? Add it Here.

Q. What is the main idea behind the Taylorian approach to software development?

Similar Questions

Discover Related MCQs

Q. What is the main assumption behind the functionalist paradigm in requirements engineering?

Q. What is the main focus of the social-relativism paradigm in requirements engineering?

Q. What is the key assumption behind the radical-structuralism paradigm in requirements engineering?

Q. What is the main goal of the radical-structuralism paradigm in requirements engineering?

Q. What is the difference between an objectivist and a subjectivist point of view in requirements engineering?

Q. Which of the following paradigms for requirements engineering is associated with the objective-order dimension?

Q. What is the central theme of the Neohumanism paradigm in requirements engineering?

Q. In practice, what is the majority of system development techniques typically associated with?

Q. In what type of systems is it important to involve end-users in the shaping of the User or Domain (UoD)?

Q. What is the main issue that automation can cause in an organization?

Q. Why is the pure functionalist paradigm not suitable during requirements engineering?

Q. What was an example of a negative consequence of not consulting with ambulance crews during the development of a Computer Aided Despatch System?

Q. What is the potential outcome of a compromise in handling different conceptual models of the participants during requirements engineering?

Q. What are the two main sources of information for the requirements elicitation process?

Q. In market-driven software development, what is the process of requirements elicitation often considered?

Q. What is one of the techniques used in requirements elicitation?

Q. What is the Delphi technique used for?

Q. What is one way that requirements for the next release of a software can be gathered?

Q. What is the Delphi technique used for in requirements elicitation?

Q. What is one way to overcome the problem of some users having more influence than others in discussion sessions?