adplus-dvertising
frame-decoration

Question

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

a.

It does not take into account the potential effects of automation on employees.

b.

It does not provide a way to reconcile the views of different stakeholders.

c.

It does not allow for end-user participation in shaping the system.

d.

It does not provide a way to gather and analyze system requirements.

Posted under Software Engineering

Answer: (a).It does not take into account the potential effects of automation on employees. Explanation:The pure functionalist paradigm is not suitable during requirements engineering because it does not take into account the potential effects of automation on employees and may lead to dissatisfied users who neglect or express additional requirements for the system.

Engage with the Community - Add Your Comment

Confused About the Answer? Ask for Details Here.

Know the Explanation? Add it Here.

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

Similar Questions

Discover Related MCQs

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?

Q. What is a major heuristic for task analysis?

Q. What is the main benefit of scenario-based analysis?

Q. What is the think aloud method?

Q. In scenario-based analysis, what type of scenarios can be used?

Q. What is the purpose of scenario-based analysis?

Q. What is another name for scenario-based analysis when tied to a UML-type of modeling?

Q. What is a potential drawback of scenario-based analysis?

Q. From what perspective can scenarios be looked at?

Q. What is a major disadvantage of eliciting requirements through interviews?

Q. How can ethnographic methods be used to study user requirements?

Q. How do thinking aloud protocols fail to capture user behavior?