Skip to main content
main-content

Über dieses Buch

lfimplementing systematic reuse is risky, not doing it is even more risky. Trying systematic reuse unsuccessfully can cost precious time and resources and may make management sceptical of trying it again. But if your competitors do it successfully and you do not, you may lose market share and possibly an entire market. W. B. Frakes and S. Isoda, 1994 Software companies today are faced with new and more challenging market pressures. In response to this challenge, they have to reduce the time-to-market with new or enhanced products, increase the diversity of products available to the customers, and enhance the standardisation and interoperability of the products. At the same time, many companies carry the burden of large legacy systems, that have become too expensive to maintain and cannot sustain the demands of the marketing department for alterations, leading to business opportunities being lost [BEN95]. However the systems are very valuable and cannot be simply replaced because of the costs that such an operation entails. Simply replacing them may be too expensive because of the huge volumes of on-line data that must be converted, among other reasons.

Inhaltsverzeichnis

Frontmatter

Experiences

Frontmatter

1. The SER Approach

Abstract
The history of of Software Engineering could can be seen the constant quest for better control of costs, quality and development time.
Svein Hallsteinsen, Maddali Paci

2. Benefits of Software Evolution and Reuse

Abstract
Reuse is still not a common practice in many companies and this is certainly due to a complex combination of elements ranging from the lack of technical opportunities to the features of the domain at hand, from the business objectives of the companies to the characteristics and skills of the management, and so many more. Nevertheless, even when all the conditions for a reuse introduction program are in place, the problem that all companies considering the introduction of reuse have to face is to assess the economical and financial impact and the actual benefits of reuse in terms of time and costs savings, of improvement in the quality of the produced software and of increased productivity.
Svein Hallsteinsen, Maddali Paci

3. Lessons Learned

Abstract
As discussed in the previous section, there are many issues that direct the design of an appropriate evolution and reuse program in a given organisation, and each organisation has to find a solution suited for its particular situation. Nevertheless it is possible to define a few typical scenarios that will be close to the actual situation in many companies.
Svein Hallsteinsen, Maddali Paci

4. Conclusions and Recommendations

Abstract
The purpose of this chapter is to summarise the experience that has been presented in the previous chapters and to identify the directions and trends that may be useful for the planning and follow up of similar software evolution and reuse enactment programmes in other companies. In particular, possible relationships among the observed results have been highlighted.
Svein Hallsteinsen, Maddali Paci

Application Experiment Reports

Frontmatter

5. XiosBank

Abstract
This report describes the application of a reuse-based software development approach to a pilot project in a bank. The approach is based on the concept of the reusable banking object and was applied to XIOSBANK of Greece over the period January-December 1995
Svein Hallsteinsen, Maddali Paci

6. Stentofon

Abstract
The work described in this section is carried out in the scope of PROTEUS, project number 6086 in the European Commission ESPRIT research and development programme. The work carried out in Norway has been partly funded by the Norwegian Research Council (NFR).
Svein Hallsteinsen, Maddali Paci

7. Garex

Abstract
Garex makes customised communication control systems. Garex has been in this market segment since the company was started, and has long experience in making such safety-critical applications. In order to keep development costs down, a standardised software architecture and extensive reuse of (software) components have been employed for numerous years. Their business success is highly dependent on high-quality, reliable, and thoroughly tested basic components.
Svein Hallsteinsen, Maddali Paci

8. Bull

Abstract
This experience has been carried out at Bull S.A. in producing software for client server based solutions in the office systems marketplace.
Svein Hallsteinsen, Maddali Paci

9. SIA

Abstract
SIA is a system engineering company concerned with electronic equipment for flight and ground applications (aircraft, spacecraft, industrial, etc.)
Svein Hallsteinsen, Maddali Paci

10. Instrumentation Laboratory

Abstract
Instrumentation Laboratory is a company that builds critical health-care instruments (blood analysis and electrolyte).
Svein Hallsteinsen, Maddali Paci

11. BPM

Abstract
BPM is an Italian bank present all over the country.
Svein Hallsteinsen, Maddali Paci

12. Pirelli

Abstract
Pirelli Informatica (PI) is the corporate I.S. department specifically intended to develop IT strategy and support systems for the manufacturing company Pirelli (PM). Pirelli is structured in two sectors (Tyres and Cables) with about 50 plants world wide.
Svein Hallsteinsen, Maddali Paci

13. Ericsson Radar

Abstract
Ericsson Radar is developing software for radar control systems for the military market. Examples of recent projects are software for an artillery hunting radar (tracks trajectory of missiles and computes launch and hit positions), and a simulator for a mobile radar unit which is part of a training simulator for an air defence system.
Svein Hallsteinsen, Maddali Paci

14. Norsonic

Abstract
Norsonic AS is a small Norwegian company that specialises on development, manufacturing and marketing equipment for measuring and monitoring noise and vibrations.
Svein Hallsteinsen, Maddali Paci

15. Telecom Company

Abstract
This experiment focused on the introduction of the application framework approach in the domain of management systems for telecommunications networks. Such systems support tasks like statistics gathering, charging and fault management.
Svein Hallsteinsen, Maddali Paci

16. Telecom Gateway Framework

Abstract
The operation of telecommunication networks involves collecting and analysing data from and tuning of a number of network elements (for instance switches). A number of administrative applications exists to support these activities, but the interaction between such applications and the network elements they manage is not very efficient today. For instance collecting data from the switches is typically done by storing the data on tapes in each local site, and then transporting the tapes to a central site for analysis.
Svein Hallsteinsen, Maddali Paci

Backmatter

Weitere Informationen