Computer-Graphics
May 31, 2024UGC NET CS 2013 Dec-paper-2
June 1, 2024UGC NET CS 2013 Dec-paper-2
|
Question 9
|
Which one of the following is not a step of requirement engineering ?
|
Requirement elicitation
|
|
|
Requirement analysis
|
|
|
Requirement design
|
|
|
Requirement documentation
|
Question 9 Explanation:
Requirements engineering (RE) refers to the process of defining, documenting and maintaining requirements in the engineering design process.
Requirement Analysis Steps:
1. Requirements inception or requirements elicitation: Developers and stakeholders meet, the latter are inquired concerning their needs and wants regarding the software product.
2. Requirements analysis and negotiation: Requirements are identified (including new ones if the development is iterative) and conflicts with stakeholders are solved. Both written and graphical tools (the latter commonly used in the design phase but some find them helpful at this stage, too) are successfully used as aids.
3. System modeling: Some engineering fields (or specific situations) require the product to be completely designed and modeled before its construction or fabrication starts and, therefore, the design phase must be performed in advance.
4. Requirements specification: Requirements are documented in a formal artifact called a Requirements Specification (RS), which will become official only after validation.
5. Requirements validation: Checking that the documented requirements and models are consistent and meet the needs of the stakeholder. Only if the final draft passes the validation process, the RS becomes official.
6. Requirements management: Managing all the activities related to the requirements since inception, supervising as the system is developed and, even until after it is put into use (e. g., changes, extensions, etc.)
Requirement Analysis Steps:
1. Requirements inception or requirements elicitation: Developers and stakeholders meet, the latter are inquired concerning their needs and wants regarding the software product.
2. Requirements analysis and negotiation: Requirements are identified (including new ones if the development is iterative) and conflicts with stakeholders are solved. Both written and graphical tools (the latter commonly used in the design phase but some find them helpful at this stage, too) are successfully used as aids.
3. System modeling: Some engineering fields (or specific situations) require the product to be completely designed and modeled before its construction or fabrication starts and, therefore, the design phase must be performed in advance.
4. Requirements specification: Requirements are documented in a formal artifact called a Requirements Specification (RS), which will become official only after validation.
5. Requirements validation: Checking that the documented requirements and models are consistent and meet the needs of the stakeholder. Only if the final draft passes the validation process, the RS becomes official.
6. Requirements management: Managing all the activities related to the requirements since inception, supervising as the system is developed and, even until after it is put into use (e. g., changes, extensions, etc.)
Correct Answer: C
Question 9 Explanation:
Requirements engineering (RE) refers to the process of defining, documenting and maintaining requirements in the engineering design process.
Requirement Analysis Steps:
1. Requirements inception or requirements elicitation: Developers and stakeholders meet, the latter are inquired concerning their needs and wants regarding the software product.
2. Requirements analysis and negotiation: Requirements are identified (including new ones if the development is iterative) and conflicts with stakeholders are solved. Both written and graphical tools (the latter commonly used in the design phase but some find them helpful at this stage, too) are successfully used as aids.
3. System modeling: Some engineering fields (or specific situations) require the product to be completely designed and modeled before its construction or fabrication starts and, therefore, the design phase must be performed in advance.
4. Requirements specification: Requirements are documented in a formal artifact called a Requirements Specification (RS), which will become official only after validation.
5. Requirements validation: Checking that the documented requirements and models are consistent and meet the needs of the stakeholder. Only if the final draft passes the validation process, the RS becomes official.
6. Requirements management: Managing all the activities related to the requirements since inception, supervising as the system is developed and, even until after it is put into use (e. g., changes, extensions, etc.)
Requirement Analysis Steps:
1. Requirements inception or requirements elicitation: Developers and stakeholders meet, the latter are inquired concerning their needs and wants regarding the software product.
2. Requirements analysis and negotiation: Requirements are identified (including new ones if the development is iterative) and conflicts with stakeholders are solved. Both written and graphical tools (the latter commonly used in the design phase but some find them helpful at this stage, too) are successfully used as aids.
3. System modeling: Some engineering fields (or specific situations) require the product to be completely designed and modeled before its construction or fabrication starts and, therefore, the design phase must be performed in advance.
4. Requirements specification: Requirements are documented in a formal artifact called a Requirements Specification (RS), which will become official only after validation.
5. Requirements validation: Checking that the documented requirements and models are consistent and meet the needs of the stakeholder. Only if the final draft passes the validation process, the RS becomes official.
6. Requirements management: Managing all the activities related to the requirements since inception, supervising as the system is developed and, even until after it is put into use (e. g., changes, extensions, etc.)