Software Engineering Final

0.0(0)
studied byStudied by 0 people
0.0(0)
full-widthCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/29

encourage image

There's no tags or description

Looks like no tags are added yet.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced
Call with Kai

No study sessions yet.

30 Terms

1
New cards

In Scrum, who is responsible for managing the product backlog?

A. Stakeholders

B. Scrum Master

C. Product Owner

D. Development Tram

C. Product Owner

2
New cards

A software product team is applying Scrum, and is breaking down the work for a use case into required developer tasks. They have identified an implementation task to write the source code. To meet a typical definition of done for this use story, which other tasks should be identified?

A. Write unit tests, write documentation, write acceptance tests

B. Test the code, document the code, accept the code

C. Write/run unit tests, integrate the code, review the code, write documentation, write/run acceptance tests

D. Write the code, commit the code, integrate the code, test the code

C. Write/run unit tests, integrate the code, review the code, write documentation, write/run acceptance tests

3
New cards

What are story points?

A. An estimate on the relative business value of a user story

B. A numeric estimate on the size of a user story based on the number of developer tasks

C. An estimate on the effort to implement a user story in hours

D. A numeric estimate on the relative effort to complete a user story

D. A numeric estimate on the relative effort to complete a user story

4
New cards

What is the main purpose of a sprint in Scrum?

A. To release a product to the customer

B. To deliver a potentially shippable product increment

C. To design the architecture of the product

D. To test and debug the product

B. To deliver a potentially shippable product increment

5
New cards

What is EARS?

A. A requirement format to specify user requirements

B. A requirement format to specify functional requirements

C. An approach to peer review requirements

D. EARS is used to write the vision and scope document

B. A requirement format to specify functional requirements

6
New cards

Which of the following is not an example of quality attributes?

A. The user needs to get the response within 3 seconds

B. The system shall be available at least 20 hours a day

C. The user needs to upload a piece of music they recorded

D. The data’s privacy and security must be preserved

C. The user needs to upload a piece of music they recorded

7
New cards

For a software life cycle process, the term “life” refers to the time from:

A. Product conception to product retirement

B. Product launch to last product upgrade

C. Idea for product to product launch

D. Product development to produce replacement

A. Product conception to product retirement

8
New cards

A specific Agile practice is to have _____ releases, so that releases happen frequently.

A. Frequent

B. Small

C. Simple

D. Continuous

B. Small

9
New cards

Which of the following is not an estimation technique?

A. Velocity Estimates

B. Story Points

C. Gantt Charts

D. CPM or PERT

D. CPM or PERT

10
New cards

In Agile, an iteration plan is generated in a _____ meeting. The developers break down each use case into _____ with estimated times, where are _____.

A. Iteration / a work breakdown structure / assigned by a manger

B. Iteration Planning / tasks / self-assigned

C. Iteration Planning / tasks / assigned by a manager

D. Iteration Planning / features / self-assigned

B. Iteration Planning / tasks / self-assigned

11
New cards

An actor in a use case is:

A. A system admin

B. A human being

C. Another system

D. An external entity that interacts with the system

D. An external entity that interacts with the system

12
New cards

Which of the following is not a use case?

A. Click the submit button

B. Check out a book

C. Buy item

D. Make deposit

A. Click the submit button

13
New cards

Which of the following is NOT recommended when writing a use case?

A. Use “verify” instead of “check if”

B. Use an effective numbering scheme to make clear steps

C. Don’t handle exceptions in the main flow

D. It is OK to include some GUI actions

D. It is OK to include some GUI actions

14
New cards

Marino and her development team have finished a project. At the end of the project, they spent some time reflecting and discussing the project. They identified a number of ways the work done could be done better the next time. These identified ways of improving the project are:

A. What went well in the project

B. Lessons learned

C. Sprint retrospectives

D. A metric

C. Sprint retrospectives

15
New cards

What is a key difference between user cases and user stories?

A. A use case description defines a benefit, while a user story generally does not

B. A use case description defines a goal, while a user story generally does not

C. A use case description defines an actor, while a user story generally does not

D. A use case description defines the interactive steps of a task, while a user story generally does not

D. A use case description defines the interactive steps of a task, while a user story generally does not

16
New cards

How do you calculate the actual velocity of a team for a sprint?

A. Take the total task hours for the tasks that developers completed within the sprint

B. Take the number of tasks that developers completed within the sprint

C. Take the number of user stories completed within the sprint

D. Take the total number of story points of the user stories completed within the sprint

D. Take the total number of story points of the user stories completed within the sprint

17
New cards

For a software requirement, a development team is planning a task to write the implementation code and a task to inspect a reviewable version of the code for defects. After the inspection, the coding task addresses the discovered defects for the final version. What kind of task dependency is this between the coding and inspection tasks?

A. Finish-Start

B. Start-Finish

C. Finish-Finish

D. Start-Finish

A. Finish-Start

18
New cards

A product support team has a long-term task to operate version 1 of an invoicing service. Version 2 is almost ready to replace version 1, so another long-term task is planned to operate that version. The service must be available at all times, so if Version 2 is not in place, Version 1 is used. What kind of task dependency is this between the Version 1 and Version 2.

A. Start-Finish

B. Finish-Start

C. Start-Start

D. Finish-Finish

A. Start-Finish

19
New cards

Within a sprint, suppose a user story estimated at 13 story points is partly completed (around 50%). The developers say the work for it is half done. How many story points would the partial work contribute toward their velocity for the sprint?

A. 8 (higher Fibonacci number)

B. 5 (lower Fibonacci number)

C. 0

D. 6.5

C. 0

20
New cards

Which of the following is correct?

A. It is OK to include QUI details when writing a use case

B. We invite the clients to attend both the sprint review and retrospective meeting at the end of a sprint

C. We break a use case into tasks during the release planning meeting

D. Waterfall process can be very useful when the requirements are stable and well-defined

D. Waterfall process can be very useful when the requirements are stable and well-defined

21
New cards

Free Response : What are the 4 design activities in software engineering?

Database, Interface, Architecture, and Component Design

22
New cards

Free Response : List one advantage and one disadvantage of the waterfall model.

Advantages : useful when requirements are clear and stable

Disadvantages : difficult for customer to state all requirements explicitly, working software comes later, not good when requirements change

23
New cards

Free Response : Why do we need to prioritize requirements?

Software requirements are important because they clearly define what a system must do and reduces the risk of error and project failure.

24
New cards

Free Response : List 4 agile practices.

The Planning Game, Simple Design, Pair Programming, 40-Hour Work Week, Small Releases, Continuous Testing, Collective Code Ownership, On-Site Customer, System Metaphor, Refactoring, Continuous Integration, Coding Standards

25
New cards

Free Response : During requirements elicitation, a stakeholder says, “The system should generate reports quickly and accurately.” Identify 2 potential ambiguities in this requirements and explain how you would clarify or refine it.

Both “quickly” and “accurately” are vague. Ask stakeholder to explain more specifically what they expect. Provide a measurable value for how quick (3 seconds, 1 minute, 5 minutes). What percentages of accuracy are they looking for?

26
New cards

Free Response : What is the difference between product backlog and sprint backlog?

Product Backlog are the requirements the product should have

Sprint Backlog are the tasks created from the list of requirements

27
New cards

Free Response : List 2 techniques used to determine if a use case is written at the right abstraction level.

The Boss Test, Elementary Business Process Test (EBP), The Size Test

28
New cards

Free Response : Why do we need prototyping?

Prototyping provides a good visual to show the clients so that they can actually see the progress. It is much easier to show a working visual prototype than to show the clients code, which they may not understand.

29
New cards

Free Response : What is the purpose of writing Vision and Scope documentation?

A Vision and Scope document defines the overall goals, boundaries, and requirements of a project so there is a clear understanding of what the system will accomplish.

30
New cards

Free Response : Recall the Software Iron Triangle. What is the main takeaway from this triangle.

The Software Iron Triangle consist of Scope, Resources, and Schedule where all 3 determine the quality of the project. The main takeaway is what a company or client prioritizes.