Chapter_11-KEY0 - A release plan B user story C patch D...

Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
Chapter 11 – Managing Systems Implementation 1. A ____ shows data that one module passes to another. A. data couple B. library module C. control module D. data pilot 2. The process of breaking a system into modules is called ____. A. cohesion B. partitioning C. desk checking D. pseudocode 3. A(n) ____ approach proceeds from a general design to a detailed structure. A. iteration B. peer-to-peer C. top-down D. bottom-up 4. A(n) ____ indicates that one or more modules are repeated. A. status flag B. parallel indicator C. iteration D. loop 5. Modules that are considered to be independent are ____ coupled. A. loosely B. tightly C. casually D. seriously 6. A short, simple requirements definition is referred to as a _____.
Background image of page 1
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: A. release plan B. user story C. patch D. test environment 7. To review the interface of the system with the actual users, companies perform a(n) ____. A. code review B. iteration planning meeting C. design walkthrough D. desk check 8. Syntax errors refer to ____ errors. A. input B. data C. logic D. language grammar 9. When ____ testing is performed, the programmer simulates each program outcome and displays a message to indicate if the program executed successfully. A. stub B. desk C. parallel D. unit 10. A ____ is a web-based audio broadcast. A. tutorial B. podcast C. help system D. flowchart...
View Full Document

{[ snackBarMessage ]}

Ask a homework question - tutors are online