Client oriented software developing

1999

Software design is the process of mapping software functional requirements into a set of modules for implementation. In this paper, a new design technique called the concurrent software design technique (CSDT) is proposed. CSDT extends software design techniques, which are based on structured analysis and design, by identifying independent concurrent tasks for implementation in multiprocessing, multitasking and the C/S environment. A case study on re-engineering a large legacy system, implemented on mainframes as a sequential system, to a C/S environment is presented next in order to highlight the benefits of the CSDT. Finally, this paper concludes with a comparison of CSDT with other existing approaches and the lessons learned from the experience with this technique.

IFIP International Federation for Information Processing, 2004

UNU-IIST is jointly funded by the Governor of Macau and the governments of the People's Republic of China and Portugal through a contribution to the UNU Endownment Fund. As well as providing twothirds of the endownment fund, the Macau authorities also supply UNU-IIST with its office premises and furniture and subsidise fellow accommodation.

1997

Software is rarely built completely from scratch. To a great extent, existing software documents source code, design documents, etc. are copied and adapted to t new requirements. Yet we are far from the goal of making reuse the standard approach to software development.

Lecture Notes in Computer Science, 2005

This paper deals with the modeling and the automatic implementation of constraints in component based applications. Constraints have been assuming an ever more relevant role in modeling distributed systems as long as business rules implementation, design-by-contract practice, and fault-tolerance requirements are concerned. Nevertheless, component developers are not sufficiently supported by existing tools to model and implement such features. In this paper, we propose a set of tools that enable developers both to model component constraints and to automatically generate component skeletons that already implement such constraints.

Arxiv preprint arXiv:1202.2425, 2012

Component based development idea was floated in a conference name "Mass Produced Software Components" in 1968 [1]. Since then engineering and scientific libraries are developed to reuse the previously developed functions. This concept is now widely used in SW development as component based development (CBD). Component-based software engineering (CBSE) is used to develop/ assemble software from existing components [2]. Software developed using components is called component ware [3]. This paper presents different architectures of CBD such as ActiveX, common object request broker architecture (CORBA), remote method invocation (RMI) and simple object access protocol (SOAP). The overall objective of this paper is to support the practice of CBD by comparing its advantages and disadvantages. This paper also evaluates object oriented process model to adapt it for CBD.

Component-based development allows us to develop and integrate product components which facilitate software reusability, high quality and simplification for testing. Component-Based Software Engineering makes use of approaches which are based on architecture definition languages, object oriented design and software architecture. These strategies assist in the development of both domain-specific and generic software products. Reusability approach speeds up software development by using already developed components, thus software development cost and time is substantially reduced. I this paper, we present a Component-Based Software Engineering framework for software reusability

2003

UNU/IIST is jointly funded by the Governor of Macau and the governments of the People's Republic of China and Portugal through a contribution to the UNU Endownment Fund. As well as providing twothirds of the endownment fund, the Macau authorities also supply UNU/IIST with its office premises and furniture and subsidise fellow accommodation.

—Elemental role of component based software engineering is to develop the systems of an assembly of parts, the development of parts in the form of reusable institutions, and maintenance and upgrading of systems by customizing and altering such parts. Component-based software Development (CBSD) is used to develop / collect Software from existing components. Component based software development follows some principles. Paper shows a study of various software reusable concepts. The aim is to gather useful information on software components and the component on which component reusability is highly dependent, as a result of the review of the software reusability that is very dependent on reusability, cost, optimization, and complexity of the interface, documentation quality and portability. In this paper, the main description is about component based software development where the components can be reused and combined together to form a software system that meets the user's actual requirements. This paper also shows different models of component based systems and the factors that affect component based development.

2002

Several proposals for component-based development methods have started to appear. However, the emphasis is still very much on the development of components as opposed to the development with components. The main focus is on how to generate ideal reusable components not on how to plug existing components and specify their interactions and connections. The concept of a coordination contract ) has been proposed to specify a mechanism of interaction between objects based on the separation between structure, what is stable, and interaction, what is changeable. This separation supports better any change of requirements, as contracts can be replaced, added or removed dynamically, i.e. in run-time, without having to interfere with the components that they coordinate. A coordination contract corresponds to an expressive architectural connector that can be used to plug existing components. In this paper we integrate the concept of a coordination contract with component-based development and show how coordination contracts can be used to specify the connectors between components.

Lecture Notes in Computer Science, 2004

This paper presents an approach to describe, deploy and manage component-based applications having dynamic functional and non-functional requirements. The approach is centered on architectural descriptions and associated high-level contracts. Besides specifying non-functional (or QoS) requirements, these contracts are used to guide architecture customizations required to enforce the requirements. The infrastructure required to manage the contracts follows an architectural pattern, which can be directly mapped to specific components included in a supporting reflective middleware. This approach allows designers to write a contract and to follow a standard recipe to insert the extra code required to its enforcement in the supporting middleware.