 |
| 1 | |
The essence of software engineering practice might be described as understand the problem, plan a solution, carry out the plan, and examine the result for accuracy. |
| | A) | True |
| | B) | False |
|
|
|
| 2 | |
Which of the following is not one of Hooker's core principles of software engineering practice? |
| | A) | All design should be as simple as possible, but no simpler |
| | B) | A software system exists only to provide value to its users. |
| | C) | Pareto principle (20% of any product requires 80% of the effort) |
| | D) | Remember that you produce others will consume |
|
|
|
| 3 | |
Every communication activity should have a facilitator to make sure that the customer is not allowed to dominate the proceedings. |
| | A) | True |
| | B) | False |
|
|
|
| 4 | |
The agile view of iterative customer communication and collaboration is applicable to all software engineering practice. |
| | A) | True |
| | B) | False |
|
|
|
| 5 | |
Software engineers collaborate with customers to define which of the following? |
| | A) | Customer visible usage scenarios |
| | B) | Important software features |
| | C) | System inputs and outputs |
| | D) | All of the above |
|
|
|
| 6 | |
Everyone on the software team should be involved in the planning activity so that we can |
| | A) | reduce the granularity of the plan |
| | B) | analyze requirements in depth |
| | C) | get all team members to "sign up" to the plan |
| | D) | begin design |
|
|
|
| 7 | |
What role(s) do user stories play in agile planning? |
| | A) | Define useful software features and functions delivered to end-users |
| | B) | Determine a schedule used to deliver each software increment |
| | C) | Provide a substitute to performing detailed scheduling of activities |
| | D) | Used to estimate the effort required build the current increment |
| | E) | both a and d |
|
|
|
| 8 | |
Which of the following activities is not one of the four things that need to be accomplished by the generic planning task set? |
| | A) | Develop overall project strategy |
| | B) | Identify the functionality to deliver in each software increment |
| | C) | Create a detailed schedule for the complete software project |
| | D) | Devise a means of tracking progress on a regular basis |
|
|
|
| 9 | |
Analysis models depict software in which three representations? |
| | A) | architecture, interface, component |
| | B) | cost, risk, schedule |
| | C) | information, function, behavior |
| | D) | None of the above |
|
|
|
| 10 | |
The customer can directly observe both the difference between the internal quality of a design and its external quality? |
| | A) | True |
| | B) | False |
|
|
|
| 11 | |
Teams using agile software practices never create models. |
| | A) | True |
| | B) | False |
|
|
|
| 12 | |
Many of the tasks from the generic task sets for analysis modeling and design can be conducted in parallel with one another. |
| | A) | True |
| | B) | False |
|
|
|
| 13 | |
Which of the following is not one of the principles of good coding? |
| | A) | Create unit tests before you begin coding |
| | B) | Create a visual layout that aids understanding |
| | C) | Keep variable names short so that code is compact |
| | D) | Write self-documenting code, not program documentation |
|
|
|
| 14 | |
A successful test is one that discovers at least one as-yet undiscovered error. |
| | A) | True |
| | B) | False |
|
|
|
| 15 | |
Which of the following are tasks in the generic task set for construction? |
| | A) | Build a software component |
| | B) | Create a user interface |
| | C) | Unit test the component |
| | D) | Assess the quality of the component |
| | E) | both a and c |
|
|
|
| 16 | |
Which of the following are valid reasons for collecting customer feedback concerning delivered software? |
| | A) | Allows developers to make changes to the delivered increment |
| | B) | Delivery schedule can be revised to reflect changes |
| | C) | Developers can identify changes to incorporate into next increment |
| | D) | All of the above |
|
|
.