Lecture 1 Flashcards

1
Q

A process used by the software industry to design, develop, and test high quality software.

A

Software Development Life Cycle (SDLC)

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

Is an international standard for software life-cycle processes

A

ISO/IEC 12207

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

The most important and fundamental stage in SDLC.

Stages In SLDC

A

Stage 1: Planning

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

This is done through an SRS (Software Requirement System) document which consists of all the product requirements to be designed and developed during the project life cycle.

Stages In SLDC

A

Stage 2: Requirement Analysis

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

SRS is the reference for product architects to come out with the best architecture for the product to be developed.

Stages In SLDC

A

Stage 3: Designing the Product Architecture

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

The programming code is generated as per DDS during this stage.

Stages In SLDC

A

Stage 4: Implementation

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

This stage is usually a subset of all the stages as in the modern SLDC models, the testing activities are mostly involved in all the stages of SDLC.

A

Stage 5: Testing

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

Sometimes product deployment happens in stages as per the business strategy of that organization.

A

Stage 6: Deployment and Maintenance

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

This is the first Process Model to be introduced. And the earliest used for software development to ensure success of the project.

A

Waterfall Model

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

Also referred to as linear-sequential life cycle mode. Simple to understand and use.

A

Waterfall Model

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

The basic idea behind this method is to develop a system through repeated cycles (iterative) and in smaller portions at a time (incremental).

A

Iterative Model

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

Combines the idea of iterative development with the systematic, controlled aspects of waterfall model.

A

Spiral Model

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

It has four phases. A software project repeatedly passes through the phases in iteration called spirals.

A

Spiral Model

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

Identification
Design
Construct or Build
Evaluation and Risk Analysis

A

Phases of Spiral Model

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

Also known as the Verification and Validation Model

A

V-Model

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

An extension of the waterfall model based on the association of a testing phase for each development stage.

A

V-Model

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q
  • A start-from-scratch SDLC model
  • Simplest SDLC model
  • Considered the worst SDLC model
  • Focuses all the possible resources in the software development and coding, with very little or no planning.
A

Big Bang Model

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

A combination of iterative and incremental process models with focus on process adaptability and customer satisfaction by rapid delivery or working software product.

A

Agile Model

19
Q
  • This model breaks down the product into small incremental builds.
  • Each iteration is a small-time “frame” (termed Time Box) that last anywhere from one to four weeks.
A

Agile Model

20
Q
  • Published in February 2001.
  • A proclamation designed to improve software development methodologies.
  • Directly responds to the inefficiency of traditional development processes.
A

The Agile Manifesto

21
Q

An agile development process focused primarily on ways to manage task in team-based development conditions.

A

Scrum (1995)

22
Q

The scrum can set up the master team, arrange the meeting and remove obstacles for the process.

A

Scrum Master

23
Q

Makes the product backlog, prioritizes the delay and is responsible for the distribution of functionality on each repetition.

A

Product owner

24
Q

The team manages its work and organizes the work to complete the sprint or cycle.

A

Scrum Team

25
Q

Each iteration of scrum is termed as.

A

Sprint

26
Q

Is a software development rapid application development technique that provides an agile project distribution structure.

A

Dynamic Software Development Method (DSDM)

27
Q

Its major goal is to provide clients with timely updated and functional software.

A

Feature Driven Development (FDD)

28
Q

Its goal is to speed up software development while lowering costs.

A

Lean Software Development

29
Q

Encourages numerous “releases” of the product in short development cycle, which increases the system’s efficiency and provides a checkpoints where any client requirements may be quickly incorporated.

A

Extreme Programming (XP)

30
Q

A model based on prototyping and iterative development without any specific planning.

A

Rapid Application Development (RAD)

31
Q

Business Modeling
Data Modeling
Process Modeling
Application Modeling
Testing and Turnover

A

RAD Phases

32
Q

A well defined task which is a collection of several operation to achieve one goal.

A

Project

32
Q

A well defined task which is a collection of several operation to achieve one goal.

A

Project

33
Q

The complete procedure of software development.

A

Software Project

34
Q

A person who undertakes the responsibility of executing the software project.

A

The Project Manager

35
Q

This technique assumes the software as a product of various compositions.

A

Decomposition Technique

36
Q

This technique uses empirically derived formulae to make estimation

A

Empirical Estimation Technique

37
Q

Any line of text in a code that is not a comment or blank line.

A

Lines of Code

38
Q

A unit of measurements to express the amount of business functionality, an information system (as a product) provides to a user.

A

Function Points (FP)

39
Q

The one who developed function Point Analysis in 1979 at IBM and it has been further modified by the International Function Point Users Group (IFPUG).

A

Allan J. Albrecht

40
Q

Is used to make estimate of the software project, including its testing in terms of functionality or function size of the software product.

A

Function Point Analysis (FPA)

41
Q

Refers to a roadmap of all activities to be done with specific order and within time slot allotted to each activity.

A

Project Scheduling

42
Q

Scrum
Crystal Clear
Extreme Programming
Lean Software Development
Feature Driven Development
Dynamic Software Development Method

A

Agile Methodologies