Implementation and Integration1 Concepts and practices.

12
Implementation and Integ ration 1 Implementation and Integration Concepts and practices

Transcript of Implementation and Integration1 Concepts and practices.

Page 1: Implementation and Integration1 Concepts and practices.

Implementation and Integration 1

Implementation and Integration

Concepts and practices

Page 2: Implementation and Integration1 Concepts and practices.

Implementation and Integration 2

Implementation

Implementation is the process of translating the detailed design into code

Generally done by teams all working at the same time on different components of the product.

Page 3: Implementation and Integration1 Concepts and practices.

Implementation and Integration 3

Documentation produced

source code (major component)Additional documentation to assist in

maintenance.all test cases against which the code should

be tested the expected results and the actual output. (NB: These documents will be used in

regression testing)

Page 4: Implementation and Integration1 Concepts and practices.

Implementation and Integration 4

Implementation Issues

Choice of programming language The use of 4th generation languages

(4GLs)Use of good programming practices

Page 5: Implementation and Integration1 Concepts and practices.

Implementation and Integration 5

Choice of programming languageIn many cases, there is no opportunity for

choice because either only one choice is available or management stipulates that the product should be implemented in a given language.

A cost-benefit analysis may be employed to decide on the language. The language with the largest expected gain would be the one selected.

A risk analysis may also be used to aid in the selection of the language. The language with the smallest overall risk is selected.

Page 6: Implementation and Integration1 Concepts and practices.

Implementation and Integration 6

The use of 4th generation languages (4GLs)

The ease of programming

The program is shorter, quicker to develop and easier to maintain

Potential productivity gain

Page 7: Implementation and Integration1 Concepts and practices.

Implementation and Integration 7

Use of good programming practices

the use of consistent and meaningful variable names

provision of proper documentation; both prologue and inline comments

use of parameters (as opposed to constants)

well formatted source code to increase readability

structured programming (i.e. modular programming)

Page 8: Implementation and Integration1 Concepts and practices.

Implementation and Integration 8

Integration

Integration is the process of combining the modules (or subsystems) and determining whether the product as a whole functions correctly.

Page 9: Implementation and Integration1 Concepts and practices.

Implementation and Integration 9

Integration Issues

Factors that may affect the quality of the resulting product include:whether the modules are integrated all at

once or one at a timethe specific integration order, i.e. top-to-

bottom in the module interconnection diagram or bottom-to-top.

Page 10: Implementation and Integration1 Concepts and practices.

Implementation and Integration 10

‘implementation and integration’

The four approaches are:separate implementation and integration

phasestop-down implementation and

integrationbottom-up implementation and

integrationsandwich implementation and

integration.

Page 11: Implementation and Integration1 Concepts and practices.

Implementation and Integration 11

Module Interconnection Diagram

Page 12: Implementation and Integration1 Concepts and practices.

Implementation and Integration 12

Approach Comparisons

Approach Advantage Disadvantage

Implementation then integration

-

No fault isolation Major design flaws

show up late Top-down implementation and integration

Fault isolation Major design flaws

show up early

Potentially reusable modules are not adequately tested

Bottom-up implementation and integration

Fault isolation Potentially reusable

modules are adequately tested

Major design flaws show up late

Sandwich implementation and integration

Fault isolation Major design flaws

show up early Potentially reusable

modules are adequately tested

-