1DIB

Some Experiences in a S.F. Diffusion.

Prof. Giuseppe Visaggio

Department of Computer Science

University of Bari

visaggio@di.uniba.it

2DIB

Enactment and Use of the SF in SER_Lab

APPBANK

RCVCHARTRE FILANTO

Software Factory

3DIB

Software ProjectsAPPBANK CHARTRE FILANTO RCV

Business Domain

Banking Banking Manufacturing Insurance

SW

Platform

COBOL: 653 programs (348 on line, 305 Batch); 70 ISAM Files with a total of 9000 fields

COBOL System working on a mainframe-terminals architecture

COBOL Program that manages 71 ISAM Files, for a total of 1,775 fields

COBOL System,

2,099 programs;

127 Files,

nearly all ISAM;

13,742 fields overall.

# SW

Developers

20

(4+16)

30

(4+26)

12

(2+10)

50

(12+27)

# SF

People

2 2 2 3

4DIB

Software Experience BaseAPPBANK CHARTRE FILANTO RCV

Projects

Purpose

Renewal of a working Software System

Migration of a software system and monitoring of the new system decay

Feasibility study for renewal of a working software system

Feasibility study for renewal of a working software system

SEB Contents Metric plan for maintenance process quality evaluation;Renewal processes;Decision model for choosing a suitable renewal processApplication architecture with information hiding;Software Aging symptoms and metricsEconomic value model for Renewal Process

Economic value model for Renewal ProcessEconomic value model vs quality of software system

Software Aging symptoms and metrics (the metrics were modified)Decision model for choosing a suitable Renewal Process (with modified metrics)

Software Aging symptoms and metrics (the metrics were modified)Decision model for choosing a suitable Renewal Process (with modified metrics)Economic value model for Renewal Process

5DIB

…Software Experience BasesAPPBANK CHARTRE FILANTO RCV

H1:Has SEB involved cultural changes?

Only for the developers of the renewal process

YES NO No, but it was very interesting

H2: Was the organization’s policy well supported by the SEB?

No, it was seen only as a mean to improve the maintenance and transferability of application knowledge

No, it was seen only as a mean to economically migrate to the new architecture.

NO NO

H3: Were the economical benefits relevant?

YES YES YES YES

H4: Was SEB used within the company after the project?

NO Only for a short period of time

NO NO

6DIB

Conclusions The Knowledge acquired was not shared within the company.

Usually its use was kept only by the group involved in the SEB building.

The SEB has always been used to introduce innovations. The management seems to accept the innovation only when the

available or used technologies are unable to solve the company’s problems.

Furthermore the solution is no longer used by management after overcoming the problems. For example in the APPBANK project the SEB was used only for the time necessary to make the maintainability and transferability of the application sustainable. After executing the renewal project the renewed application was adopted but the SF was no longer used.