SWE 3313 Intro to Software Engineering Final Exam Study Guide Latest Update 2024 Questions and Verified Correct Answers Guaranteed Success Briefly explain two different ways to decide when to stop testing. - CORRECT ANSWER:2 different ways to decide when to stop testing are when: every planned test case is carried out and when all the problems that have been seen are fixed.
Explain AOP. - CORRECT ANSWER: AOP stands for aspect oriented programming.
This approach to programming is aimed towards more modular, cohesive, and well- defined interfaces or coupling in the design of a system. This concept is geared towards modularizing the implementation of the cross-cutting concerns in OO programming into a single, cohesive unit.
Explain how the requirements prioritization list is used to prune the requirements to be developed - CORRECT ANSWER: A requirements prioritization list is basically a table that lists different requirements as priority 1 and so on, so it is then known which requirement(s) need the most attention.
Explain how the requirements prioritization list is used to prune the requirements to be developed. - CORRECT ANSWER: A requirements prioritization list is basically a table that lists different requirements as priority 1 and so on, so it is then known which requirement(s) need the most attention.
Explain the statement "Halstead metrics measure the program's lexical complexity." -
CORRECT ANSWER: Halstead metrics have been criticized for a number of reasons.
Among them is that the Halstead metrics really measure only the lexical complexity of the source program and not the structure or the logic. Therefore, they have a limited value in the analysis of program complexity, let alone design characteristics.
Explain the UI goal to ensure that there is a consistent pattern across all the interfaces.
- CORRECT ANSWER: Consistency ensures that common terminology is used across
the system's display screens, reports, database elements, and process logic. It also ensures that common approaches are taken to handle errors, warnings, and information messages that get displayed.
Explain WMC. - CORRECT ANSWER: WMC is a weighted sum of all the methods in a
class. It basically measures how prone a program is to error. The more lines of code there, the more prone it is to error, and thus a bigger WMC.
From the definition of software engineering, list three areas that software engineering
must touch on. - CORRECT ANSWER: Software engineering must touch on project
coordination and management, particular methods and/or strategies, and technical and business procedures. 1 / 2
Give an example of different views that are useful to different stakeholders. -
CORRECT ANSWER: For example, with today's large enterprise resource planning
(ERP) systems, there are several major components including financial, human resource, planning, and inventory. The financial person using the system will provide requirements with the financial lingo and an emphasis on finance. The human resource person will have another perspective, using the human resource terminology and having a bias toward human resources.
Important nontechnical concerns in large software development are: - CORRECT
ANSWER:estimation and planning
In many cases, a company's product may have change before the software product is released using traditional development methods. Does Agile Method address this issue
and if so, how? - CORRECT ANSWER: Yes. Agile Methods do address this issue
because unlike traditional development methods, agile are really good with product requirement changes. Agile methods involve making changes to the product as more and more requirements become known.
In many cases, a company's product may have change before the software product is released using traditional development methods. Does Agile Method address this issue
and if so, how? - CORRECT ANSWER: Yes. Agile Methods do address this issue
because unlike traditional development methods, agile are really good with product requirement changes. Agile methods involve making changes to the product as more and more requirements become known.
List and explain in your own words three characteristics of a good software
implementation - CORRECT ANSWER: Three characteristics of a good software
implementation are: readability, performance, and completeness. Readability means that the other programmers can easily comprehend and follow the code. Performance means that the code can function in as less time as possible. Completeness means that the code meets all the needs for the system.
List four factors that should be considered in deciding how many post-release people will be needed. - CORRECT ANSWER: Some of those factors are: the number of anticipated users and customers, the size of user training, the size of support personnel training, and the number of development people committed to supporting the system.
List three "bad smells" signaling that your code probably should be refactored. - CORRECT ANSWER: Three "bad smells" that indicate that one's code should maybe be refactored are: duplicated code, an unnecessarily long method, or an unnecessarily long class.
List two technical concerns in developing large systems. - CORRECT ANSWER: The
concerns in developing large systems are: problem and design decomposition, choices of database, network, middleware, and other technical components like code version
- / 2