Abstract

The field of software engineering and software technology is developing very fast. Perhaps as a consequence, there is seldom enough interest or opportunity for systematic investigation of how the underlying technology will actually perform. That is, we introduce new concepts, methods, techniques and tools – or change existing ones and emphasize their value. A major turn in software engineering leading to Componentware has dramatically changed the shape of software development and introduced interesting methods for the design and rapid development of systems which may provide cost-effective benefits. In this paper we will discuss Componentware, process model, architecture, principles and the drivers, advantages, disadvantage and reveal profound changes from the traditional software engineering approaches.

Highlights

  • The past 20 years has been a time of change in the field of IT as we see a succession of new technological inventions

  • The 1990s have focused on methods and techniques to support prototyping, iterative development, and a variety of rapid application development (RAD) techniques based upon the object oriented (OO) paradigm

  • In this paper we address the background leading to the need for a Componentware approach

Read more

Summary

Introduction

The past 20 years has been a time of change in the field of IT as we see a succession of new technological inventions. The past practices associated with programming using machine code, assembly languages, high level languages, fourth generation languages, and further on to CASE tools, appear to act to solve some technological problems and help us meet requirements and develop better systems Those in the profession recognize that previous approaches have not managed to minimize project failures and project shortfalls [1,2]. The signal of a software crisis on the increase in businesses became apparent decades ago, with the move to object-oriented approaches (such as the Object Modelling Technique) which became standard they were deemed unsuccessful for corporate developers. The problem is not helped by the fact that requirements changes are more frequent as businesses jostle for position in the market and try to find ways to increase their competitive advantage by means of strategic corporate software Another confounding factor is the destabilizing force of accelerating technology innovation, both in commercial software and hardware platforms. The move from traditional approaches to the Componentware era, component technology, the drivers and factors of Componentware, advantages, disadvantage and conclusion

The Move from Traditional Software Engineering to Componentware
Component Technology
Component Architecture and Principles
Componentware
Component Infrastructures
Component-Based Development
The Component-Based Development Process
Architectural Design of a Component-Based System
Objective
Code availability
The Drivers of Componentware
Disadvantage of Componentware
Conclusions

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.