Which of the following is NOT a function of system design?

• A. Defining the architecture
• B. Defining the components
• C. Demanding actions and answers
• D. Satisfying specific requirements

Answer: (C)

System design focuses on creating the structure that lets the system meet its needs: defining the overall architecture, breaking the system into components, and planning how those parts interact and how data and control flow between them to satisfy requirements. Saying what the architecture is and what components exist are fundamental design activities, and the aim is to ensure the design can meet the specified requirements.

Demanding actions and answers isn’t a function of system design. Forcing user actions or input relates to how the system will be used—the user interface, workflows, and business rules—rather than the structural blueprint of how the system is built. The design should accommodate required actions and inputs, but the act of demanding them belongs to interaction design and policy/requirements implementation, not to defining the system’s architecture and components.