Methodologies (Midterms) Flashcards

1
Q
  • A structured set of activities required to develop a software system.

-an abstract representation of a process. It presents a description of a process from some particular perspective.

A

Software process

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

processes where all of the process
activities are planned in advance and progress is measured against
this plan.

A

Plan-driven processes

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

planning is incremental and it is easier to change the process to reflect changing customer requirements

A

Agile processes

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

sequential design used in software
development process, in which progress is seen as flowing
steadily downwards.

it is a Plan-driven model

A

Waterfall model

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q
  • Combines the structure of the waterfall methodology and
    the flexibility of the spiral methodology by enforcing the prioritization of
    activities.
  • priorities are evaluated and those activities that are
    considered most valuable are completed first
A

Water sluice model

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

The requirement specifications from first phase are studied in this phase and system design is prepared

A

System Design

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

unifies a software team by providing a common view of the
development process and a shared vision of a common goal

A

Rational unified model

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q
  • A way to manage a project by breaking it up into several phases.
  • Group of software development methodologies based on iterative
    development.
A

Agile methodology

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

The aim of agile methods

A

to reduce overheads

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q
  • Are based on an iterative approach to software development
  • Are intended to deliver working software quickly and evolve this quickly to meet changing
    requirements.
A

Agile methodology

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

A approach to software engineering is based around separate
development stages with the outputs to be produced at each of these stages planned in advance.

A

Plan-driven development

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

Specification, design, implementation and testing are inter-leaved and the outputs from the development process are decided through a process of negotiation during the software development process.

A

Agile development

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

An iterative and incremental agile software development methodology for managing product development.

A

SCRUM MODEL

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

determine the Sprint Goal

A

Sprint Planning

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

a short (15 minutes long) meeting, which is held every day before
the Team starts working

A

Daily Scrum

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

team presents what is accomplished during the sprint

A

Sprint Review

17
Q

a facilitator who arranges daily meetings, tracks the backlog of work to be done, records decisions, measures progress against the backlog and communicates with customers and management outside of the team.

A

Scrum master

18
Q
  • Also referred to as RAD
  • incremental software development process model that allows usable
    systems to be built in as little as 60-90 days.
  • put less emphasis on planning and more emphasis on process.
  • Requires highly skilled developers/designers
A

Rapid application development model

19
Q

a methodology that combines the features of the prototyping model and the waterfall model

A

Spiral model

20
Q

a software development methodology which is intended to improve software quality and responsiveness to changing customer requirements.

A

Extreme programming methodology

21
Q

a software development methodology which is intended to improve software quality and responsiveness to changing customer requirements.

A

Extreme programming methodology

22
Q

A type of development in which emphasis is placed on developing prototypes early in the development process to permit early feedback and analysis in support of the development
process.

A

Prototyping model

23
Q

software development where the product is designed, implemented and tested incrementally (a little more is added each time) until the product is finished

A

Incremental Development/Model

24
Q

The process is repeated until the entire product development is
completed.

A

Iterative and incremental model