
Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Community
Ask the community for help and clear up your study doubts
Discover the best universities in your country according to Docsity users
Free resources
Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors
A quiz for the cse 70 software engineering course, focusing on extreme programming (xp), software project failures, cohesion, coupling, and design architecture. Students are required to answer multiple-choice questions related to these topics.
Typology: Exercises
1 / 1
This page cannot be seen from the preview
Don't miss anything!
This quiz is to be taken by yourself with closed books, closed notes, no electronic devices.
Extreme Programming (XP) is considered an example of A. Waterfall Model B. Spiral Model C. Agile Model D. Layered Model E. The version of Windows before Vista
More software projects have gone awry (failed) because of A. Lack of manpower B. Lack of time C. Lack of funding D. Lack of good software engineering tools E. Lack of testing
Probably the biggest drawback of the Waterfall Model is
What does it mean for a design (say, a class) to have high cohesion? A. Methods in a class work together on a focused task B. Methods in a class are grouped together because they are frequently used methods (object management optimization) C. Methods in a class are grouped together because they provide the same basic function (like I/O) D. Methods in a class access data in other classes to provide the glue that ties the whole program together
Upfront fully-defined requirements analysis is a big part of a Plan-Driven process like the Waterfall Model. One of the nice features of XP is there is no requirements analysis at all. True or False (Circle correct answer)
What does it mean for a design (say, a group of classes) to have low coupling? A. Multiple classes share a common set of "global" variables for low overhead communication B. Multiple classes rely on the inner workings deep ("low") inside each other C. Multiple classes are not dependent on each other; instead they use a public interface to exchange parameter-less messages (or events) D. Multiple classes are coupled by inheritance of implementation low in the inheritance hierarchy
Which is considered a good and desirable design? A. Low cohesion and low coupling B. Low cohesion and high coupling C. High cohesion and low coupling D. High cohesion and high coupling
A Strict Layered architecture style exhibits which of the above? A B C D