SWE201c p2

• When is testing complete?

  
  

  A. When you find the last bug

  B. When you have completed all the tests in the test plan

  C. When you run out of time

  D. When you have tested every input

  C
• Which of the following is an example of black-box testing?

  
  

  A. Developing additional tests when every if statement does not evaluate both true and false once given the current test suite

  B. Developing additional test cases to force a division by zero

  C. Developing test cases to exercise error-prone constructs

  D. Developing test cases based on typical user behavior

  D
• In waterfall method, you get your product in one big bang deployment

  
  

  A. True

  B. False

  A
• Sashimi model may help decrease the time duration of the project by

  
  

  A. Adding more skilled resources of the project

  B. Overlapping the phases

  B
• In predictive models, change during the development is expected.

  
  

  A. True

  B. False

  B
• In which model might you end up building something different than what you originally planned?

  
  

  A. Adaptive models

  B. V-Model

  C. Waterfall models

  A
• Which model is the best model to use in all situations?

  
  

  A. Adaptive since it has most advantages

  B. None

  C. Waterfall

  B
• In the Unified Process, all requirements work is done upfront and no requirements work is done in the construction phase.

  
  

  A. True

  B. False

  B
• A team divided the application they were building into 4 parts and planning to build one part at a time. To build each part, they are planning to go through the steps of requirements, design, implementation, test, and deployment. Also, they are planning to complete each part fully with high fidelity. By fidelity we mean the completeness of the features implemented in each part. Based on this information, what type of model do you suggest they use for their software development process?

  
  

  A. Iterative and Incremental

  B. Iterative

  C. Incremental

  C
• A team is working on a problem where the requirements are well known but they are short on time. They prefer to start the design phase when some of the requirements have been defined. Similarly, they want to start coding when the design for part of the system is ready. What model will best fit their needs?

  
  

  A. Sashimi

  B. V-model

  C. Waterfall

  D. Spiral

  A
• In the incremental model variation where you do requirements and design for all of the application once and then just increment on implementation, testing, and deployment, are you making the process more suitable for a predictive or adaptive situation?

  
  

  A. Predictive

  B. Adaptive

  A
• Which of following is NOT true about incremental and iterative models?

  
  

  A. Iterative approaches release every feature with low fidelity and then improve fidelity over time. By fidelity we mean the completeness of the feature.

  B. Incremental approaches release features as they are finished with high fidelity.

  C. An incremental model is one where you can build each part of the system individually but you release all at once.

  D. In a model which is both iterative and incremental, we release features when they are usable. Over time the development team improves existing features and adds new ones

  C
• Which of the following is NOT true for the Waterfall model, V-model and Sashimi model?

  
  

  A. In these models, the team is expected to know the solution really well.

  B. These models will be a good model to be used by a startup implement a new idea that is new to market

  C. In these models, the cost of change depends on how late we find out about the change. If problem requiring a change is found during the implementation phase, it will be more expensive to fix than one found during the design phase.

  D. In these models, we assume that we know requirements really well.

  B
• In the Unified Process, what does the milestone of "Lifecycle Architecture" mean?

  
  

  A. Agreement among stakeholders about the objectives of the project and to proceed with the project.

  B. Agreement among the stakeholders about the technical approach.

  C. Agreement among the stakeholders about the deployment of the system to actual users.

  B
• Select situations listed below where you would NOT use the Unified Process framework.

  
  

  A. Medium-sized project with some risks involved.

  B. Very small, simple project where the problem and solution are well known.

  C. Situation where the organization wants to deliver part of the application early to capture the market ahead of competition.

  D. All requirements are not known early in the project.

  B
• Which of the following is NOT true for Spiral Model?

  
  

  A. It minimizes waste by allowing teams to tailor the effort put into different processes based on the risk involved in each cycle.

  B. Spiral Model is not a model but a process model generator.

  C. You always have to perform all the steps mentioned in the Spiral Model diagram

  D. It is suitable for very large high risk projects

  C
• Which of the following is NOT the benefits of the Unified Process?

  
  

  A. Supports to incorporate other models in the process for example you can use Agile in the construction phase.

  B. Supports / encourages risk identification and mitigation.

  C. Easy to understand and implement.

  D. Supports quality and reuse by putting an emphasis on architecture.

  E. Flexible for handling change.

  C
• Which of the following statements align with the value "Working software over comprehensive documentation" of the Agile manifesto?

  
  

  A. Don't do documentation on an Agile project.

  B. Create documentation when it provides value.

  C. Must write documentation to fulfill company policy.

  B
• Which one of the following statements/situations/conversations align with an Agile mindset?

  
  

  A. Manager: "The customer is suggesting another change in feature X which is complete as per specification. They agree that it was built as we agreed upon but it lacks some functionality and will result in user frustration. Should we implement the change or not?"

  Developer: "Yes, if it does not fulfill user needs, we should make the change."

  B. A manager providing a status update to a customer says: "We are done with requirements and design so we are 50% done."

  C. A software vendor says to a client: "We must define exactly what the user needs and put that in agreement."

  D. A manager e-mails her team: "Meeting face to face just for a 15 minute discussion is inefficient, let us all just dial-in from our desk."

  A
• In Scrum, when is the sprint backlog created?

  
  

  A. At the beginning of the project

  B. During the sprint planning meeting

  C. During the backlog refinement meeting

  D. Whenever needed

  B
• In Scrum, how is Product Backlog Arranged?

  
  

  A. Most important items at the top, least important items at the bottom.

  B. Large items at the top, small items at the bottom

  C. Into categories, P1, P2, P3, etc.

  D. Items are randomly arranged

  A
• Which Agile Value does the following principle align with:

  "Build projects around motivated individuals, give them the environment and support they need and trust them to get the job done."

  
  

  A. Individuals and Interaction Over Process and Tools

  B. Respond to Change Over Following a plan

  C. Customer collaboration over contract negotiation

  D. Working software over comprehensive documentation

  A
• Which of the following align with the agile principle:

  "Business people and developers work together daily throughout the project."

  
  

  A. Since agile methodologies do not recommend writing all detailed requirements upfront, it is really important to support greater collaboration between business people and developers so that they can build a shared understanding of what needs to be built.

  B. Business people and developers MUST meet face-to-face daily to clarify confusions, questions etc.

  C. Business people also need to code together with developers to make faster progress.

  A
• If a developer says "we don't to do any discussion or upfront design" because we are agile", is he/she truely representing what agile means

  
  

  A. Yes, because in agile, we start coding right away

  B. No, agile does not mean start coding right away.

  B
• When applying agile, we don't need to do any release planning.. We only plan for a week.

  
  

  A. True

  B. False

  B
• Which one of the following statements/situations/conversations align with an agile mindset?

  
  

  A. A manager e-mails her team: "Meeting face to face just for a 15 minute discussion is inefficient, let us all just dial-in from our desk."

  B. Manager: "The customer is suggesting another change in feature X which is complete according to the specification. They agree that it was built as we agreed upon but it lacks some functionality and will result in user frustration. Should we implement the change or not?"

  Developer: "Yes, if it does not fulfill user needs, we should make the change."

  C. A manager providing a status update to a customer says: "We are done with requirements and design so we are 50% done."

  D. A software vendor says to a client: "We must define exactly what the user needs and put that in the agreement."

  B
• Which of the following statements align with following Agile Principle:

  "Deliver working software frequently, from a couple of weeks to a couple of months, with a preference for the shorter timescale"

  
  

  A. We MUST release software to actual users every couple weeks.

  B. We should frequently deliver software in some environment (not necessarily to production always) to gather user/client feedback

  C. We should NOT release software to a production environment on a shorter timeframe. We should ONLY release it in lower environment (e.g., a test environment).

  B
• Which of the following align with this principle:

  " Working software is the primary measure of progress."

  
  

  A. If a team has written the requirements and done the design for 5 out of 10 stories, then the team has made some progress (they are more than 0% done)

  B. On a 10 month project, the team has been working for 5 months. Thus, the project is 50% complete.

  C. If a team has delivered 5 features out of 10 features (or stories), team has made progress (they are more than 0% done)

  C
• In which of the following situations, would you NOT recommend using an agile process?

  
  

  A. For a project where the customer wants to build an e-commerce website but the development team has never done something like this before. Further, the company knows that they want to build an e-commerce website but are not sure about the functionality at this time.

  B. For a project where requirements are well known but the technology and solution are unknown (i.e., changes expected in the solution).

  C. For a project where change is not expected. requirements are well known, and the solution is both well known and repeatable.

  D. For a project where the customer has an idea of what they want to build but is not sure of his/her exact needs.

  C
• Which of the following is true for agile projects?

  
  

  A. An agile methodology may help a team to go to market early by delivering with limited functionality.

  B. Agile methods do not require rework because the team knows exactly what they building. No refactoring of code is needed.

  C. Scrum is the best way to implement agile.

  D. If somebody says, they use an agile methodology, they must be doing either Scrum or XP.

  A
• What issues do you see in following story?

  As a grocery buyer, I want to see different food items in different colors: red for meats, brown for grains, green for vegetables so that i can identify food items by type.

  
  

  A. This story breaks the quality of negotiable.

  B. This story is not testable.

  C. The user "grocery buyer" is not a valid user.

  D. This story has no issues. It has all the info we need in a story.

  A
• The goal of a story writing workshop is to:

  
  

  A. Write as many foundational stories as possible.

  B. Write as many user stories as possible in priority order.

  C. Write as many user stories as possible under the themes identified.

  D. Write as many themes as possible.

  C
• Who estimates the effort to complete a product backlog item (a user story)?

  
  

  A. The scrum development team after clarifying the requirement.

  B. The scrum master with input from the scrum development team.

  C. The most senior people in the organization such as the engineering managers and the chief architect.

  D. The product owner with input from the scrum development team.

  A
• A team was doing release planning and they decided that the next release will include all stories from Story 1 to Story 11 (see table 2 below).

  The velocity range to be used for the release planning is 15-22.

  The team works in a 2 week iteration.

  It costs about $50,000 per iteration to fund the entire team.

  Calculate the estimated duration for next release. Additionally, how much will this release cost?

  
  

  Table 2: Prioritized Product Backlog

  "Story Title" - "Estimate (in ideal days)"

  Story 1 - 5

  Story 2 - 5

  Story 3 - 8

  Story 4 - 3

  Story 5 - 5

  Story 6 - 5

  Story 7 - 3

  Story 8 - 5

  Story 9 - 8

  Story 10 - 8

  Story 11 - 3

  Story 12 - 3

  Story 13 - 3

  Story 14 - 5

  Story 15 - 8

  Story 16 - 3

  Story 17 - 5

  Story 18 - 5

  Story 19 - 8

  Story 20 - 8

  
  

  A. Duration: 6-8 weeks, Cost: 150K to 200K

  B. Duration: 3-4 weeks, Cost: 150K to 200K

  C. Duration: 10-14 weeks, Cost: 500K to 700K

  D. Duration: 6-8 weeks, Cost: 300K to 400K

  A
• Due to an unpredictable market event, the Product Owner (PO) asked the team to complete the next release in 6 weeks. Assuming the backlog in Table 2 is up to date and prioritized from highest to lowest, the Product Owner wants you to estimate what can be done in next 6 weeks. Describe 1) what can be done, 2) what might be done, and 3) what will not be done.

  The velocity range to be used for the release planning is 15-22.

  The team works in 2 week iteration.

  
  

  Table 2: Prioritized Product Backlog

  "Story Title" - "Estimate (in ideal days)"

  Story 1 - 5

  Story 2- 5

  Story 3 - 8

  Story 4 - 3

  Story 5 - 5

  Story 6 - 5

  Story 7 - 3

  Story 8 - 5

  Story 9 - 8

  Story 10 - 8

  Story 11 - 3

  Story 12 - 3

  Story 13 - 3

  Story 14 - 5

  Story 15 - 8

  Story 16 - 3

  Story 17 - 5

  Story 18 - 5

  Story 19 - 8

  Story 20 - 8

  
  

  A. Most likely: Story 1 to Story 8; Might Be Done: Story 9 to Story 13; Not likely: Rest of the stories

  B. Most likely: Story 1 to Story

  A
• What do we mean by Velocity in agile terms?

  
  

  A. It is calculated at the team level and represents the estimated duration of current iteration.

  B. It is calculated at the team level and represents how much work a team can get done in an iteration.

  C. It represents actual work done in the first iteration of project.

  D. It is a velocity of the individual team members, not the team

  B
• Who prioritizes the work in Scrum?

  
  

  A. Product Owner

  B. The Team

  C. Team Manager

  D. Scrum Master

  A
• In Scrum, when is the sprint backlog created?

  
  

  A. At the beginning of the project

  B. During the sprint planning meeting

  C. During the backlog refinement meeting

  D. Whenever needed

  B
• In Scrum, how is the Product Backlog arranged?

  
  

  A. Into categories, P1, P2, P3, etc.

  B. Items are randomly arranged.

  C. Large items at the top, small items at the bottom.

  D. Most important items at the top, least important items at the bottom.

  D
• In which artifact is the customer requirements stored?

  
  

  A. In the Product Backlog

  B. In a database

  C. In a Scrum Product Requirement Specification

  D. Nowhere. The Scrum Product Owner knows them

  A