Description
Q1. A fundamental precept of RAD Application Development is that:
a. it is crucially essential to control customer changes to requirements b.
the most effective way of capturing customer requirements is to employ highly skilled business analysts to elicit requirements from customers
c. the most effective way of capturing customer requirements is to let customers see what they will get
d. the customer is always right
Q2. When customers have a long-list of desired features they want to include in a product, an effective and objective way to prioritize them is: a. to ask customers to identify “must haves” and “wanna have.s” b. to let the project manager determine which features are high priority, which are middle priority, and which are low priority c. to let the technical team review the features to determine which can and which cannot be achieved in the project’s limited time frame d. to employ the Poor Man’s Hierarchy
Q3. Under what conditions is the Waterfall model most appropriate? a. Large, relatively routine projects b. Small, dynamic projects c. Large, dynamic projects d. The current consensus is that it is not appropriate in any circumstances
Q4. Which of the following s/w development approaches is most effective in most situations? a. agile methods b. iterative methods c. traditional Waterfall methods d. No one approach is most effective in most situations — the developer’s challenge is to determine which method best fits the circumstances being faced
Q5. Agile techniques, such as Scrum, see s/w project management: a. as requiring a high level of discipline and process b. as largely useless, because s/w development is filled with so many uncertainties that it defies project management discipline c. as largely concerned with “art” rather than “science,” where effective use of people is central to effective s/w development d. as indistinguishable from the system development life cycle
Q6. In Scrum, the iteration during which work is done is called: a. a scrum b. a burst c. a sprint d. a round
Q7. When plotting incremental progress on a project, we find at the early stages incremental progress is great, but beyond a certain point, incremental progress becomes smaller and smaller. a. true b. false
Q8. A primary driver of RUP is risk mitigation. a. true b. false
Q9. A use case views a system from the perspective of a user. a. true b. false
Q10. Application Development holds that traditional systems analysis has little value in identifying customer requirements. a. true b. false
Q11. Top-down iterative s/w development a. produces usable results as early as Iteration 1 b. focuses on maintaining overall systems integrity through a gradual development process c. completely rejects the employment of Waterfall stages when developing s/w d. is driven by careful pre-specification of project requirements
Q12. With RUP, architectural issues are of primary importance in: a. the inception phase b. the elaboration phase c. the construction phase d. the transition phase
Q13. The staged iterative approach to s/w developmen.t a. produces usable results as early as Iteration 1 b. focuses on maintaining overall systems integrity through a gradual development process c. completely rejects the employment of Waterfall stages when developing s/w d. is driven by careful pre-specification of project requirements
Q14. A fundamental precept of RAD Application Development is that: a. it is crucially important to control customer changes to requirements b. the most effective way of capturing customer requirements is to employ highly skilled business analysts to elicit requirements from customers c. the most effective way of capturing customer requirements is to let customers see what they will get d. the customer is always right
Q15. RAD Application Development holds that traditional systems analysis has little value in identifying customer requirements. a. true b. false Q16. When estimating project parameters: a. estimates can only be made when estimators have access to performance data from previous projects b. estimates are quite accurate in the earliest stage of the project, then gradually decrease in accuracy as the project is executed c. estimates are about 20% accurate on high-risk projects, and 10% accurate on more routine projects d . estimates are quite inaccurate in the earliest stages in the project, then gradually improve as the project is executed Q17. Iterative software development gained a measure of popularity in the 1980s with Barry Boehm’s roll out of: a. Application prototyping b . The spiral model c. The Capability Maturity Model d. Scrum Q18. When testing at the end of an iteration shows the existence of breakage, this is a sign that the project is out of control. a. true b . false Q19. With RUP, Scrum, and time-boxed scheduling, the releases that are generated by each iteration: a. should be comprised of executable code b. need to go through rigorous customer acceptance testing c. should be traceable to elements of the WBS contained in the master plan d. can be documents and artifacts Q20. With time-boxed scheduling, project team members: a. typically operate in a virtual team environment b. coordinate their efforts through monthly project team meetings c. Constantly look for opportunities to carry out work concurrently to speed the schedule d . meet in daily scrums Q21. Which of the following requirements definition tools depends on brain storming requirements in a single day? a. process/environment (P/E) diagram b. Flow chart c. JAD session d. structured English Q22. A culture trait common among software developers who are effective in using agile development techniques is: a. they are comfortable with the linear development of software b . they are most comfortable working within 8-12 week time frames c . They adhere to strong software development discipline d . they are impatient with formal development processes Q23. Data employed in the Project Definition Document (PDD) constitutes: a. conceptual estimates b. preliminary estimates c. definitive estimates d. integral estimates Q24. The most effective way to get customers to see that they can’t have it all is: a. to prioritize features using the 80:20 Rule b. to allow them to select whatever features they want, then to deliver only those features that are produced in the time-boxed schedule c. to have the technical team determine which customer desired features can be delivered, and which cannot d. to have the customer wish-list of features prioritized by the project manager Q25. Which of the following requirements definition tools focuses on defining players/rules/interfaces/data sets? a. process/environment (P/E) diagram b. flow chart c. JAD session d. structured English