In the “Define | Design | Build” workflow, what is mainly done during the Define stage?

Question

BlackTom AI · Accepted Answer

The Define stage establishes the clear, testable requirements and boundaries for what will be built, so specifying inputs, outputs, units, constraints, and acceptance criteria is primary.

1) Relevant knowledge points and concepts
- Software/engineering lifecycle broken into Define → Design → Build.  
- Define = requirements/specification: what the system must do, with measurable criteria.  
- Design = architecture, algorithms, data structures, interfaces.  
- Build = implementation, testing, validation, documentation.  
- Acceptance criteria and units ensure requirements are unambiguous and verifiable.

2) Complete reasoning process step by step
- Start by mapping each option to the lifecycle stages: Identify which activity best matches “Define.”  
- Option c lists specification elements (inputs, outputs, units, constraints, acceptance criteria) — these are classic requirement artifacts created during Define.  
- Option b (choose data structures and write detailed code) is a design/development activity, not defining requirements.  
- Option a (implement, test, validate, document the final code) is explicitly Build-stage work.  
- Option d (upload final answer without checking) is not a valid engineering activity and contradicts quality practices.

3) Calculations/intermediate steps
- No numerical calculations are required. The “intermediate steps” are conceptual: map activities → stages (Define → requirements, Design → structure, Build → implementation/testing).

4) Why the correct answer is correct
- Defining inputs, outputs, units, constraints, and acceptance criteria converts stakeholder needs into precise, testable requirements. This ensures downstream design and build work can be verified against objective criteria — exactly the purpose of the Define stage.

5) Why other options are incorrect
- a: Describes Build stage tasks (implementation & validation), not Define.  
- b: Describes Design/implementation-level decisions (data structures, code), which occur after requirements are defined.  
- d: Poor practice and unrelated to any formal stage; not a correct choice.

6) Conclusion
- Therefore the correct choice is c: Specify inputs, outputs, units, constraints, and acceptance criteria, which matches the provided answer.

In the “Define | Design | Build” workflow, what is mainly done during the Define stage?单项选择题

类似问题

Recording a system requirement for future use is called?

What is the final outcome of the Requirement Specification process, which serves as a reference point for developers ?

Recording a system requirement for future use is called?

True or false: The software requirements specification is a document created by the vendor containing all the features and functionality of the software they need to create.

A specification for a new game is shown below.'The application must be multi-user and contain a timer and three levels'At which stage will such a specification be required?

True or false: The software requirements specification is a document created by the vendor containing all the features and functionality of the software they need to create.

A specification for a new game is shown below.'The application must be multi-user and contain a timer and three levels'At which stage will such a specification be required?

更多留学生实用工具

智能学习助手

风格化写作助手

论文查重助手

文献引用助手

课堂转译助手

课堂笔记助手

Quiz搜索助手

学校历年真题

智能刷题助手

智能匹配练习

希望你的学习变得更简单