Home »
Software Engineering MCQs
MCQ | Technology Directions in Software Engineering
Software Engineering | Technology Directions MCQ: This section contains the multiple-choice questions on Technology Directions in Software Engineering.
Submitted by IncludeHelp, on September 19, 2021
Technology Directions in Software Engineering MCQs
Here you will find the MCQs on Technology Directions in Software Engineering. The MCQs will enhance the learning and knowledge base with respect to Technology Directions in Software Engineering.
Q1. With reference to technology direction, amongst which of the following can be considered as new technology.
- Strategy transforms
- Hyped
- Improvement strategy
- All of the mentioned above
Answer: B) Hyped
Explanation:
Introducing a new “hyped” technology (it could be a new procedure, a novel method, or an interesting tool) into the marketplace. Software engineering is about much more than just technology; it is about people and their capacity to articulate their needs and innovate in order to make those demands a reality. Software engineering is a multidisciplinary field that encompasses many different disciplines.
Q2. ____ rarely survive in a dynamic business environment.
- Capability determination
- The maturity
- SPI strategies
- None of the mentioned above
Answer: C) SPI strategies
Explanation:
Long-term SPI strategies are rarely successful in the fast-paced world of software development, particularly in a dynamic commercial environment. Too much is changing at an alarming rate. In this case, a steady, step-by-step road map for SPI may have to be substituted with a framework that stresses short-term goals that are oriented toward a specific product.
Q3. Automated ____ will move away from global process management.
- Software process technology
- Iterative
- Maturity model
- None of the mentioned above
Answer: A) Software process technology
Explanation:
It is anticipated that automated software process technology would shift away from global process management (which provides broad-based assistance for the entire software process) and instead concentrate on those elements of the software process that can most benefit from automated support.
Q4. The life of software within a digital device rarely lasts beyond are known as ____.
- 1 to 3 years
- 3 to 5 years
- 3 to 7 years
- All of the mentioned above
Answer: B) 3 to 5 years
Explanation:
However, the complicated avionics systems in an aircraft have a useful life of at least 20 years, whereas the software life of a digital gadget is rarely more than three to five years. Automobile software falls somewhere in the middle of the spectrum.
Q5. Software engineers ____ across time zones and international boundaries.
- Collaborate
- Business process
- Corporate
- All of the mentioned above
Answer: A) Collaborate
Explanation:
Time zones and international boundaries are no barrier to software engineers' collaboration. Every single one of them is required to share information. In the case of open-source projects, when hundreds or thousands of software developers collaborate to create an open-source application, the same principle applies.
Q6. What are the basic requirements engineering actions are known as ____.
- Elicitation and elaboration
- Negotiation
- Specification and validation
- All of the mentioned above
Answer: D) All of the mentioned above
Explanation:
Elicitation, elaboration, negotiation, specification, and validation - these are the fundamental requirements engineering activities. There are four main tasks in requirements engineering: requirements elicitation, requirements analysis and negotiation with stakeholders, requirements specification or documentation, and requirements validation (also known as requirements validation).
Q7. ____ approaches begin with the creation of user scenarios.
- Maturity model
- Requirements engineering
- Process maturity
- All of the mentioned above
Answer: B) Requirements engineering
Explanation:
The generation of user scenarios is the starting point for the most "informal" requirements engineering methodologies (e.g., use cases). More formal approaches develop one or more requirements models, which are then used as the foundation for design. With the help of formal approaches, a software engineer can represent requirements in a mathematical notation that can be verified.
Q8. ____ couples domain-specific modeling languages with transformation engines and generators.
- Assessment and maturity
- Education and training
- Model-driven software development
- None of the mentioned above
Answer: C) Model-driven software development
Explanation:
Model-driven software development8 is a technique that combines domain-specific modeling languages with transformation engines and generators in a way that makes it easier to represent abstraction at higher levels of abstraction and then transform it into lower ones.
Q9. In ____ requirements for a software component serve as the basis for the creation of a series of test cases.
- Maturity model
- Test-driven development
- Selection and justification
- None of the mentioned above
Answer: B) Test-driven development
Explanation:
Under the principles of test-driven development (TDD), requirements for a software component are used to generate a set of test cases that exercise the interface and seek to identify faults in the data structures and functionality provided by that component. While not a new technology, test-driven development (TDD) is a trend that stresses the design of test cases prior to the creation of source code in software development.
Q10. Software engineers grapple with abstraction at virtually every step in the ____ process.
- People CMM
- Evaluation activity
- Software engineering
- None of the mentioned above
Answer: C) Software engineering
Explanation:
At practically every stage of the software engineering process, software developers are confronted with the abstraction problem. As design begins, architectural and component-level abstractions are expressed and evaluated at the architectural level.
Model-driven software development is a technique that combines domain-specific modeling languages with transformation engines and generators in a way that makes it easier to describe abstraction at high levels of abstraction and then transform it into lower levels of abstraction.