Chapter 29.2 Flashcards

(20 cards)

1
Q

Procedural cohesion

A

-Elements of procedural cohesion ensure the order of execution.

-Actions are still weakly connected and unlikely to be reusable

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

Temporal cohesion

A

The elements are related by their timing involved. In a module connected with temporal cohesion, all the tasks must be executed in the same time span

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

Logical cohesion:

A

The elements are logically related and not functionally

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

Types of high cohesion

A

-Functional cohesion
-Sequential cohesion
-Procedural cohesion

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

Types of low cohesion

A

-Temporal cohesion
-Logical cohesion

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

Coupling

A

Coupling is the measure of the degree of interdependence between the modules.

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

Types of loose coupling

A

-Data coupling
-Stamp coupling
-Control coupling

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

Types of tight coupling

A

-External coupling
-Common coupling
-Content coupling

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

Data coupling

A

If the dependency between the modules is based on the fact that they communicate by passing only data.

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

Stamp coupling

A
  • The complete data structure is passed from one module to another even if not all fields are used.
  • The unnecessary data is referred to as tramp data.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Control coupling

A

-The modules communicate by passing control information.

-It can be bad if parameters indicate completely different behaviour and good if parameters allow factoring and reuse of functionality

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

External coupling

A

The modules depend on other modules, external to the software being developed

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

Common coupling

A

The modules have shared data such as global data structures.

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

Content coupling

A

In a content coupling, one module can modify the data of another module

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

requirements for any piece of
Software to be regarded as good:

A
  • It must do what it is supposed to.
  • It must be possible to change.
  • It should be readable.
  • It should be efficient,
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Refactoring

A

A systematic process of improving code without creating new functionality that
can transform a mess into clean code and simple design

17
Q

The SDLC

A

-Requirements gathering
-System design
-Implementation
-Testing
-Deployment
-Maintenance

18
Q

Requirements gathering

A

the capturing, analysis and documentation of the
requirements for the system

19
Q

System design

A

The design such as the database entity relationship diagram, compiling of use cases with typical scenarios of usage

20
Q

Implementation

A

The design is implemented into software.