Lessons 3-4 Flashcards

1
Q

What is SDLC?

A

Software Development Life Cycle

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

What are the 7 Phases of SDLC?

A
  • Identifying problems, opportunities, and objectives
  • Determining human information requirements
  • Analyzing system needs
  • Designing the recommended system
  • Developing and documenting software
  • Testing and maintaining the system
  • Implementing and evaluating the system
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What are the 5 phases of SDLC? (Process Flows) R. Pressman, SE 7th Ed

A
  • Communication
  • Planning
  • Modeling
  • Construction
  • Deployment
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What are the 4 kinds of Process Flows?

A
  1. Linear Process Flow
  2. Iterative Process Flow
  3. Evolutionary Process Flow
  4. Parallel Process Flow
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What are the Sequential/Prescriptive Process models?

A
  • Waterfall Model
  • V-model
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What are the Evolutionary/Iterative/Incremental Process Models?

A
  • Incremental Model
  • Spiral Model
  • Prototyping
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What are the other terms for the Waterfall Model? (other names)

A
  • Linear-sequential life cycle model
  • Classic Life Cycle
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What does the Classic life cycle suggest?

A

It suggests a systematic sequential approach to software development

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

Each phase must be completed before the next phase can begin and there is no overlapping in the phases.

A

Waterfall Model

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

Who created the Original Waterfall Model?

A

Winston Royce, 1970

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

What types of systems are appropriate for the waterfall model?

A
  • Embedded systems
  • Critical Systems
  • Large Software Systems
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Waterfall Model Appropriate System

There are some issues which come up in the client environment. To fix those issues, patches are released. Also to enhance the product some better versions are released. Maintenance is done to deliver these changes in the customer environment.

A

Embedded Systems

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

Waterfall Model Appropriate System

where there is a need for extensive safety and security analysis of the software specification and design

A

Critical Systems

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

Waterfall Model Appropriate System

that are part of broader engineering systems developed by several partner companies

A

Large Software Systems

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

What are the 6 phases in the Waterfall Model?

A
  • Requirement Gathering and Analysis
  • System Design
  • Implementation
  • Integration and Testing
  • Deployment of system
  • Maintenance
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Waterfall Model Phase

All possible requirements of the system to be developed are captured in this phase and documented in a requirement specification document

A

Requirement Gathering and analysis

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

Waterfall Model Phase

The requirement specifications from first phase are studied in this phase and the ________ is prepared. ________ helps in specifying hardware and system requirements and helps in defining the overall system architecture.

A

System Design

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

Waterfall Model Phase

With inputs from the system design, the system is first developed in small programs called units, which are integrated in the next phase. Each unit is developed and tested for its functionality, which is referred to as Unit Testing.

A

Implementation

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

Waterfall Model Phase

All the units developed in the implementation phase are integrated into a system after testing of each unit. Post integration the entire system is tested for any faults and failures.

A

Integration and Testing

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

Waterfall Model Phase

Once the functional and non-functional testing is done; the product is deployed in the customer environment or released into the market.

A

Deployment of system

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

Waterfall Model Phase

There are some issues which come up in the client environment. To fix those issues, patches are released. Also to enhance the product some better versions are released. This is done to deliver these changes in the customer environment.

A

Maintenance

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

Illustrates how verification and validation actions are associated with earlier engineering actions

A

V-Model

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

Depicts the relationship of quality assurance actions to the actions associated with communication, modeling, and early construction activities

A

V-Model

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

How does the V-Model work?

A

As a software team moves down the left side of the V, basic problem requirements are refined into progressively more detailed and technical representations of the problem and its solution.

Once code has been generated, the team moves up the right side of the V, essentially performing a series of tests (quality assurance actions) that validate each of the models created as the team moved down the left side

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

A software project repeatedly passes through these phases in iterations

A

Spiral Model

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

Who created the Spiral Model?

A

Boehm, 1988

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

In the spiral model, what is term for “ repeatedly passes through these phases in iterations”?

A

Spirals

29
Q

Combines change avoidance with change tolerance

A

Spiral Model

30
Q

Assumes that changes are a result of project risks and includes explicit risk management activities to reduce these risks

A

Spiral Model

31
Q

What are the phases for the Spiral Model?

A
  • Objective setting
  • Risk assessment and reduction
  • Development and validation
  • Planning
32
Q

Spiral Model Phase

Specific objectives for that phase of the project are defined

A

Objective Setting

33
Q

Spiral Model Phase

Constraints on the process and the product are identified and a detailed management plan is drawn up

A

Objective Setting

34
Q

Spiral Model Phase

Project risks are identified

A

Objective Setting

35
Q
A
36
Q

Spiral Model Phase

Alternative strategies, depending on these risks, may be planned

A

Objective Setting

37
Q

Spiral Model Phase

For each of the identified project risks, a detailed analysis is carried out

A

Risk Assessment and Reduction

38
Q

Spiral Model Phase

Steps are taken to reduce the risk

A

Risk Assessment and Reduction

39
Q

Spiral Model

After risk evaluation, a development model for the system is chosen

A

Development and Validation

40
Q

Spiral Model Phase

The project is reviewed and a decision made whether to continue with a further loop of the spiral

A

Planning

41
Q

Spiral Model Phase

If it is decided to continue, plans are drawn up for the next phase of the project

A

Planning

42
Q

building software application prototypes which displays the functionality of the product under development, but may not actually hold the exact logic of the original software

A

Prototyping

43
Q

enables to understand customer requirements at an early stage of development

A

Prototyping

44
Q

helps get valuable feedback from the customer and helps software designers and developers understand about what exactly is expected from the product under development

A

Prototyping

45
Q

What are the 4 Types of Prototyping?

A
  • Throwaway Prototyping/rapid or close ended prototyping
  • Evolutionary Prototyping/breadboard prototyping
  • Incremental Prototyping
  • Extreme Prototyping
46
Q

Type of Prototyping

uses very little efforts with minimum requirement analysis to build a prototype

A

Throwaway Prototyping

47
Q

Type of Prototyping

once the actual requirements are understood, the prototype is discarded and the actual system is developed with a much clear understanding of user requirements

A

Throwaway Prototyping

48
Q

Type of Prototyping

based on building actual functional prototypes with minimal functionality in the beginning

A

Evolutionary Prototyping

49
Q

Type of Prototyping

the prototype developed forms the heart of the future prototypes on top of which the entire system is built

A

Evolutionary Prototyping

50
Q

Type of Prototyping

the well-understood requirements are included in the prototype and the requirements are added as and when they are understood

A

Evolutionary Prototyping

51
Q

Type of Prototyping

refers to building multiple functional prototypes of the various sub-systems then integrating all the available prototypes to form a complete system

A

Incremental Prototyping

52
Q

Type of Prototyping

used in the web development domain

A

Extreme Prototyping

53
Q

Types of Prototyping

This process is used to draw attention to the second phase of the process, where a fully functional UI is developed with very little regard to the actual services

A

Extreme Prototyping

54
Q

What are the three phases of Extreme Prototyping?

A
  • basic prototype with all the existing pages is presented in the HTML format
  • the data processing is simulated using a prototype services layer
  • the services are implemented and integrated to the final prototype
55
Q

based on the idea of developing an initial implementation, exposing this to user comment and evolving it through several versions until an adequate system has been developed

A

Incremental Model

56
Q

specification, development, and validation activities are interleaved rather than separate, with rapid feedback across activities

A

Incremental Model

57
Q

a fundamental part of agile approaches

A

Incremental Model

58
Q

better than a waterfall approach for most business, e-commerce, and personal systems

A

Incremental Model

59
Q

it is cheaper and easier to make changes in the software as it is being developed

A

Incremental Model

60
Q

```

~~~

The basic idea behind this method is to develop a system through repeated cycles and in smaller portions at a time, allowing software developers to take advantage of what was learned during development of earlier parts or versions of the system

A

Iterative and Incremental Model

61
Q

What does WBS mean?

A

Work Breakdown Structure

62
Q

What is WBS?

A

A repeatable process that can be used as a template for future projects

63
Q

How is WBS used?

A

1) effectively decompose the project scope
2) improve estimating
3) better control the project execution and
4) more accurately verify project completion

64
Q

Why should you use GANTT charts for project scheduling?

A
  • an easy way to schedule tasks
  • bars represent each task or activity
  • the length of each bar represents the relative length of the task
65
Q

Who invented GANTT charts?

A

Henry Gantt

66
Q

What are the advantages of using GANTT charts?

A
  1. main advantage: simplicity
  2. Another advantage: the size of the bar indicates the relative length of time it will take to complete each task
67
Q

What does PERT mean?

A

Program Evaluation and Review Techniques

68
Q

When and how was PERT developed?

A

Developed in the late 1950s for use in the US Navy’s Polaris nuclear submarine project

69
Q

Represented by a network of nodes and arrows that are then evaluated to determine the critical activities, improve the schedule if necessary, and review progress once the project is undertaken

A

PERT Diagram