Chapter 2 Flashcards

(51 cards)

1
Q

is one of the earliest and most traditional software development models.

A

Waterfall MOdel

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Who introduced Waterfall model?

A

Winston W. Royce in 1970

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

it follows a linear and sequential apprach. where each development must be completed before the next

A

Waterfall model

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q
  • Sequential and rigid (each phase must finish before the next starts).
  • Documentation-heavy (detailed records at each stage).
  • Requirements must be clear and stable before development begins.
  • Testing comes late in the process.
A

Waterfall model

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

foundational SDLC approach that offers simplicicity and structure

A

Waterfall model

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

that emphasizes quick prototyping, fast iterations, and user involvement over lengthy documentation and rigid planning.

A

Rapid Application development

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

focuses on building functional prototypes quickly, gathering feedback from users, and refining the system in multiple iterations until the final product is achieved.

A

RAD

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

is especially useful when project requirements are not fully known at the start or are expected to change during development.

A

RAD

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

is a software development approach where a prototype (an early working version of the software) is built, tested, and refined until it evolves into the final product

A

Prototyping model

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Instead of trying to gather and finalize all requirements upfront, this model allows developers and users to interact with an initial version of the system, provide feedback, and continuously refine the software.

A

Prototyping model

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

is an early approximation of a final system or product. It is not the complete software but a partial implementation that demonstrates core features, user interface, or workflow.

A

Prototype

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Prototype that is built quickly and discarded once requirements are clarified.

A

Throwaway/Disposable

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Prototype that is continuously refined until it becomes the final system.

A

Evolutionary

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Prototype that is Developed in pieces (modules) and integrated

A

Incremental

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Prototype that is Built rapidly using reusable components

A

Extreme

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

is an effective approach when project requirements are unclear or evolving. By engaging users early and often, it ensures that the final system meets user needs and expectations

A

Prototyping model

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

is a software development approach where the system is designed, implemented, and tested in small increments until the final product is complete.

A

Incremental

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

. Instead of delivering the entire system at once, developers divide it into smaller modules or parts. Each increment adds new functionality to the software, and the product grows progressively.

A

Incremental Model

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

This model is considered a balance between the Waterfall Model and Iterative Model — it provides structure while still allowing flexibility for changes.

A

Incremental model

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

is an effective approach when projects need early delivery, gradual improvements, and flexibility in handling changing requirements.

A

Incremental model

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

While it requires careful planning and can be costly in integration, its benefits in terms of early usability, reduced risk, and customer satisfaction make it one of the most widely used models in modern software development.

A

Incremental mdoel

22
Q

The ____ combines elements of linear and parallel process flows.

A

incremental model

23
Q

The ___ applies linear sequences in a staggered fashion as calendar time progresses

A

incremental model

24
Q

is a powerful software development approach that allows systems to evolve through repeated cycles of development, testing, and feedback.

A

Iterative model

25
It reduces risks, improves quality, and adapts to changing requirements. However, it requires skilled teams, proper planning, and close stakeholder involvement.
Iterative model
26
___ methodology was introduced — a flexible, collaborative, and iterative approach to software development
Agile
27
a software development methodology that emphasizes: - Iterative and incremental delivery - Customer collaboration - Flexibility in responding to change - Continuous improvement
Agile model
28
Who introduced Agile model
Agile Manifesto (2001)
29
What is the four core values of Agile Manifesto
- Indiciduals and interactions - working software - Customer collaboration - Responding to change
30
lightweight Agile framework used to manage and control software development.
Scrum
31
It provides a structured process with defined roles, events, and artifacts that help teams deliver working software incrementally.
Scrum
32
____ is not a methodology but a framework — it provides guidelines, not strict rules, and teams adapt it to their context.
Scrum
33
What are the Scrum Roles
Product Owner Scrum Master Development Team
34
Represents the customer/stakeholders. Manages the Product Backlog (list of features, requirements, improvements).
product owner
35
Ensures the team delivers value to the business.
Product owner
36
Facilitates the Scrum process. Ensures Scrum principles are followed
Scrum master
37
Removes obstacles (impediments) for the team. Acts as a servant-leader, not a boss.
Scrum master
38
Cross-functional professionals (developers, testers, designers, etc.). Self-organizing, no external manager.
Development teams
39
Responsible for delivering potentially shippable increments each sprint.
Dvelopment team
40
What are the srum events
- Sprint Planning - Daily Scrum - Sprint Review - Sprint retrospective
41
Held at the start of each sprint. Product Owner presents prioritized backlog items. Team decides what they can deliver in the sprint. Sprint Goal is defined.
Sprint Planning
42
15-minute daily meeting. Team members answer:
Daily Scrm
43
Held at the end of each sprint. Team demonstrates the completed increment to stakeholders. Feedback is collected to adjust the product backlog.
Sprint Review
44
After the sprint review. Team reflects on the sprint process. Discusses what went well, what didn’t, and how to improve in the next sprint.
Sprint Retrospective
45
What are the scrum artifacts
- Product backlog -Sprint backlog - Increment
46
An ordered list of all features, requirements, and enhancements for the product. Owned and prioritized by the Product Owner.
Product Backlog
47
A list of tasks selected for a specific sprint. Created during sprint planning.
Sprint Backlog
48
The sum of all completed backlog items during a sprint. Must be in a usable state, meeting the Definition of Done (DoD).
Increment
49
is a philosophy and mindset for flexible, iterative software development.
Agile
50
is a structured framework within Agile that defines roles, events, and artifacts to implement Agile effectively.
Scrum
51
No process, just coding. Works only for small experimental or research projects, but highly risky.
Big Bang