ICT 114 midterms part 2 Flashcards

1
Q

also called process model
a descriptive and diagrammatic representation of the software life cycle
captures the order in which the activities are to be undertaken

A

LIFE CYCLE MODEL

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

The most obvious way to develop software.
Though tis model is elegant and intuitively obvious, it is not a practical model in the sense that it cannot be used in actual software development projects.

A

CLASSICAL WATERFALL MODEL

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

This study is to determine whether it would be financially and technically feasible to develop the product.

A

Feasibility study

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

This phase is to understand the exact requirements of the customer and to document them properly.

A

Requirements analysis and specification-

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

This phase is to transform the requirements specified in the Software Requirement Specifications document into a structure that is suitable for implementation in some programming language.

A

Design

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

Two distinctly different design approaches are available:

A

traditional design approach and the object-oriented design approach.

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

this consists of two different activities; first a structured analysis of the requirements specification is carried out where the detailed structure of the problem is examined.

A

Traditional design approach

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

In this technique, various objects that occur in the problem domain and the solution domain are first identified, and the different relationships that exist among these objects are identified.

A

Object-oriented design approach

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

The purpose of the coding phase (sometimes called the implementation phase) of software development is to translate the software design into source code.

A

Coding and unit testing

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

Integration of different modules is undertaken once they have been coded and unit tested. During the integration and system testing phase, the modules are integrated in a planned manner.

A

Integration and system testing:

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

when all the modules have been successfully integrated and tested.

A

System Testing

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

System testing usually consists of three different kinds of testing activities:
It is the system testing performed by the development team.

It is the system testing performed by a friendly set of customers.

It is the system testing performed by the customer himself after the product delivery to determine whether to accept or reject the delivered product.

A

A testin
B testing
and
Acceptance testing

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

of a typical software product requires much more than the effort necessary to develop the product itself.

A

Maintenance

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

Maintenance involves performing any one or more of the following three kinds of activities:

A

Corrective maintenance
perfective maintenance
and
adaptive maintenance

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

Correcting errors that were not discovered during the product development phase.

A

corrective maintenance.

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

Improving the implementation of the system, and enhancing the functionalities of the system according to the customer’s requirements.

A

perfective maintenance.

17
Q

Porting the software to work in a new environment. For example, porting may be required to get the software to work on a new computer platform or with a new operating system.

A

This is called adaptive maintenance.

18
Q

Developed to overcome the major shortcomings of the classical waterfall model
provide feedback paths for error correction when detected later in a phase.

A

ITERATIVE WATERFALL MODEL

19
Q

a ‘toy’ implementation of the system.
usually exhibits limited functional capabilities, low reliability, and inefficient performance compared to the actual software.

A

PROTOTYPING MODEL

20
Q

During the first quadrant, it is needed to identify the objectives of the phase.
Examine the risks associated with these objectives.

A

First quadrant (Objective Setting)

21
Q

A detailed analysis is carried out for each identified project risk.
Steps are taken to reduce the risks. For example, if there is a risk that the requirements are inappropriate, a prototype system may be developed.

A

Second Quadrant (Risk Assessment and Reduction)

22
Q

Develop and validate the next level of the product after resolving the identified risks

A

Third Quadrant (Development and Validation)

23
Q

Review the results achieved so far with the customer and plan the next iteration around the spiral. * Progressively more complete version of the software gets built with each iteration around the spiral

A

Fourth Quadrant (Review and Planning)

24
Q

The spiral model is called a

A

meta model

25
Q

refers to a development life cycle designed to give much faster development and higher quality systems than the traditional life cycle

A

Rapid Application Development

26
Q

Is an incremental and iterative process of software development. It defines each iteration’s number, duration, and scope in advance. Every iteration is considered a short “frame” which mostly lasts from two to four weeks.

A

Agile Model

27
Q

In Agile development, self-organization and motivation are important, as are interactions like co-location and pair programming.

A

Individuals and interactions

28
Q

Demo working software is considered the best means of communication with the customers to understand their requirements, instead of just depending on documentation.

A

Working software

29
Q

As the requirements cannot be gathered completely in the beginning of the project due to various factors, continuous customer interaction is very important to get proper product requirements.

A

Customer collaboration

30
Q

Agile Development is focused on quick responses to change and continuous development.

A

Responding to change